W3C home > Mailing lists > Public > www-dom@w3.org > July to September 2003

DOM3 Load & Save Last Call Comments

From: Mikko Honkala <honkkis@tml.hut.fi>
Date: Fri, 01 Aug 2003 15:53:43 +0300
Message-ID: <3F2A62D7.5020404@tml.hut.fi>
To: www-dom@w3.org


I've revieved the DOM3 Load & Save Last Call spec [1] for the XForms WG
and have the following Last Call comments:

1. Inconsistency in DOMParserFilter

Inconsistency: 1.1 says DOMParserFilter filters only elements, while 1.3
says all kinds of nodes (e.g. attributes and text nodes) can be
filtered. Which is right? The preferred answer is that of 1.3. Please
fix this in the spec.

2. Inconsistency in DOMSerializerFilter

Inconsistency: 1.1 says DOMSerializerFilter can be used to filter out
nodes, but 1.3 says that only elements can be filtered. Why doesn't this
interface include attributes? An example of a use case: in XForms the
'relevant' attribute can be set to false on a attribute, which removes
it from the serialization. Please fix this so that also attributes and
text nodes can be filtered out.

3. 1.4 Convenience Interfaces should be made mandatory

Why are these interfaces optional? If the claim is right that they are
just convenience methods, they should be trivial to implement. For users
it will be a pain to check whether an implementation supports these
interfaces. Please fix this by making them mandatory.

[1] DOM3 LS
Received on Friday, 1 August 2003 08:50:52 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 20 October 2015 10:46:11 UTC