W3C home > Mailing lists > Public > public-qt-comments@w3.org > May 2006

[Bug 3070] How does "embedded simplified" work?

From: <bugzilla@wiggum.w3.org>
Date: Thu, 04 May 2006 21:57:10 +0000
To: public-qt-comments@w3.org
Message-Id: <E1Fblos-0001Bs-Ca@wiggum.w3.org>


mike@saxonica.com changed:

           What    |Removed                     |Added
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED

------- Comment #6 from mike@saxonica.com  2006-05-04 21:57 -------
Following the decision of the working group today:

Referring to comment #4,

change (1) has been applied.

change (2) has been applied. The rationale for dropping any mention of
embedding in a non-XML resource is not that it's impossible or disapproved of,
but that it's out of scope. If someone wants to define a way of embedding XSLT
in Java, that's up to them.

(3) and (4) don't exist

(5) At the end of 3.7 I've added:
<phrase diff="add" at="ZA">Simplified stylesheets therefore cannot use 
<termref def="dt-global-variable">global variables</termref>,
<termref def="dt-stylesheet-parameter">stylesheet parameters</termref>, 
<termref def="dt-stylesheet-functions">stylesheet functions</termref>, 
<termref def="dt-key">keys</termref>, 
<termref def="dt-attribute-set">attribute-sets</termref>, or
<termref def="dt-output-definitions">output definitions</termref>.  
In turn this means that the only useful way to initiate a transformation is to
supply a document node as the
<termref def="dt-initial-context-node">initial context node</termref>, to be
matched by the
implicit <code>match="/"</code> template rule using the <termref

(6) Change applied as proposed. Yes, the aim is to be illustrative rather that

We don't want to prescribe (or even describe) the many ways that a processor
might choose to locate an embedded stylesheet module, other than directly by
using its id. In some cases it might be implicit in the rules of another
language, for example there might be an <ant:transformation> element that has
the <xsl:stylesheet> element as a child. Or someone designing a content
management system might want to define an XML document format containing
multiple <xsl:stylesheet> elements, each with attributes (in some namespace)
suggesting the circumstances in which it is to be used. All such mechanisms are
essentially ways of identifying the root node of the stylesheet to be used: we
only need to say that the node must be identified, not how.

I was directed by the WG to mark this as fixed after reporting the changes
applied, which I will now do. Feel free, however, to comment further.

Michael Kay
for the XSL WG
Received on Thursday, 4 May 2006 21:57:25 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:57:12 UTC