|Introduction | Sustainability Factors | Content Categories | Format Descriptions | Contact|
|Full name||DOCX Strict, (Office Open XML, WordprocessingML) ISO 29500-1:2008-2012, also ECMA-376, Editions 2-4.|
The Strict variant of DOCX disallows a variety of elements and attributes that are permitted in the more common Transitional variant (DOCX/OOXML_2012). The markup for the Strict variant is essentially a subset of markup for the Transitional variant, but the schemas use different namespaces and are distributed separately in complete form.
Among the disallowed elements and attributes are:
The Strict variant of DOCX described here was introduced during the standardization in ISO/IEC 29500 in 2008 with the intention of excluding features included in ECMA-376, Edition 1 that were present simply to handle bugs and features of earlier word-processors or to permit continued use of deprecated markup (e.g. VML markup for drawings). The intent of the split of the markup specification into Strict (Part 1) and Transitional (Part 4) was that applications would create new documents in the Strict variant; however, in practice, pressure for backwards compatibility has meant that most new files are marked up by applications using the Transitional namespace even if they use no features that are incompatible with the Strict specification.
For discussion of other aspects of the Strict DOCX format, see the description of the more common Transitional variant of DOCX, DOCX/OOXML_2012.
|Production phase||Can be used in any production phase. Likely used primarily for creating documents (initial state) and for editing and review (middle-state). Documents that are formally published are often converted to a format that is designed for final publication and not for convenient editing.|
|Relationship to other formats|
|Subtype of||OOXML Family, OOXML (ISO/IEC 29500) Format Family|
|Subtype of||OPC/OOXML_2012, Open Packaging Conventions (Office Open XML), ISO 29500-2:2008-2012|
|Modification of||DOCX/OOXML_2012, DOCX Transitional (Office Open XML), ISO 29500:2008-2012, ECMA-376, Editions 1-4. The Transitional form of DOCX allows additional legacy markup to address backward compatibility with bugs and features of older word-processors. The legacy markup is specified in Part 4 of ISO 29500.|
|May contain||MCE/OOXML_2012, Markup Compatibility and Extensibility (Office Open XML), ISO 29500-3:2008-2012, ECMA-376, Editions 1-4|
|Defined via||XML, Extensible Markup Language (XML)|
|LC experience or existing holdings||In 2014, the Library of Congress is not aware of any documents in the Strict form of DOCX in its collections.|
|LC preference||The list of Library of Congress Recommended Format Specifications for Textual and Musical works, as of June 2014, includes the OOXML family of formats, which includes the DOCX format, as acceptable for textual works and electronic serials. It does not distinguish between the Strict and the more common Transitional DOCX/OOXML_2012 form in its preferences.|
|Disclosure||International open standard. Maintained by ISO/IEC JTC1 SC34/WG4 as Part 1 of ISO/IEC 29500, first published in 2008.|
ISO/IEC 29500-1, Information technology -- Document description and processing languages -- Office Open XML File Formats -- Part 1: Fundamentals and Markup Language Reference. Latest version (dated 2012 as of August 2014) is available from ISO/IEC Publicly Available Standards.
All editions of the OOXML standards as published by ECMA are available from ECMA-376: Office Open XML File Formats. The split between Strict and Transitional variants of DOCX was introduced in Edition 2 of ECMA-376 which is identical to ISO/IEC 29500:2008.
The Strict variant of DOCX is not widely used or supported as of September 2014. The ability to read Strict DOCX files was implemented in Microsoft's Word 2010; Word 2013 added the ability to write Strict files as an option. Office 365 (a cloud-based product) can also read and write Strict files. As of September 2014, the latest version of Word for a desktop Mac (in Office for Mac 2011) can neither write nor read Strict files.
Versions of LibreOffice since 4.2.3 can read Strict DOCX files. A test using LibreOffice 4.3 suggests that DOCX files written by that application are always in the more common Transitional form.
Whether the Strict version of DOCX is more widely used in the future will likely depend on whether pressure on software vendors from governments for its adoption outweighs market pressure, which currently seems to favor backwards compatibility.
|Licensing and patents||See the more common Transitional form of DOCX, DOCX/OOXML_2012.|
|Transparency||See the more common Transitional form of DOCX, DOCX/OOXML_2012.|
|Self-documentation||See the more common Transitional form of DOCX, DOCX/OOXML_2012|
|External dependencies||See the more common Transitional form of DOCX, DOCX/OOXML_2012.|
|Technical protection considerations||See the more common Transitional form of DOCX, DOCX/OOXML_2012.|
|Normal rendering||See the more common Transitional form of DOCX, DOCX/OOXML_2012 for functionality supported.|
||Used for Strict and the more common Transitional form of DOCX.|
|Internet Media Type||application/vnd.openxmlformats-officedocument.wordprocessingml.document
||From IANA registration.|
|XML namespace declaration||http://purl.oclc.org/ooxml/wordprocessingml/main
||This namespace declaration is for the Strict variant of DOCX. It occurs in the mandatory Main Document part of a DOCX file (package) with the name /word/document.xml and is mapped to the prefix w.|
||Will occur in the top-level Relationships part (/_rels/.rels part in an OPC package in the <Relationships> element of a DOCX file. In the Strict variant, it will be the target of a relationship of type http://purl.oclc.org/ooxml/relationships/officeDocument. See root namespace and source relationship for Main Document Part in ISO/IEC 29500-1:2012, §11.3.10.|
|General||See the more common Transitional form of DOCX, DOCX/OOXML_2012|
|History||See the more common Transitional form of DOCX, DOCX/OOXML_2012|