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

Re: Pipeline Composition and our Recent Pipeline Name/Library Decision

From: Norman Walsh <Norman.Walsh@Sun.COM>
Date: Fri, 16 Mar 2007 10:39:59 -0400
To: public-xml-processing-model-wg@w3.org
Message-ID: <87odmt9rr4.fsf@nwalsh.com>
/ ht@inf.ed.ac.uk (Henry S. Thompson) was heard to say:
| Here's an alternative I could live with: Pipelines are named with
| expanded names, steps are named with simple names, pipe/@step is an
| NCName, because that's all you need to refer to another step, and
| likewise from _inside_ a pipe all you need is its local name.

I guess that might work, but then we have the weird wrinkle that
the following pipeline is an error:

  <p:pipeline name="x:something" xmlns:x="http://www.example.com/ns/pipe">
    <p:xslt name="something"/>

which seems awkward to explain. (It's an error because you MUST NOT
have two steps with the same name in the same environment.)

                                        Be seeing you,

Norman Walsh
XML Standards Architect
Sun Microsystems, Inc.

Received on Friday, 16 March 2007 14:40:44 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:32:42 UTC