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

Re: URIs as inputs and outputs

From: Norman Walsh <Norman.Walsh@Sun.COM>
Date: Thu, 06 Apr 2006 10:00:41 -0400
To: public-xml-processing-model-wg@w3.org
Message-ID: <87sloqajna.fsf@nwalsh.com>
/ ht@inf.ed.ac.uk (Henry S. Thompson) was heard to say:
| 'static' resources.  That is, on the pure dataflow model, you need
| e.g. two XSLT components, one with one input and a static resource
| stylesheet, and one with two inputs.

Uhm, why is this not sufficient?

  <p:step name="xslt">
    <p:input name="stylesheet" href="stylesheet.xsl"/>
    <p:input name="document" label="ptrtosomestepsoutput"/>
  </p:step>

| One obvious glitch is document sequences. . .

Indeed. It also seems to impose a particular implementation on the
processor. I'd like it if (some subset of) pipelines could be used to
describe straight-through SAX event streams which is how some pipeline
processors are currently implemented.

                                        Be seeing you,
                                          norm

-- 
Norman.Walsh@Sun.COM / XML Standards Architect / Sun Microsystems, Inc.
NOTICE: This email message is for the sole use of the intended
recipient(s) and may contain confidential and privileged information.
Any unauthorized review, use, disclosure or distribution is prohibited.
If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.

Received on Thursday, 6 April 2006 14:01:00 GMT

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