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] targetNamespace and default namespace

At 2016-09-29 16:26 +0100, Michael Kay wrote:
Someone, I think, had the bright idea that if a container element is in a namespace

<svg:svg xmlns:svg="http://svg.com/";>
<rectangle/>
<circle/>
</svg:svg>

then there is no good reason why its children need to be in a namespace: like attributes, they are scoped by the container. The idea didn't catch on, but the schema spec was written in the belief that this was the way forwards.
This happened to be adopted for OASIS genericode. Only the document element is in the genericode namespace, all descendants are in no namespace.

We have a RDDL document at the URL of the namespace URI:

http://docs.oasis-open.org/codelist/ns/genericode/1.0/

So not only do we get scoping of the elements by the document element, we also get a pointer to documentation (by convention, not by spec).

. . . . . . . Ken


--
Check our site for free XML, XSLT, XSL-FO and UBL developer resources |
Streaming hands-on XSLT/XPath 2 training @US$45: http://goo.gl/Dd9qBK |
Crane Softwrights Ltd. _ _ _ _ _ _ http://www.CraneSoftwrights.com/x/ |
G Ken Holman _ _ _ _ _ _ _ _ _ _ mailto:gkholman@CraneSoftwrights.com |
Google+ blog _ _ _ _ _ http://plus.google.com/+GKenHolman-Crane/posts |
Legal business disclaimers: _ _ http://www.CraneSoftwrights.com/legal |



[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