Content deleted Content added
+cat |
m →Office MathML (OMML): HTTP to HTTPS for Blogspot |
||
| (9 intermediate revisions by 8 users not shown) | |||
Line 5:
{{Infobox file format
| name = Office Open XML Document
| icon =
| logo sg
| screenshot =
| caption =
| extension = .docx, .docm
| mime = application/vnd.<br />openxmlformats-officedocument.<br />wordprocessingml.<br />document<ref name="mimetype">{{ cite web | url = https://technet.microsoft.com/en-us/library/cc179224.aspx | title = Register file extensions on third party servers | author = Microsoft | date = 26 February 2008 | access-date = 2009-09-04 | publisher = microsoft.com }}</ref>
| type code =
| uniform type =
Line 24:
| extended to =
| standard = ECMA-376, ISO/IEC 29500
| url = [http://www.ecma-international.org/publications-and-standards/standards/
{{Infobox file format
| name = Office Open XML Presentation
| icon =
| logo =
| screenshot =
| caption =
| extension = .pptx, .pptm
| mime = application/vnd.<br />openxmlformats-officedocument.<br />presentationml.<br />presentation<ref name="mimetype">{{ cite web | url = https://technet.microsoft.com/en-us/library/cc179224.aspx | title = Register file extensions on third party servers | author = Microsoft | date = 26 February 2008 | access-date = 2009-09-04 | publisher = microsoft.com }}</ref>
| type code =
| uniform type =
Line 46:
| extended to =
| standard = ECMA-376, ISO/IEC 29500
| url = [http://www.ecma-international.org/publications-and-standards/standards/
{{Infobox file format
| name = Office Open XML Workbook
| icon =
| logo =
| screenshot =
| caption =
| extension = .xlsx, .xlsm
| mime = application/vnd.<br />openxmlformats-officedocument.<br />spreadsheetml.<br />sheet<ref name="mimetype">{{ cite web | url = https://technet.microsoft.com/en-us/library/cc179224.aspx | title = Register file extensions on third party servers | author = Microsoft | date = 26 February 2008 | access-date = 2009-09-04 | publisher = microsoft.com }}</ref>
| type code =
| uniform type =
Line 68:
| extended to =
| standard = ECMA-376, ISO/IEC 29500
| url = [http://www.ecma-international.org/publications/standards-and-standards/
}}
The '''Office Open XML file formats''' are a set of [[file format]]s that can be used to represent electronic [[Office suite|office]] documents. There are formats for [[word processing]] documents, [[spreadsheets]] and [[presentations]] as well as specific formats for material such as mathematical
The formats were developed by [[Microsoft]] and first appeared in [[Microsoft Office 2007]]. They were standardized between December 2006 and November 2008, first by the [[Ecma International]] consortium, where they became ECMA-376, and subsequently, after a [[Standardization of Office Open XML|contentious standardization process]], by the ISO/IEC's Joint Technical Committee 1, where they became ISO/IEC 29500:2008.
Line 164:
Shared markup language materials include:
* Office Math Markup Language (OMML)
* DrawingML used for vector drawing, charts, and for example, text art (additionally, though deprecated, [[Vector Markup Language|VML]] is supported for drawing)
* Extended properties
* Custom properties
Line 190:
| date=21 October 2008 }}</ref>
The [[W3C XML Schema|XML Schema]] of Office Open XML emphasizes reducing load time and improving [[parsing]] speed.<ref>{{Cite web| title=Software Developer uses Office Open XML to Minimize File Space, Increase Interoperability| url=http://www.openxmlcommunity.org/documents/casestudies/Intellisafe_OpenXML_Final.pdf
The naming of elements and attributes within the text has attracted some criticism. There are three different syntaxes in OOXML (ECMA-376) for specifying the color and alignment of text depending on whether the document is a text, spreadsheet, or presentation. Rob Weir (an [[IBM]] employee and co-chair of the [[OASIS (organization)|OASIS]] [[OpenDocument Format]] TC) asks "What is the engineering justification for this horror?". He contrasts with [[OpenDocument]]: "ODF uses the W3C's XSL-FO vocabulary for text styling, and uses this vocabulary consistently".<ref>{{ cite web | url=http://www.robweir.com/blog/2008/03/disharmony-of-ooxml.html | title= Disharmony of OOXML | author=Rob Weir | date=14 March 2008}}</ref>
Some have argued the design is based too closely on Microsoft applications.
In August 2007, the [[Linux Foundation]] published a blog post calling upon ISO National Bodies to vote "No, with comments" during the International Standardization of OOXML. It said, "OOXML is a direct port of a single vendor's binary document formats. It avoids the re-use of relevant existing international standards (e.g. several cryptographic algorithms, VML, etc.). There are literally hundreds of technical flaws that should be addressed before standardizing OOXML including continued use of binary code tied to platform specific features, propagating bugs in MS-Office into the standard, proprietary units, references to proprietary/confidential tags, unclear [[Intellectual property|IP]] and patent rights, and much more".<ref>{{
The version of the standard submitted to [[ISO/IEC JTC 1|JTC 1]] was 6546 pages long. The need and appropriateness of such length has been questioned.<ref name="GooglesPositiononOOXML">{{ cite web | url = http://www.odfalliance.org/resources/Google%20OOXML%20Q%20%20A.pdf | title = Google's Position on OOXML as a Proposed ISO Standard | date = February 2008 | publisher = [[Google]] | quote = If ISO were to give OOXML with its 6546 pages the same level of review that other standards have seen, it would take 18 years (6576 days for 6546 pages) to achieve comparable levels of review to the existing ODF standard (871 days for 867 pages) which achieves the same purpose and is thus a good comparison. Considering that OOXML has only received about 5.5% of the review that comparable standards have undergone, reports about inconsistencies, contradictions and missing information are hardly surprising | url-status = dead | archive-url = https://web.archive.org/web/20100818112807/http://www.odfalliance.org/resources/Google%20OOXML%20Q%20%20A.pdf | archive-date = 2010-08-18 }}</ref><ref>{{ cite web | url = http://www.ibm.com/developerworks/library/x-ooxmlstandard.html | title = OOXML: What's the big deal? | date = 2008-02-19 | publisher = [[IBM]] | url-status = dead | archive-url = https://web.archive.org/web/20091003044227/http://www.ibm.com/developerworks/library/x-ooxmlstandard.html | archive-date = 2009-10-03 }}</ref> [[Google]] stated that "the ODF standard, which achieves the same goal, is only 867 pages"<ref name="GooglesPositiononOOXML"/>
Line 212:
=== Office MathML (OMML) ===
Office Math Markup Language is a mathematical markup language which can be embedded in WordprocessingML, with intrinsic support for including word processing markup like revision markings,<ref>{{cite web|url = http://idippedut.dk/post/Do-your-math-OOXML-and-OMML|title = Do your math - OOXML and OMML (Updated 2008-02-12)|author = Jesper Lund Stocholm|publisher = A Mooh Point blog|date = 2008-02-12|access-date = 2015-11-18|archive-date = 2016-03-26|archive-url = https://web.archive.org/web/20160326225935/http://idippedut.dk/post/Do-your-math-OOXML-and-OMML|url-status = dead}}</ref> footnotes, comments, images and elaborate formatting and styles.<ref>{{cite web| url=http://blogs.msdn.com/murrays/archive/2007/06/05/science-and-nature-have-difficulties-with-word-2007-mathematics.aspx| title=Science and Nature have difficulties with Word 2007 mathematics| author=Murray Sargent| publisher=MSDN blogs| date=2007-06-05| access-date=2007-07-31}}</ref>
The OMML format is different from the [[World Wide Web Consortium]] (W3C) [[MathML]] recommendation that does not support those office features, but is partially compatible<ref>{{cite web| url=
The following Office MathML example defines the [[fraction (mathematics)|fraction]]: <math>\frac{\pi}{2}</math>
Line 228:
</syntaxhighlight>
Some have queried the need for Office MathML (OMML) instead advocating the use of [[MathML]], a [[World Wide Web Consortium|W3C]] recommendation for the "inclusion of mathematical expressions in Web pages" and "machine to machine communication".<ref>{{cite web| url=
=== DrawingML ===<!-- English Metric Unit links to here -->
Line 242:
DrawingML is unrelated to the other [[vector graphics]] formats such as [[Scalable Vector Graphics|SVG]]. These can be converted to DrawingML to include natively in an Office Open XML document. This is a different approach to that of the [[OpenDocument]] format, which uses a subset of SVG, and includes vector graphics as separate files.
A DrawingML graphic's dimensions are specified in ''English Metric Units'' (EMUs). It is so called because it allows an exact common representation of dimensions originally in either [[English units|English]] or [[Metric system|metric]] units—defined as 1/360,000 of a [[centimeter]], and thus there are 914,400 EMUs per [[inch]], and 12,700 EMUs per [[point (typography)|point]], to prevent round-off in calculations. [[Rick Jelliffe]] favors EMUs as a rational solution to a particular set of design criteria.<ref>{{cite web |title=Why EMUs? |last1=Jelliffe |first1=Rick |url=http://www.oreillynet.com/xml/blog/2007/04/what_is_an_emu.html |website=O'Reilly XML Blog |publisher=O'Reilly |access-date=2009-05-19 |archive-url=https://web.archive.org/web/20141229020130/http://archive.oreilly.com/pub/post/what_is_an_emu.html |archive-date=2014-12-29 |url-status=dead}}</ref>
Some have criticised the use of DrawingML (and the transitional-use-only [[Vector Markup Language|VML]]) instead of [[World Wide Web Consortium|W3C]] recommendation [[Scalable Vector Graphics|SVG]].<ref>{{ cite web | url=http://reddevnews.com/features/article.aspx?editorialsid=2356 | title= The X Factor | publisher=reddevnews.com |date=October 2007 }}</ref> VML did not become a W3C recommendation.<ref>{{ cite web | url = http://www.w3.org/TR/NOTE-VML | title = VML — the Vector Markup Language | publisher = W3.org | date = 1998-05-13 | access-date = 2009-05-19 }}</ref>
| |||