W3C home > Mailing lists > Public > public-qt-comments@w3.org > October 2016

[Bug 29957] New: [XSLT30] Non-schema-aware processors and schema-attribute and schema-element node tests: error or not?

From: <bugzilla@jessica.w3.org>
Date: Sat, 22 Oct 2016 22:18:28 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-29957-523@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29957

            Bug ID: 29957
           Summary: [XSLT30] Non-schema-aware processors and
                    schema-attribute and schema-element node tests: error
                    or not?
           Product: XPath / XQuery / XSLT
           Version: Candidate Recommendation
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XSLT 3.0
          Assignee: mike@saxonica.com
          Reporter: abel.braaksma@xs4all.nl
        QA Contact: public-qt-comments@w3.org
  Target Milestone: ---

In XPath, the descriptions of schema-attribute and schema-element node tests
are in reference to the in-scope schema definitions (namely, the in-scope
attribute declarations and in-scope element declarations).

If such declaration is not found, XPST0008 must be raised.

However, in XPath it is also defined that the test succeeds if the type
derives-from the declared type, and the name matches.

In XSLT in contrast we say that any SequenceType other than xs:untyped and
xs:untypedAtomic for as-clauses should raise error XTSE1660, but there's no
mention of node tests.

It stands to reason (but couldn't find this) that the in-scope schema
definitions are the empty set for non-schema-aware processors. But one could
also argue that these definitions automatically include mappings for xs:untyped
and xs:untypedAtomic for all elements/attributes.

It's unclear to me whether match="schema-attribute('foo', 'xs:int')" should be
rejected, whether it should ignore 'xs:int' and match on 'foo', or whether, if
rejected, it should raise XTSE1660 or XPST0008.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Saturday, 22 October 2016 22:18:35 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:58:02 UTC