| TITLE: | Comment Disposition for the voting on JTC 1/SC 34 N 538 - Document Schema Definition Language (DSDL) - Part 3: Rule-based validation (Schematron) |
| SOURCE: | Mr. Rick Jelliffe |
| PROJECT: | CD 19757-3: Document Schema Definition Language (DSDL) Part 3 - Rule-based validation |
| PROJECT EDITOR: | Mr. Rick Jelliffe |
| STATUS: | Disposition of Comments |
| ACTION: | The editor is instructed to create FCD text. |
| DATE: | 2004-10-27 |
| DISTRIBUTION: | SC34 and Liaisons |
| REFER TO: | N0524 - 2004-06-01 - Document Schema Definition Language (DSDL) - Part 3: Rule-base
validation (Schematron) N0538 - 2004-09-10 - Summary of Voting on JTC 1/SC 34 N 524 - Document Schema Definition Language (DSDL) - Part 3: Rule-base validation (Schematron) N0541 - 2004-09-14 - UK's comments on SC34 Ballot N524: Document Schema Definition Language (DSDL) - Part 3: Rule-base validation (Schematron) |
| 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: [email protected] http://www.jtc1sc34.org |
Items marked "accepted" have been discussed in the Working Group and alterations consonant with the suggested fix have been made to the draft by the Editor.
| Comment | Disposition |
|---|---|
| Japan | |
| (1) Clause 3 is misleading. Although the first sentence says "The definitions of Part 1 and Part 2 also apply to this part of ISO/IEC 19757", some terms in Part 2 (e.g., "valid with respect to a schema", "pattern") are used differently from Part 2. The first sentence should be removed and every word borrowed from Part 1 and Part 2 should be explicitly listed. | Accepted The first sentence has been removed. No terms from Part 1 or Part 2 are borrowed. |
| (2) Sub-clause 4.2 does not make any sense (probably due to a formatting problem). Please rewrite and reformat this sub-clause. | Accepted Section 4.2 (of the CD) and section 6.3 (of the CD) have been simplified and rewritten. Special thanks to Dr Murata for his kind help here. As part of this, the terminology "minimal" syntax has been used instead of "simple" or "simplified" syntax throughout, because those words are also used in other contexts, notably the S in SRVL. |
| United Kingdom | |
| Foreword Correct list of standards to show correct numbers and titles of parts | Accepted (note that boilerplate goes in stylesheet |
| Introduction Add first two paragraphs from Introduction to Part 2 (also used in Part 4) | Accepted |
| Change three occurrences of "a normative annexes" to "a normative annex" Delete the last paragraph | Accepted |
| Delete the last paragraph | Withdrawn In working group discussions, the contribution of Open Source implementations to the technology was discussed and the example of Part 2. |
| 1. Scope In second paragraph delete last "the". | Accepted |
| 3. Terms and Definitions Order the terms alphabetically so that they are easy to refer to when reading the text. | Accepted |
| 3.2 Delete "committee-draft" | Accepted Replaced by markup <this>this part of ISO/IEC 19575</this>. This markup now used throughout document. Document stage moved to "approval" in header. |
| 3.3 Capitalize It. | Accepted |
| 3.14 Correct "expression" (only 2 s's) | Accepted |
| 3.19 Change "and repair" to "together with repair" | Accepted |
| 4.1 Move second sentence to the start of 5.1 (or move the first para of 5.1 to 4.1 and then adjust the title of 5.1) | Accepted Working group comment was to clarify that "sch" is not magic. |
| 4.2 Delete the third item listed (which repeats the second) How should the first expression be displayed? Is it correct that expressions 2 to 7 are identical in the proof? | See Japanese comment 2) |
| 5.1 Change "grammar" to "Schematron grammar" and change URI to form used for Part 4, based on ISO URNs. Review last paragraph, which is ambiguous. Does "Schematron-namespace elements" refer to any elements with an sch: prefix or only those used to define namespaces (e.g. the RNC definition for namespace)? Is a "Schematron-namespace attribute" one that has the sch: namespace or one that is associated with an element in the sch: namespace? | Accepted URI to use "http://purl.oclc.org/dsdl/schematron" because existing namespace is not controlled by ISO and we need to be sensitive to potential anti-Taiwan sentiments. SC34 to be asked to thank Academia Sinica Computing Centre for the provision of the previous namespace. NOTE: Registration procedure not performed yet. A new namespace means we don't need a the schema/@version attribute now; it has been removed from schemas, text and examples. It is also prudent because it sharply distinguidhes old snd new implementations. However, it is tedious and goes against statements made by the editor previously that there would be a level of compatability. |
| 5.2 Add sentence pointing out that the formal definitions of core elements are provided in Annex A. | Accepted |
| 5.2.2 In note, change "information, however" to "information. Users should note, however, that". Some mention should be made that the flag, role and subject attributes are defined in the following clause. | Accepted |
| 5.2.4 Change "with" to "containing" | Accepted |
| 5.2.5 Change "are used" to "are tested". | Accepted |
| 5.2.6 In Annex A a select attribute has not been defined. I suspect this is an error in the annex, as select makes much more sense than path for the attribute name. In second paragraph insert "element" after name. | Accept"path" is the correct name (from pre-ISO Schematron). Second paragraph is a duplicate, and has been removed. |
| 5.2.7 Change "required prefix attribute" to "optional prefix attribute" or change model provided in Annex A to conform with statement. Remove Note 2 - it duplicates preceding sentence. | Accepted The attribute is required. Note 2 has been deleted. Former section 7, on using Schematron in other vocabularies, has been made a normative annex. Note 3 has been deleted, and former section 7 clarified to express the intent of note 3. The introduction has been updated accordingly. |
| 5.2.8 The use of the name token as the model for name attribute in Annex A. >From the definition given here it looks as if it should have been defined as xs:NAME but at present it is impossible to work out exactly what the content of the name attribute should really be. | Accepted The names of datatypes have been suffixed by "Value" for clarity. Also, the schema has had all dependencies on XML 1.0 removed, as far as the documents being validated is concerned: consequently Schematron uses ID/IDREF for internal links, but everything else is just a string. Full conformance has been adjusted accordingly. |
| 5.2.9 Explain role of abstract attribute and the link between is-a and param | accepted Several paragraphs and examples added |
| 5.2.10 Delete the second sentence or add a name attribute to the model for phase in Annex A. | Accepted "id" is the correct name for the attribute |
| Add definition of #ALL and #DEFAULT to Annex A or remove the second para of this subclause. | Withdrawn #ALL and #DEFAULT are for external use. sch:schema/@defaultPhase was wrongly called @phase. This is corrected. The schema is correct as far as this is concerned. However, the text has been clarified. |
| Add description of linkable attributes and explain why they apply here. | Accepted text and notes added |
| 5.2.11 In note, change "information, however" to "information. Users should note, however, that". | Accepted |
| 5.2.12 Explain role of abstract attribute | accepted extra material added |
| 5.2.13 Remove "empty" from end of first sentence. | Accepted |
| A better name for the "language" attribute might be "bound-to". (Language is ambiguous, and will be confused with xml:lang.) | Accepted @queryBinding instead of @language |
| 5.2.14 Remove "either". | Accepted |
| 6.3 Either change subject ε schema or, in Note 7, change "the pattern being a member of the schema" to "the subject being a member of the schema". | Accepted Rewritten: see Japanese comment 2) above. |
| 6.4 Define the meaning of the phrase "query language binding" either in this clause or in the Terms and Definitions clause. In Note 8, add a comma after xslt. In the next paragraph change "the specification" to "the requested specification". Explain what a "specification language" is either in this clause or in the Terms and Definitions clause (term is used in the last para). | Accepted definition added. "Specification language" is a mistake, should be "query language binding" |
| 6.5 Add periods to the end of the second and third paras. Change the (to Europeans meaningless) Australian word "interected" for one that actually appears in the Oxford English Dictionary! In Note 9 correct the spelling of constraints. | Accepted "Elaborated rule context expressions" now in terms section and better explained without interections. |
| 8.1 and 8.2, first list item After (RELAX NG) add "compact syntax" At end of Note 12 and Note 14, add "defined in Annex D" | Accepted |
| Annex A Remove 7th to 18th comment lines Check that changes noted above have been made and that schema reflects latest version of normative text. | Accepted |
| Should some form of limiting pattern be defined for the strings identified by the tokens path and fpi? Should the namespace for the datatype used to validate expr constrain the expression to be expressed in a particular notation? | Withdrawn On discussion, it was decided that the schema should be made as independent of XPath and xml 1.0 as possible, for futureproofing |
| Annex B Change "schema" at end of first line to "Schematron schema:" | Accepted |
| Is definition of the rule for context sch:active correct? Why does it not have the [@pattern] qualifier as is used in the next rule? Is the definition of the rule for the rule for context sch:extends correct? Should there not be a [@rule] qualifier for the context path? | Withdrawn they are correct |
| Annex C Add colon at end of first para. Capitalize P in production (5 occurrences) | Accepted |
| D.1 Remove second sentence of first para. | Accepted |
| D.2 Replace DTD with RNC definition for consistency. | Withdrawn DTDs are part of XML and SGML (and intended as part of ISO DSDL) and the use of DTDs displays plurality. |
| D.3 Change two occurrences of "Report Validation" to "Validation Report" and change "SRVL" to "SVRL". In message for the second rule change "any elements" to "any embedded elements". Ensure a blank line precedes each rule | Accepted |
| Annex E What does "line-to-one mapping" mean? Is this another Australian term that is not known in Europe? | Accepted |
| Working Group Instructions | |
| Explain multi-lingual operation | A non-normative annex has been added with a simple example. A link has been made from the diagnostics element clause, and the introduction updated. |
| Allow external variables | let values may be over-ridden by command line option |
These are mainly to correct the schema. Also, spell-check and check XML well-formedness. The feedback and suggestions the implementors of the previous draft, Daniel Cazzulino, Uche Ogbuji and Brian Ewins have also been checked.
| @flag allowed sch:rule--schema is wrong | |
| assert and report allow value-of as child | |
| include has attribute @href not @src, to follow RELAX NG example | |
| Correct use of @name instead of @id for elements rule and pattern in text and Annex A |