DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18405>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18405 Comination of fields in <xsd:unique> acts as <xsd:key> [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID ------- Additional Comments From [EMAIL PROTECTED] 2003-03-27 19:45 ------- Hello. The Schema Structures spec says in section 3.11.4 [1]: "3 For each node in the �target node set� all of the {fields}, with that node as the context node, evaluate to either an empty node-set or a node-set with exactly one member, which must have a simple type." The target node set is the set of nodes on which the selector is matched. Note that this condition must hold for *any* identity constraint; only in bullet 4 of the tableau are the differences between key and unique described. Therefore, it seems clear that, if a selector matches, then either all of the fields must match or none of them must match; even for xsd:unique, you can't have some fields matching. [1]: http://www.w3.org/TR/xmlschema-1/#cvc-identity-constraint --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
