ECMA's Office Open XML (OOXML) Specifications

ISO Korean Member Body's Commnets

It's refered by http://www.dis29500.org/.
Comment ID Country Clause Paragraph Type Comments Proposed Change
KR-0001 KR All   ge Harmonization:
DIS 29500 does not have any specifications to ensure interoperability for ISO/IEC 26300 approved asthe international standard to exchange office documents without any limitations. If DIS 29500 is approved without securing interoperability, it would give confusion to both a market and users
DIS 29500 should provide a faithful interoperability for ISO/IEC 26300(ODF) not by plug-in translators but by DIS 29500 itself, as it does for the legacy binary format.
KR-0002 KR     te Platform dependency:
DIS 29500 lacks supports for other platforms and browsers. It restricts the use of Linux platform and browsers such as FireFox, Opera and Safari
DIS 29500 should support various platforms and browsers such as Linux, FireFox, Opera and Safari
KR-0003 KR Part 1, 15.2.14   te DEVMODE structure lacks cross-platform adaptability as print settings be stored in a platform specific binary format DIS 29500 should support various platforms and browsers such as Linux, FireFox, Opera and Safari
KR-0004 KR Part 4, 2.15.2.32   te ‘optimizeForBrowser’ element of WordProcessingML is defined in a way which ignores the existing browsers other than IE. For example, Firefox, Safari, Opera are not supported and all settings will be disabled in these browsers DIS 29500 should support various platforms and browsers such as Linux, FireFox, Opera and Safari
KR-0005 KR Part 4, 6.4.3.1   te The ‘Clipboard Format Type’ allowed in this element are all Windows-platform formats; Bitmap(Bitmap), Pict(EMF), PictOld(WMF), PictPrint(Printer Picture). PNG format used in Linux platform is not allowed DIS 29500 should support various platforms and browsers such as Linux, FireFox, Opera and Safari
KR-0006 KR     te Insufficient information for legacy application behaviours:
Many elements in DIS 29500 mimic legacy application behaviours However, the draft does not contain sufficient details on how to replicate these behaviours
The details of application behaviours should be described in Part 5.11 ,’Application-Defined Extension Elements”
KR-0007 KR Part 4, 2.15.3.26   te footnoteLayoutLikeWW8 :  unknown application behaviour The details of application behaviours should be described in Part 5.11 ,’Application-Defined Extension Elements”
KR-0008 KR Part 4, 2.15.3.31   te lineWraplikeWord6 : unknown application behaviour The details of application behaviours should be described in Part 5.11 ,’Application-Defined Extension Elements”
KR-0009 KR Part 4, 2.15.3.32   te mwSmallCaps : unknown application behaviour The details of application behaviours should be described in Part 5.11 ,’Application-Defined Extension Elements”
KR-0010 KR Part 4, 2.15.3.41   te shapeLayoutLikeWW8 : unknown application behaviour The details of application behaviours should be described in Part 5.11 ,’Application-Defined Extension Elements”
KR-0011 KR Part 4, 2.15.3.53   te truncateFontHeightsLikeWP6 : unknown application behaviour The details of application behaviours should be described in Part 5.11 ,’Application-Defined Extension Elements”
KR-0012 KR Part 4, 2.15.3.54   te uiCompat97To2003 : unknown application behaviour The details of application behaviours should be described in Part 5.11 ,’Application-Defined Extension Elements”
KR-0013 KR Part 4, 2.15.3.6   te autoSpaceLikeWord95 : unknown application behaviour The details of application behaviours should be described in Part 5.11 ,’Application-Defined Extension Elements”
KR-0014 KR Part 4, 2.15.3.63   te useWord2002TableStyleRles : unknown application behaviour The details of application behaviours should be described in Part 5.11 ,’Application-Defined Extension Elements”
KR-0015 KR Part 4, 2.15.3.64   te useWord97LineBreakRules : unknown application behaviour The details of application behaviours should be described in Part 5.11 ,’Application-Defined Extension Elements”
KR-0016 KR Part 4, 2.15.3.65   te wpJustification : unknown application behaviour The details of application behaviours should be described in Part 5.11 ,’Application-Defined Extension Elements”
KR-0017 KR Part 4, 2.15.3.66   te wpSpaceWidth : unknown application behaviour The details of application behaviours should be described in Part 5.11 ,’Application-Defined Extension Elements”
KR-0018 KR     te Re-use of the existing standards:
DIS 29500 incorporates very little of existing standards. Instead, it demands to use the specific vendor’s proprietary and the legacy formats, even though the relevant standards exist. Approving DIS 29500 would result in reinventing the wheel for the existing standards giving inconvenience to users
DIS 29500 should use the existing standards and remove  VML and DrawingML
KR-0019 KR Part 4, 3.17.4.1   te Date Representation : it conflicts with ISO 8601 DIS 29500 should use the existing standards and remove  VML and DrawingML
KR-0020 KR Part 4, 2.18.52   te ST_LangCode : it conflicts with ISO 639 DIS 29500 should use the existing standards and remove  VML and DrawingML
KR-0021 KR Part 4, 6.2.3.17   te ST_OLELinkType : It uses Enhanced metafile instead of ISO/IEC 8632 DIS 29500 should use the existing standards and remove  VML and DrawingML
KR-0022 KR Part 4, 6.4.3.1   te ST_OLELinkType : It uses windows metafile instead of ISO/IEC 8632 DIS 29500 should use the existing standards and remove  VML and DrawingML
KR-0023 KR Part 4, 5   te DrawingML Reference Material : it conflicts with W3C SVG DIS 29500 should use the existing standards and remove  VML and DrawingML
KR-0024 KR Part 4, 2.15.1.28   te documentProtection :The element does not adopt the existing standards such as ISO/IEC 10118-3, W3C XML-ENC but it defines new hashing algorithms DIS 29500 should use the existing standards and remove  VML and DrawingML
KR-0025 KR Part 4, 4.6.1   te Anim(Animate): it contradicts with W3C SMIL(Synchronized Multimedia Integration Language) DIS 29500 should use the existing standards and remove  VML and DrawingML