I don't know if anyone has pointed this out yet, but this document doesn't take into account the nature of XML Schemas, and the potentially for the same name to exist more than once in a Schema with a different meaning depending on its context. Granted, it's bad style to design a schema in such a way, but it definitely happens. For example: <MyInfo xmlns="http://blah.com"> <name>Tom</name> <address> <address1>123 Main Street</address1> <city>Virginia Beach</city> <state>VA</state> </address> <host_info> <address>192.168.2.30</address> </host_info> </MyInfo> My point being that the element 'address' appears twice in this document under the same namespace, and with two contextually different meaning, which according to some schema may be perfectly legal. How would I define a URN to explicitly talk about one or the other? -- Tom Bradford - Virtuoso Technology Evangelist OpenLink Software: http://www.openlinksw.com/ Personal Web Log: http://www.tbradford.org/ Rich Salz wrote: > Some folks here may be interested in the following Internet-Draft that > Dave Orchard and I wrote. > http://www.ietf.org/internet-drafts/draft-rsalz-qname-urn-00.txt > > Unlike most writing on URNs and URIs, this is very short. :) > > > This specification defines a Uniform Resource Name namespace for XML > namespace-qualified names, QNames. As long as the URN is encoded in the > same character set as the document containing the original QName, the > Qname URN provides enough information to maintain the semantics, and > optionally the exact syntax, of the original name. >
PURCHASE STYLUS STUDIO ONLINE TODAY!
Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!
Download The World's Best XML IDE!
Accelerate XML development with our award-winning XML IDE - Download a free trial today!
Subscribe in XML format