- From: Norman Walsh <ndw@nwalsh.com>
- Date: Mon, 04 Jun 2007 13:41:02 -0400
- To: public-xml-processing-model-wg@w3.org
- Message-ID: <871wgrwrbl.fsf_-_@nwalsh.com>
In order to allow pipelines to be defined in a namespace even when they are not part of a library (as well as allowing a library to contain pipelines from more than one namespace), I think we should allow the namespace attribute on p:pipeline (with the semantics of @namespace on p:pipeline-library). Several recent messages have included examples of the form: <p:pipeline name="xx:name" xmlns:xx="http://www.example.com/ns/xx"> ... </p:pipeline> but that's an error. At the moment, you'd need: <p:pipeline-library namespace="http://www.example.com/ns/xx"> <p:pipeline name="name"> ... </p:pipeline> </p:pipeline-library> but I think we should allows this as well[*]: <p:pipeline name="name" namespace="http://www.example.com/ns/xx"> Be seeing you, norm [*] 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 :-) -- Norman Walsh <ndw@nwalsh.com> | Nothing is worth more than this day.-- http://nwalsh.com/ | Goethe
Received on Monday, 4 June 2007 17:41:11 UTC