felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefano Lenzi <kis...@interfree.it>
Subject Re: [FELIX-219] Applying the patch
Date Tue, 28 Aug 2007 12:16:04 GMT
Clement Escoffier wrote:
> Hello, 
>> -----Message d'origine-----
>> De : Stefano Lenzi [mailto:kismet@interfree.it]
>> Envoyé : vendredi 17 août 2007 18:47
>> À : dev@felix.apache.org
>> Cc : Maxime Vincent
>> Objet : Re: [FELIX-219] Applying the patch
>> Stefano Lenzi wrote:
>>> Clement Escoffier wrote:
>>>> Hello,
>> [cut]
>>>> For sure, using Castor seems to me the right approach. But first, we
>>>> need to
>>>> write the OBR XML Schema (Castor input)
>>> I'm going to write it :)
>> I'm trying to define the XML Schema but there is a problem in using XML
>> Schema to implement the parser for the OBRv2 XML, in fact the problem
>> is
>> that the OBRv2 RFC
>> (http://www2.osgi.org/download/rfc-0112_BundleRepository.pdf) do not
>> does not define any official tag for:
>>   - source
>>   - documentation
>>   - size
>>   - license
>>   - etc.
> Maxime uses :
> <source>URI</source> (used the SCM element of the pom file)
> <documentation>URI</documentation> (use the URL element of the pom file)
> <size>size in bytes</size>
> <licence>URI</licence> (gathered by using bindex and the pom file (licences
> URI are separated by ';')
>> So there is not way to create a XML Schema for such tag, which at the
>> moment are handled manually :S
> I am not sure if these conventions are corrects (according to the spec),
> however we never use it really these tags (only for resource describing).

The problem is the spec allow any TAG for metadata and the spec do not 
define the tag name for metadata information. For example: a resource 
may use the tag <bundle-docurl> to store the link to documentation, or 
it could use <length> for define the size of the bundle.

IMO, I think that the definition of a common set of tags should be 
proposed as part of OBR-RFC, in order to avoid incompatibility of 
metadata information.

Stefano "Kismet" Lenzi

View raw message