ISO/IEC JTC 1/SC 34N0748
ISO/IEC JTC 1/SC 34
Information Technology --
Document Description and Processing Languages
|TITLE:||Disposition of Comments to N0738 Summary of Voting - Document Schema Definition Language (DSDL) - Part 9: Namespace- and datatype-aware DTDs|
|SOURCE:||Mr. Martin Bryan|
|PROJECT:||CD 19757-9: Information technology - Document Schema Definition Languages (DSDL) - Part 9: Datatype- and namespace-aware DTDs|
|PROJECT EDITOR:||Mr. Francis Cave|
|STATUS:||Disposition of Comments|
|ACTION:||The editor is directed to make the changes|
|DISTRIBUTION:||SC34 and Liaisons|
|REFER TO:||N0738 - 2006-05-28 - Summary of Voting on JTC 1/SC 34 N 709 - Text for CD Ballot - ISO/IEC CD 19757-9 - Document Schema Definition Language (DSDL) Part 9 - Namespace- and datatype-aware DTDs|
Dr. James David Mason
(ISO/IEC JTC 1/SC 34 Secretariat - Standards Council of Canada)
Crane Softwrights Ltd.
Kars, ON K0A-2E0 CANADA
Telephone: +1 613 489-0999
Facsimile: +1 613 489-0995
Network: [email protected]
Suppose that an instance and a DTD use different namespace prefixes but they are associated with the same namespace name. Then, is the document valid? If this is the case, how can Part9-aware DTD validators can interwork with Part9-unaware DTD validators? If this is not the case, how can Part 9 interwork with recent XML specifications?
A mechanism will be provided to allow users to indicate whether or not their definitions require tools that are able to identify when different prefixes have been assigned to the same namespace name. A mechanism will be added to allow users to indicate whether or not the document will be valid with respect to the DTD when processed by a parser that is not DSDL9 aware.
Use IRIs rather than URIs.
1. General comments
1.1 There is currently no explanation of where within an instance or DTD the namespace or datatype declarations are to be placed. A full explanation is needed of how to include declarations in a DTD or instance, whether in PI syntax or XML syntax. In particular, a mechanism is needed to invoke (from within the DTD) declarations expressed using the XML syntax.
A processing instruction will be provided that will reference namespace and datatype definitions in an external file. The option will include an attribute that will allow users to indicate whether the referenced definitions are defined as processing instructions or XML elements.
1.2 Although alternative ways of implementing this Part of DSDL may be found, it would encourage implementation if a reference implementation were available. The design of such a reference implementation should be included in an informative annex to this standard.
The need for a developer capable of creating a reference application will be brought up at the Extreme 2006 conference to be held in Montreal in August.
1.3 An informative Annex should be added containing examples of the use of this language in both PI and XML syntax. The examples should be representative of the full scope of the application of namespaces and datatypes. In the case of namespaces, examples should include:
unqualified names in the instance being bound to a default namespace and validated against unqualified names in the DTD
unqualified names in the instance being bound to a default namespace and validated against qualified names in the DTD
qualified names in the instance being bound to a namespace and validated against unqualified names in the DTD
qualified names in the instance being bound to a namespace and validated against qualified names in the DTD (the qualifying prefixes in the instance may or may not be the same as the qualifying prefixes in the DTD)
2. Specific comments
2.1 Text is needed for Section 3 'Terms and definitions'.
2.2 Examples should not be included in Sections 4 through 7, but in an informative Annex – see comment 1.3 above.