Gary Edwards on 2009-03-09
bingo. kudos to marbux for catching this discussion.
Group annotations on this page
-
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 ...-
Jlundstocholm on 2009-03-22The sad thing is that with the agreement between JTC1 and OASIS regarding ODF, it seems that SC34 has been completely cut out of the loop in terms of "fixing ODF", as you put it.
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.
-
-
garyedwards on 2009-03-09So 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. -
jlundstocholm on 2009-03-22So 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.
Public Stiky Notes
Would you like to comment?
Join Diigo for a free account, or sign in if you are already a member.