ISO/IEC JTC 1/SC 34N0622
ISO/IEC JTC 1/SC 34
Information Technology --
Document Description and Processing Languages
|TITLE:||Summary of Voting on JTC 1/SC 34 N 599 - PDTR 9573-13: Maths and scientific character sets|
|PROJECT:||PDTR 9573-13:2004 (type 3) 2nd Edition: Information technology -- SGML support facilities -- Techniques for using SGML -- Part 13: Public entity sets for SGML -- for mathematics and science|
|PROJECT EDITOR:||Dr. David P. Carlisle|
|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 strongly consider disapproved votes. Please advise the Secretariat regarding (1) the change to status 30.92, 30.98 or 30.99, and (2) the next project status and anticipated date that project status will change.|
|DISTRIBUTION:||SC34 and Liaisons|
|REFER TO:||N0599b - 2005-02-24 - Ballot due 2005-05-24 PDTR 9573-13: Maths and scientific character sets
N0599 - 2005-02-24 - PDTR 9573-13: Maths and scientific character sets
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]
|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|
ABSTENTION for lack of experts.
(1.1) The scope should make clear that this DTR is applicable to XML or not. In particular, will this TR provide entity declarations using SDATA entities?
(1.2) Since different entity sets assign different UCS code values to the same names, it may well be too late to resolve such conflicts.
(2.1) The first para in Section 4:
This is not a standard but rather a TR.
(2.2) The first para in 4.2:
First, there is no one-to-one replationship between characters and glyphs. Some characters in 10646 do not have glyphs. Other characters have different glyphs depending on combining characters.
Second, this subsection merely expand parsed entities by replacing them with numeric character references. Since this expansion is a standard behaviof of SGML or XML processors, we do not understand why this subsection is present.
Needs to be aligned with SC2 chagnes to USC character set.