[EMAIL PROTECTED] wrote on 2008/08/21 02:03:30 AM:

> [image removed] 
> 
> Re: [osgi-dev] Correct XML format for SCR?
> 
> Carsten Ziegeler 
> 
> to:
> 
> OSGi Developer Mail List
> 
> 2008/08/21 02:15 AM
> 
> Sent by:
> 
> [EMAIL PROTECTED]
> 
> Please respond to OSGi Developer Mail List <[email protected]>
> 
> Hi BJ,
> 
> thanks for your information,
> 
> BJ Hargrave wrote:
> > 
> > See http://www.w3.org/TR/xmlschema-0/#UnqualLocals
> > 
> > Since the SCR schema uses the default of unqualified for
> > elementFormDefault and  attributeFormDefault, the namespace prefix of
> > scr MUST only be specified for the component element. All other 
elements
> > and attributes for document MUST not specify the prefix.
> Yes, the SCR schema uses unqualified locals - but on the other hand the
> schema can't be used to validate the docs anyway, as the schema requires
> an order of the contained elements which is not required by the spec.

Only because the XML Schema 1.0 spec is too limiting in the required 
ordering of elements. :-(

> > 
> > If the Felix SCR requires contained elements to use the scr prefix, it
> > would seem to require non well-formed XML document which is bad.
> The XML document is well-formed, but it's not conforming to the schema
> (see http://www.w3.org/TR/xmlschema-0/#QualLocals).
> 
> Usually namespaces in xml documents are used to qualify all elements
> belonging to this domain, but YMMV of course.
> 
> So if the intention of the spec is to use unqualified locals we have to
> fix our implementation in the Apache Felix project (which is easy to
> do). However, it would be great if this information could be added to
> the spec then.

Per the XML schema for SCR, which uses the default values for 
elementFormDefault and  attributeFormDefault, I think this is already well 
specified. I don't really want to repeat information from the XML Schema 
spec in the DS spec. The only way to be more explicit would be to put 
elementFormDefault and  attributeFormDefault in the SCR schema and state 
the default value of unqualified for them.

> 
> Thanks
> Carsten
> -- 
> Carsten Ziegeler
> [EMAIL PROTECTED]
> _______________________________________________
> OSGi Developer Mail List
> [email protected]
> https://mail.osgi.org/mailman/listinfo/osgi-dev

-- 

BJ Hargrave
Senior Technical Staff Member, IBM
OSGi Fellow and CTO of the OSGi Alliance
[EMAIL PROTECTED]

office: +1 386 848 1781
mobile: +1 386 848 3788

_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev

Reply via email to