- From: <bugzilla@wiggum.w3.org>
- Date: Sun, 22 Jun 2008 14:29:50 +0000
- To: public-xml-schema-testsuite@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=4063
Michael Kay <mike@saxonica.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |INVALID
--- Comment #2 from Michael Kay <mike@saxonica.com> 2008-06-22 14:29:50 ---
In 1.0 we can argue that because the attribute is skipped, it has no type,
therefore it does not "have a simple type", therefore it is invalid. (Assuming
this phrase means "has a governing type definition that is a simple type".)
Added a comment to bug #5780 which affects the same text in the spec.
Noted that in 1.1 the definition "Call the sequence of the [schema actual
value]s of the element and/or attribute information items in those node-sets in
order the key-sequence of the node." is less than clear. (a) "those node-sets"
are actually node sequences, and (b) the idea is that they DONT include the
skipped nodes. So in 1.1 the target node-set contains the foo element, this
node-set contains a node for which the XPath expression selects no (unskipped)
nodes, and this makes the qualified node-set empty.
Another 1.1 concern here is the term "skipped", which means "attributed to a
skip wildcard". Can we determine this from PSVI properties? Answer: yes, the
PSVI property "attribute attribution" tells us.
Under both definitions we have come to the conclusion that the instance is
indeed invalid. Therefore no change to the test suite is required (except that
a comment referring to this explanation would be helpful!)
--
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Sunday, 22 June 2008 14:30:23 UTC