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

Re: Allow @namespace on p:pipeline

From: Jeni Tennison <jeni@jenitennison.com>
Date: Mon, 04 Jun 2007 19:10:49 +0100
Message-ID: <466455A9.8000005@jenitennison.com>
To: public-xml-processing-model-wg@w3.org

Norman Walsh wrote:
> but I think we should allows this as well[*]:
> 
>   <p:pipeline name="name" namespace="http://www.example.com/ns/xx">

Yes. It should definitely be possible to declare pipelines in different 
namespaces within a single pipeline library.

(Arguments for a <div> element to provide scoping of namespace 
attributes elided. We can always add it later.)

> [*] Truth be told, I think we should just allow name to be a QName,
> but I'm not reopening that issue unless we get a last call comment
> to that effect. Assuming we *get* to last call before our charter
> expires, of course :-)

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>.

Cheers,

Jeni
-- 
Jeni Tennison
http://www.jenitennison.com
Received on Monday, 4 June 2007 18:11:10 GMT

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