W3C home > Mailing lists > Public > public-qt-comments@w3.org > September 2011

[Bug 10065] [XPath] Rules for matching substitution groups differ from those in formal semantics

From: <bugzilla@jessica.w3.org>
Date: Sat, 10 Sep 2011 18:26:07 +0000
To: public-qt-comments@w3.org
Message-Id: <E1R2SFj-00033L-UJ@jessica.w3.org>

Jonathan Robie <jonathan.robie@gmail.com> changed:

           What    |Removed                     |Added
             Status|REOPENED                    |RESOLVED
         Resolution|                            |FIXED

--- Comment #4 from Jonathan Robie <jonathan.robie@gmail.com> 2011-09-10 18:26:07 UTC ---
(In reply to comment #3)
> I am reopening this bug because the agreed resolution does not appear in the
> current status quo draft of the specification.

I'm confused. The Working Group's internal Working Draft says this:


A SchemaElementTest matches a candidate element node if all of the following
conditions are satisfied:

1. The name of the candidate node matches the specified ElementName, or it
matches the name of an element in a substitution group headed by an element
named ElementName and the substituted element is not abstract. Call this
element the substituted element.

2. derives-from( AT, ET ) is true, where AT is the type annotation of the
candidate node and ET is the schema type declared for the substituted element
in the in-scope element declarations.

3. If the the substituted element is not nillable, then the nilled property of
the candidate node is false.

Does this not match the decision that was made? If so, in what way? I'm closing
this, please reopen if the internal draft got this wrong.

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 Saturday, 10 September 2011 18:26:09 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:45:46 UTC