TITLE: | Summary of Voting on JTC 1/SC 34 N 586 - ISO/IEC 19757-4/FCD - Document Schema Definition Language (DSDL) - Part 4: Namespace-based Validation Dispatching Language (NVDL) |
SOURCE: | SC34 Secretariat |
PROJECT: | FCD 19757-4: Document Schema Definition Language (DSDL) Part 4 - Namespace-based Validation Dispatching Language |
PROJECT EDITOR: | Mr. MURATA Makoto [FAMILY Given] |
STATUS: | Summary of voting |
ACTION: | Based on the ballot responses, this FCD is APPROVED and the project status changes to 40.60. Project Editors are requested to review comments and advise the Secretariat regarding (1) the change to status 40.92, 40.93 or 40.99, and (2) the next project status and anticipated date that project status will change. |
DATE: | 2005-05-11 |
DISTRIBUTION: | SC34 and Liaisons |
REFER TO: | N0586b - 2005-01-10 - Ballot due 2005-05-10 - Document Schema Definition Language (DSDL) - Part 4:
Namespace-based Validation Dispatching Language (NVDL) N0586 - 2005-01-10 - ISO/IEC 19757-4/FCD - Document Schema Definition Language (DSDL) - Part 4: Namespace-based Validation Dispatching Language (NVDL) |
REPLY TO: |
Dr. James David Mason (ISO/IEC JTC 1/SC 34 Secretariat - Standards Council of Canada) Crane Softwrights Ltd. Box 266, Kars, ON K0A-2E0 CANADA Telephone: +1 613 489-0999 Facsimile: +1 613 489-0995 Network: jtc1sc34@scc.ca http://www.jtc1sc34.org |
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 | X | |||||
Netherlands | X | |||||
Norway | X | |||||
United Kingdom | X | |||||
United States | X |
Template for comments and secretariat observations |
Date: 2005-05-05 |
Document:ISO/IEC 19757-4/FCD - SC34N0586 |
1 |
2 |
(3) |
4 |
5 |
(6) |
(7) |
MB1 |
Clause No./ |
Paragraph/ |
Type of com-ment2 |
Comment (justification for change) by the MB |
Proposed change by the MB |
Secretariat observations |
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 |
5th 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 |
1st para |
Ed |
Change "an element" to "a foreign element". |
|
|
GB |
Clause D.3.2.2 |
|
Ed |
Change "esnXhtml2 and esnXhtml2" to "esnXhtml2 and esnXhtml3". |
|
|
1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. FR for France; comments from the CMC editing unit are identified by ***)
2 Type of comment: ge = general te = technical ed = editorial