TITLE: | Disposition of Comments to JTC 1/SC 34 N 792 - Text for FCD ballot for ISO/IEC 19757-8: Document Schema Definition Language (DSDL) Part 8 - Document Schema Renaming Language (DSRL) |
SOURCE: | Mr. Martin Bryan |
PROJECT: | FCD 19757-8: Information technology - Document Schema Definition Languages (DSDL) - Part 8: Document Schema Renaming Language (DSRL) |
PROJECT EDITOR: | Mr. Martin Bryan |
STATUS: | Disposition of comments |
ACTION: | For information |
DATE: | 2007-03-24 |
DISTRIBUTION: | SC34 and Liaisons |
REFER TO: | N0792 - 2006-10-17 - Text for FCD ballot for ISO/IEC 19757-8: Document Schema Definition Language (DSDL) Part 8 - Document
Schema Renaming Language (DSRL) N0817 - 2007-02-22 - Summary of Voting on JTC 1/SC 34 N 792 - Text for FCD ballot for ISO/IEC 19757-8: Document Schema Definition Language (DSDL) Part 8 - Document Schema Renaming Language (DSRL) |
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 |
1: The namespace should comply with that from the other parts of ISO/IEC 19757, especially Part 2.
Not Accepted: Part 8 namespace aligns with all other namespaces, except Part 2, which preceded the decision to use permanent URLs for namespace resolution.
1.1: Clarify the scope
Accept: Overriding of existing values will not be permitted in DSRL, but default content of both attributes and elements can be defined to allow the addition of missing markup
Consider possibility of mapping attributes to elements (or vice versa, if it does not involve contradictions in terms of context, especially if elements contain mixed content).
1.2: Introduce a processing model
Accept: Describe the two phase processing model and note that it can be implemented using XSLT 2.0 as described in the informative annex.
1.3: Drop entity definitions
This is no longer a requirement following the response to 1.2.
2.1 Allow value-maps for elements
Accept: This requires a check first to ensure that there are no child elements or PIs within the text. Then a map of the white-space normalized text content of the element can be created.
2.2 Introduce precedence rules
Not Accepted: The existing text of 6.1 includes the statement "No two dsrl:element-map elements shall have the same contents for both their dsrl:within element and their dsrl:from element." and "No two dsrl:attribute-map elements within a given dsrl:element-map may have the same value for their dsrl:from element."
2.3 Use datatypes in schemas
Accept: Add normative reference to XML Schema Part 2: Datatypes
2.4 Name token groups
Approve. Called an Enumeration in XML.
2.5 Drop default values and default contents
Not Accepted: See response to 1.1. Overriding will be dropped.