29957 2016-10-22 22:18:28 +0000 [XSLT30] Non-schema-aware processors and schema-attribute and schema-element node tests: error or not? 2016-10-27 16:51:06 +0000 1 1 1 Unclassified XPath / XQuery / XSLT XSLT 3.0 Candidate Recommendation PC Windows NT RESOLVED INVALID P2 normal --- 1 abel.braaksma mike public-qt-comments oldest_to_newest 127934 0 abel.braaksma 2016-10-22 22:18:28 +0000 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. 127939 1 mike 2016-10-23 08:49:55 +0000 >But one could also argue that these definitions automatically include mappings for xs:untyped and xs:untypedAtomic for all elements/attributes. I don't quite see what form such an argument might take. XSLT 5.3.1 says: The in-scope schema definitionsXP30 for the XPath expression are the same as the in-scope schema components for the stylesheet, and are as specified in 3.14 Built-in Types. [The reference should really include 3.15 as well.] Section 3.15 says: The schema components included in the in-scope schema components (that is, the components whose names are available for use within the stylesheet) are the top-level element and attribute declarations and type definitions that are available for reference within the synthetic schema document. See [XML Schema Part 1] (section 4.2.3, References to schema components across namespaces). If there is no import-schema, then the synthetic schema document contains no global attribute declarations, therefore schema-element(foo) refers to an attribute name that is not present in the in-scope schema declarations, therefore a static error occurs. The error code XTSE1660 applies specifically to non-schema-aware processors, not to schema-aware processors when there is no imported schema, and there's room for debate about which error code takes precedence. But either way, "foo" is not in the in-scope schema declarations and therefore can't be referenced in schema-attribute(). XPath says "If the ElementName specified in the SchemaElementTest is not found in the in-scope element declarations, a static error is raised [err:XPST0008]." which seems pretty unambiguous to me. 127941 2 abel.braaksma 2016-10-24 09:36:19 +0000 Somehow I came to the conclusion that if you use that type that it automatically exists (in that "give me an element X with type annotation Y"). But now I think that my reasoning took a shortcut. Using schema-element *requires* a declaration in a schema to be present for that element. That all elements are considered to be of type xs:untyped is irrelevant. (conversely, if my argument were correct in any sense, using schema-element(x) would have little effect if it meant that any element existed automatically as xs:untyped element) So, bottom line, schema-element() and schema-attribute() cannot possibly select anything for non-schema-aware processors and will always raise one of these two errors. 127972 3 mike 2016-10-27 16:51:06 +0000 Closed with no action.