<div>Daniel, we are talking about whether to implement this checking rather than how to implement, I guess you might have misunderstandings. Let me summarize it. </div>
<div> </div>
<div>As defined in spec, xs:ID restriction is used to guarantee the uniqueness of contents. The question is who guarantee the uniqueness, users or tools? Mark's opinion is that users who create XML instance files should guarantee the uniqueness and XML::Compile::Schema just builds XML reader according to schema and does not check the uniqueness. My opinion is that users have used xs:ID to define schema and expect tools to check uniqueness, if tools leave this task to users, why do we need xs:ID restriction? </div>
<div> </div>
<div>Mark further argues that there is no deadly definitions on this checking in spec, and I point out this implementation is a valuable enhancement to his module. (Frankly speaking, I hope he can release a new version with this checking implemented.)</div>
<div> </div>
<div>That's all. </div>
<div> </div>
<div>Mark is observing discussions in this group and waiting more good arguments to help him make a wise decision. So I'm waiting on this thread, too. <br> </div>
<div><span class="gmail_quote">On 5/16/08, <b class="gmail_sendername">Daniel Ruoso</b> <<a href="mailto:daniel@ruoso.com">daniel@ruoso.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Sex, 2008-05-16 às 10:20 +0200, Mark Overmeer escreveu:<br>> This puts the responsibility of correct behavior with the user. I do not<br>
> like that. Most users do not read the specs.<br><br>The point is... If the specification is not 'strict' on a definition,<br>there's no "correct" behavior. There are good practices and bad<br>practices, but they are all valid (in terms of compliance to spec), a<br>
framework should promote the good practice (make "die" by default), but<br>should allow the variations that are valid according to the spec...<br><br>daniel<br><br></blockquote></div><br>