RE: [XSLT2.0] XML versions and XSLT stylesheet as a data model in stance

Thanks for the comment. Unofficial interim response: 

We had some debate on this question and I think the results were somewhat
inconclusive. We need to sort this out.

The danger is that if we specify that the stylesheet is a DM document,
rather than serial XML, then that's one more place for little
interoperability problems to creep in. But we do tend to describe the
semantics of instructions on the assumption that they are nodes in a tree,
so I think it makes sense to go down that route.

Michael Kay



> -----Original Message-----
> From: public-qt-comments-request@w3.org 
> [mailto:public-qt-comments-request@w3.org] On Behalf Of David Carlisle
> Sent: 10 December 2003 15:21
> To: public-qt-comments@w3.org
> Subject: [XSLT2.0] XML versions and XSLT stylesheet as a data 
> model instance
> 
> 
> 
> 
> 
> Section 1 says:
> 
> 
>   [Definition: A transformation in the XSLT language is 
> expressed in the
>   form of a stylesheet, whose syntax is well-formed XML [XML 1.0]
>   conforming to the Namespaces in XML Recommendation [XML Namespaces
>   1.0].] 
> 
> 
> Is it intentional that a stylesheet has to be xml 1.0, so 
> presumably may not be expressed in xml 1.1 (or later) even 
> though source and result documents may be xml 1.1 (if the 
> system supports that)
> 
> Section 4.1 says
> 
>    Construction of the data model is outside the scope of this
>    specification, so XSLT 2.0 places no formal requirements on an XSLT
>    processor to accept input from either XML 1.0 documents or XML 1.1
>    documents or both.
> 
> This leads to a more general question, should the stylesheet 
> modules be instances of the data model (rather than XML 
> documents matching the production in the XML spec). If they 
> were defined this way, 4.1 would apply and so the xml version 
> number would be unconstrained (as would one or two other 
> things presently, such as white space handling, but that is 
> the subject of a separate comment)
> 
> 
> In practice several systems allow in-memory modification of 
> the stylesheet as a DOM of some sort, after it has been 
> parsed but before it is applied, so specifying that the 
> stylesheet is an instance of the DM might in fact be closer 
> to current practice than specifying that it must be a 
> document matching the productions in the XML spec.
> 
> 
> David
> 
> 
> ______________________________________________________________
> __________
> This e-mail has been scanned for all viruses by Star 
> Internet. The service is powered by MessageLabs. For more 
> information on a proactive anti-virus service working around 
> the clock, around the globe, visit: http://www.star.net.uk 
> ______________________________________________________________
> __________
>

Received on Wednesday, 10 December 2003 14:46:32 UTC