W3C home > Mailing lists > Public > www-xml-schema-comments@w3.org > April to June 2008

[Bug 5726] XPath Context for Assertions must not include Element Name

From: <bugzilla@wiggum.w3.org>
Date: Fri, 30 May 2008 21:16:44 +0000
To: www-xml-schema-comments@w3.org
Message-Id: <E1K2Bxs-0001kV-9u@wiggum.w3.org>


------- Comment #1 from mike@saxonica.com  2008-05-30 21:16 -------
I wonder whether this is being excessively purist? I can see users wanting to
reuse the same type for two different elements and then attach some
constraints, for example (in the schema for schemas) one could imagine defining
key, keyref, and unique as having the same complex type, and then add the
constraint that the ref attribute is allowed only if the element name is
keyref. Do we really want to defend a decision that we aren't allowing users to
do this because we thought it was architecturally impure? And users are going
to be very confused if they do test the element name and it doesn't match what
the element name "really is".

Also, we're providing other bits of context like the base URI and the namespace
context, which are equally impure.
Received on Friday, 30 May 2008 21:17:19 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:50:08 UTC