- From: Oliver Kusche <oli@trip.net>
- Date: Thu, 13 Apr 2006 18:31:55 +0200
- To: xmlschema-dev@w3.org
Thanks for pointing this out. I'm merely setting elementFormDefault="unqualified" to hide namespaces from my instance documents so that it's not visible which component an element belongs to (making instance documents a lot more readable). So do you suggest that's not really a good practice? cheers, Oli Michael Kay <mike@saxonica.com> writes: > > elementFormDefault="unqualified" means that a locally-declared element (one > declared with <element name="x"> as part of a complex type) will be in no > namespace. (I've always thought this was a weird thing to want to do.) > Elements declared at the top level of a schema are always in the target > namespace of that schema, regardless of the value of elementFormDefault in > either their own schema document or in a referencing schema document. > > You might be able to achieve what you want using chameleon includes, but > that's another strange facility that I prefer to admire from a distance. > > Michael Kay > http://www.saxonica.com/ ----------------------------------------------------------------
Received on Thursday, 13 April 2006 16:32:17 UTC