XML.orgXML.org
FOCUS AREAS |XML-DEV |XML.org DAILY NEWSLINK |REGISTRY |RESOURCES |ABOUT
OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
Re: [xml-dev] Venetian Blinds vs Garden of Eden patterns for industrystandards XML Schemas

Hi David,

On Fri, Oct 29, 2010 at 2:43 AM, David Carlisle <davidc@nag.co.uk> wrote:
> elementFormDefault is really just a wart in XSD and I can't see any reason
> why it would ever be set to anything other than qualifiesd

This is by design in XML Schema language. Please do consider these two
XML document variants and related explanations:

1.
<x xmlns="http://ns1";>
  <y/>
</x>

Here the outermost element and all included elements are in namespace,
and this can be specified by elementFormDefault="qualified" definition
in schema document.

2.
<ns1:x xmlns:ns1="http://ns1";>
  <y/>
  <y/>
</ns1:x>

Here only the outermost element is in a namespace, but inner ones are
not in namespace (the inner elements are in no/null namespace). These
document constraints can be specified by
elementFormDefault="unqualified" (and this is available by default in
a schema document, if not specified by schema author).

I personally do not agree that only elementFormDefault="qualified"
should exist (either by syntax or implicitly available by language
design) in XML schema language. Allowing schema authors to specify
either "qualified" or "unqualified" for elements (and also for
attributes) is a significant design made into the XML Schema language
(and i personally do find this OK :)




-- 
Regards,
Mukul Gandhi


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 1993-2007 XML.org. This site is hosted by OASIS