2423 2005-10-28 18:55:12 +0000 Clearly define value equality 2009-04-21 19:21:40 +0000 1 1 1 Unclassified XML Schema Datatypes: XSD Part 2 unspecified All All CLOSED WONTFIX thimble, work, eq cluster resolved P2 normal --- 2045 2048 2175 2499 1 sandygao cmsmcq www-xml-schema-comments oldest_to_newest 6955 0 sandygao 2005-10-28 18:55:12 +0000 The spec needs to clearly define when actual values are equal. This relates to bug 2045 and bug 2048 about equality of values of list and union types. A specific issue is to answer the question about whether the following 2 values are equal: - a list value that only contains the integer value "5" - the integer value "5" 7163 1 cmsmcq 2005-11-11 22:03:59 +0000 We discussed this at astonishing length during the Toronto ftf meeting. As far as the WG can tell, no schema + instance pair can be constructed for which the result of schema-validity assessment depends on an answer to this question. To the extent that we wish to provide an answer anyway, just to have a complete story, the majority view at the ftf was that the integer 5 should be neither identical nor equal to a singleton list containing an integer 5. We agreed to instruct the editors to draft wording accordingly. 7165 2 davep 2005-11-11 22:48:10 +0000 (In reply to comment #1) > We discussed this at astonishing length during the Toronto ftf meeting. > > As far as the WG can tell, no schema + instance pair can be constructed > for which the result of schema-validity assessment depends on an > answer to this question. Not at the meeting, but I concur with this conclusion. > To the extent that we wish to provide an > answer anyway, just to have a complete story, the majority view at the > ftf was that the integer 5 should be neither identical nor equal > to a singleton list containing an integer 5. I strongly concur with this decision as well. 11919 3 cmsmcq 2006-09-21 00:00:30 +0000 At the face to face meeting of January 2006 in St. Petersburg, the Working Group decided not to take further action on this issue in XML Schema 1.1. (This issue was not discussed separately; it was one of those which were dispatched by a blanket decision that all other open issues would be closed without action, unless raised again in last-call comments.) Some members of the Working Group expressed regret over not being able to resolve all the issues dealt with in this way, but on the whole the Working Group felt it better not to delay Datatypes 1.1 in order to resolve all of them. This issue should have been marked as RESOLVED /WONTFIX at that time, but apparently was not. I am marking it that way now, to reduce confusion.