---

P-Member	APPROVAL OF THE DRAFT AS PRESENTED	APPROVAL OF THE DRAFT WITH COMMENTS AS GIVEN ON THE ATTACHED	DISAPPROVAL OF THE DRAFT FOR REASONS ON THE ATTACHED	DISAPPROVAL (appropriate changes in the text will change vote to APPROVAL)	ABSTENTION (For Reasons Below)	NO RESPONSE
Canada	X
China						X
Italy					X
Japan				X
Korea, Republic of	X
Netherlands	X
Norway		X
United Kingdom	X
United States		X

Italy

Abstention for lack of experts.

Japan

General

Since this part is not normative, it should not be a standard but rather a TR (type 3).

Introduce a new section for schema inclusion and recommend the use of XInclude (or external parsed entities) for syntactical inclusion of schemas.

State that other parts may be added later when new requirements are recognized.

3.4 Schema

Replace "XML-encoded set" with "set".

3.5 The role of document schemas

Restate that an SGML document is first converted to an information set by validation against SGML DTDs. This assumption is stated only in the scope section.

6 Validation Management

Delete this section and move its content to Section 4 or 8.10.

Figures 1 and 2 are misleading, since RNG validation does not create any XML documents.

8.2 Part 2

Since this part is RELAX NG, the first paragraph should not mention other regular-grammar-based schema languages.

Remove the last paragraph, since new parts may be added anyway.

8.3 Part 3

Since this part is Schematron, the first paragraph should not mention other rule-based schema languages.

Remove the last paragraph, since new parts may be added anyway.

8.4 Part 4

Drop the fourth paragraph (about NRL). NRL is not the only ancestor of NVDL and NRL is not identical to NRL. Moreover, unlike RELAX NG and Schematron, NRL is not widely used. The history of NVDL should rather be explained in Part 4.

Remove the editorial notes, since NVDL already provides a mechanims ("trigger") that specifies element names for creating validation candidates.

Remove the last paragraph, since NVDL schemas do specify which schema and which schema language is used for validation candidates.

8.5 Part 5

Replace "regular expression grammars" with "regular expressions", since regular expressions, regular grammars, and regular right-hand-part grammars are different from each other.

Mention the equivalence relationship. (e.g, are "1" and "01" equivalent?)

8.6 Part 6

Remove the third paragraph (about extracting fragments by XPath), since such extraction of fragments has never been in the scope of this part.

Mention better integration with Part 2 (e.g., static typechecking) as an advantage of this part.

This part should not have a mechanism for embedding fragments from other documents.

Do not mention XPath in Part 1, since different parts have good reasons to create different variations of XPath. In particular, path expressions in Part 4 are NOT XPath.

Since extraction of fragments by XPath should be done by an XSLT stylesheet, DSDL should not duplicate this functionality.

8.8 Part 8

Drop entity renaming unless such renaming is implementable without changing the behaviour of conformant XML processors.

Norway

(comments absent from form; NB requested to forward comments directly to working group)

United States

As noted in ISO/IEC CD 19757-1, Document Schema Definition Language (DSDL) - Part 1: Overview, at page 5, paths should be treated in part 10 of DSDL.