![]() |
![]() | ![]() | ![]() | Altova Mailing List Archives>Archive Index >xmlschema-dev Archive Home >Recent entries >Thread Prev - no targetNamespace, elementFormDefault qualified [Thread Next] RE: no targetNamespace, elementFormDefault qualifiedTo: "'Bryan Rasmussen'" <BRS@----.-->, <xmlschema-dev@--.---> Date: 4/3/2006 2:10:00 PM No, because form=qualified means "in the target namespace if there is one, or in the non-namespace if there isn't". The schema spec (like XSLT) generally treats the set-of-names-in-no-namespace in the same way as a namespace, despite the perverse insistence of the Namespaces Rec that this set of names is not a namespace at all. Michael Kay http://www.saxonica.com/ > -----Original Message----- > From: xmlschema-dev-request@w... > [mailto:xmlschema-dev-request@w...] On Behalf Of Bryan Rasmussen > Sent: 03 April 2006 12:27 > To: xmlschema-dev@w... > Subject: no targetNamespace, elementFormDefault qualified > > > Hi, > > Given that "If the URI reference in a default namespace > declaration is > empty, then unprefixed elements in the scope of the > declaration are not > considered to be in any namespace" thus there is no namespace > to make up the > namespace part of the QName if one has a blank namespace, > shouldn't a schema > with no targetNamespace and a declaration of > elementFormDefault qualified > raise errors? I'm asking because I just encountered a schema with this > structure, and it bugs me. > > > Cheers, > Bryan > > From BRS@i... Mon Apr 03 12:23:16 2006 Received: from lisa.w3.org ([128.30 | ![]() | ![]() | ![]() |
| Company | Legal | Press | Partners | Careers | Sitemap | Contact Us | Altova Blog | |||||
|
