Template for comments and secretariat observations



Download 456.43 Kb.
Page1/5
Date conversion09.07.2018
Size456.43 Kb.
  1   2   3   4   5

Template for comments and secretariat observations


Date: 2007-08-30

Document: ISO/IEC DIS 29500




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



DE

Part 1, Section 2.4

line 22


Ed

This line require conformance with “Unicode Standard” without specifying a version. XML 1.0 referred to Unicode 2.0, though the informative Appendix A of OOXML Part 1 lists Unicode 4.0. Which is it?


Although Annex A is informative, to be of any use (i.e. giving valuable information) it should still be consistent with the rest of the document.




DE

Part 1

behavior, implementation-defined

Te

“application-specific”, at least in common standards use, is not the same as application-defined, viz. ANSI C Programming Language


Correct the consistence use of application-defind and application specific




DE

Part 1, Section 9.1.1

-

Ed

ASCII requires a normative reference since there are several national variations.

Suggested reference be made to ISO/IEC 646:1983 or ANSI X3.4-1986




DE

Part 1, Section 9.1.5

-

te

This sub-clause, buried in introductory material, negates a provision of the more detailed OPC specification in Part 2. This will likely be missed by implementors.


If interleaving is not permitted then it should not be described in Part 2




DE

Part 1, Section 10.1.2

line 20

Ed

Reference is made to material in Part 12, Clause 12. Although a clause of that number does exist, it does not contain the material 10.1.2 references it for.

Correct the reference to point to the correct clause.




DE

Part 1, Section 11.3.1

lines 15-17

te

This is requiring that a conforming OOXML consumer also be able to understand a specified list of other document formats, including proprietary ones such as MHTML and RTF, and for conforming producers to understand how to convert these formats to OOXML.

Review the example




DE

Part 1, Section 12.3.5

-

te

This binary part is said to be used for the storage of “arbitrary user-defined data”. No further detail is given as to what user action would trigger the use of this “user-defined” data. Without further definition, no interoperability of this feature is possible.


Clarify definition




DE

Part 1, Section 15.2.6

-

ed

What is meant by “This part shall have no contents”? Does this mean that there shall be nothing in the Zip file with the declared name? Or does it mean that a zero- byte file shall be created with the declared name? Or something else?

Clarify the meaning.




DE

Part 1, Section 15.2.12

-

Ed

There is no reference made to a particular dated version of TrueType or OpenType specifications. And if TrueType and OpenType differ, then there should be different ways to refer to them, rather than calling them both “application/x-font-ttf”

Provide reference to intended specifications for TrueType and OpenType

If they are ISO standards, then give the ISO standard number, else provide a reference according to JTC1 Directives, Annex N, "The Normative Referencing of Specifications other than International Standards in JTC 1 International Standards"






DE

Part 1, Section 15.2.14

-

Te

It is unsatisfactory to store printer settings in OS-dependent binary formats like DEVMODE structures. This is a considerable security concern (DEVMODE structures are loaded directly into device driver memory), as well as lacking cross-platform adaptability. There is also no interoperability with print settings as currently defined.


Default DEVMODE stucture should be XML, optional within binary adressable by a unique identifier.

Or better


Model device settings in XML for interoperability and platform neutrality. In any case, require a datatype or format identification for these settings like a MIME type or XML Namespace, so that a processing application can decide whether and how to interpret that information. Require applications to round-trip unknown device settings.




DE

Part 1, Appendix

-

Ed

The reference given for the Zip format does not provide a date or version, though this specification is frequently revised

pkzip version must be defined




DE

Part 4, Introduction

page vii, line 7

Ed

Full compatibility of the proposed OOXML with any existing application is demonstrably unreachable (because the proposed OOXML explicitly gives up describing parts of what it aims to describe, e.g. Part 4 page 1378 lines 12-17).

Rephrase the compatibility goal so as to make it realistic.




DE

Part 4, Introduction

page vii, line 8

Ed

A standard should not rely on existing applications and brands for its description.


Remove the reference to Microsoft Office.




DE

Part 4, Introduction

page vii, lines 7&8

Ed

The use of 'large' into 'large existing investments in Microsoft Office documents' is a judgment call relying upon unsupported assertions.

Remove 'large'.




DE

Part 4, Section 2.2

page 26, lines 27&28

Te

The definition of 'story' is inappropriate. As far as OOXML documents are concerned, the use of a text editor enables any user to modify (type into) each and any region of any XML subpart of a document.

