- From: <bugzilla@wiggum.w3.org>
- Date: Fri, 12 Jan 2007 15:52:53 +0000
- To: www-xml-schema-comments@w3.org
- CC:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=2312
sandygao@ca.ibm.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sandygao@ca.ibm.com
Status|ASSIGNED |RESOLVED
Resolution| |INVALID
Version|unspecified |1.0/1.1 both
------- Comment #1 from sandygao@ca.ibm.com 2007-01-12 15:52 -------
The Schema WG considered this issue at its 2006-12-22 telecon, and decided to
close this issue with no further action. The resolution is somewhere between
"invalid" and "wontfix".
The analysis from the email exchange is correct: "the success of
keyref-resolution is dependant on a specific constellation of the keys in the
tree".
This can be viewed both as a feature and a bug. One can certainly argue that
key values specified on the parent element *overrides* those specified on the
children, which would support rules in the current spec.
This was a deliberate decision in the schema spec; it will only affect very few
cases (recursive element references with key/keyref); changing it may
dis-stablize the spec. The WG decided not to change the spec based on these
factors.
Received on Friday, 12 January 2007 15:53:11 UTC