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=19333>. 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=19333 key/keyref constraint is not working [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID ------- Additional Comments From [EMAIL PROTECTED] 2003-07-25 17:24 ------- Xerces emits this error when, for some instance document, the element information items whose declaration a key is on is not in the scope (that is, not either the same or nested within) of the element information item whose declaration the keyref that points to that key is on. There was an unfortunate contradiction on this point between the Schema Structures Spec and the original Schema Primer. Quite a while back, the Schema Working Group published an erratum to the Primer; I think this document will be corrected whenever a new edition of the Primer is published. Unfortunately, this confusion resulted in implementations having different behaviours; XML Spy's follows the original (wrong) example from the Primer, Xerces followed the Structures spec. So, hopefully at some point the XML Spy implementation will be changed to accord with the Schema WG's erratum, and everyone will get consistent behaviour. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