Clarify the definition of 'story'.

The definition of "Story" is appropriate as it is the region of content (main document, comments, headers, etc.) within a document where user can type/modify information.  






DE

Part 4, Section 2.2.1

page 27, lines 1&2

te

Assuming that background be referring to the background of the document defined by one of its enclosing elements, assuming that the notion of document page and the notion of displaying be properly defined and that their definitions match commonly accepted ones, then the 'This background shall be displayed on all pages of the document, behind all other document content.' sentence makes unclear whether the total surface of a page must be filled with the background, or else how the subpart of the said surface can be determined.


Clarify the definition of 'background'.




DE

Part 4, Section 2.2.1

page 27, lines 8&21

te

Contradicting use of accent3 and accent5.

Clarify the definition of 'background' information




DE

Part4, Section 6.1

page 4343, lines 11&12

te

OOXML states that VML should be considered as deprecated. A new standard should not contain deprecated parts.

VML remains in the standard for compatibility reasons. However, new documents shall not use VML. VML shall be used only for backward compatibility reasons to enable the migration of older documents to Open XML. One possibility would be to move VML to a separate section as an informative annex or save as part




DE

Part 4, Section 2.2.1, 2.3.3.19, 2.3.3,

6.1,


6.2,

6.3,


6.4,

6.5

page 28, line 0

page 262, line 1

page 264, line 19

page 805, line 1

page 4753, lines 18&19,

page 4902, lines 8&9,

page 4920, lines 20&21,

page 4958, lines 6&7



te

The reference to the urn:schemas-microsoft-com:vml namespace references VML, which is considered as deprecated (Part 4, page 4343, lines 11&12). A new standard should not contain deprecated parts.

VML remains in the standard for compatibility reasons. However, new documents shall not use VML. VML shall be used only for backward compatibility reasons to enable the migration of older documents to Open XML. One possibility would be to move VML to a separate section as an informative annex or save as part




DE

Part4, Section 6.

pages 4343-4960

te

All subsections of Section 6 describe deprecated only material, making Section 6 deprecated as a whole. A new standard should not contain deprecated parts.

VML remains in the standard for compatibility reasons. However, new documents shall not use VML. VML shall be used only for backward compatibility reasons to enable the migration of older documents to Open XML. One possibility would be to move VML to a separate section as an informative annex or save as part




DE

Part 4, Section 2.2.1

page 28, line 0

te

The reference to the 6.2 subclause references VML, which is considered as deprecated (Part 4, page 4343, lines 11&12). A new standard should not contain deprecated parts.


VML remains in the standard for compatibility reasons. However, new documents shall not use VML. VML shall be used only for backward compatibility reasons to enable the migration of older documents to Open XML. One possibility would be to move VML to a separate section as an informative annex or save as part




DE

Part 4, Section 2.2.1

page 28, line 0

te

Child elements of background are described using deprecated namespaces only. Accordingly, the background element should either be described in terms of current OOXML elements or deprecated.

VML remains in the standard for compatibility reasons. However, new documents shall not use VML. VML shall be used only for backward compatibility reasons to enable the migration of older documents to Open XML. One possibility would be to move VML to a separate section as an informative annex or save as part




DE

Part 4, Section 2.2.1

page 28, line 1

ed

The sentence 'This color may either be presented as a hex value (in RRGGBB format)' does not make proper reference to a well accepted color description system.

The text should be clear which colorspace is intended here.




DE

Part 4, Section 2.2.1

page 28, line 1


ed

The sentence 'or auto to allow a
consumer to automatically determine the background color as appropriate.' does not define the appropriate behavior of the consumer, whereas the definition of the corresponding simple type, found in Part 4, page 1737, explicitly states that 'This value shall be used to specify an automatically determined color value, the meaning of which is interpreted based on the context of the parent XML element.'

Define the characteristics of the auto value for the color attribute of the background element properly.




DE

Part 4, Section 2.2.1

page 28, line 1

ed

The definition of the themeColor attribute references the document's Theme part without properly defining it nor providing an explicit reference to the OOXML section that defines it.

Define the Theme part of a document properly or else add an explicit reference to the section that does so.




DE

Part 4, Section 2.2.1

page 28, line 1


ed

The sentence 'the color resulting from the use of this attribute with any appropriate themeTint and themeShade attribute value calculations applied' somewhat contradicts the first sentence of the definition for themeColor.


