Date: prev next · Thread: first prev next last
2016 Archives by date, by thread · List index

Re: [tdf-discuss] OOXML ECMA-376, transitionnal and strict


So. 

Is it correct to say that the Transitionnal OOXML format is not compliant with any international 
standard or norm ? Neither ECMA, nor ISO, nor anything but MS$ itself. 

If so, 
Does this means that NO version of MS$ office (from 2010 to the actual) writes BY DEFAULT in a 
standardized or normalised format. 
(cf. https://technet.microsoft.com/en-us/library/cc179191%28v=office.16%29.aspx for default 
formats) 

Is anyone confident enough in his knowledge of OOXML to acknowledge this ? 
Maybe this place is not the best one to ask the question ? 
If so, would please somebody advice me the best place to post the question ? 


----- Mail original -----

De: "Florian Reisinger" <florei@libreoffice.org> 
À: mjollnir66@laposte.net, discuss@documentfoundation.org 
Envoyé: Mardi 26 Avril 2016 13:26:12 
Objet: Re: [tdf-discuss] OOXML ECMA-376, transitionnal and strict 



Short answer: Any release (2007,2010,2013,2016) has it's own transitional format. AFAIK 



< mjollnir66@laposte.net > schrieb am Di., 26. Apr. 2016, 10:13: 


Hello, 

I'm a french user willing to get some answers about OOXML format. 
This post is already released on the fr.discuss mailing list. 

As you may know, something changing the game just happened in France. 
The second version of the Interoperability General Refenrential was just released. 
It demands all the public administrations (by law) to conform to certain file formats when the 
exchanged from administration to administration or from a citizen to an administration and vice et 
versa. 

ODF is recommended. 

OOXML strict is tolerated in some case. 
OOXML transitionnal is not. 
Binary older file formats are not either. 

Thus, it becomes very interresting to investigate what's behind OOXML. 

in this article : 
https://joinup.ec.europa.eu/community/osor/case/complex-singularity-versus-openness 

3 different OOXML formats are described : 
"There is the ECMA version (that’s the one MS Office 2007 writes, which was certified by ECMA 
International). Then there is OOXML Transitional, which is relatively close to the ECMA version, 
and is the format that all later versions to date write as default. Finally, there is OOXML 
Strict." 

In this MS$ tab : 
https://blogs.office.com/2012/08/13/new-file-format-options-in-the-new-office/#DR3YrKG0ymm0vmwB.97 
Only two OOXML formats are described : transitionnal and strict 

A very simple question to an OOXML specialist : 

Is transitionnal OOXML ECMA-376 compliant ? 

If not, is transitionnal OOXML compliant with any norm or standard ? 

Best regards and thanks in advance for any answer. 

M. 


-- 
To unsubscribe e-mail to: discuss+unsubscribe@documentfoundation.org 
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ 
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette 
List archive: http://listarchives.documentfoundation.org/www/discuss/ 
All messages sent to this list will be publicly archived and cannot be deleted 





-- 
To unsubscribe e-mail to: discuss+unsubscribe@documentfoundation.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.documentfoundation.org/www/discuss/
All messages sent to this list will be publicly archived and cannot be deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.