GB

Ge

Some concepts used in the document are not clearly defined. There needs to be more explanatory matter to put the use of the described functions into context. Examples that deal with multiple instances of context would be helpful.

GB

Clause 2

Ed

Note at end of list needs to be resolved and removed

GB

Clause 3

Ed

A cross reference to terms defined in ISO 8879 could usefully be added to the start of the list

GB

Clause 3.10

Ed

Change "identifier" to "token"

GB

Clause 3.11

Ed

The term "action-mode pair" is not understandable, and seems to be self-referenceable.

GB

Clause 3.20

Ed

The definition of slot node is circular. Not everyone understands what a slot is: the term should be defined in the standard.

GB

Clause 4

Notation

Ed

An introductory paragraph should be added to provide context for the following statements. This could be along the lines:

"The following conventions have been adopted in the formal definitions provided in this standard:"

In definition of |e| change "number of elements" to "number of descendant elements"

GB

Clause 4& subsequent sections

Ed

The term "place holder" is used consistently throughout the standard. The Oxford English Dictionary, however, gives the spelling of "placeholder" and does not offer an alternative with a space.

GB

Clause 5.1

5^th para

Ed

The last phrase, "or that of some descendent of e" appears to be incorrect.

GB

Clause 5.1

Note 1

Ed

This note is unclear.

GB

Clause 6.1

Ed

In the last sentence the word "may" is used, implying that simplification is optional. Is the accurate, or should the word be replaced by "must" or, alternatively, "will"?

GB

Clause 6.4.2

Ed

The term "Qualified attributes" is not defined in clause 3, or in any of the XML documents referred to (which only ever refer to "unqualified attributes")

GB

Clause 6.4.4

Note

Ed

Change "ans" to "and"

GB

Clause 6.4.12

Ed

The term "Collision" in the heading is not used in the text. In the text the term "Competition" is used. Standardize on one term, e.g. "Competition within mode"

It would appear that Case 3 can only exist in the case where w1=w2. The purpose of nsTail2 is, therefore, unclear.

For Case 4 and Case 5 it should be made clear that the stripping of the first character occurs if it matches either w1 or w2.

GB

Clause 6.4.14

Ed

In second paragraph "allow element" should be "reject element".

GB

Clause 7.2 & 7.3

Ed

Change "the child sequences ... is" to "the child sequences ... are"

GB

Clause 7.6

Ed

See note above re "placeholder" and consider changing "placeHolder" to "placeholder".

GB

Clause 7.7

Ed

Change "denoted" to "known as".

GB

Clause 8.2

Paras 5-8

Ed

The phrase "the parent element section" restricts the action to the immediately preceding element, rather than allowing it to affect all ancestor elements. Is this deliberate? If so, please explain why there is a (s) in the following "path(s)" as it would seem that only one path can be created.

In the third Case 2 entry the phrase "some ending sequence" implies that any possible subsequence can match the specified sequence of Ncnames, not that all of the end must match it. Is this correct?

In the fourth Case 2 what does the term "elder sibling" mean? If it means "

"preceding sibling" then change the term to the more standard terminology used throughout the XML specification.

In the penultimate paragraph should "nsOrAny in mode" be "nsOrAny in mode'" (i.e. should mode be qualified by a quote?)

GB

Clause 8.6

Note

Ed

Change "is meant to choose" to "selects".

GB

Clause 8.7.1

Note

Ed

Change "do not have" to "do not include".

GB

Clause 8.7.2

1^st para

Ed

Change "an element" to "a foreign element".

GB

Clause D.3.2.2

Ed

Change "esnXhtml2 and esnXhtml2" to "esnXhtml2 and esnXhtml3".