W3C home > Mailing lists > Public > public-xml-processing-model-wg@w3.org > February 2007

Re: Chameleon components

From: Norman Walsh <Norman.Walsh@Sun.COM>
Date: Thu, 08 Feb 2007 10:46:36 -0500
To: public-xml-processing-model-wg@w3.org
Message-ID: <87wt2stzxf.fsf@nwalsh.com>
/ Alex Milowski <alex@milowski.org> was heard to say:
| On 2/7/07, Alessandro Vernet <avernet@orbeon.com> wrote:
|>
|>
|> On 2/6/07, Norman Walsh <Norman.Walsh@sun.com> wrote:
|> >   <p:xslt version="2.0">
|> >     ...
|> >   </p:xslt>
|>
|> How do you set the value of the "version" attribute based on the
|> output of a previous step? And I won't take "you can't" as an
|> acceptable answer ;).
|
| I that case, wouldn't you just set the version attribute on the
| transform ?

Maybe. But let me be crystal clear. Given:

  <p:xslt name="xform10" version="1.0">
    <p:input port="stylesheet">
      <p:inline>
        <xsl:stylesheet version="2.0">...</xsl:stylesheet>
      </p:inline>
    </p:input>
    ...
  </p:xslt>

I expect the xform10 step to perform XSLT 1.0 processing on the
stylesheet irrespective of the version number on the input stylesheet.


I can live with a world where this step:

  <p:xslt name="xform">
    <p:input port="stylesheet">
      <p:inline>
        <xsl:stylesheet version="2.0">...</xsl:stylesheet>
      </p:inline>
    </p:input>
    ...
  </p:xslt>

has the semantic that the processor MUST do 2.0 processing if it can,
otherwise it can use an XSLT processor for some other version of XSLT.

Not truely interoperable, but possibly convenient enough to warrant
support anyway.

                                        Be seeing you,
                                          norm

-- 
Norman Walsh
XML Standards Architect
Sun Microsystems, Inc.

Received on Thursday, 8 February 2007 15:46:59 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:21:49 GMT