W3C home > Mailing lists > Public > public-qt-comments@w3.org > June 2005

[Bug 1501] Distinction between basic and Schema Aware XSLT 2.0 processor

From: <bugzilla@wiggum.w3.org>
Date: Thu, 16 Jun 2005 18:12:21 +0000
To: public-qt-comments@w3.org
Cc:
Message-Id: <E1Diyqj-0000cV-8m@wiggum.w3.org>

http://www.w3.org/Bugs/Public/show_bug.cgi?id=1501


mike@saxonica.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|                            |FIXED




------- Additional Comments From mike@saxonica.com  2005-06-16 18:12 -------
I have made changes to this paragraph which I hope you will find satisfactory.
It now reads:

The conformance rules for XSLT 2.0, defined in [], distinguish between a basic
XSLT processor and a schema-aware XSLT processor. As the names suggest, a basic
XSLT processor does not support the features of XSLT that require access to
schema information, either statically or dynamically. 

A stylesheet that works with a basic XSLT processor will produce the same
results with a schema-aware XSLT processor provided that the source documents
are untyped (that is, they are not validated against a schema). However, if
source documents are validated against a schema then the results may be 
different from the case where they are not validated. Some constructs that work
on untyped data may fail with typed data (for example, an attribute of type
xs:date cannot be used as an argument of the substring function) and other
constructs may produce different results depending on the data type (for
example, given the element &lt;product price="10.00" discount="2.00"/&gt;,
the expression @price gt @discount will return true if the attributes have type
xs:decimal, but will return false if they are untyped).

Please feel free to reopen the bug if you think this can be improved further.
Received on Thursday, 16 June 2005 18:12:26 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 March 2012 18:14:38 GMT