Office Open XML File Formats - Open Packaging Conventions
|First published||December 7, 2006|
|Latest version||ISO/IEC 29500-2:2012|
August 22, 2012
|Organization||Microsoft, Ecma, ISO/IEC|
|Base standards||ECMA-376, ISO/IEC 29500-2|
|Related standards||XML, ZIP|
The Open Packaging Conventions (OPC) is a container-file technology initially created by Microsoft to store a combination of XML and non-XML files that together form a single entity such as an Open XML Paper Specification (OpenXPS) document. OPC-based file formats combine the advantages of leaving the independent file entities embedded in the document intact and resulting in much smaller files compared to normal use of XML.
The ISO/IEC 29500-2:2008 specification and the second edition of ECMA-376 makes a normative reference to PKWARE, Inc.'s .ZIP File Format Specification version 6.2.0 (2004), and supplements it with a normative set of clarifications. Note: The older first edition of ECMA-376 makes an informative (i.e., non-normative) reference to the newer PKWARE Inc's ".ZIP File Format Specification" version 6.2.1 (2005). The ZIP format is not specified by any international standard but has widespread community and developer acceptance.
Microsoft submitted a draft in 2006 to the Internet Engineering Task Force for a "pack" URI Scheme (
pack://) to be used for URI references to OPC-based packages. The draft expired in 2009, the specified syntax is incompatible with the Internet Standard for URI schemes (STD 66, RFC 3986). The scheme is now listed as historical.
The ISO 19165:1-2018 recommends the use of the Open Packaging Conventions to implement the Geospatial Package defined in the Open Archival Information System.
Both the XML Paper Specification (XPS) and Office Open XML (OOXML) use Open Packaging Conventions (OPC), which provide a profile of the common ZIP format. In addition to data and document content in XML markup, files in the ZIP package can include other text and binary files in formats such as PNG, BMP, AVI, PDF, RTF, or even an already packaged ODF file. OPC also defines some naming conventions and an indirection method to allow position independence of binary and XML files in the ZIP archive.
The OPC is the foundation technology for many new file formats:
|File format||Filename extension||Content||Standard|
|3MF Consortium 3D Manufacturing Format (3MF) file format||.3mf||CAD design data for additive manufacturing (3D printing)|
|Autodesk AutoCAD Design Web Format (DWFX) file format||.dwfx||CAD design data (2D/3D computer graphics and technical drawings)|
|Circuit Diagram Document||.cddx||Circuit diagram containing layout, connections and embedded components|
|Family.Show file format||.familyx||genealogical family data, stories, and photos|
|Field Device Integration FDI Packages||.fdix||Field Device Integration information||IEC 62769-4:2015|
|Microsoft Application Virtualization file format||.appv||Portable application|
|Microsoft Semblio file format||.semblio||Interactive learning material, such as e-books containing images, audio, and video|
|Microsoft Visual Studio 2010+ Extensions file format||.vsix||Integrated development environment extension|
|Microsoft Visio 2013 drawing file format||.vsdx||Replaces .vsd (Visio binary file) and .vdx (Visio XML Drawing) formats used in earlier versions|
|Microsoft Windows 8, Windows 8.1 and Windows Phone 8.1 App Package||.appx||Software package for applications listed on Microsoft's Windows Store and Windows Phone Store|
|Microsoft Windows 8.1 and Windows Phone 8.1 App Bundle||.appxbundle||Software package that bundles hardware platforms, languages, and resources for an application listed on Microsoft's Windows Store and Windows Phone Store|
|Microsoft Windows Azure C# Package||.cspkg||Cloud platform data|
|Microsoft XML Paper Specification||.xps||Fixed document for document exchange|
|MiraMon open compressed map||.mmzx||Geographic information (Geospatial Raster graphics, vector graphics and tabular data, symbolization and metadata in files, links to geoservices, etc)||ISO 19165-1:2018|
|NuGet Package||.nupkg||Software package for a package management system|
|Office Open XML Document||.docx||Word processing document||ECMA-376, ISO/IEC 29500:2008|
|Office Open XML Presentation||.pptx||Presentation file||ECMA-376, ISO/IEC 29500:2008|
|Office Open XML Workbook||.xlsx||Spreadsheet workbook||ECMA-376, ISO/IEC 29500:2008|
|Open XML Paper Specification||.oxps||Fixed document for document exchange||ECMA-388|
|Platform Industrie 4.0 - Administrative Asset Shell||.aasx||Package file format for Administrative Asset Shells (AAS)|
|Siemens PLM Software file format||.jtx|
|MathWorks Simulink model file||.slx||Dynamic system specification for Model-based design|
|SMPTE Media Package||.smpk||Storage format for distribution and playback of multimedia video and audio files||SMPTE ST 2053-2011|
|SpaceClaim 3D solid model file||.scdoc||Embedded 3D CAD data files include Standard ACIS Binary (SAB) solid model files|
|Microsoft XAML Package||-||Not a specification. Function supported by .NET Framework only for saving WPF FlowDocument with images|
OPC is natively supported in Microsoft .NET Framework 3.0 by the System.IO.Packaging namespace. Open source libraries exist for other languages.
Alternatively, ZIP libraries can be used to create and open OPC files, as long as the correct files are included in the ZIP and the conventions followed.
In OPC terminology, the term package corresponds to a ZIP archive and the term part corresponds to a file stored within the ZIP. Every part in a package has a unique URI-compliant part name along with a specified content-type expressed in the form of a MIME media type. A part's content-type explicitly defines the type of data stored in the part and reduces duplication and ambiguity issues inherent with file extensions.
OPC packages can also include relationships that define associations between the package, parts, and external resources. In addition to a hierarchy of directories and parts, OPC packages commonly use relationships to access content through a directed graph of relationship associations. Relationships are composed of four elements:
OPC packages can store parts that contain any type of data (text, images, XML, binary, whatever). The extension ".rels", however, is reserved for storing relationships metadata within "/_rels" subfolders. The subfolder name "_rels", the file extension ".rels" within such directory, and the filename "[Content_Types].xml" in any folder are the only three reserved names for files stored in an OPC package.
<Default Extension="rels" ContentType="application/vnd.openxmlformats-package.relationships+xml"/>
All relationships (including the relations associated to the root package) are represented as XML files. If you open a ".rels" file in a text editor, you can view the actual XML markup that defines all the relationships targeted from that part. A typical relationships file contains XML code like this:
<Relationships xmlns="http://schemas.openxmlformats.org/package/2006/relationships"> <Relationship Id="R0" Type="http://schemas.microsoft.com/xps/2005/06/fixedrepresentation" Target="/FixedDocumentSequence.fdseq"/> <Relationship Id="R1" Type="http://schemas.openxmlformats.org/package/2006/relationships/metadata/thumbnail" Target="/Documents/1/Metadata/Page1_Thumbnail.JPG"/> </Relationships>
which defines two relations for the root package, the first one being considered as the root package (here for an early Microsoft XPS document, before it was standardized as Open XML Paper Specification within the openxmlformats collection), and the other one being used to reference an alternate form (here a thumbnail rendered image of the first page of the document).
The main parts of the embedded documents are often stored within a folder named "/Document" (which may contain subdirectories itself, if the file contains several related documents each of them with various parts), and the optional metadata parts that are not needed for processing the main parts of the document are stored in a folder named "/Metadata"; however these actual folder names are actually specified within the XML-formatted data in "[partname].rels" relationship files and the OPC specification allows any folder organisation that is convenient for the application and these two folder names are not required.
It encourages documents to be split into small chunks. This is better for reducing the effect of file corruption. And better for data access: for example, all the style information in one XML part, each separate worksheet or table in their own different parts. This allows faster access and less object creation for clients and makes it easier for multiple processes to be working on the same document.
In the Open Packaging Conventions, each file that has reference has its own _rels file with the indirection lists. This makes it easier to cut and paste some information with all its associated resources in some cases, provides name scoping to remove the chance of name clashing between files, and so on.