Re: More L3 Core Comments

On Thu, 2003-07-17 at 00:25, Curt Arnold wrote:
> Interface DOMStringList:
> 
> "ordered collection of parallel pairs of name and namespace values"
> 
> This phrase also appears in the description for NameList.
> 
> Interface NameList:
> 
> "ordered collection... values"
> 
> Maybe "ordered collection of qualified names"

We change NameList: "ordered collection of parallel pairs of name and
namespace values (which could be null values)"

> The description for the return values of getName and getNamespaceURI are 
> identical, though from the context you could guess that one is a name 
> and the other a NamespaceURI.

Fixed.

> getName does not define whether the return value is a local name or 
> might contain a namespace prefix. 

Correct. This depends on its usage. NameList is meant to be a generic
interface and used in different ways depending on the context. The DOM
Level 3 Validation draft has been clarified to make that context clear:
[[
if the schema is a DTD, the element information item names are simply
local names; if the schema is a W3C XML schema, the names are qualified
names, which may contain namespace prefixes.
]]

> Exception clauses of getName() and getNamespaceURI() contain "number of 
> nodes in the list" though the list does not contain nodes. 

We removed the exceptions to match NodeList.

>  The expected 
> behavior for negative indexes is not defined. 

Correct, since the index is unsigned. Given the recent discussion on
this list, it looks like we may need to say something about that. Not
sure if it will end up in the draft before the publication of the
candidate recommendation.

>  Throwing an exception on 
> out of range indexes is not consistent with DOMStringList and other 
> lists.   I can understand the motivation since getNamespaceURI() could 
> be null before the end of the list, however you could distinguish 
> between a null namespace and end of the list since getName would be null 
> at the end of the list.

We are now matching NodeList.

Philippe