ISO/IEC JTC 1/SC34 N258

ISO/IEC logo

 

ISO/IEC JTC 1/SC34

Information Technology --

Document Description and Processing Languages

 

TITLE:

 

Summary of Voting on SC 34 N 216 - PDAM1 to ISO/IEC 10179: Extensions to DSSSL

SOURCE:

SC 34 Secretariat

PROJECT:

 

PROJECT EDITOR:

SC 34 / WG 2

STATUS:

 

ACTION:

This document is submitted to JTC 1/SC 34 for information and to WG 2 for preparation of a disposition of comments report and recommendation on further progression of the work. 

DATE:

 

DISTRIBUTION:

SC34 and Liaisons

REFER TO:

 

REPLY TO:

Dr. James David Mason
(ISO/IEC JTC1/SC34 Chairman)
Y-12 National Security Complex
Information Technology Services
Bldg. 9113 M.S. 8208
Oak Ridge, TN 37831-8208 U.S.A.
Telephone: +1 865 574-6973
Facsimile: +1 865 574-1896
E-mail: mailto:[email protected]
http://www.y12.doe.gov/sgml/sc34/sc34oldhome.htm

Ms. Sara Hafele, ISO/IEC JTC 1/SC 34 Secretariat
American National Standards Institute
25 West 43rd Street
New York, NY 10036
Tel: +1 212 642 4937
Fax: +1 212 840 2298
E-mail: [email protected]


SC 34 N 258

2001-10-04

 

 

 

SC 34 Voting Summary on JTC 1/SC 34 N 216

PDAM1 Ballot for ISO/IEC 10179: Extensions to DSSSL

 

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

Acceptance of these reasons and appropriate changes in the text will change our vote to approval

ABSTENTION (For Reasons Below):

Brazil

 

 

 

 

 

Canada

 

X

(editorial and technical)

 

 

 

China

 

 

 

 

 

Denmark

X

 

 

 

 

France

 

 

 

 

 

Ireland

 

 

 

 

 

Italy

X

 

 

 

 

Japan

 

X

(editorial and technical)

 

 

 

Republic of Korea

 

 

 

 

 

Netherlands

X

 

 

 

 

Norway

 

X

(editorial)

 

 

 

United Kingdom

 

 

X

X

 

United States

X

 

 

 

 

 

 

According to the JTC 1 Directives, Section 9.4.3

 

Consideration of successive CD/PDAM/PDISP/PDTRs (types 2 and 3) shall continue until the substantial support of the P-members of the committee has been obtained or a decision to abandon or defer the project has been reached.

 

 

 

 

 

 

 

 

 

SC 34 National Body Comments on N 216

 

Canada

 

(1) I suspect Annex C has a typo "CICAGO" perhaps is supposed to be "CHICAGO" in the example

 

(2) the table in Annex E includes entries indicated with "c" yet not defined in the legend; also, the use and utility of the table could be explained in an introductory paragraph or two

 

(3) the use and utility of the table could be explained in an introductory paragraph or two

 

Japan

 

1. In the headings of Annex B, C, D, E and F, there should be the indication of "Informative".

2. In 12.6.28.5, 12.6.28.6, 12.6.28.7, "disply" should be replaced with "display".

3. In Annex C, just before example, the incorrect tagging <P< P> should be replaced with <P>.

4. In clause 3. and 4. of Annex B, each unordered list item should be added with some explanations.

5. In Annex D, the Grove Plan and SGML Property Set should be added with some explanations.

6. In Annex E, the large table should be split into several parts for rendering on pages of ISO documents.

7. In Annex F, types and relational characteristics should be clarified in the table. The descriptions "<unknown>" should be "unknown".

 

Norway

 

The language throughout this PDAM is in need of editing, with respect to both grammar and orthography. The text should not be added to the standard without having been edited.

Annex B:

                     Why is the 'quantity' type introduced? its place in the numeric tower (see section 6.2.1 of R5RS) needs to be made clear. also, the   relationship, if any, of the 'length' type with the rest of the    numeric types must also be made clear.  it is very important that  the relationship between the numeric types as defined in R5RS is   retained in DSSSL, and that extensions fit cleanly in with the existing types.

                     why is a separate 'language' type needed? what is the difference  between instances of this type, and instances of the 'symbol' type? The same applies to the 'style' and 'address' types.

                     'culumn-set-model' should be 'column-set-model'

Annex C:

                     'CICAGO' should be 'CHICAGO'

                     'VIRTICAL ahould be 'VERTICAL'