So suggested is to rewrite this sentence as: "If the color attribute is specified, its value shall be ignored in favor of the color resulting from the use of the themeColor attribute with any appropriate themeTint and themeShade attribute value calculations applied."




DE

Part 4, Section 2.2.1

page 29, line 0


ed

There are several instances of the word 'border' that are meaningless in this context (the text is supposed to describe the 'background' element at that location).

Clarify which border the text refers to (if any notion of border must be introduced here) or else rewrite the text so that it makes sense.




DE

Part 4, Section 3.17.4

page 2522

te

The proposed date and time system makes no reference to ISO 8601, and is markedly different from it. This is supported by no explicit and acceptable reason. Introducing brand new conventions where established standards exist is costly and brings no value to the public. Moreover, it brings confusion, and compels application implementors to add converters.

Replace the proposed date and time system by ISO 8601.

Proposed resolution: DIS 29500 should be augmented by the possibility to enter other dates and introduce a Boolean variable that indicates how to treat the leap year calculation (Excel already provides this function as a consumer)





DE

Part 4, Section 3.17.4

page 2522, lines 7&8

ed

The 'As dates and times are numeric 8 values, they can take part in arithmetic operations' sentence is misleading, since arithmetics on dates and times is ill-formed except for very narrow cases (mainly duration, with restrictions though).

Explain the relationship between dates, times and calendars and warn that dates arithmetics is misleading, or drop the sentence altogether.




DE

Part 4, Section 3.17.4.1

page 2522, lines 14-18

te

The text proposes a dual date base system. There is no clear advantage to having two slightly different systems, and this brings significant costs and confusion, as illustrated by the need to specify a default base system, etc.

Choose and keep a single date system.

Proposed resolution: DIS 29500 should be augmented by the possibility to enter other dates and introduce a Boolean variable that indicates how to treat the leap year calculation (Excel already provides this function as a consumer)






DE

Part 4, Section 3.17.4.1

page 2522, lines 19


te

The proposed date system does not cope with dates anterior to 1900-01-01.

Propose a better date system.

Proposed resolution: DIS 29500 should be augmented by the possibility to enter other dates and introduce a Boolean variable that indicates how to treat the leap year calculation (Excel already provides this function as a consumer)






DE

Part 4, Section 3.17.4.1

page 2523, lines 1-6

te

The 1900 date base system is bogus, according to the OOXML text itself. A standard should not deliberately include bogus features.

Remove the 1900 date base system or reform it.

Proposed resolution: DIS 29500 should be augmented by the possibility to enter other dates and introduce a Boolean variable that indicates how to treat the leap year calculation (Excel already provides this function as a consumer)






DE

Part 4, Section 3.17.4.1

page 2522, lines 16&18

te

The documented upper limits for serial date times match 9999-12-31 00:00:00, which is most probably not what was intended. The expected upper limits would match 9999-12-31 23:59:59.


It is true that 2,958,465 matches 9999-12-31. But it is false where the text says that this is the upper limit and that, "A serial value outside of the range for its date base system is ill-formed."

Specifically, all hours of 9999-12-31 are allowed, so a serial values of 2,958,465.999999 is also allowed.






DE

Part 4, Section 2.18.51

page 1747, line 18

te

The use of an union for the ST_Lang type only brings extra costs and confusion, and should be replaced by a single representation that leverages the appropriate standards.

In the case of language tags and other such closed lists, DIS29500 should be extended to replace closed lists with open lists that can accept values of existing standards (e.g. ST_Lang should reference BCP47 for language tags). Other closed lists should also be studied to consider opening their values to existing standards.




DE


: doc
doc -> Rosemary is a young woman about twenty-one years old. For a long time she has been engaged to a young man named hernando, and she is coming from a great distance to meet him for their scheduled wedding
doc -> Vernon Lee: a glimpse at her Italian Cultural Circle
doc -> New directions newsletter the domestic abuse shelter of knox county
doc -> As a child Collins studied classical piano with Antonia Brico, making her public debut at age 13 performing Mozart's
doc -> The Archetype
doc -> Straight From the Heart by Dr. Linda Boen
doc -> Early Childhood iPad App Recommendations note
doc -> This romantic story is about two college students, Jenny and Oliver, who meet when Oliver visits the library to buy a book. Although Oliver’s family is poor and Jenny’s is rich, the two young people fall in love


  1   2   3   4   5


The database is protected by copyright ©hestories.info 2017
send message

    Main page