ISO/IEC JTC 1/SC 34N0539

ISO/IEC logo

ISO/IEC JTC 1/SC 34

Information Technology --
Document Description and Processing Languages

TITLE: Summary of Voting on JTC 1/SC 34 N 525 - Document Schema Definition Language (DSDL) - Part 4: Namespace-based Validation Dispatching Language (NVDL)
SOURCE: SC34 Secretariat
PROJECT: CD 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 CD is APPROVED and the project status changes to 30.60. Project Editors are requested to review comments and advise the Secretariat regarding (1) the change to status 30.92 or 30.99, and (2) the next project status and anticipated date that project status will change.
DATE: 2004-09-10
DISTRIBUTION: SC34 and Liaisons
REFER TO: N0525b - 2004-06-01 - Ballot due 2004-09-01 - Document Schema Definition Language (DSDL) - Part 4: Namespace-based Validation Dispatching Language (NVDL)
N0525 - 2004-06-01 - 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 Chairman)
Y-12 National Security Complex
Bldg. 9113, M.S. 8208
Oak Ridge, TN 37831-8208 U.S.A.
Telephone: +1 865 574-6973
Facsimile: +1 865 574-1896
Network: masonjd@y12.doe.gov
http://www.y12.doe.gov/sgml/sc34/
ftp://ftp.y12.doe.gov/pub/sgml/sc34/

Mr. G. Ken Holman
(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, Republic of X          
Netherlands X          
Norway X          
United Kingdom           X
United States           X

Japan

1. General

(1.1) Since this part is based on a fast-track DTR submitted from Japan, we request that this part be freely available.

2. Technical

(2.1) The combination of XML 1.1 and Namespaces 1.1 should be allowed.

(2.2) It should be possible to create multiple element sections from a single-namespace document. This allows the use of NVDL for large single-namespace vocabularies (e.g., DocBook or CALS). We propose to introduce <trigger> elements as children of the <rules> element.

    <rules>
      <trigger ns="..." name="...."/>
      <trigger ns="..." name="...."/>
        ...
      <mode...>
        ...
      </mode>
      ...
    </rules>

(2.3) Improve "mode inclusion" on the basis of multiple inheritance in programming languages.

(2.4) Introduce schema rewriting for those RELAX NG schemas which are referenced from validate actions applied to attribute sections.

(2.5) The semantics of path expression matching should be clearly defined.

(2.6) Introduce the dummy and root-only option.

(2.7) Register a media type for the RELAX NG compact syntax at IANA and mention it in this standard.

3. Editorial

(3.1) Section 7.7 (invoking non-NVDL validators) should be deleted, since we already have Section 8.7.

(3.2) In 6.4.12 (mode inclusion), clearly state that the use of XInclude or parsed entities is intended for syntactical inclusion and that "mode inclusion" provides post-processing after syntactical inclusion.

(3.3) In Section 8, a new subsection is needed for explaining the creation of sections from instances. This section should refer to 5.2.

(3.4) Options have problems as below:

  1. It is impossible for this part to specify options for all schema languages,
  2. Different implementations of one schema language may provide different options, and
  3. The syntax of options might be more complicated than name-value pairs. To overcome these problems, we propose to make the syntax and semantics of options entirely implementation-dependent.