Template for comments and secretariat observations Date: Document: ISO/IEC DIS 29500

Transcription

1 Templa for s and secretariat observations Da: Document: ISO/IEC DIS (3) 4 5 (6) (7) on each submitd CH Results the Comments Resolution Meeting ( August 007) Version August 007 The following table displays the results the s resolution meeting for the DIS 9500 ballot held on August 007. The document has been derived from the nos taken during the meeting, and contained in original form in document CRM_Outcome.pdf, posd on Livelink in UK14 folder 0 (DIS9500 CRM sub-folder). Colored type is used as follows: Text for submission to ISO in black type (quos " ": Text for inclusion into the DIS 9500). Original xt as submitd by the member but not for submission to ISO in gray type. This may occur either because the was rejecd, or another xt was deemed preferable. Conclusions not for submission to ISO in red type Text to be replaced in the next document version in green type Text for submission to ISO has been worded suitably. Conclusions have been worded and enhanced to be understandable by those not at-nding the meeting. Hereby, the aim was not to change the meaning. Those who did atnd the meeting are kindly asked to compare this document with the orig-inal xt in CRM_Outcome.pdf and to advise me any perceived change meaning or any inconsisncy with that document. Corrections and proposals for improvement the wording are as well welcome. 1 MB = Member body (enr the ISO 3166 two-letr country code, e.g. CN for China; s from the ISO/CS editing unit are identified by **) : ge = general = chnical ed = editorial NOTE Columns 1,, 4, 5 are compulsory. ISO electronic balloting ing mpla/version page 1 8

2 Templa for s and secretariat observations Da: Document: ISO/IEC DIS (3) 4 5 (6) (7) on each submitd Conclusions are the following types: Justified by JTC1 directives: It is justifiable by the JTC1 directives to issue the to ISO. Not admissible: JTC1 directives forbid the issuance this to ISO. Established: A claim has been established by the claimant, and the pro has been accepd in the meeting. Rejecd: A claim has been rejecd in the meeting. Accepd: A has been accepd. Acknowledged: A has been accepd that a has some truth, though the was not formally accepd as a whole and as worded. Withdrawn: The submitr withdraw the. CH Part 1, introduction (page xii) and entire document ed It is not acceptable for an inrnational standard to be designed primarily around the goal compatibility with a particular company's products. Justified by JTC1 Directives section 1. Inroperability, I Inroperability Policy. Established: DIS 950 is relad to MS file formats. Established: It is common JTC1 practice to issue standards imperfect inroperability, such as JPEG1, JPEG000. Established: Major Swiss users accept OOXML for its improved inroperability. Rejecd: Based on the preceding claims established, it was rejecd that it should not be acceptable OOXML to be primarily targeting MS file formats. The is not admissible by JTC1 Directives sec- 1 MB = Member body (enr the ISO 3166 two-letr country code, e.g. CN for China; s from the ISO/CS editing unit are identified by **) : ge = general = chnical ed = editorial NOTE Columns 1,, 4, 5 are compulsory. ISO electronic balloting ing mpla/version Change the goal from being fully compatible with existing investments in Microst Office documents to seeking at attain the same high level compatibility not only with Microst's formats, but also with the inrnational norm ISO/IEC 6300 (OpenDocument). Review the entire draft standard and modify it corresponding to this revised goal. Add to introduction: "Atntion is drawn to DIN document (MS to provide reference) regarding mapping between OXML and ISO " page 8

3 Templa for s and secretariat observations Da: Document: ISO/IEC DIS (3) 4 5 (6) (7) on each submitd tion 13.4, as clearly being a contradiction to be addressed during the review period, no longer applicable during the 5-month ballot. This is particularly inappropria where, as in the pre-sent case, compatibility with an existing inrnational standard is neglecd in favor the one-sided goal maximal compatibility with document file formats intro-duced by one company, and where the proposed stan-dard does not provide equal opportunities for compatibil-ity to that company's present and future competitors. Rejcd, as not justified by JTC1 Directives and practice. Unless this shortcoming DIS 9500 is fixed, accepting this specification as a national or inrnational standard would be a violation Swiss and inrnational law. DIS9500, which is relad to Microst file formats, does not explain the mapping to ODF. CH Entire document ge Microst's Open Specification Promise is explicitly restricd to only the required portions the Covered Specification (emphasis added). While this promise may be valuable with regard to specifications that de-clare all the important functionality as required and only unimportant additions as optional, in DIS 9500 sections.4,.5 and.6 clearly (and in fact appropri-aly) describe most the functionality provided by DIS 9500 as optional rather than required for a conforming implementation. Microst should publish a stronger open specification promise which is not limid to only the required portions covered specifications. Established: MS is fering at least RAND conditions. Rejecd: The claim that MS failed to provide the pant information was rejecd. CH Entire document ge There is at least legal uncertainty about whether Microst's Open Specification Promise is compatible with the GNU LGPL license under which OpenOffice, Microst should, in addition to the open specification promise, make any relevant pants it controls available under a license which is clearly 1 MB = Member body (enr the ISO 3166 two-letr country code, e.g. CN for China; s from the ISO/CS editing unit are identified by **) : ge = general = chnical ed = editorial NOTE Columns 1,, 4, 5 are compulsory. ISO electronic balloting ing mpla/version page 3 8

