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

Re: Allow @namespace on p:pipeline

From: Henry S. Thompson <ht@inf.ed.ac.uk>
Date: Wed, 06 Jun 2007 11:32:32 +0100
To: Jeni Tennison <jeni@jenitennison.com>
Cc: public-xml-processing-model-wg@w3.org
Message-ID: <f5bwsyhe5kv.fsf@hildegard.inf.ed.ac.uk>

Hash: SHA1

Jeni Tennison writes:

> Actually, looking at <p:declare-step>, it struck me that perhaps we
> should have:
>   <p:pipeline name="local-name" type="my:qualified-name">
>     ...
>   </p:pipeline>
> In other words, have the type attribute hold a QName that provides the
> name of the element that you use to invoke the pipeline (just like the
> type attribute on <p:declare-step>), and the name attribute hold a
> NCName that provides a local name for the step attribute in <p:pipe>.

I like this.  I would go a bit further, and say that

 a) type is optional (and ignored if not in a library)
 b) the 'public name' of a pipeline (only relevant for pipelines in
    libraries) is determined as follows:
    1) @type if present
    2) otherwise {../@namespace}@name if ../@namespace is present
    3) otherwise @name

- -- 
 Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh
                     Half-time member of W3C Team
    2 Buccleuch Place, Edinburgh EH8 9LW, SCOTLAND -- (44) 131 650-4440
            Fax: (44) 131 650-4587, e-mail: ht@inf.ed.ac.uk
                   URL: http://www.ltg.ed.ac.uk/~ht/
[mail really from me _always_ has this .sig -- mail without it is forged spam]
Version: GnuPG v1.2.6 (GNU/Linux)

Received on Wednesday, 6 June 2007 10:32:43 UTC

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