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

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





------- Comment #2 from david_marston@us.ibm.com  2006-04-12 17:12 -------
Part 3.11 begins with a bullet list of two forms of embedding that are
possible,
neither of which is a simplified stylesheet (no xsl:stylesheet element) within
an XML document other than as the document element. This is not precisely
aligned with the definition of embedded stylesheet module given at the
beginning of Chapter 3. Since the verbiage makes clear that embedded simplified
exists, we want to know how one would determine the boundaries of the
stylesheet module(s) in an XML document, but not the document element, in the
absence of an xsl:stylesheet element.

3.10.1 clearly says that xsl:import and xsl:include can pull in an embedded
simplified stylesheet module. If a standalone standard stylesheet has no
template for match="/" and has an xsl:include referencing the file below (the
whole file, without a fragment identifier), what do we expect?

<?xml version="1.0"?>
<outer xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
  <foo>
    <bar1 xsl:version="2.0">
      <xsl:value-of select="concat('bar1','was','called')"/>
    </bar1>
    <bar2>bar2 content</bar2>
  </foo>
  <bar3 xsl:version="2.0">
    <xsl:value-of select="concat('bar3','was','called')"/>
  </bar3>
</outer>

It looks like there would be two match="/" templates resulting from the
include.
Next question: same as above, but xsl:version="2.0" is also present on <outer>.
Next question: if the xsl:include supports fragment identifiers, what if <foo>
is indicated as the start of the fragment?

Received on Wednesday, 12 April 2006 17:13:02 UTC