4 Templa for s and secretariat observations Da: Document: ISO/IEC DIS (3) 4 5 (6) (7) on each submitd Rejecd as JTC1 Directives do not require GNU LGPL compatibility. Not admissible: Licensing compliance is not in UK14's authority, but only in ITTF's. Contradictions regarding licencing must be addressed in the review period and are no longer admissible during the 5-month ballot. which is currently the primary competitor to Microst's fice stware, is licensed. Richard Stallman, the au-thor the GPL and LGPL licenses, has publicly stad that relying on Microst's promise (this presumes ac-cepting Microst's pants as valid) would viola the GPL (see ). Stallman's remarks apply equally to the LGPL, the relevant provisions which are identical to those in the GPL. Microst's websi addresses the question the GPL compatibility the Open Specifi-cation Promise by refusing to take position on this question, stating only that the GPL is not universally in-rpred the same way by everyone and based on feedback from the open source community we believe that a broad audience developers can implement the specification(s). While it is certainly true that free st-ware and open source licenses exist which are compati-ble with Microst's promise, the primary question is whether DIS 9500 can be implemend in derivative works the LGPL-licensed OpenOffice stware. It is not fair if only Microst can implement the standard di-rectly in their fice stware while competitors have to use a different format inrnally and must rely on docu-ment format conversion utilities. CH Part ed There are many normative references to the ZIP file format specification, but no actual such specification is included and no explicit reference to any such exrnal document is provided. compatible with GPL and LGPL. Provide a detailed specification for the ZIP format or provide a normative reference to a specification which must itself be an open standard 1 MB = Member body (enr the ISO 3166 two-letr country code, e.g. CN for China; s from the ISO/CS editing unit are identified by **) : ge = general = chnical ed = editorial NOTE Columns 1,, 4, 5 are compulsory. ISO electronic balloting ing mpla/version page 4 8

5 Templa for s and secretariat observations Da: Document: ISO/IEC DIS (3) 4 5 (6) (7) on each submitd CH Part 3, Part 4, CH Part 4, Accepd Disallowing das before 1900 in spreadsheets is wrong. There are people alive today who were born before Historical studies n consider das before Accepd DIS 9500 specifies that in the year 1900, for das between January 1 and February 8, WEEKDAY shall return a value for the day immedialy prior to the cor-rect day and also assigns a serial value to the non-existing day February 9, This is wrong. Stware bugs should be fixed, not expord by means ISO standards to the programs competitors. Resolve this in the same way as ISO 6300 does. Allow the serial value to be negative in the 1904 baseline sys Make the calendar sysm configurable, with a default the Gregorian calendar, allowing alrnatives to be specified by means providing code for the computation year, month, weekday and day--the-month. This mechanism can then be used for replicating the broken behavior Microst Excel where that is desired. See next CH Part 3, Part 4, Having two different da sysms with different base das side-by-side in the same standard document format makes no sense. Rather, it is appropria to fix a single base da. Applications which use a different base da can convert from the da representation used in the standard document format to the applica-tion's preferred da representation, and vice versa. Dele all references to the 1904 base da sysm. Add the following xt MS to specify the xt position: "Implementors are encouraged to use the 1904 baseline sysm avoiding the 1900 baseline sysm's leap year bug. " Acknowledged. Established: The two base das pose problems. Established: Conversions must 1-t bidirectional conversion. The coexisnce the two baseline sysms causes some problems. CH Part 4, In the inrnet age, it is inappropria to represent times simply as a numeric value without timezone information. Acknowledged In OOXML, time values in cells are represend in UTC Specify that when stored in OOXML files, das and times are always expressed in rms UTC. Add a mechanism for storing in the file information on what timezone should be used to represent the time in human-readable form. 1 MB = Member body (enr the ISO 3166 two-letr country code, e.g. CN for China; s from the ISO/CS editing unit are identified by **) : ge = general = chnical ed = editorial NOTE Columns 1,, 4, 5 are compulsory. ISO electronic balloting ing mpla/version page 5 8

6 Templa for s and secretariat observations Da: Document: ISO/IEC DIS (3) 4 5 (6) (7) on each submitd CH Part 4, CH Part 4,.18.5 not by default. The combined da and time representation is broken in Switzerland and all other locales which switch to daylight-saving time and back, on those days which are 3 hours or 5 hours long insad the usual 4 hours. Acknowledged Having two different language representation sysms, one based on ISO standards and one with arbitrary hexcodes for a subset the languages makes no sense. Applications which use arbitrarily-chosen numeric val-ues to represent some languages can convert from the standard language representation sysm to the codes they use inrnally, and vice versa. Withdrawn, but underlying problem acknowledged. DIS 9500 defines two language codings. CH ge Die Norm wäre nicht aus der vereinn Erfahrung und Expertise aller inressiern Kreise entstanden (z.b. Produzenn, Verkäufer, Käufer, Nut-zer und Regulatoren), sondern nur durch Microst allein. Rejecd CH ge Es existiert bereits die Norm ISO6300, auch Open Document Format (ODF) genannt. Eine doppel Normung erhöht die Kosnbelastung sowohl für uns als Anbier als auch für unsere Kunden. In OOXML, UTC is default for metadata, serial time for cell data. UTC strings can also be placed in cells, or cread using string manipulation functions on other cells. Request to illustra this with some informative examples. Illustra by some informative examples the placement UTC strings in cells, or their crea-tion from other cell data This problem is most easily avoided by always using UTC for the combined da and time representation. Clarify the behaviour on transitions to daylight saving time and back. Dele all references to ST_Langcode. Add the following xt MS to specify the xt position: "Implementors are encouraged to use the ISO-compatible coding." 1 MB = Member body (enr the ISO 3166 two-letr country code, e.g. CN for China; s from the ISO/CS editing unit are identified by **) : ge = general = chnical ed = editorial NOTE Columns 1,, 4, 5 are compulsory. ISO electronic balloting ing mpla/version page 6 8

7 Templa for s and secretariat observations Da: Document: ISO/IEC DIS (3) 4 5 (6) (7) on each submitd see above CH Die Spezifikation verletzt andere ISO Normen, wie zum Beispiel ISO 8601 (Darsllung von Datum und Uhrzeit), ISO 639 (Namenund Landerkürzel) see above oder ISO/IEC (Kryptographischer Hash). Eine Doppelnormung see above in diesem Be-reich hat ebenfalls viele zusätzliche Kosn für uns und unsere Kunden zur Folge. Established: Various popular hash algorithms are foreseen in OOXML, as well as some proprietary ones (see Part 4, ) CH Mehr als 10% der Beispiele in der Spezifikation erfüllen nicht die Anforderungen gültigen XMLs. Acknowledged. There are some editorial and chnical deficiencies present. CH In dem Spezifikationsdokument fehlen Informationen, zum Beispiel über die Bedeutung von Definitionen wie autospacelikeword95 und use-word97linebreakrules. Dies erschwert ebenfalls die Inroperabilität mit unseren Produkn. Established: These definitions are missing. Established: These elements are not required by implementations. Rejecd: Claim that missing definitions cause inroperability problems CH Es besht ein Designfehler in der Definition des Tabellenkalkulationsformats, welcher das Einfügen eines Datums unmöglich macht, das vor dem Jahr 1900 liegt. Dieser Fehler betrifft sowohl die OOXMLSpezifikation als auch StwareProduk wie Microst Excel 000, XP, 003 und 007. Rejecd: Request to discard the proprietary has algorithms No change, as the submitr failed to provide examples. Editorial and chnical corrections are known to be submitd by other countries, and to be welcomed by SC34. No change 1 MB = Member body (enr the ISO 3166 two-letr country code, e.g. CN for China; s from the ISO/CS editing unit are identified by **) : ge = general = chnical ed = editorial NOTE Columns 1,, 4, 5 are compulsory. ISO electronic balloting ing mpla/version page 7 8

8 Templa for s and secretariat observations Da: Document: ISO/IEC DIS (3) 4 5 (6) (7) on each submitd see above CH ge Es existiert keine beleg Implementation der OOXMLSpezifikation. Microst Office 007 unrstützt lediglich ein Derivat von OOXML, aber kein Dokumennformat, welches mit der Spezifikation übereinstimmt. Dies bedeut für uns eine Unsicherheit bezüglich der Inroperabilität mit Microst Office 007 und anderen Produkn, wel-che die Spezifikation erfüllen. Acknowledged that the current version MS Office 007 may not be 100% compliant with DIS CH ge Der vorliegende Standard ist ilweise von Pann betrfen. Eine Implementation ist daher sts mit Kosn für die Lizensierung der Pan ver-bunden und macht eine freie Implementation. des Standards unmöglich. Dies ist nicht im Inresse unserer Kunden. Wir bedanken uns für diese Gelegenheit, unsere Meinung zur ISOStandardisierung von Microst. see above MS aims to be compliant with DIS 9500, and will treat examples the contrary as bugs. UK14 members are encouraged to report such examples to the following link. 1 MB = Member body (enr the ISO 3166 two-letr country code, e.g. CN for China; s from the ISO/CS editing unit are identified by **) : ge = general = chnical ed = editorial NOTE Columns 1,, 4, 5 are compulsory. ISO electronic balloting ing mpla/version page 8 8