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

Re: New "New" draft: 22 Aug 2007

From: Jeni Tennison <jeni@jenitennison.com>
Date: Wed, 22 Aug 2007 21:31:34 +0100
Message-ID: <46CC9D26.8000800@jenitennison.com>
To: public-xml-processing-model-wg@w3.org


Just three things this time (looking at the p:namespaces section).

First, I don't see it explicitly stated that if the <p:namespaces> 
element hasn't got an element or option attribute on it then the 
namespaces come from the in-scope namespaces on the <p:namespaces> 
element. (Also I think the text and examples are a bit misleading in 
that they lead you to think you have to actually have xmlns:foo 
attributes on the <p:namespaces> element itself, which of course you 
don't: its in-scope namespaces are used, wherever they're actually 

Second, the paragraph:

   The except-prefixes attribute can be used to exclude one or more
   namespaces from the set. The value of the except-prefixes attribute is
   a sequence of tokens, each of which must be the prefix of a namespace.
   It is a static error (err:XS0005) if any token specified in the prefix
   list is not the prefix of an in-scope namespace.

I think it needs to be clearer that the except-prefixes attribute 
excludes namespaces from the set of namespaces indicated by the 
<p:namespaces> element. These might be the namespaces in-scope on the 
<p:namespaces> element (if it doesn't have an element or option 
attribute), or they might be namespaces from an option or element as 
selected by the option or element attribute.

Third, the final paragraph:

   The expression is evaluated in the appropriate context, See Section
   2.8, “XPath Context”.

would be better placed near to the place where you talk about the 
element attribute.


Jeni Tennison
Received on Wednesday, 22 August 2007 20:31:38 UTC

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