Lists Home |
Date Index |
On second though, maybe in this case, it doesn't really matter much.
Tom Bradford - Virtuoso Technology Evangelist
OpenLink Software: http://www.openlinksw.com/
Personal Web Log: http://www.tbradford.org/
Tom Bradford wrote:
> 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">
> <address1>123 Main Street</address1>
> <city>Virginia Beach</city>
> 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.
>> 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.
> The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
> initiative of OASIS <http://www.oasis-open.org>
> The list archives are at http://lists.xml.org/archives/xml-dev/
> To subscribe or unsubscribe from this list use the subscription
> manager: <http://www.oasis-open.org/mlmanage/index.php>