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

/ Jeni Tennison <jeni@jenitennison.com> was heard to say:
| 2. Allow pipelines to be given a local NCName (in the name attribute)
| and a global QName (in an 'export' attribute, for example):
|
| <p:pipeline name="top" export="x:resolve-and-include">
|   ...
| </p:pipeline>
|
| I kinda like this because I think the names you want to use to refer
| to pipelines from outside (when you use them in other pipelines) are
| likely to be long and descriptive, whereas the names you want to use
| to refer to pipelines from inside are likely to be short and
| convenient. So having two names makes a kind of sense.

Of the proposals on the table, I think I still prefer simply using
QNames. But if we don't re-open that issue, I think my second choice
is the two-name approach that Jeni outlines above.

                                        Be seeing you,
                                          norm

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