Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


ID Conflicts in Namespaces.

From: Ben Trafford <ben@--------.-->
To: xml-dev@-----.---.---
Date: 8/17/2006 10:59:00 PM
(Woo! Looks like XML-DEV is back!)

	Hi!

	I have a question. To illustrate it, take a look at this markup:

<document xmlns="http://www.example.com/document" 
xmlns:sample="http://www.sample.com/sample">
	<paragraph id="one">This is a sample paragraph.</paragraph>
	<sample:text id="one">This is another sample paragraph.</sample:text>
</document>

	Let's assume that the schema for the "document" said that the "id" 
attribute on "paragraph" was is an ID (as in the attribute type). 
Let's also assume that the schema for the "sample" said that the "id" 
attribute on "text" is an ID.

	Should a validation tool flag an error (e.g. using two identical IDs 
in one document)?

	I don't think it ought to (since it's one document, but two 
different schemas), but I also think of namespace-qualified document 
fragments as being islands in and unto themselves.

	Anybody got any ideas? And pointers to specifications that define 
what ought to be happening here?

--->Ben


transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent