DOM Level 3 Validation Issues List

This document contains a list of issues regarding the DOM Level 3 Validation specification Candidate Recommendation period. All comments or issues regarding the specification or this document must be reported to www-dom@w3.org (public archives) before 31 August, 2003.

Id: Title	State	Type	Ack.
curt-1 : values for NodeEditVAL.VAL_TRUE, VAL_FALSE, VAL_UNKNOWN	declined	proposal	Agreement

State description

Raised: Initial state; The group has not accepted the issue yet.
Accepted: Initial state; The group has agreed to address the issue.
Deferred: The Group has not reached a decision on this issue, but does not intend to work on it further without new input.
agreed: The Group has made a decision and decided to follow the suggestion.
Declined: The Group has decided not to address this issue.
Moved: The issue was moved in an other group. The Group does not intent to resolve this issue.
Subsumed: The issue has been subsumed by an other issue. A link to the other issue is given.

Decision cycle description

Announced: Initial decision cycle; The group has announced his decision.
Agreement: The group received an agreement to refine his decision.
Proposal: The group received a proposal to refine his decision.
Objection: The group received an objection to his decision.
Accepted: The group reopened an issue to reconsider his decision after received an objection or proposal. A link to the new issue is given.
Maintained: The group maintained his decision after received an objection or proposal.

Issue details

Validate my issues file

curt-1: values for NodeEditVAL.VAL_TRUE, VAL_FALSE, VAL_UNKNOWN

The values assigned for VAL_TRUE, VAL_FALSE and VAL_UNKNOWN appear to just follow the sequence established by VAL_WF, VAL_NS_WF, VAL_INCOMPLETE and VAL_SCHEMA (1, 2, 3, 4).

In scripting languages where the symbolic constants are not available, that would lead to code like:

	      if (node.canInsertBefore(node1, node2) == 6)

which isn't obvious. It would be beneficial to change the values so that, at least, VAL_FALSE is 0. I'd recommend, VAL_FALSE = 0, VAL_TRUE = 1 and VAL_UNKNOWN = 2.

Proposal concerning: NodeEditVal

Transition history

raised on 3 Dec 2003 by Curt Arnold

declined on 3 Dec 2003

While Curt has a point, this change happens late at the end of the Candidate Recommendation phase. We decided not to do the requested change.

Acknowledgment cycle

announced by group on 3 Dec 2003
agreement by reviewer on 3 Dec 2003