<div>It sounds you have accepted my "feature request", aha?</div>
<div>Thanks a lot! :)<br><br> </div>
<div><span class="gmail_quote">On 5/16/08, <b class="gmail_sendername">Mark Overmeer</b> <<a href="mailto:mark@overmeer.net">mark@overmeer.net</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"><br>Other people's input welcome!<br><br>* MENG Xin (<a href="mailto:zinces@gmail.com">zinces@gmail.com</a>) [080515 09:54]:<br>
> I'm not very familar about spec. Here is text from XML Schema 2nd Edtion,<br>> O'Reilly, ISBN 0-596-00252-1, chapter 16 Datatype Reference Guide, xs:ID<br>> section:<br><br>Well, that's second-hand info.<br>
The XML-Schema spec is at <a href="http://www.w3.org/TR/xmlschema-2/#ID">http://www.w3.org/TR/xmlschema-2/#ID</a> and<br>says really nothing useful:<br>3.3.8 ID<br>[Definition:] ID represents the ID attribute type from [XML 1.0 (Second<br>
Edition)]. The ·value space· of ID is the set of all strings that<br>·match· the NCName production in [Namespaces in XML]. The ·lexical<br>space· of ID is the set of all strings that ·match· the NCName<br>production in [Namespaces in XML]. The ·base type· of ID is NCName.<br>
<br>The XML 1.0 spec says:<br><br><a href="http://www.w3.org/TR/2000/WD-xml-2e-20000814">http://www.w3.org/TR/2000/WD-xml-2e-20000814</a><br>Validity constraint: ID<br> Values of type ID must match the Name production. A name must not<br>
appear more than once in an XML document as a value of this type;<br> i.e., ID values must uniquely identify the elements which bear them.<br><br>The RFC definition of "must" is less strong than "shall". The former<br>
means: "should be, but not deadly", where the latter means: error.<br>I do not known how to interpret the XML use of the word "must".<br><br>Anyone else: what is correct behavior? An error or warning on double<br>
IDs, of simply ignore it?<br><br>> And I know that validator integrated in oXygen XML editor for Eclipse also<br>> does such task.<br>> So I guess validators should guarantee the unique restriction of xs:ID.<br>> After all, it is not difficult to implement, right?<br>
<br>> I quote the correct behavior is just to show my superise: xs:pattern based<br>> on xs:ID can be checked perfectly, but xs:ID itself is not checked. That's<br>> all.<br><br>There are quite some different needs from checking seperate values against<br>
some rules (very locally) and document global ID administration. Although<br>the second is possible (of course).<br><br>--<br>Regards,<br> MarkOv<br><br>------------------------------------------------------------------------<br>
Mark Overmeer MSc MARKOV Solutions<br> Mark@Overmeer.net <a href="mailto:solutions@overmeer.net">solutions@overmeer.net</a><br><a href="http://Mark.Overmeer.net">http://Mark.Overmeer.net</a> <a href="http://solutions.overmeer.net">http://solutions.overmeer.net</a><br>
<br></blockquote></div><br>