- From: Norman Walsh <ndw@nwalsh.com>
- Date: Tue, 21 Aug 2007 11:35:54 -0400
- To: public-xml-processing-model-wg@w3.org
- Message-ID: <m2ps1grjc5.fsf@nwalsh.com>
/ Jeni Tennison <jeni@jenitennison.com> was heard to say: [...] |> | 6. We need to say something about the default namespace. I'm inclined |> | to say that options never have a default namespace (which means that |> | you have to always give a prefix to QNames passed as option values). |> |> Yes. I thought we said that. | | I think we say it for QNames that are used in XProc (like the value of | the type attribute), but this section has to say it for namespace | bindings passed into options -- the context is different here. Fixed. | Like Mohamed suggested, we should provide a way to ignore other | namespace bindings, particularly if we're going to error if there are | any clashes. I don't want my binding for the XProc namespace to clash | with a binding from a configuration document just because we happened | to both use 'p' as the prefix. I added an except-prefixes attribute. Be seeing you, norm -- Norman Walsh <ndw@nwalsh.com> | My fate cannot be mastered; it can only http://nwalsh.com/ | be collaborated with and thereby, to | some extent, directed. Nor am I the | captain of my soul; I am only its | noisiest passenger.--Aldous Huxley
Received on Tuesday, 21 August 2007 15:34:42 UTC