Alex Brown on the ODF Zero Interop problem: The discussion to limit the use of Foreign elem... - 0 views
-
So I think users need to understand, very clearly, that an ODF
document/app of *either* conformance class has an EXTREMELY WEAK CLAIM
TO INTEROPERABILITY. The "pure ODF conformance" sticker would be at best
valueless and at worst positively misleading.
So what I'd like to see is some real effort from the TC going into
resolving this problem ...
-
So I think users need to understand, very clearly, that an ODF
document/app of *either* conformance class has an EXTREMELY WEAK CLAIM
TO INTEROPERABILITY. The "pure ODF conformance" sticker would be at best
valueless and at worst positively misleading.
So what I'd like to see is some real effort from the TC going into
resolving this problem ... Alex Brown
What Alex fails to mention is that the "foreign elements and alien attributes" components in the ODF Section 1.5 "Compliance and Conformance" clause was originally put there in early 2003 to provide a compatibility layer for MSOffice binary documents. Without this clause, it would be impossible to convert the billions of legacy MSOffice binary documents to ODF without breaking the fidelity. Now th OASIS ODF TC wants to limit the use of the compatiblity clause. An action that would seriously cripple Microsoft's efforts to implement ODF in MSOffice 14.
No surprises here. It was only a matter of time until IBM and Sun ganged up on the newest TC member, Microsoft. -
So I think users need to understand, very clearly, that an ODF
document/app of *either* conformance class has an EXTREMELY WEAK CLAIM
TO INTEROPERABILITY. The "pure ODF conformance" sticker would be at best
valueless and at worst positively misleading.
So what I'd like to see is some real effort from the TC going into
resolving this problem ... Alex Brown
What Alex fails to mention is that the "foreign elements and alien attributes" components in the ODF Section 1.5 "Compliance and Conformance" clause was originally put there in early 2003 to provide a compatibility layer for MSOffice binary documents. Without this clause, it would be impossible to convert the billions of legacy MSOffice binary documents to ODF without breaking the fidelity. Now th OASIS ODF TC wants to limit the use of the compatiblity clause. An action that would seriously cripple Microsoft's efforts to implement ODF in MSOffice 14.
No surprises here. It was only a matter of time until IBM and Sun ganged up on the newest TC member, Microsoft.
I cannot see how SC34 will be able to play any part in this - besides rubber-stamping ODF 1.2 when it comes our way.