[
Lists Home |
Date Index |
Thread Index
]
Title: Message
Mike,
I think issue 546, conformance levels,
will be a key issue for many current users of XSLT 1.0.
The conformance levels for XSLT 2.0
are fully defined in the XSLT 2.0 specification. Issue 546 is essentially
an XQuery issue. It's possible that some more technical work may be needed on
the XSLT side to define edge cases, for example the situation where a
schema-validated document is supplied to a non-schema-aware processor, or the
handling of type information derived from DTDs, but I think the conformance
modules and levels defined in the XSLT 2.0 draft are essentially agreed and
workable.
(Under these rules, a Basic XSLT Processor must be able
to manipulate atomic values conforming to any of the XML Schema built-in types,
for example strings, integers, decimals, doubles, dates, times, QNames.
But a Basic XSLT processor does not support type annotations on nodes
in the data model: all nodes are untyped. And it does not support user-defined
types.)
The XSL WG takes the view that the XPath specification
does not need to define any conformance rules; all the conformance rules for an
XSLT 2.0 processor, including those for XPath-within-XSLT, will be defined in
the XSLT specification itself.
Issue 546 is there because some members of the XQuery
group want to make some prescriptive statements about how input data models
might be constructed, e.g. from source XML documents, schemas, and DTDs. The XSL
WG has taken the decision that this is outside the boundary of the XSLT
specification and not subject to any conformance
rules.
Michael
Kay
|
