Template for comments and secretariat observations – DIS 29500 (OOXML) Date: 2007-08-31 Document:
 
1 2 (3) 4 5 (6) (7)
MB1 
Clause No./ 
Subclause No./ 
Annex 
(e.g. 3.1)
Paragraph/ 
Figure/Table/Note 
(e.g. Table 1)
Type of com-ment2 Comment (justification for change) by the MB Proposed change by the MB Secretariat observations 
on each comment submitted

IE Various.  See Proposed Change for detail.   te The DIS refers to a large number of additional technical specifications which are not explicitly listed as Normative References.  Under JTC1 directives, any normative references that are not International standards must either come from an Approved Referencing Organization (ARO), or must be accompanied by a Referencing Explanatory Report (RER). Note that as of January 2007, W3C is an ARO. The following references (taken from each part of the specification's bibliography) should be defined in the relevant section’s list of Normative References.  Should the specification change to no longer require specific normative references then they shall be removed from this list.

All ISO references and W3C and Unicode Consortium references can be directly moved - the latter two coming from Approved Referencing Organisations (ARO).

In addition, RER descriptions should be prepared for specifications originated by IANA, IETF and Dublin Core and they should be moved to Normative References. Similarly, specifications such as PANOSE by Hewlett Packard, ZIP format by PKWARE, Inc are one of the few vendor-dependant specifications. 

Note:

Tags of Dublin Core are used in Core Properties (See " 10.1 Core Properties Part " in "Part 2: Open Packaging Conventions"). PANOSE can be specified as Font Substitution Data of WordprocessingML (eg. <w:panose1 w:val="020B0A04020102020204" />). (See "2.8.2. 13panose1 (Pansose-1 Typeface Classification Number) " in " Part 4: Markup Language Reference"). 

ZIP format in OOXML specification is explained in "physical mapping to a ZIP archive" and used in Office products. (See "9.2 Mapping to a ZIP Archive" in " Part 2: Open Packaging Conventions ").  ZIP may be satisfactorily addressed by reference to the relevant URL. 

<< Part 1: Fundamentals >>

Annex A. Bibliography 

[IANA]

- Character Sets from IANA, as specified at http://www.iana.org/assignments/character-sets 

[IETF]

- RFC 2119, Bradner, Scott, 1997: "Key words for use in RFCs to Indicate Requirement Levels." http://www.ietf.org/rfc/rfc2119.txt.

- RFC 2045, Borenstein, N., and N. Freed. "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies.

" The Internet Society. 1996. http://www.rfc-editor.org

- RFC 2616, Berners-Lee, T., R. Fielding, H. Frystyk, J. Gettys, P. Leach, L. Masinter, and J. Mogul. "Hypertext Transfer Protocol-HTTP/1.1." The Internet Society. 1999. http://www.rfc-editor.org

- RFC 3066, Alvestrand, H. "Tags for the Identification of Languages." The Internet Society. 2001.http://www.rfc-editor.org

- RFC 3339, Klyne, G. and C. Newman "Date and Time on the Internet: Timestamps." The Internet Society. 2002. http://www.rfc-editor.org

- RFC 3629, Yergeau, F. "UTF-8, a transformation format of ISO 10646." The Internet Society. 2003. http://www.rfc-editor.org

- RFC 3986, Berners-Lee, T., R. Fielding, and L. Masinter. "Uniform Resource Identifier (URI): Generic Syntax." The Internet Society. 2005. http://www.rfc-editor.org 

[Unicode Consortium]

- The Unicode Consortium. The Unicode Standard, Version 5.0, defined by: The Unicode Standard, Version 5.0 (Reading, MA, Addison-Wesley, 2006. ISBN 0-321-48091-0). 

[W3C]

- XML, Bray, Tim, Eve Maler, Jean Paoli, C. M. Sperberg-McQueen, and Fran?ois Yergeau (editors). "Extensible Markup Language (XML) 1.0," Third Edition. World Wide Web Consortium. 2004.  http://www.w3.org/TR/2004/REC-xml-20040204/xml11-20040204/)

- XML Base, Marsh, Jonathan. "XML Base." World Wide Web Consortium. 2001.  http://www.w3.org/TR/2001/REC-xmlbase-20010627/

- XML Namespaces, Bray, Tim, Dave Hollander, Andrew Layman, and Richard Tobin (editors). "Namespaces in XML 1.1." World Wide Web Consortium. 2004. http://www.w3.org/TR/2004/REC-xml-names11-20040204/

- XML Path Language Specification, Version 1.0, W3C Recommendation 16 November 1999 http://www.w3.org/TR/xpath

- XML Schema Part 0: Primer Second Edition, W3C R 1 ecommendation 28 October 2004 http://www.w3.org/TR/xmlschema-0/

- XML Schema Part 1: Structures Second Edition, W3C Recommendation 28 October 2004 http://www.w3.org/TR/xmlschema-1/

- XML Schema Part 2: Datatypes Second Edition, W3C Recommendation 28 October 2004 http://www.w3.org/TR/xmlschema-2/ 

[Vender Specification]

- PANOSE Classification Guide, Version 1.2, Hewlett Packard Co., 1992. (Hewlett Packard)

- ZIP File Format Specification from PKWARE, Inc., as specified in appnote, the Application Note on the Zip file format, at http://www.pkware.com.(PKWARE, Inc) 

<< Part 2: Open Packaging Conventions >>

Annex I. Bibliography 

[ISO]

- ISO/IEC Directives Part 2, Rules for the structure and drafting of International Standards, Fourth edition, 2001, ISBN 92-67-01070-0.  

[Unicode Consortium]

- The Unicode Consortium. The Unicode Standard, Version 5.0, defined by: The Unicode Standard, Version 5.0 (Reading, MA, Addison-Wesley, 2006. ISBN 0-321-48091-0) 

[Dublin Core]

- Dublin Core Element Set v1.1. http://purl.org/dc/elements/1.1/

- Dublin Core Terms Namespace. http://purl.org/dc/terms/ 

[W3C ]

- Extensible Markup Language (XML) 1.0 (Third Edition), W3C Recommendation, 04 February 2004.

- Namespaces in XML 1.1, W3C Recommendation, 4 February 2004.

- W3C NOTE 19980827, Date and Time Formats, Wicksteed, Charles, and Misha Wolf, 1997, http://www.w3.org/TR/1998/NOTE-datetime-19980827.

- XML Base, W3C Recommendation, 27 June 2001.

- XML Path Language (XPath), Version 1.0, W3C Recommendation, 16 November 1999.

- XML Schema Part 1: Structures, W3C Recommendation, 28 October 2004.

- XML Schema Part 2: Datatypes, W3C Recommendation, 28 October 2004.

- XML-Signature Syntax and Processing, W3C Recommendation, 12 February 2002.  

[IETF]

- RFC 2616 Hypertext Transfer Protocol-HTTP/1.1, The Internet Society, Berners-Lee, T., R. Fielding, H. Frystyk, J. Gettys, P.Leach, L. Masinter, and J. Mogul, 1999, http://www.rfc-editor.org.

- RFC 3986 Uniform Resource Identifier (URI): Generic Syntax, The Internet Society, Berners-Lee, T., R. Fielding, and L. Masinter, 2005, http://www.rfc-editor.org.

- RFC 3987 Internationalized Resource Identifiers (IRIs), The Internet Society, Duerst, M. and M. Suignard, 2005,  
http://www.rfc-editor.org.

- RFC 4234 Augmented BNF for Syntax Specifications: ABNF, The Internet Society, Crocker, D., (editor), 2005, 21  
http://www.rfc-editor.org.
 

[Vender Specification]

- ZIP File Format Specification, Version 6.2.1, PKWARE Inc., 2005. (PKWARE, Inc) 

<< Part 3: Primer >>

Bibliography N/A 

<< Part 4: Markup Language Reference >>

Bibliography N/A 

<< Part 5: Markup Compatibility and Extensibility >>

Annex B. Bibliography 

[ISO]

- ISO/IEC 197575-4, Information technology - Document Schema Definition Languages (DSDL) - Part 4: Namespace-based Validation Dispatching Language (NVDL).

- ISO/IEC Directives Part 2, Rules for the structure and drafting of International Standards, Fourth edition, 2001, ISBN 92-67-01070-0.  

[W3C]

- Extensible Markup Language (XML) 1.0 (Fourth Edition), W3C Recommendation, 16 August 2006.

- Namespaces in XML 1.0 (Second Edition), W3C Recommendation, 16 August 2006. 

- XML Base, W3C Recommendation, 27 June 2001.

- XML Schema Part 1: Structures Second Edition, W3C Recommendation, 28 October 2004.

- XML Schema Part 2: Datatypes Second Edition, W3C Recommendation, 28 October 2004.

 
IE Part 4, Section 3.17.4   te The DIS specifies that dates are represented using a “non-negative numeric serial value”, and provides for two possible date bases for those serial values (1900 and 1904). 

The result of this is that pre-1900 dates cannot be represented in a strongly-typed way, for example a typical spreadsheet application will treat pre-1900 dates as a string rather than a date, and so will be unable to perform date-related calculations on such data. 

The Irish NB believes that allowing pre-1900 dates in a strongly typed way is a use case that should be supported.

The specification could be changed in two ways to support strongly-typed pre-1900 dates: by allowing the use of negative serial values; or by the use of ISO 8601.  Each of these approaches should be  carefully considered.  
IE Part 4, Section 3.17.4, Section 3.17.6.7   te The DIS provides for two schemes to represent dates (the 1900 and 1904 date base systems), both based on an integer serial value. The Irish NB believes that allowing ISO 8601 dates to have the same standing as the integer date format. (i.e. strongly typed) may be useful. The editor should consider changing the specification to allow ISO 8601 dates have the same standing as the integer date format.  
IE Part 4, Section 2.18.51   te The ST_Lang (Language Reference) type allows language to be specified by either a hexadecimal language code (ST_LangCode) or by an ISO 639-1 letter code. The editor should consider adding a note in the specification deprecating ST_LangCode.  
IE Part 4, Section 3.17.7   ed The definitions of some formulae in this section reflect current spreadsheet semantics and may not match common practice.  New functions may need to be defined that provide alternative semantics to the formulae in the current specification where these new functions will reflect common understanding of those formulae. The editor should add an informativel note to the specification stating that the current formulae reflect current spreadsheet semantics and may not match common practice.  
IE Part 4, Section 3.17.7.48 Table “Liquid Measure”, p2575 te Some units of measure allowed as arguments to the CONVERT function are under-defined.  Traditional liquid measures such as “cup” and “tablespoon” vary from country to country.  The DIS does not specify which version is assumed. The specification should define the units of measurement for arguments to the CONVERT function.  
IE Part 4, Section 3.17.7   ed For the trigonometric functions, SIN (Part 4, Section 3.17.7.287), COS (Part 4, Section 3.17.7.50) and TAN (Part 4, Section 3.17.7.313), the specification fails to state whether their arguments should express angles in radians or degrees. A similar problem exists for the return value of the inverse functions, ASIN (Part 4, Section 3.17.7.12), ACOS (Part 4, Section 3.17.7.4), ATAN (Part 4, Section 3.17.7.14), and ATAN2 (Part 4, Section 3.17.7.15). The specification should be changed to declare the use of radians for arguments to these functions.  
IE Part 4, Section 3.17.7   te Many of the financial functions (e.g. ACCRINT Part 4, Section 3.17.7.2) depend on a "day count basis" flag, to denote use of US (NASD) 30/360, Actual/Actual, Actual/360, Actual/365, European 30/360. These represent various conventions for how days and months are counted.  However, the DIS does not define these conventions, nor does it point to an authority for their definition. The specification should be changed to define the day count basis for financial functions.  
IE Part 4, Section 6   te This section describes VML, which “should be considered a deprecated format included in Office Open XML for legacy reasons only”.  Deprecated material in a new ISO/IEC standard is considered problematic. Normative text regarding deprecated material is considered to be problematic; this matter should be addressed.  
IE Part 4, Section 2.15.3   te This section defines Compatibility Settings used to preserve visual fidelity of documents created in earlier word processing applications.  For several of the listed elements the semantics are insufficiently defined, and the following guidance is given:  ““To faithfully replicate this behavior, applications must imitate the behavior of that application, which involves many possible behaviors and cannot be faithfully placed into narrative for this Office Open XML Standard. If applications wish to match this behavior, they must utilize and duplicate the output of those applications.”

For example “autoSpaceLikeWord95” (Section 2.15.3.6), “footnoteLayoutLikeWW8” (Section 2.15.3.26), and “useWord97LineBreakRules” (Section 2.15.3.64).

The specification should be changed to define the semantics of those tags for which definitions can be supported.  For those which cannot ber defined, a specific note should be added outlining this issue and noting that under different implementations different behaviours may be exhibited  
IE Part 4, various   ed There are syntax errors in various informative examples of XML throughout the DIS. The specification should change to correct syntax errors in examples.  
IE Part 4, Section 3.17.7.65   ed The description of the CUBEKPIMEMBER function specifies that it retrieves an OLAP Cube from a “SQL Server”. The description of the CUBEKPIMEMBER function should be changed to allow any OLAP Cube implementation. Additionally, the examples should be improved to illustrate the return values.  
             

MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **)

2 Type of comment: ge = general te = technical  ed = editorial

NOTE Columns 1, 2, 4, 5 are compulsory.

page of 10

ISO electronic balloting commenting template/version 2001-10


Top