South Korea - KATS

Harmonization:

DIS 29500 does not have any specifications to ensure interoperability for ISO/IEC 26300 approved as the 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.

 

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

 

Part 1, 15.2.14

 

DEVMODE structure lacks cross-platform adaptability as print settings be stored in a platform specific binary format

 

Part 4, 2.15.2.32

 

"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

 

 

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

 

Part 4, 2.15.3.26

 

footnoteLayoutLikeWW8 : unknown application behaviour

 

Part 4, 2.15.3.31

 

lineWraplikeWord6 : unknown application behaviour

 

Part 4, 2.15.3.32

 

mwSmallCaps : unknown application behaviour

 

Part 4, 2.15.3.41

 

shapeLayoutLikeWW8 : unknown application behaviour

 

Part 4, 2.15.3.53

 

truncateFontHeightsLikeWP6 : unknown application behaviour

 

Part 4, 2.15.3.54

 

uiCompat97To2003 : unknown application behaviour

 

Part 4, 2.15.3.6

 

autoSpaceLikeWord95 : unknown application behaviour

 

Part 4, 2.15.3.63

 

useWord2002TableStyleRles : unknown application behaviour

 

Part 4, 2.15.3.64

 

useWord97LineBreakRules : unknown application behaviour

 

Part 4, 2.15.3.65

 

wpJustification : unknown application behaviour

 

The details of application behaviours should be described in Part 5.11 , "Application-Defined Extension Elements €

 

 

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

 

Part 4, 3.17.4.1

 

Date Representation : it conflicts with ISO 8601

 

Part 4, 2.18.52

 

ST_LangCode : it conflicts with ISO 639

 

Part 4, 6.2.3.17

 

ST_OLELinkType : It uses Enhanced metafile instead of ISO/IEC 8632

 

Part 4, 6.4.3.1

 

ST_OLELinkType : It uses windows metafile instead of ISO/IEC 8632

 

Part 4, 5

 

DrawingML Reference Material : it conflicts with W3C SVG

 

Part 4, 2.15.1.28

 

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

 

 

Harmonization:

DIS 29500 does not have any specifications to ensure interoperability for ISO/IEC 26300 approved as the 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.

 

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

 

Part 1, 15.2.14

 

DEVMODE structure lacks cross-platform adaptability as print settings be stored in a platform specific binary format

 

Part 4, 2.15.2.32

 

"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

 

 

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

 

Part 4, 2.15.3.26

 

footnoteLayoutLikeWW8 : unknown application behaviour

 

Part 4, 2.15.3.31

 

lineWraplikeWord6 : unknown application behaviour

 

Part 4, 2.15.3.32

 

mwSmallCaps : unknown application behaviour

 

Part 4, 2.15.3.41

 

shapeLayoutLikeWW8 : unknown application behaviour

 

Part 4, 2.15.3.53

 

truncateFontHeightsLikeWP6 : unknown application behaviour

 

Part 4, 2.15.3.54

 

uiCompat97To2003 : unknown application behaviour

 

Part 4, 2.15.3.6

 

autoSpaceLikeWord95 : unknown application behaviour

 

Part 4, 2.15.3.63

 

useWord2002TableStyleRles : unknown application behaviour

 

Part 4, 2.15.3.64

 

useWord97LineBreakRules : unknown application behaviour

 

Part 4, 2.15.3.65

 

wpJustification : unknown application behaviour

 

The details of application behaviours should be described in Part 5.11 , "Application-Defined Extension Elements €

 

 

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

 

Part 4, 3.17.4.1

 

Date Representation : it conflicts with ISO 8601

 

Part 4, 2.18.52

 

ST_LangCode : it conflicts with ISO 639

 

Part 4, 6.2.3.17

 

ST_OLELinkType : It uses Enhanced metafile instead of ISO/IEC 8632

 

Part 4, 6.4.3.1

 

ST_OLELinkType : It uses windows metafile instead of ISO/IEC 8632

 

Part 4, 5

 

DrawingML Reference Material : it conflicts with W3C SVG

 

Part 4, 2.15.1.28

 

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