Office Open XML File Formats

ECMA-376

1st Edition / December 2006

Office Open XML File Formats

Standard

ECMA-376

1st Edition / December 2006

Office Open XML

Part 1: Fundamentals

December 2006

Table of Contents

Forewordxi

Introductionxii

1.Scope1

2.Conformance2

2.1Goal2

2.2Issues2

2.3What this Standard Specifies3

2.4Document Conformance3

2.5Application Conformance3

2.6Interoperability Guidelines3

3.Normative References5

4.Definitions6

5.Notational Conventions8

6.Acronyms and Abbreviations9

7.General Description10

8.Overview11

8.1Packages and Parts11

8.2Consumers and Producers11

8.3WordprocessingML11

8.4SpreadsheetML12

8.5PresentationML13

8.6Supporting MLs14

8.6.1DrawingML14

8.6.2VML15

8.6.3Custom XML Data Properties15

8.6.4File Properties15

8.6.5Math15

8.6.6Bibliography15

9.Packages16

9.1Constraints on Office Open XML's Use of OPC16

9.1.1Part Names16

9.1.2Part Addressing16

9.1.3Fragments16

9.1.4Physical Packages16

9.1.5Interleaving16

9.1.6Unknown Parts17

9.1.7Trash Items17

9.1.8Invalid Parts17

9.1.9Unknown Relationships17

9.2Relationships in Office Open XML17

10.Markup Compatibility and Extensibility23

10.1Constraints on Office Open XML's Use of Markup Compatibility and Extensibility23

10.1.1PreserveElements and PreserveAttributes23

10.1.2Office Open XML Native Extensibility Constructs23

11.WordprocessingML24

11.1Glossary of WordprocessingML-Specific Terms24

11.2Package Structure25

11.3Part Summary27

11.3.1Alternative Format Import Part28

11.3.2Comments Part29

11.3.3Document Settings Part31

11.3.4Endnotes Part33

11.3.5Font Table Part35

11.3.6Footer Part36

11.3.7Footnotes Part38

11.3.8Glossary Document Part41

11.3.9Header Part43

11.3.10Main Document Part46

11.3.11Numbering Definitions Part48

11.3.12Style Definitions Part51

11.3.13Web Settings Part52

11.4Document Template53

11.5Framesets54

11.6Master Documents and Subdocuments55

11.7Mail Merge Data Source56

11.8Mail Merge Header Data Source57

11.9XSL Transformation58

12.SpreadsheetML59

12.1Glossary of SpreadsheetML-Specific Terms59

12.2Package Structure60

12.3Part Summary62

12.3.1Calculation Chain Part63

12.3.2Chartsheet Part64

12.3.3Comments Part65

12.3.4Connections Part67

12.3.5Custom Property Part68

12.3.6Custom XML Mappings Part69

12.3.7Dialogsheet Part70

12.3.8Drawings Part72

12.3.9External Workbook References Part73

12.3.10Metadata Part75

12.3.11Pivot Table Part78

12.3.12Pivot Table Cache Definition Part79

12.3.13Pivot Table Cache Records Part81

12.3.14Query Table Part82

12.3.15Shared String Table Part83

12.3.16Shared Workbook Revision Headers Part84

12.3.17Shared Workbook Revision Log Part85

12.3.18Shared Workbook User Data Part87

12.3.19Single Cell Table Definitions Part87

12.3.20Styles Part89

12.3.21Table Definition Part90

12.3.22Volatile Dependencies Part91

12.3.23Workbook Part92

12.3.24Worksheet Part94

12.4External Workbooks96

13.PresentationML98

13.1Glossary of PresentationML-Specific Terms98

13.2Package Structure98

13.3Part Summary101

13.3.1Comment Authors Part102

13.3.2Comments Part103

13.3.3Handout Master Part104

13.3.4Notes Master Part106

13.3.5Notes Slide Part107

13.3.6Presentation Part109

13.3.7Presentation Properties Part111

13.3.8Slide Part111

13.3.9Slide Layout Part113

13.3.10Slide Master Part115

13.3.11Slide Synchronization Data Part116

13.3.12User Defined Tags Part117

13.3.13View Properties Part118

13.4HTML Publish Location119

13.5Slide Synchronization Server Location120

14.DrawingML122

14.1Glossary of DrawingML-Specific Terms122

14.2Part Summary122

14.2.1Chart Part123

14.2.2Chart Drawing Part125

14.2.3Diagram Colors Part126

14.2.4Diagram Data Part127

14.2.5Diagram Layout Definition Part128

14.2.6Diagram Style Part130

14.2.7Theme Part131

14.2.8Theme Override Part133

14.2.9Table Styles Part134

15.Shared136

15.1Glossary of Shared Terms136

15.2Part Summary136

15.2.1Additional Characteristics Part137

15.2.2Audio Part138

15.2.3Bibliography Part139

15.2.4Custom XML Data Storage Part140

15.2.5Custom XML Data Storage Properties Part141

15.2.6Digital Signature Origin Part141

15.2.7Digital Signature XML Signature Part142

15.2.8Embedded Control Persistence Part143

15.2.9Embedded Object Part146

15.2.10Embedded Package Part148

15.2.11File Properties149

15.2.12Font Part154

15.2.13Image Part154

15.2.14Printer Settings Part155

15.2.15Thumbnail Part156

15.2.16Video Part157

15.2.17VML Drawing Part158

15.3Hyperlinks159

Annex A.Bibliography161

Annex B.Index163

Foreword

This multi-part Standard deals with Office Open XML Format-related technology, and consists of the following parts:

Part 1: "Fundamentals" (this document)

Part 2: "Open Packaging Conventions"

Part 3: "Primer"

Part 4: "Markup Language Reference"

Part 5: "Markup Compatibility and Extensibility"

Parts 2 and 4 include a number of annexes that refer to data files provided in electronic form only.

Introduction

This Part is one piece of a Standard that describes a family of XML schemas, collectively called Office Open XML, which define the XML vocabularies for word-processing, spreadsheet, and presentation documents, as well as the packaging of documents that conform to these schemas.

The goal is to enable the implementation of the Office Open XML formats by the widest set of tools and platforms, fostering interoperability across office productivity applications and line-of-business systems, as well as to support and strengthen document archival and preservation, all in a way that is fully compatible with the large existing investments in Microsoft Office documents.

The following organizations have participated in the creation of this Standard and their contributions are gratefully acknowledged:

Apple, Barclays Capital, BP, The British Library, Essilor, Intel, Microsoft, NextPage, Novell, Statoil, Toshiba, and the United States Library of Congress

Scope

This Standard defines Office Open XML's vocabularies and document representation and packaging. It also specifies requirements for consumers and producers of Office Open XML.

Conformance

The text in this Standard is divided into normative and informative categories. Unless documented otherwise, any feature shall be implemented as specified by the normative text describing that feature in this Standard. Text marked informative (using the mechanisms described in §7) is for information purposes only. Unless stated otherwise, all text is normative.

Use of the word “shall” indicates required behavior.

Any behavior that is not explicitly specified by this Standard is implicitly unspecified (§4).

Goal

The goal of this clause is to define conformance, and to provide interoperability guidelines in a way that fosters broad and innovative use of the Office Open XML file format, while maximizing interoperability and preserving investment in existing files and applications (§4). By meeting this goal, this Standard benefits the following audiences:

Developers that design, implement, or maintain Office Open XML applications.

Developers that interact programmatically with Office Open XML applications.

Governmental or commercial entities that procure Office Open XML applications.

Testing organizations that verify conformance of specific Office Open XML applications to this Standard. (Note that this Standard does not include a test suite.)

Educators and authors who teach about Office Open XML applications.

Issues

To achieve the above goal, the following issues need to be considered:

The application domain encompasses a range of possible consumers (§4) and producers (§4) so broad that defining specific application behaviors would restrict innovation. For example, stipulating visual layout would be inappropriate for a consumer that extracts data for machine consumption, or that renders text in sound. Another example is that restricting capacity or precision runs the risk of diluting the value of future advances in hardware.

Commonsense user expectations regarding the interpretation of an Office Open XML package (§4) play such an important role in that package's value that a purely syntactic definition of conformance would fail to effect a useful level of interoperability. For example, such a definition would admit an application that reads a package, and then writes it in a manner that, though syntactically valid, differs arbitrarily from the original.

Legitimate operations on a package include deliberate transformations, making blanket change prohibitions inappropriate in the conformance definition. For example, collapsing spreadsheet formulas to their calculated values, or converting complex presentation graphics to static bitmaps, could be correct for an application whose published purpose is to perform those operations. Again, commonsense user expectation makes the difference.

Existing files and applications exercise a broad range of formats and functionality that, if required by the conformance definition, would add an impractical amount of bulk to the This Standard and could inadvertently obligate new applications to implement a prohibitive amount of functionality. This issue is caused by the breadth of currently available functionality and is compounded by the existence of legacy formats.

What this Standard Specifies

To address the issues listed above, this Standard constrains both syntax and semantics, but it is not intended to predefine application behavior. Therefore, it includes, among others, the following three types of information:

Schemas and an associated validation procedure for validating document syntax against those schemas. (The validation procedure includes un-zipping, locating files, processing the extensibility elements and attributes, and XML Schema validation.)

Additional syntax constraints in written form, wherever these constraints cannot feasibly be expressed in the schema language.

Descriptions of element semantics. The semantics of an element refers to its intended interpretation by a human being.

Document Conformance

Document conformance is purely syntactic; it involves only Items 1 and 2 in §2.3 above.

A conforming document shall conform to the schema (Item 1) and any additional syntax constraints (Item 2).

The document character set shall conform to the Unicode Standard and ISO/IEC 10646-1, with either the UTF-8 or UTF-16 encoding form, as required by the XML 1.0 standard.

Any XML element or attribute not explicitly included in this Standard shall use the extensibility mechanisms described by Parts 4 and 5 of this Standard.

Application Conformance

Application conformance is purely syntactic; it also involves only Items 1 and 2 in §2.3 above.

A conforming consumer shall not reject any conforming documents of the document type (§4) expected by that application.

A conforming producer shall be able to produce conforming documents.

Interoperability Guidelines

[Guidance: The following interoperability guidelines incorporate semantics (Item 3 in §2.3 above).

For the guidelines to be meaningful, a software application should be accompanied by publicly available documentation that describes what subset of this Standard it supports. The documentation should highlight any behaviors that would, without that documentation, appear to violate the semantics of document elements. Together, the application and documentation should satisfy the following conditions.

The application need not implement operations on all elements defined in this Standard. However, if it does implement an operation on a given element, then that operation should use semantics for that element that are consistent with this Standard.

If the application moves, adds, modifies, or removes element instances with the effect of altering document semantics, it should declare the behavior in its documentation.

The following scenarios illustrate these guidelines.

A presentation editor that interprets the preset shape geometry “rect” as an ellipse does not observe the first guideline because it implements “rect” but with incorrect semantics.

A batch spreadsheet processor that saves only computed values even if the originally consumed cells contain formulas, may satisfy the first condition, but does not observe the second because the editability of the formulas is part of the cells’ semantics. To observe the second guideline, its documentation should describe the behavior.

A batch tool that reads a word-processing document and reverses the order of text characters in every paragraph with “Title” style before saving it can be conforming even though this Standard does not anticipate this behavior. This tool’s behavior would be to transform the title “Office Open XML” into “LMX nepO eciffO”. Its documentation should declare its effect on such paragraphs. end guidance]

Normative References

The following normative documents contain provisions, which, through reference in this text, constitute provisions of this Standard. For dated references, subsequent amendments to, or revisions of, any of these publications do not apply. However, parties to agreements based on this Standard are encouraged to investigate the possibility of applying the most recent editions of the normative documents indicated below. For undated references, the latest edition of the normative document referred to applies. Members of ISO and IEC maintain registers of currently valid International Standards.

ISO/IEC 2382.1:1993, Information technology — Vocabulary — Part 1: Fundamental terms.

ISO/IEC 10646:2003 (all parts), Information technology — Universal Multiple-Octet Coded Character Set (UCS).

Definitions

For the purposes of this Standard, the following definitions apply. Other terms are defined where they appear in italic type or on the left side of a syntax rule. Terms explicitly defined in this Standard are not to be presumed to refer implicitly to similar terms defined elsewhere. [Note: This part uses OPC-related terms, which are defined in Part 2: "Open Packaging Conventions". end note]

application — A consumer or producer.

behavior — External appearance or action.

behavior, implementation-defined — Unspecified behavior where each implementation documents that behavior, thereby promoting predictability and reproducibility within any given implementation. (This term is sometimes called “application-specific behavior”.)

behavior, locale-specific — Behavior that depends on local conventions of nationality, culture, and language.

behavior, unspecified —Behavior where this Standard imposes no requirements. [Note: To add an extension, an implementer must use the extensibility mechanisms described by this Standard rather than trying to do so by giving meaning to otherwise unspecified behavior. end note]

document type — One of the three types of Office Open XML documents: Wordprocessing, Spreadsheet, and Presentation, defined as follows:

A document whose package-relationship item contains a relationship to a Main Document part (§11.3.10) is a document of type Wordprocessing.

A document whose package-relationship item contains a relationship to a Workbook part (§12.3.23) is a document of type Spreadsheet.

A document whose package-relationship item contains a relationship to a Presentation part (§13.3.6) is a document of type Presentation.

An Office Open XML document can contain one or more embedded Office Open XML packages (§15.2.10) with each embedded package having any of the three document types. However, the presence of these embedded packages does not change the type of the document.

DrawingML — A set of conventions for specifying the location and appearance of drawing elements in an Office Open XML document.

extension — Any XML element or attribute not explicitly included in this Standard, but that uses the extensibility mechanisms described by this Standard.

Office Open XML document — A package containing ZIP items as required by, and satisfying Parts 1 and 4 of, this Standard. A rendition of a data stream formatted using the wordprocessing, spreadsheet, or presentation ML and its related MLs as described in this Standard. Such a document is represented as a package.

package— A ZIP archive that conforms to the Open Packaging Conventions specification defined in Part 2 of this Standard.

package, embedded— A package that has been stored as the target of a valid Embedded Package relationship (§15.2.10) in an Office Open XML document

PresentationML — A set of conventions for representing an Office Open XML document of type Presentation.

relationship —The kind of connection between a source part and a target part in a package. Relationships make the connections between parts directly discoverable without looking at the content in the parts, and without altering the parts themselves. (See also Package Relationships.)

relationships part — A part containing an XML representation of relationships.

relationship, explicit — A relationship in which a resource is referenced from a source part’s XML using the Id attribute of a Relationship tag.

relationship, implicit — A relationship that is not explicit.

SpreadsheetML — A set of conventions for representing an Office Open XML document of type Spreadsheet.

WordprocessingML — A set of conventions for representing an Office Open XML document of type Wordprocessing.

Notational Conventions

The following typographical conventions are used in this Standard:

The first occurrence of a new term is written in italics. [Example: … is considered normative. end example]

A term defined as a basic definition is written in bold. [Example: behavior — External … end example]

The name of an XML element is written using an Element style. [Example: The root element is document. end example]

The name of an XML element attribute is written using an Attribute style. [Example: … an id attribute. end example]

An XML element attribute value is written using a constant-width style. [Example: … value of CommentReference. end example]

An XML element type name is written using a Type style. [Example: … as values of the xsd:anyURI data type. end example]

Acronyms and Abbreviations

This clause is informative

The following acronyms and abbreviations are used throughout this Standard:

IEC — the International Electrotechnical Commission

ISO — the International Organization for Standardization

W3C — World Wide Web Consortium

End of informative text

General Description

This Standard is intended for use by implementers, academics, and application programmers. As such, it contains a considerable amount of explanatory material that, strictly speaking, is not necessary in a formal specification.

This Part is divided into the following subdivisions:

Front matter (clauses 1–7);

Overview (clause 8);

Main body (clauses 9–14);

Annexes

Examples are provided to illustrate possible forms of the constructions described. References are used to refer to related clauses. Notes are provided to give advice or guidance to implementers or programmers. Rationale provides explanatory material as to why something is or is not in this Standard. Annexes provide additional information or summarize the information contained in this Standard.

Clauses 1–5, 7, and 9–14 form a normative part of this Part; and the Introduction, clauses 6 and 8, as well as the annexes, notes, examples, rationale, guidance, and the index, are informative.

Except for whole clauses or annexes that are identified as being informative, informative text that is contained within normative text is indicated in the following ways:

[Example: code fragment, possibly with some narrative … end example]

[Note: narrative … end note]

[Rationale: narrative … end rationale]

[Guidance: narrative … end guidance]

Overview

This clause is informative.

This clause contains an overview of Office Open XML.

Packages and Parts

An Office Open XML document is represented as a series of related parts that are stored in a container called a package. Information about the relationships between a package and its parts is stored in the package's package-relationship ZIP item. Information about the relationships between two parts is stored in the part-relationship ZIP item for the source part. A package is an ordinary ZIP archive, which contains that package's content-type item, relationship items, and parts. (Packages are discussed further in Part 2.)

A WordprocessingML document contains a part for the body of the text; it might also contain a part for an image referenced by that text, and parts defining document characteristics, styles, and fonts. A SpreadsheetML document contains a separate part for each worksheet; it might also contain parts for images. A PresentationML document contains a separate part for each slide.

Consumers and Producers

A tool that can read and understand a package is called a consumer, while one that can create a package is called a producer. An application can be a consumer, a producer, or both. For example, when a word processor creates a new document, it acts as a producer. When it is used to open an existing document for reading or search purposes, it acts as a consumer. When it is used to open an existing document, edit it, and save the result, it acts as both consumer and producer. Similar scenarios exist for spreadsheet and presentation applications.

WordprocessingML

This subclause introduces the overall form of a WordprocessingML package, and identifies some of its main element types. (See Part 3 for a more detailed introduction.)

A WordprocessingML package has a relationship of type officeDocument, which specifies the location of the main part in the package. For a WordprocessingML document, that part contains the main text of the document.

A WordprocessingML package’s main part starts with a word processing root element. That element contains a body, which, in turn, contains one or more paragraphs (as well as tables, pictures, and the like). A paragraph contains one or more runs, where a run is a container for one or more pieces of text having the same set of properties. Like many collection element types, each run and paragraph can have associated with it a set of properties. For example, a run might have the property bold, which indicates that run's text is to be displayed in a bold typeface.

A WordprocessingML document is organized into sections, and the layout of a page on which the text appears within a section is controlled by that section's properties. For example, each section can have its own headers and footers.

One relationship from the document part specifies the document’s styles. A style defines a text display format. A style can have properties, which can be applied to individual paragraphs or runs. Styles make runs more compact by reducing the number of repeated definitions and properties, and the amount of work required to make changes to the document's appearance. With styles, the appearance of all the pieces of text that share a common style can be changed in one place, in that style's definition.

A series of paragraphs can have numbering applied to them via a numbering definition instance or a numbering style.

Data in a WordprocessingML document can be organized in a table, a two-dimensional grid of cells organized into rows and columns. Cells and whole tables can have associated properties. A cell can contain text and paragraphs, for example.

Text within a WordprocessingMLdocument can be determined dynamically via the use of fields. Fields consist of field instructions (the text that dictates the field's dynamic behavior) and the field result (the text resulting from the dynamic calculation of the field instructions. For example, page numbers are represented as fields. A hyperlink consists of two pieces of information: the hyperlink itself—the text the user will click—and the target for the link. Potential targets include external files, e-mail addresses, web sites, and bookmarks within the document itself.

A WordprocessingML document can also contain custom markup, user-defined semantics applied to arbitrary document content.

A WordprocessingML document is not stored as one large body in a single part; instead, the elements that implement certain groupings of functionality are stored in separate parts. For example, all footnotes in a document are stored in one footnote part, while each section can have up to three different header parts and three different footer parts, to support headers and footers on odd-numbered pages, even-numbered pages, and the first page.

SpreadsheetML

This subclause introduces the overall form of a SpreadsheetML package, and identifies some of its main element types. (See Part 3 for a more detailed introduction.)

A SpreadsheetML package has a relationship of type officeDocument, which specifies the location of the main part in the package. For a SpreadsheetML document, that part contains the workbook definition.

A SpreadsheetML package’s main part starts with a spreadsheet root element. That element is a workbook, which refers to one or more worksheets, which, in turn, contain the data. A worksheet is a two-dimensional grid of cells that are organized into rows and columns.

The cell is the primary place in which data is stored and operated on. A cell can have a number of characteristics, such as numeric, text, date, or time formatting; alignment; font; color; and a border. Each cell is identified by a cell reference, a combination of its column and row headings.

Each horizontal set of cells in a worksheet is called a row, and each row has a heading numbered sequentially, starting at 1. Each vertical set of cells in a worksheet is called a column, and each column has an alphabetic heading named sequentially from A–Z, then AA–AZ, BA–BZ, and so on.

Instead of data, a cell can contain a formula, which is a recipe for calculating a value. Some formulas—called functions—are predefined, while others are user-defined. Examples of predefined formulas are AVERAGE, MAX, MIN, and SUM. A function takes one or more arguments on which it operates, producing a result. For example, in the formula SUM(B1:B4), there is one argument, B1:B4, which is the range of cells B1–B4, inclusive.

Other features that a SpreadsheetML document can contain include the following: comments, hyperlinks, images, and sorted and filtered tables.

A SpreadsheetML document is not stored as one large body in a single part; instead, the elements that implement certain groupings of functionality are stored in separate parts. For example, all the data for a worksheet is stored in that worksheet's part, all string literals from all worksheets are stored in a single shared string part, and each worksheet having comments has its own comments part.

PresentationML

This subclause introduces the overall form of a PresentationML package, and identifies some of its main element types. (See Part 3 for a more detailed introduction.)

A PresentationML package has a relationship of type officeDocument, which specifies the location of the main part in the package. For a PresentationML document, that part contains the presentation definition.

A PresentationML package’s main part starts with a presentation root element. That element contains a presentation, which, in turn, refers to a slide list, a slide master list, a notes master list, and a handout master list. The slide list refers to all of the slides in the presentation; the slide master list refers to all of the slide masters used in the presentation; the notes master contains information about the formatting of notes pages; and the handout master describes how a handout looks.

A handout is a printed set of slides that can be handed out to an audience for future reference.

As well as text and graphics, each slide can contain comments and notes, can have a layout, and can be part of one or more custom presentations. (A comment is an annotation intended for the person maintaining the presentation slide deck. A note is a reminder or piece of text intended for the presenter or the audience.)

Other features that a PresentationML document can contain include the following: animation, audio, video, and transitions between slides.

A PresentationML document is not stored as one large body in a single part; instead, the elements that implement certain groupings of functionality are stored in separate parts. For example, all comments in a document are stored in one comment part while each slide has its own part.

Supporting MLs

This subclause introduces the set of markup languages used across package types. (See Part 3 for a more detailed introduction.)

The three markup languages described above define the structure of a package that is either a document (WordprocessingML), a spreadsheet (SpreadsheetML), or a presentation (PresentationML). However, there is also a set of shared markup languages used for common elements such as charts, diagrams, and drawing objects. These MLs are discussed below.

DrawingML

DrawingML specifies the location and appearance of drawing elements in a package. For example, these elements could be, but are not limited to, shapes, pictures, and tables. The root element of a DrawingML XML fragment specifies the presence of a drawing at this location in the document.

A shape is a geometric object such as a circle, square, or rectangle; a picture is an image presented inside the document; and a table is a two-dimensional grid of cells organized into rows and columns. Cells and whole tables can have associated properties. A cell can contain text, for example.

DrawingML also specifies the location and appearance of charts in a package. The root element of a chart part is chart, and specifies the appearance of the chart at this location in the document.

In addition, DrawingML specifies package-wide appearance characteristics, such as the package's theme. The theme of a document specifies the color scheme, fonts, and effects, which can be referenced by parts of the document—such as text, drawings, charts, and diagrams—in order to create a consistent visual presentation.

A chart is a presentation of data in a graphical fashion, such as a pie chart, bar chart, line chart, in order to make trends and exceptions in the data more visually apparent.

DrawingML also specifies the location and appearance of diagrams in a document. Together, the following four parts define a diagram:

The data part (§14.2.4) specifies individual items of information presented in the diagram. Typically, each piece is a simple line of text, but depending on the diagram, an item of data might also be an image.

The layout part (§14.2.5) specifies how the data and shapes are laid out to create the resulting diagram.

The colors part (§14.2.3) specifies the color which is applied to each individual shape in the diagram.

The styles part (§14.2.6) defines how each individual shape in the diagram maps to the document's theme.

VML

VML specifies the appearance and content of certain shapes in a document. This is used for shapes such as text boxes, as well as shapes which must be stored to maintain compatibility with earlier versions of consumer/producer applications.

[Note: The VML format is a legacy format originally introduced with Office 2000 and is included and fully defined in this Standard for backwards compatibility reasons. The DrawingML format is a newer and richer format created with the goal of eventually replacing any uses of VML in the Office Open XML formats. VML should be considered a deprecated format included in Office Open XML for legacy reasons only and new applications that need a file format for drawings are strongly encouraged to use preferentially DrawingML. end note]

A shape definition is typically specified using two elements: shapeData, which stores information about the shape, and shape, which stores the shape definition and appearance directly.

Custom XML Data Properties

Custom XML Data properties allow the ability to store arbitrary XML in a package, along with schema information used by that XML.

File Properties

The core file properties of a package enable users to discover, get, and set common sets of properties from within that package, regardless of whether it’s a WordprocessingML, SpreadsheetML, or PresentationML package, or another use of OPC. Such properties include creator name, creation date, title, and description.

Extended file properties are specific to Office Open XML packages. For example, for a WordprocessingML package, these properties include the number of characters, words, lines, paragraphs, and pages in the document. For a SpreadsheetML package, these properties include worksheet titles. For a PresentationML package, these properties include presentation format, the number of slides, the number of notes, and whether or not any slides are hidden.

Custom file properties are defined by the user. Examples include the name of the client for whom the document was prepared, a date/time on which some event happened, a document number, or some Boolean status flag. Each custom file property has a value, and that value has a type.

Math

Math specifies the structure and appearance of equations in a document; it is specified with a root element of math.

Bibliography

Bibliography specifies the structure for all references stored within a document, for use in citations or a bibliography.

End of informative text.

Packages

An Office Open XML document is stored as a package, whose format is defined by Part 2: "Open Packaging Conventions". This subclause contains information regarding Office Open XML's use of OPC.

Throughout this Standard, the Open Packaging Conventions are referred to by their abbreviated name, OPC.

Constraints on Office Open XML's Use of OPC

While the OPC specification is designed for the representation of Office Open XML documents, it could also support a much broader range of applications. As a result, the use of some OPC features is restricted within Office Open XML documents. These additional requirements are discussed in the following subordinate subclauses. Any requirement not mentioned here is inherited from the OPC specification.

Part Names

An Office Open XML part name shall contain only ASCII characters, in non-escaped or escaped form. The following ASCII characters are permitted in non-escaped form: "!", "$", "%", "&", "'", "(", ")", "*", "+", ",", "-", ".", the decimal digits "0"–"9", ":", ";", "=", "@", the Latin alphabetic characters "A"–"Z" and "a"–"z", "_", and "~". All other ASCII characters are permitted only when escaped as an encoded triplet of the form "%HH", where H is a hexadecimal digit.]

Part Addressing

Parts in an Office Open XML package targeted by relationships are addressed in relationship markup through part names. External document resources targeted by a relationship can be addressed using both relative and absolute references.

Fragments

Fragment identifiers are supported as part of all Office Open XML external relationship targets and some Office Open XML internal relationship targets.

Physical Packages

Each Office Open XML document is implemented as a ZIP archive.

Interleaving

Office Open XML document parts shall be arranged contiguously in a package as defined by simple ordering.

Parts within an Office Open XML package shall not be interleaved. All parts shall be stored as complete ZIP items, and the interleaving functionality defined in Part 2 of this Standard shall not be used. [Note: Part 2 of this Standard specifies a method for interleaving parts, which is a very useful capability for stream processing. In order to simplify initial implementations of the Standard, interleaving is not used in this current version of the Office Open XML formats but it may be used in further versions of the standard or by other formats that leverage OPC. end note]

Unknown Parts

With the exception of relationship parts, all other parts in an Office Open XML document that are not the target of a valid relationship are considered unknown parts. Unknown parts shall be ignored on document consumption and can, but need not, be discarded on production.

Trash Items

Trash items represent parts that have been discarded or are no longer in use. Trash items shall not conform to OPC part naming guidelines as defined in Part 2 and shall not be associated with a content type. All trash items shall follow the naming scheme: [trash]/hhhh.dat where h represents a hexadecimal value.

[Example: A package has two parts that must be updated in-place but both parts have grown beyond their growth hints. The newer updated parts are added as new ZIP items while the original parts are renamed to:

[trash]/0000.dat[trash]/0001.dat

end example]

Invalid Parts

ZIP archive items that do not conform to OPC part naming guidelines or are not associated with a content type shall not be allowed in an Office Open XML document, with the exception of items specifically defined by Part 2: “Open Packaging Conventions” and trash items.

Unknown Relationships

All relationships not defined within this Standard are considered unknown relationships. Unknown relationships are valid within an Office Open XML document provided that they conform to relationship markup guidelines as defined by the OPC specification. Specifically:

Conforming consumers shall not fail to load a document containing unknown relationships.

Conforming producers are encouraged to roundtrip and preserve unknown relationships and their target parts.

Relationships in Office Open XML

In OPC, relationships describe references from parts to other internal resources in the package or to external resources. They represent the type of connection between a source part and a target resource, and make the connection directly discoverable without looking at the part contents, so they are quick to resolve.

The same ZIP item can be the target of multiple relationships. [Note: Having multiple paths to a target can make access to that target more convenient. end note]

Office Open XML imposes constraints on relationships, described in subsequent clauses of this part. Relationships in Office Open XML are either explicit or implicit.

For an explicit relationship, a resource is referenced from a source part’s XML using the Id attribute of a Relationship tag. [Example: A document part can have a relationship to a hyperlink only if that hyperlink's Relationship element’s Id attribute value is referenced explicitly by the document part’s XML. end example] [Note: Because this mechanism is used generically across multiple tag types, explicit relationships can be extracted from an Office Open XML document without prior knowledge of tag semantics. end note]. Certain relationships shall be explicit.. All other relationships are implicit [Note: The syntax for specifying an implicit relationship varies among tag types. end note]. Relationships that are required or permitted, and restrictions on those relationships are described in §10–15 of this Part.

[Example: Consider a WordprocessingML document that contains the following footnote sentence fragment, "… produced by Ecma1 (http://www.ecma-international.org/).", which contains a footnote and a hyperlink to a web site. The relationship from a source to a footnote is implicit while that to a hyperlink is explicit.

The Main Document part’s relationship file contains the following:

All footnotes for a WordprocessingML document are contained in the same Footnotes part. Let’s look at how the Main Document refers to the footnote. At the point at which the footnote reference is inserted, the following XML is present:

<w:r> <w:footnoteReference w:id="2"/></w:r>

The w:id=“2” refers to the footnote with id=2 in the Footnotes part, the relevant piece of which is:

<w:footnote w:id="2"> … Ecma is an international standards development organization (SDO). …</w:footnote>

In the case of the hyperlink, the main document part makes an explicit reference to this relationship when it refers to the hyperlink, by using the following:

<w:hyperlink r:id="rId7" w:history="1"> …</w:hyperlink>

The important distinction here is that there is no explicit reference to a relationship ID designating the Footnotes part. The reference to the footnote with id=2 is “understood” to be in the Footnotes part that must always exist if there are any footnotes in the document. end example]

[Example: The following figure shows how the source, relationship item, and the target relate to each other for implicit and explicit relationships, respectively. The target does not have to be a file, however.

The dots correspond to attributes of relevant elements. Where one attribute refers to a piece in another part, this is indicated by arrows. Solid arrows indicate that the value of the source directly corresponds to the value at the target (for instance, id=rId4 in the source part corresponds to id=rId4 in the relationship item).

Dotted arrows indicate that the value of the source only implicit corresponds to the value of the target (for instance, "footnoteReference" in the source indicates the type "footnotes" in the relationship item).

The main difference between the two types of relationship is that for implicit relationships, the id of the reference refers to an element with the same id in the target part, whereas for explicit relationships, the id refers to a relationship with the same id in the relationship item.

Both relationship types use the target URI of the relationship in the relationship item to locate the target.

For explicit relationships, the id in the source XML links to a relationship item with a direct explicit reference to the target. For implicit relationships, the relationship item is implied by the containing tag (e.g., footnote) and the id in the source XML is used to locate the correct element within the implied target.

end example]

[Example: The following figure shows the implicit relationship for the footnote example described earlier.

end example]

[Example: The following figure shows an explicit relationship.

end example]

Markup Compatibility and Extensibility

Office Open XML documents are designed to allow for innovation by extending their capabilities via a scheme defined by Part 5: "Markup Compatibility and Extensibility". This subclause contains information regarding Office Open XML's use of the Markup Compatibility constructs.

Constraints on Office Open XML's Use of Markup Compatibility and Extensibility

While the Markup Compatibility and Extensibility specification is designed for and used by Office Open XML documents, it could also be used to support a much broader range of applications. As a result, the use of some Markup Compatibility and Extensibility features is restricted within Office Open XML documents. These additional requirements are discussed in the following subordinate subclauses. Any requirement not mentioned here is inherited from the Markup Compatibility and Extensibility specification.

PreserveElements and PreserveAttributes

The PreserveElements and PreserveAttributes elements, as defined in Part 5, allow a markup language to specify the conditions under which extensions should be round-tripped, even when their contents are edited. Within the context of the markup languages explicitly defined by this Standard, no such conditions are specified, and therefore applications are not obliged to support these hints at any point in an Office Open XML document. Instead, the well-defined extensibility constructs defined below should be used.

All other constructs defined in Part 5 shall be supported.

Office Open XML Native Extensibility Constructs

Clause 12 of Part 5 specifies the ability for a markup language to define additional constructs for extensibility of a specific markup language. Within the context of Office Open XML documents, the extLst element(s) defined in individual markup languages shall allow the round-tripping of all unknown content regardless of the state of the PreserveElements and PreserveAttributes elements. See Part 4 for additional information on the valid use of the extLst construct.

WordprocessingML

This clause contains specifications for relationship items and parts that are specific to WordprocessingML. Parts that can occur in a WordprocessingML document, but are not WordprocessingML-specific, are specified in §15.2. Unless stated explicitly, all references to relationship items, content-type items, and parts in this clause refer to WordprocessingML ZIP items.

Glossary of WordprocessingML-Specific Terms

The following terms are used in the context of a WordprocessingML document:

comment — A note that an author or reviewer attaches to a piece of text in a document. Although a consumer may chose to display comments, they are not considered part of the body of the document. A comment includes the text of the note, the comment author's name and initials, and date of creation, among other things.

document setting — A reusable element in a template. [Note: Such elements include boilerplate text, cover pages, equations, footers, headers, tables, text boxes, and watermarks. end note]

glossary document — An additional WordprocessingML document story used to store reusable fragments of rich WordprocessingML content. It is called the glossary document as this story contains one or more fragments that can be indexed and extracted by name, like items in a glossary.

master document — A document that is the parent of one or more subdocuments. [Note: A master document can be used to manage a multipart document, such as a book having several chapters. In such as case, the master document might contain the cover page, front matter, table of contents, and cross-reference index, while each chapter and appendix resides in its own subdocument. end note]

section — A portion of a document in which certain page formatting options can be set. [Note: A new section is created to change such properties as line numbering, number of columns, or headers and footers. end note]

subdocument — A piece of a master document. [Note: A chapter or appendix might be a subdocument in a book. end note]

supplementary document storage location — A part within a WordprocessingML document in which fragments of WordprocessingML content can be stored separate from the printed page. See also glossary document

template — A document that is a pattern for creating other documents. A template can contain text, formatting, and graphics, among other things, such that documents based on it automatically have access to these elements.

Package Structure

A WordprocessingML package shall contain a package-relationship item and a content-type item. The package-relationship item shall contain implicit relationships with targets of the following type:

One Main Document part (§11.3.10)

The package-relationship item is permitted to contain implicit relationships with targets of the following type:

Digital Signature Origin (§15.2.6)

File Property parts (§15.2.11) (Application-Defined File Properties, Core File Properties, and Custom File Properties), as appropriate.

Thumbnail (§15.2.14).

The required and optional relationships between parts are defined in §11.3 and its subordinate clauses.

[Example: The following package represents the minimal conformant WordprocessingML package as defined by this Standard:

First, the content type for relationship parts and the Main Document part (the only required part) must be defined (physically located at /[Content_Types].xml in the package):

</Types>

Next, the single required relationship (the package-level relationship to the Main Document part) must be defined (physically located at /_rels/.rels in the package):

</Relationships>

Finally, the minimum content for the Main Document part must be defined (physically located at /document.xml in the package):

<w:document xmlns:w="…"> <w:body> <w:p/> </w:body></w:document>

end example]

[Example: Consider a WordprocessingML document that is an early draft of this Standard. Here’s an example of the hierarchical folder structure that might be used for the ZIP items in the package for that document. As shown, one part, Main Document (stored in the ZIP item /word/document.xml), has its own relationship item:

/[Content_Types].xmlContent-type item/_rels/.relsPackage-relationship item/docProps/app.xmlApplication-Defined File Properties part/docProps/core.xmlCore File Properties part/word/document.xml Main Document part/word/_rels/document.xml.relsPart-relationship item

/word/comments.xmlComment part/word/endnotes.xmlEndnotes part/word/fontTable.xmlFont Table part

/word/footer1.xmlFooter parts/word/footer2.xml/word/footer3.xml/word/footer4.xml

/word/footnotes.xmlFootnotes part

/word/header1.xmlHeader parts/word/header2.xml/word/header3.xml/word/header4.xml/word/header5.xml/word/header6.xml

/word/numbering.xmlNumbering Definitions part/word/settings.xmlDocument Settings part/word/styles.xmlStyle Definitions part/word/theme/theme1.xmlTheme part

The package-relationship item contains the following:

end example]

Part Summary

The subclauses subordinate to this one describe in detail each of the part types specific to WordprocessingML. [Note: For convenience, information from those subclauses is summarized in the following table:

Part

Relationship Target of

Root Element

Ref.

Alternative Format Import

Comments, Endnotes, Footer, Footnotes, Header, or Main Document

Not applicable

§11.3.1

Comments

Glossary Document or Main Document

comments

§11.3.2

Document Settings

Glossary Document or Main Document

settings

§11.3.3

Endnotes

Glossary Document or Main Document

endnotes

§11.3.4

Font Table

Glossary Document or Main Document

fonts

§11.3.5

Footer

Glossary Document or Main Document

ftr

§11.3.6

Footnotes

Glossary Document or Main Document

footnotes

§11.3.7

Glossary Document

Main Document

glossaryDocument

§11.3.8

Header

Glossary Document or Main Document

hdr

§11.3.9

Main Document

WordprocessingML package

document

§11.3.10

Numbering Definitions

Glossary Document or Main Document

numbering

§11.3.11

Style Definitions

Glossary Document or Main Document

styles

§11.3.12

Web Settings

Glossary Document or Main Document

webSettings

§11.3.13

end note]

Alternative Format Import Part

Content Type:

Any content, support for which is application-defined.

[Note: Some examples of formats which might be supported include:

Text = application/txt

RTF = application/rtf

HTML = application/html

XML = application/xml

end note]

Root Namespace:

not applicable

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/aFChunk

An alternative format import part allows content specified in an alternate format (HTML, MHTML, RTF, earlier versions of WordprocessingML, or plain text) to be embedded directly in a WordprocessingML document in order to allow that content to be migrated to the WordprocessingML format.

Any document part that permits a p element can also contain an altChunk element, whose id attribute refers to a relationship. That relationship shall target a part within the package, which contains the content to be imported into this WordprocessingML document.

A package is permitted to contain zero or more Alternative Format Import parts, each of which shall have a corresponding alternate format file that is the target of an explicit relationship from a Comments (§11.3.2), Endnotes (§11.3.4), Footer (§11.3.6), Footnotes (§11.3.7), Header (§11.3.9), or Main Document (§11.3.10) part. This relationship shall be explicitly referenced using its relationship ID in the source part using the appropriate XML syntax (i.e.; in the id attribute on the altChunk element), and the presence of this relationship without such a reference shall be considered invalid.

A WordprocessingML consumer shall treat the contents of such legacy text files as if they were formatted using equivalent WordprocessingML, and if that consumer is also a WordprocessingML producer, it shall emit the legacy text in WordprocessingML format.

This Standard does not specify how one might create a WordprocessingML package that contains Alternative Format Import relationships and altChunk elements.

However, a conforming producer shall not create a WordprocessingML package that contains Alternative Format Import relationships and elements. [Note: The Alternative Format Import machinery provides a one-time conversion facility. A producer could have an extension that allows it to generate a package containing these relationships and elements, yet when run in conforming mode, does not do so. end note]

[Example: The following Main Document part-relationship item contains a relationship to an Alternative Format Import part:

The Main Document part contains the following XML fragment:

<w:body> … <w:p/> <w:altChunk r:id="rId5"/> <w:p/> …</w:body>

which results in the entire contents of Demo.html being converted and brought into the document at that point (assuming that the content type of Demo.html is supported by the application consuming this WordprocessingML file). end example]

An Alternative Format Import part shall be located within the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal).

An Alternative Format Import part shall not have any explicit or implicit relationships to parts defined by this Standard.

Comments Part

Content Type:

application/vnd.openxmlformats-officedocument.wordprocessingml.comments+xml

Root Namespace:

http://schemas.openxmlformats.org/wordprocessingml/2006/main

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/comments

An instance of this part type contains the information about each comment in the document.

A package shall contain no more than two Comments parts. If it exists, one instance of that part shall be the target of an implicit relationship from the Main Document (§11.3.10) part, and the other shall be the target of an implicit relationship from the Glossary Document (§11.3.8) part.

[Example: The following Main Document part-relationship item contains a relationship to the Contents part, which is stored as the ZIP item comment.xml:

end example]

The root element for a Comment part shall be comments.

[Example:

<w:comments … > <w:comment> … </w:comment> …</w:comments>

end example]

The XML markup for a comment in a Main Document part uses the commentReference element.

[Example: Consider the case in which the Main Document part contains the text "… in the Standard.", and there is an comment inserted immediately after the period:

<w:p …> … <w:r> <w:t>... in the Standard.</w:t> </w:r> <w:r> <w:commentReference w:id="1"/> </w:r></w:p>

end example]

Each comment has a corresponding comment element in the Comments part, which contains the text of the comment.

[Example: The text of the comment is "This is my comment.":

<w:comments xmlns:w="…" <w:comment w:id="1"> <w:p> <w:r> <w:t>This is my comment.</w:t> </w:p> </w:comment></w:comments>

end example]

A Comments part shall be located within the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal).

A Comments part is permitted to contain explicit relationships to the following parts defined by this Standard:

Alternative Format Import (§11.3.1)

Chart (§14.2.1)

Diagrams: Diagram Colors(§14.2.3), Diagram Data(§14.2.4), Diagram Layout Definition(§14.2.5) and Diagram Styles (§14.2.6)

Embedded Control Persistence (§15.2.8)

Embedded Object (§15.2.9)

Embedded Package (§15.2.10)

Hyperlinks (§15.3)

Images (§15.2.13)

Video (§15.2.16)

A Comments part shall not have any implicit or explicit relationships to any other part defined by this Standard.

Document Settings Part

Content Type:

application/vnd.openxmlformats-officedocument.wordprocessingml.settings+xml

Root Namespace:

http://schemas.openxmlformats.org/wordprocessingml/2006/main

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/settings

An instance of this part type contains all the document's properties.

A package shall contain no more than two Document Settings parts. If it exists, one instance of that part shall be the target of an implicit relationship from the Main Document (§11.3.10) part, and the other shall be the target of an implicit relationship from the Glossary Document (§11.3.8) part.

[Example: The following Main Document part-relationship item contains a relationship to a Document Settings part, which is stored in the ZIP item documentProperties1.xml:

end example]

The root element for a part of this content type shall be settings.

[Example:

<w:settings … > … <w:defaultTabStop w:val="360"/> <w:footnotePr> … </w:footnotePr>

<w:endnotePr> … </w:endnotePr>

<w:rsids> … </w:rsids> …</w:settings>

end example]

A Document Settings part shall be located within the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal).

A Document Settings part is permitted to contain explicit relationships to the following parts defined by this Standard:

Document Template (§11.4)

Mail Merge Data Source (§11.7)

Mail Merge Header Data Source (§11.8)

XSL Transformation (§11.9)

A Document Settings part shall not have any implicit or explicit relationships to any other part defined by this Standard.

Endnotes Part

Content Type:

application/vnd.openxmlformats-officedocument.wordprocessingml.endnotes+xml

Root Namespace:

http://schemas.openxmlformats.org/wordprocessingml/2006/main

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/endnotes

An instance of this part type contains all the endnotes for the document.

A package shall contain no more than two Endnotes parts. If it exists, one instance of that part shall be the target of an implicit relationship from the Main Document (§11.3.10) part, and the other shall be the target of an implicit relationship from the Glossary Document (§11.3.8) part.

[Example: The following Main Document part-relationship item contains a relationship to the Endnotes part, which is stored as the ZIP item endnotes.xml:

end example]

The root element for an Endnotes part shall be endnotes.

[Example:

<w:endnotes xmlns:w="…" …> <w:endnote …> … </w:endnote> <w:endnote …> … </w:endnote></w:endnotes>

end example]

The XML markup for an endnote in a Main Document part uses the endnoteReference element.

[Example: Consider the case in which the Main Document part contains the text "… in the Standard.", and there is an endnote inserted immediately after the period:

<w:p …> … <w:r> <w:t>... in the Standard.</w:t> </w:r> <w:r> <w:rPr> <w:rStyle w:val="EndnoteReference"/> </w:rPr> <w:endnoteReference w:id="5"/> </w:r></w:p>

end example]

Each endnote has a corresponding endnote element in the Endnotes part, which contains the text of the endnote, and the endnoteRef element.

[Example: The text of the endnote is "This can be downloaded from http://www.aabbcc.com/index.html." where "http://www.aabbcc.com/index.html" is marked as a hyperlink:

<w:endnotes xmlns:w="…"> <w:endnote w:id="5"> <w:p> <w:r> <w:rPr> <w:rStyle w:val="EndnoteReference"/> </w:rPr> <w:endnoteRef/> </w:r>

<w:r> <w:t xml:space="preserve"> This can be downloaded from </w:t> </w:r>

<w:hyperlink r:id="rId2"> <w:r> <w:rPr> <w:rStyle w:val="Hyperlink"/> </w:rPr> <w:t>http://www.aabbcc.com/index.html</w:t> </w:r> </w:hyperlink>

<w:r> <w:t>.</w:t> </w:p> </w:endnote></w:endnotes>

end example]

An Endnotes part shall be located within the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal).

An Endnotes part is permitted to contain explicit relationships to the following parts defined by this Standard:

Alternative Format Import (§11.3.1)

Chart (§14.2.1)

Diagrams: Diagram Colors(§14.2.3), Diagram Data(§14.2.4), Diagram Layout Definition(§14.2.5) and Diagram Styles (§14.2.6)

Embedded Control Persistence (§15.2.8)

Embedded Object (§15.2.9)

Embedded Package (§15.2.10)

Hyperlinks (§15.3)

Images (§15.2.13)

Video (§15.2.16)

An Endnotes part shall not have any implicit or explicit relationships to any other part defined by this Standard.

Font Table Part

Content Type:

application/vnd.openxmlformats-officedocument.wordprocessingml.fontTable+xml

Root Namespace:

http://schemas.openxmlformats.org/wordprocessingml/2006/main

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/fontTable

An instance of this part type contains information about each of the fonts used by content in the document. When a consumer reads a WordprocessingML document, it shall use this information to determine which fonts to use to display the document when the specified fonts are not available on the consumer’s system.

A package shall contain no more than two Font Table parts. If it exists, one instance of that part shall be the target of an implicit relationship in the part-relationship item for the Main Document (§11.3.10) part, and the other instance shall be the target of an implicit relationship from the Glossary Document (§11.3.8) part.

[Example: The following Main Document part-relationship item contains a relationship to the Font Table part, which is stored as the ZIP item fontTable.xml:

end example]

The root element for a part of this content type shall be fonts.

[Example:

<w:fonts … > <w:font w:name="Calibri"> <w:panose1 w:val="020F0502020204030204"/> <w:charset w:val="00"/> <w:family w:val="swiss"/> <w:pitch w:val="variable"/> <w:sig w:usb0="A00002EF" w:usb1="4000207B" w:usb2="00000000" w:usb3="00000000" w:csb0="0000009F" w:csb1="00000000"/> </w:font></w:fonts>

end example]

A Font Table part shall be located within the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal).

A Font Table part is permitted to contain explicit relationships to the following parts defined by this Standard:

Fonts (§15.2.12)

A Font Table part shall not have any implicit or explicit relationships to any other part defined by this Standard.

Footer Part

Content Type:

application/vnd.openxmlformats-officedocument.wordprocessingml.footer+xml

Root Namespace:

http://schemas.openxmlformats.org/wordprocessingml/2006/main

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/footer

An instance of this part type contains the information about a footer displayed for one or more sections.

A package is permitted to contain zero or one Footer part for each kind of footer (first page, odd page, or even page) in each section of the document. Each Footer part shall be the target of an explicit relationship in the part-relationship item for the Main Document (§11.3.10) part, or the Glossary Document (§11.3.8) part.

[Example: The Main Document part-relationship item contains one relationship, for the odd footer part, which is stored as the ZIP item footer3.xml:

end example]

The root element for a Footer part type shall be ftr.

[Example:

<w:ftr xmlns:w="…" …> …</w:ftr>

end example]

The XML markup for a footer in a section of a Main Document part involves the footerReference element in that section's sectPr element which explicitly references the relationship for the header.

[Example: Consider the case in which a section in the Main Document part contains odd and even headers, and an odd footer:

<w:document xmlns:w="…"> … <w:sectPr> <w:footerReference w:val="rId89" w:type="default"/> <w:footerReference w:val="rId90" w:type="even"/> <w:footerReference w:val="rId91" w:type="first"/> <w:type w:val="oddPage"/> <w:pgSz w:w="11909" w:h="16834" w:code="9"/> <w:pgMar w:top="1440" w:right="1152" w:bottom="1440" w:left="1152" w:header="720" w:footer="720" w:gutter="0"/> <w:lnNumType w:countBy="1"/> <w:pgNumType w:numFmt="lowerRoman"/> <w:cols w:space="720"/> </w:sectPr></w:document>

end example]

Each footer has a corresponding ftr element in a Footer part, which contains the text of the footer.

[Example: Here is the odd footer corresponding to the example above. It has the page number centered and displayed using lowercase Roman numerals (as set by the pgNumType element above):

<w:ftr xmlns:w="…"> <w:p> <w:pPr> <w:pStyle w:val="Centered"/> </w:pPr>

<w:fldSimple w:instr="PAGE">

<w:r> <w:rPr> <w:noProof/> </w:rPr> <w:t>i</w:t> </w:r> </w:fldSimple> </w:p></w:ftr>

end example]

A Footer part shall be located within the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal).

A Footer part is permitted to have explicit relationships to the following parts defined by this Standard:

Alternative Format Import (§11.3.1)

Chart (§14.2.1)

Diagrams: Diagram Colors(§14.2.3), Diagram Data(§14.2.4), Diagram Layout Definition(§14.2.5) and Diagram Styles (§14.2.6)

Embedded Control Persistence (§15.2.8)

Embedded Object (§15.2.9)

Embedded Package (§15.2.10)

Hyperlinks (§15.3)

Images (§15.2.13)

Video (§15.2.16)

A Footer part shall not have any implicit or explicit relationships to any other part defined by this Standard.

Footnotes Part

Content Type:

application/vnd.openxmlformats-officedocument.wordprocessingml.footnotes+xml

Root Namespace:

http://schemas.openxmlformats.org/wordprocessingml/2006/main

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/footnotes

An instance of this part type contains all the footnotes for the document.

A package shall contain no more than two Footnotes parts. If it exists, one instance of that part shall be the target of an implicit relationship from the Main Document (§11.3.10) part, and the other shall be the target of an implicit relationship from the Glossary Document (§11.3.8) part.

[Example: The Main Document part-relationship item contains a relationship to the Footnotes part, which is stored as the ZIP item footnotes.xml:

end example]

The root element for a Footnotes part shall be footnotes.

[Example:

<w:footnotes xmlns:w="…" …> <w:footnote …> … </w:footnote> <w:footnote …> … </w:footnote></w:footnotes>

end example]

The XML markup for a footnote in a Main Document part involves the footnoteReference element.

[Example: Consider the case in which the Main Document part contains the text "… in the Standard.", and there is a footnote inserted immediately after the period:

<w:p …> … <w:r> <w:t>... in the Standard.</w:t> </w:r> <w:r> <w:rPr> <w:rStyle w:val="FootnoteReference"/> </w:rPr> <w:footnoteReference w:id="5"/> </w:r></w:p>

end example]

Each footnote has a corresponding footnote element in the Footnotes part, which contains the text of the footnote and the footnoteRef element.

[Example: The text of the footnote is "This can be downloaded from http://www.aabbcc.com/index.html." where "http://www.aabbcc.com/index.html" is marked as a hyperlink:

<w:footnotes xmlns:w="…" <w:footnote w:id="5"> <w:p> <w:r> <w:rPr> <w:rStyle w:val="FootnoteReference"/> </w:rPr> <w:footnoteRef/> </w:r>

<w:r> <w:t xml:space="preserve">This can be downloaded from </w:t> </w:r>

<w:hyperlink r:id="rId2" w:history="1"> <w:r> <w:rPr> <w:rStyle w:val="Hyperlink"/> </w:rPr> <w:t>http://www.aabbcc.com/index.html</w:t> </w:r> </w:hyperlink>

<w:r> <w:t>.</w:t> </w:r> </w:p> </w:footnote>

</w:footnotes>

end example]

A Footnotes part shall be located within the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal).

A Footnotes part is permitted to have explicit relationships to the following parts defined by this Standard:

Alternative Format Import (§11.3.1)

Chart (§14.2.1)

Diagrams: Diagram Colors(§14.2.3), Diagram Data(§14.2.4), Diagram Layout Definition(§14.2.5) and Diagram Styles (§14.2.6)

Embedded Control Persistence (§15.2.8)

Embedded Object (§15.2.9)

Embedded Package (§15.2.10)

Hyperlinks (§15.3)

Images (§15.2.13)

Video (§15.2.16)

A Footer part shall not have any implicit or explicit relationships to any other part defined by this Standard.

Glossary Document Part

Content Type:

application/vnd.openxmlformats-officedocument.wordprocessingml.document.glossary+xml

Root Namespace:

http://schemas.openxmlformats.org/wordprocessingml/2006/main

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/glossaryDocument

An instance of this part type is a supplementary document storage location which stores the definition and content for content that shall be carried with the document for future insertion and/or use, but which shall not be visible within the contents of the main document story. [Example: A legal contract template might include one or more optional clauses that shall not appear in the document until those clauses are inserted explicitly via a user action. To store these optional clauses until they are inserted, their contents are placed in the glossary document part. end example]

[Note: This part is intended for storage of optional "document fragments" which are often used to perform document assembly. The use of the word glossary is a reference to the fact that each of these entries was historically referenced by its first word in legacy word processing applications, like definitions of terms in a traditional glossary. end note]

The root element for a part of this content type shall be glossaryDocument.

[Example: The following part contains two building blocks. The first block is named "rainbow colors", belongs to a category called "Misc", belongs to a gallery called "docParts", and contains the text "The colors … and violet." The details of the second block have been omitted:

<w:glossaryDocument xmlns:w="…" > <w:docParts> <w:docPart> <w:docPartPr> <w:name w:val="rainbow colors"/> <w:style w:val="Normal"/> <w:category> <w:name w:val="Misc"/> <w:gallery w:val="docParts"/> </w:category> </w:docPartPr>

<w:docPartBody> <w:p> <w:r> <w:t>The colors of the rainbow are red, orange, yellow, green, blue, indigo, and violet.</w:t> </w:r> </w:p> </w:docPartBody> </w:docPart>

<w:docPart> … </w:docPart> </w:docParts></w:glossaryDocument>

end example]

A package shall contain at most one Glossary Document part, and that part shall be the target of an implicit relationship from the Main Document (§11.3.10) part.

[Example: The following Main Document part-relationship item contains a relationship to a Glossary Document part, which is stored in the ZIP item glossary/document.xml:

end example]

A Glossary Document part shall be located within the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal).

A Glossary Document part is permitted to have implicit relationships to the following parts defined by this Standard:

Comments (§11.3.2)

Document Settings (§11.3.3)

Endnotes (§11.3.4)

Font Table (§11.3.5)

Footnotes (§11.3.7)

Numbering Definitions (§11.3.11)

Style Definitions (§11.3.11)

A Glossary Document part is permitted to have explicit relationships to the following parts defined by this Standard:

Alternative Format Import (§11.3.1)

Chart (§14.2.1)

Diagrams: Diagram Colors (§14.2.3), Diagram Data (§14.2.4), Diagram Layout Definition (§14.2.5) and Diagram Styles (§14.2.6)

Embedded Control Persistence (§15.2.8)

Embedded Object (§15.2.9)

Embedded Package (§15.2.10)

Footer (§11.3.6)

Header (§11.3.9)

Hyperlinks (§15.3)

Images (§15.2.13)

Printer Settings (§15.2.14)

Video (§15.2.16)

A Glossary Document part shall not have implicit or explicit relationships to any other part defined by this Standard.

Header Part

Content Type:

application/vnd.openxmlformats-officedocument.wordprocessingml.header+xml

Root Namespace:

http://schemas.openxmlformats.org/wordprocessingml/2006/main

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/header

An instance of this part type contains the information about a header displayed for one or more sections.

A package shall contain zero or one Header part for each kind of header (first page, odd page, or even page) in each section of the document. Each Header part shall be the target of an explicit relationship from the Main Document (§11.3.10) part or the Glossary Document (§11.3.8) part.

[Example: The Main Document part-relationship item contains two relationships: one for the even header part (which is stored as the ZIP item header2.xml) and one for the odd header part (which is stored as the ZIP item header3.xml):

end example]

The root element for a Header part shall be hdr.

[Example:

<w:hdr xmlns:w="…" …> …</w:hdr>

end example]

The XML markup for a header in a section of a Main Document part involves the headerReference element in that section's sectPr element.

[Example: Consider the case in which a section in the Main Document part contains odd and even headers, and an odd footer:

<w:body> … <w:sectPr w:rsidR="00363F31" w:rsidSect="008D4B40"> <w:headerReference w:val="rId89" w:type="default"/> <w:headerReference w:val="rId90" w:type="even"/> <w:headerReference w:val="rId91" w:type="first"/> <w:type w:val="oddPage"/> <w:pgSz w:w="11909" w:h="16834" w:code="9"/> <w:pgMar w:top="1440" w:right="1152" w:bottom="1440" w:left="1152" w:header="720" w:footer="720" w:gutter="0"/> <w:lnNumType w:countBy="1"/> <w:pgNumType w:fmt="lowerRoman"/> <w:cols w:space="720"/> </w:sectPr></w:body>

end example]

Each header has a corresponding hdr element in a Header part, which contains the text of the header.

[Example: Here is the even header corresponding to the examples above:

<w:hdr xmlns:w="…"> <w:p> <w:pPr> <w:pStyle w:val="Header"/> </w:pPr> <w:r> <w:t>My Test Document</w:t> </w:r> </w:p></w:hdr>

Here is the odd header corresponding to the examples above:

<w:hdr xmlns:w="…"> <w:p> <w:pPr> <w:pStyle w:val="Header"/> </w:pPr> <w:r> <w:tab/> <w:t>Table of Contents</w:t> </w:r> </w:p></w:hdr>

end example]

A Header part shall be located within the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal).

A Header part is permitted to have explicit relationships to the following parts defined by this Standard:

Alternative Format Import (§11.3.1)

Chart (§14.2.1)

Diagrams: Diagram Colors(§14.2.3), Diagram Data(§14.2.4), Diagram Layout Definition(§14.2.5) and Diagram Styles (§14.2.6)

Embedded Control Persistence (§15.2.8)

Embedded Object (§15.2.9)

Embedded Package (§15.2.10)

Hyperlinks (§15.3).

Images (§15.2.13)

Video (§15.2.16)

A Header part shall not have any implicit or explicit relationships to other parts defined by this Standard.

Main Document Part

Content Type(s):

application/vnd.openxmlformats-officedocument.wordprocessingml.main+xml

application/vnd.openxmlformats-officedocument.wordprocessingml.template.main+xml

Root Namespace:

http://schemas.openxmlformats.org/wordprocessingml/2006/main

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/officeDocument

An instance of this part type contains the body of the document.

A package shall contain a Main Document part (§11.3.10) part. The Main Document part shall be the target of a relationship in the package-relationship item.

The root element for a part of this content type shall be document.

[Example: Given the following package-relationship item excerpt:

/word/document.xml" contains the following:

<w:document …> <w:body> … </w:body></w:document>

end example]

A Main Document part shall be located within the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal).

A Main Document part is permitted to have implicit relationships to the following parts defined by this Standard:

Additional Characteristics (§15.2.1)

Bibliography (§15.2.3)

Comments (§11.3.2)

Custom XML Data Storage (§15.2.4)

Document Settings (§11.3.3)

Endnotes (§11.3.4)

Font Table (§11.3.5)

Footnotes (§11.3.7)

Glossary Document (§11.3.8)

Numbering Definitions (§11.3.11)

Style Definitions (§11.3.12)

Theme (§14.2.7)

Thumbnail (§15.2.14)

A Main Document part is permitted to contain explicit relationships to the following parts defined by this Standard:

Alternative Format Import (§11.3.1)

Chart (§14.2.1)

Diagrams: Diagram Colors(§14.2.3), Diagram Data(§14.2.4), Diagram Layout Definition(§14.2.5) and Diagram Styles (§14.2.6)

Embedded Control Persistence (§15.2.8)

Embedded Object (§15.2.9)

Embedded Package (§15.2.10)

Footer (§11.3.6)

Header (§11.3.9)

Hyperlinks (§15.3)

Images (§15.2.13)

Printer Settings (§15.2.14)

Subdocument (§11.6)

Video (§15.2.16)

A Main Document shall not have implicit or explicit relationships to any other part defined by this Standard.

Numbering Definitions Part

Content Type:

application/vnd.openxmlformats-officedocument.wordprocessingml.numbering+xml

Root Namespace:

http://schemas.openxmlformats.org/wordprocessingml/2006/main

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/numbering

An instance of this part type contains a definition for the structure of each unique numbering definition in this document.

[Example: If a set of paragraphs are added to a document which have a circle bullet at the first level, a square bullet at the second level, and a checkmark bullet at the third level, such as the following:

First level

Second level

Third level

The numbering definition part will contain the definition for each of these levels (their bullet style, indent, etc.) even if the second and third levels are not actually used in the document end example]

A package shall contain no more than two Numbering Definitions parts. If they exist, one instance of that part shall be the target of an implicit relationship from the Main Document (§11.3.10) part, and the other shall be the target of an implicit relationship from the Glossary Document (§11.3.8) part.

[Example:

end example]

The XML markup for a list usage involves a reference to a numbering definition via the child elements of the numPr element.

[Example: Here we have a paragraph set using the style Text, followed by a list of things which have the paragraph style ListBullet, followed by another paragraph set using the style Text:

<w:p> <w:pPr> <w:pStyle w:val="Text"/> </w:pPr> <w:r> <w:t>The kinds of fruit needed are:</w:t> </w:r></w:p>

<w:p> <w:pPr> <w:pStyle w:val="ListBullet"/> <w:numPr> <w:ilvl w:val="0" /> <w:numId w:val="5" /> </w:numPr> </w:pPr> <w:r> <w:t>Apples</w:t> </w:r></w:p>

<w:p> <w:pPr> <w:pStyle w:val="ListBullet"/> <w:numPr> <w:ilvl w:val="0" /> <w:numId w:val="5" /> </w:numPr> </w:pPr> <w:r> <w:t>Oranges</w:t> </w:r></w:p>

<w:p> <w:pPr> <w:pStyle w:val="Text"/> </w:pPr> <w:r> <w:t>Other items may be needed too.</w:t> </w:r></w:p>

end example]

The root element for a Numbering Definition part shall be numbering, with each numbering definition being defined by an abstractNum element.

[Example:

<w:numbering xmlns:w="…"> <w:abstractNum w:numId="11"> <w:nsid w:val="394E2425"/> <w:multiLevelType w:val="hybridMultilevel"/> <w:tmpl w:val="F628E89A"/> <w:lvl w:ilvl="0" w:tplc="151C4798"> <w:start w:val="1"/> <w:numFmt w:val="bullet"/> <w:pStyle w:val="ListBullet"/> <w:lvlText w:val="…"/> <w:lvlJc w:val="left"/>

<w:pPr> <w:tabs> <w:tab w:val="list" w:pos="720"/> </w:tabs> <w:ind w:left="720" w:hanging="360"/> </w:pPr>

<w:rPr> <w:rFonts w:ascii="Symbol" w:hAnsi="Symbol" w:hint="default"/> </w:rPr> </w:lvl>

… </w:abstractNum></w:numbering>

end example]

A Numbering Definitions part shall be located within the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal).

A Numbering Definitions part is permitted to contain explicit relationships to the following parts defined by this Standard:

Images (§15.2.13)

A Numbering Definitions part shall not have any implicit or explicit relationships to any other part defined by this Standard.

Style Definitions Part

Content Type:

application/vnd.openxmlformats-officedocument.wordprocessingml.styles+xml

Root Namespace:

http://schemas.openxmlformats.org/wordprocessingml/2006/main

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/styles

An instance of this part type contains the definition for a set of styles used by this document.

A package shall contain at most two Style Definitions parts. One instance of that part shall be the target of an implicit relationship from the Main Document (§11.3.10) part, and the other shall be the target of an implicit relationship in from the Glossary Document (§11.3.8) part.

[Example:

end example]

The root element for a Styles Definition part shall be styles, which is a container for one or more style elements.

[Example: Here is the style ListBullet (which is used in a Main Document Part in §11.3.10):

<w:styles xmlns:wx="…" xmlns:w="…" … xml:space="preserve"> <w:style w:type="paragraph" w:styleId="ListBullet"> <w:name w:val="List Bullet"/> <w:basedOn w:val="Text"/> <w:autoRedefine/> <w:rsid w:val="00081289"/>

<w:pPr> <w:pStyle w:val="ListBullet"/> <w:numPr> <w:numId w:val="1"/> </w:numPr> <w:tabs> <w:tab w:val="clear" w:pos="360"/> </w:tabs> <w:ind w:left="648"/> </w:pPr> </w:style></w:styles>

end example]

A Style Definitions part shall be located within the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal).

A Style Definitions part shall not have implicit or explicit relationships to any part defined by this Standard.

Web Settings Part

Content Type:

application/vnd.openxmlformats-officedocument.wordprocessingml.webSettings+xml

Root Namespace:

http://schemas.openxmlformats.org/wordprocessingml/2006/main

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/webSettings

An instance of this part type contains the definition for web-specific settings used by this document.

A package shall contain at most two Web Settings parts. One instance of that part shall be the target of an implicit relationship from the Main Document (§11.3.10) part, and the other shall be the target of an implicit relationship from the Glossary Document (§11.3.8) part.

[Example:

end example]

The root element for a Web Settings part shall be webSettings.

[Example:

<w:webSettings …> <w:frameset> … <w:frame> <w:sz w:val="216" /> <w:name w:val="Frame2" /> <w:sourceFileName r:id="rId1" /> </w:frame>

<w:frame> <w:name w:val="Frame1" /> <w:sourceFileName r:id="rId2" /> </w:frame> </w:frameset></w:webSettings>

end example]

A Web Settings part shall be located within the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal).

A Web Settings part is permitted to contain explicit relationships to the following parts defined by this Standard:

Frameset (§11.5)

A Web Settings part shall not contain implicit or explicit relationships to any other part defined by this Standard.

Document Template

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/attachedTemplate

A document template can be represented by an instance of a WordprocessingML package, and contains styles, numbering definitions, and so on that are made available when documents based on that template are edited. A WordprocessingML document can refer to another document as its document template, by having a Document Settings part (§11.3.3) that contains an explicit relationship to the file location of the necessary document template using the id attribute on the attachedTemplate element.

[Example: Consider a document specifying a document template located at c:\template.docx:

The document’s Document Settings part contains an attachedTemplate element that explicitly references this relationship:

<w:settings … > <w:attachedTemplate r:id="rId1"/></w:settings>

end example]

Framesets

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/frame

A frameset is a WordprocessingML document which specifies the location and placement of other WordprocessingML documents (which, when used in this context, are referred to as frames). A frameset shall be represented by an instance of a WordprocessingML document with a Web Settings part (§11.3.13) whose relationship item targets each of that frameset's frames.

[Example: Consider a frameset document having two frames. The frameset's Web Settings part-relationships item contains the following, in which frame1.docx and frame2.docx are packages containing the corresponding frames:

The frameset document’s Web Settings part contains a frameset element that references its frames:

<w:webSettings …> <w:frameset> … <w:frame> <w:sz w:val="216" /> <w:name w:val="Frame2" /> <w:sourceFileName r:id="rId1" /> </w:frame>

<w:frame> <w:name w:val="Frame1" /> <w:sourceFileName r:id="rId2" /> </w:frame> </w:frameset></w:webSettings>

end example]

A frame shall be represented by an instance of a WordprocessingML package.

A frame shall be located external to the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be External).

Master Documents and Subdocuments

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/subDocument

A master document shall be represented by an instance of a WordprocessingML document whose Main Document (§11.3.10) part targets each of that master document’s subdocuments.

[Rationale: Sometimes, it is convenient to deal with a document as a collection of pieces, especially when those pieces might be edited by different authors in a collaborative group. Perhaps it simply makes sense to think about a book as a collection of chapters rather than as one big document. The breaking-up of a document into such pieces can be achieved by having a master document with one or more subdocuments. end rationale]

[Example: Consider a master document, whose three subdocuments are called Start, Middle, and End, respectively. Master’s Main Document part has a corresponding relationships part that contains the following, in which Start.docx, Middle.docx, and End.docx are packages containing the corresponding subdocuments:

The master document’s Main Document part contains subDoc elements that reference its subdocuments:

<w:document xmlns:r="…" xmlns:wx="…" …> <w:body> <w:p …> <w:pPr> … </w:pPr> </w:p> <w:subDoc r:id="rId5"/>

… <w:subDoc r:id="rId6"/> … <w:subDoc r:id="rId7"/> … </w:body></w:document>

end example]

A subdocument shall be represented by an instance of a WordprocessingML package.

A subdocument shall be located external to the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be External).

Mail Merge Data Source

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/mailMergeSource

A document that stores information about a mail merge operation is permitted to contain a Document Settings part (§11.3.3) whose relationship item targets the file location of the necessary data source using this relationship.

[Example: Consider a document specifying a mail merge whose data source is located at http://www.openxmlformats.org/data.txt:

The document’s Document Settings part contains a dataSource element that explicitly references this relationship:

<w:settings …> <w:mailMerge> … <w:dataSource r:id="rId1" /> … </w:mailMerge></w:settings>

end example]

A mail merge data source shall be located external to the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be External).

Mail Merge Header Data Source

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/mailMergeHeaderSource

[Example: Consider a document specifying a mail merge whose header data source is located at http://www.openxmlformats.org/header.txt:

The document’s Document Settings part contains a headerSource element that explicitly references this relationship:

<w:settings …> <w:mailMerge> … <w:headerSource r:id="rId2" /> … </w:mailMerge></w:settings>

end example]

A mail merge header data source shall be located external to the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be External).

XSL Transformation

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/transform

A document can store information about an XSL Transformation which might be applied on save, by containing a Document Settings part (§11.3.3) whose part relationship item contains an explicit relationship to the file location of the XSL Transformation using this relationship.

[Example: Consider a document specifying an XSL Transformation located at http://www.openxmlformats.org/test.xsl:

The document’s Document Settings part contains a saveThroughXslt element that explicitly references this relationship:

<w:settings …> … <w:saveThroughXslt r:id="rId8" /> …</w:settings>

end example]

An XSL transformation shall be located external to the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be External).

SpreadsheetML

This clause contains specifications for relationship items and parts that are specific to SpreadsheetML. Parts than can occur in a SpreadsheetML document, but are not SpreadsheetML-specific, are specified in §15.2. Unless stated explicitly, all references to relationship items, content-type items, and parts in this clause refer to SpreadsheetML ZIP items.

Glossary of SpreadsheetML-Specific Terms

The following terms are used in the context of a SpreadsheetML document:

cell — The location at the intersection of a row and column, in which numeric or textual data or a formula is stored. A cell can have a number of characteristics, such as numeric or text formatting, alignment, font, color, and border.

cell reference — An individual cell's designation using a combination of its column and row headings, as in A13, H19, and BX1200. A relative cell reference in a formula automatically changes when the formula is copied down a column or across a row. An absolute cell reference is fixed. Absolute references don't change when a formula is copied from one cell to another. A mixed cell reference has either an absolute column and a relative row, or an absolute row and a relative column.

chart — A graphical representation of data, as in a bar, column, line, pie chart, for example.

column — Any vertical set of cells in a worksheet. Each column has an alphabetic heading. Columns are named sequentially, going from A–Z, then AA–AZ, BA–BZ, and so on.

comment — A reminder or annotation that can be attached to a cell.

connection — The means by which external data—that is, data stored outside of a workbook (in a database or on a Web server, for example)—can be imported into a worksheet.

formula — A recipe for calculating a value. Some formulas are predefined; others are user-defined.

function — A predefined formula, such as AVERAGE, MAX, MIN, and SUM. A function takes one or more arguments on which it operates, producing a result. [Note: In the formula =SUM(B1:B4), there is one argument, B1:B4, which is the range of cells B1–B4, inclusive. end note]

pivot table — A kind of table that is used to manage and analyze related data that is stored elsewhere.

row — Any horizontal set of cells in a worksheet. Each row has a numeric heading. Rows are numbered sequentially, starting at 1.

table — A rectangular-shaped set of related rows and columns that can be sorted, filtered, and totaled as a group. Rows in a table can be hidden by applying autofilters to one or more columns.

workbook — A collection of worksheets.

worksheet — A two-dimensional grid of cells that are organized into rows and columns.

Package Structure

A SpreadsheetML package shall contain a package-relationship item and a content-type item. The package-relationship item shall contain implicit relationships with targets of the following type:

One Workbook part (12.3.23).

The package-relationship item is permitted to contain implicit relationships with targets of the following type:

Digital Signature Origin (§15.2.6)

File Property parts (§15.2.11) (Application-Defined File Properties, Core File Properties, and Custom File Properties), as appropriate.

Thumbnail (§15.2.14).

The required and optional relationships between parts are defined in §12.3 and its subordinate clauses.

[Example: The following package represents the minimal conformant SpreadsheetML package as defined by this Standard:

First, the content types for relationship parts, the Workbook part, and at least one Sheet part must be defined (physically located at /[Content_Types].xml in the package):

</Types>

Next, the required package-level relationship to the Workbook part must be defined (physically located at /_rels/.rels in the package):

</Relationships>

Next, the minimum content for the Workbook part must be defined (physically located at /workbook.xml in the package):

Next, the required workbook-level relationship to the single Sheet part must be defined, (physically located at /_rels/workbook.xml.rels in the package):

</Relationships>

Finally, the minimum content for a single Sheet part must be defined (physically located at /sheet1.xml in the package):

end example]

[Example: Consider a SpreadsheetML document that contains a workbook having three worksheets. Here’s an example of the hierarchical folder structure that might be used for the ZIP items in the package for that document. As shown, one part, Workbook (stored in the ZIP item /xl/workbook.xml), has its own relationship item:

/_rels/.relsPackage-relationship item/[Content_Types].xmlContent-type item

/docProps/app.xmlApplication-Defined File Properties part/docProps/core.xmlCore File Properties part

/xl/workbook.xml Workbook part/xl/_rels/workbook.xml.rels Part-relationship item

/xl/calcChain.xmlCalculation Chain part/xl/sharedStrings.xmlShared String Table part/xl/styles.xmlStyles part/xl/volatileDependencies.xmlVolatile Dependencies part/xl/theme/theme1.xmlTheme part

/xl/worksheets/sheet1.xmlWorksheet parts/xl/worksheets/sheet2.xml/xl/worksheets/sheet3.xml

The package-relationship item contains the following:

end example]

Part Summary

The subclauses subordinate to this one describe in detail each of the part types specific to SpreadsheetML. [Note: For convenience, information from those subclauses is summarized in the following table:

Part

Relationship Target of

Root Element

Ref.

Calculation Chain

Workbook

calcChain

§12.3.1

Chartsheet

Workbook

chartsheet

§12.3.2

Comments

Chartsheet, Dialogsheet, Worksheet

comments

§12.3.3

Connections

Workbook

connections

§12.3.4

Custom Property

Workbook

Not applicable

§12.3.5

Custom XML Mappings

Workbook

mapInfo

§12.3.6

Dialogsheet

Workbook

dialogSheet

§12.3.7

Drawings

Chartsheet, Worksheet

wsDr

§12.3.8

External Workbook References

Workbook

externalReference

§12.3.9

Metadata

Workbook

metadata

§12.3.10

Pivot Table

Worksheet

pivotTableDefinition

§12.3.11

Pivot Table Cache Definition

Pivot Table, Workbook

pivotCacheDefinition

§12.3.12

Pivot Table Cache Records

Pivot Table Cache Definition

pivotCacheRecords

§12.3.13

Query Table

Worksheet

queryTable

§12.3.14

Shared String Table

Workbook

sst

§12.3.15

Shared Workbook Revision Headers

Workbook

headers

§12.3.16

Shared Workbook Revision Log

Shared Workbook Revision Headers

revisions

§12.3.17

Shared Workbook User Data

Workbook

users

§12.3.18

Single Cell Table Definitions

Dialogsheet, Worksheet

singleCells

§12.3.19

Styles

Workbook

styleSheet

§12.3.20

Table Definition

Dialogsheet, Worksheet

table

§12.3.21

Volatile Dependencies

Workbook

volTypes

§12.3.22

Workbook

SpreadsheetML package

workbook

§12.3.23

Worksheet

Workbook

worksheet

§12.3.24

end note]

Calculation Chain Part

Content Type:

application/vnd.openxmlformats-officedocument.spreadsheetml.calcChain+xml

Root Namespace:

http://schemas.openxmlformats.org/spreadsheetml/2006/main

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/calcChain

An instance of this part type contains an ordered set of references to all cells in all worksheets in the workbook whose value is calculated from any formula. The ordering allows inter-related cell formulas to be calculated in the correct order when a worksheet is loaded for use.

A package shall contain no more than one Calculation Chain part. If it exists, that part shall be the target of an implicit relationship from the Workbook part (§12.3.23).

[Example: The following Workbook part-relationship item contains a relationship to the Calculation Chain part, which is stored in the ZIP item calcChain.xml:

end example]

The root element for a part of this content type shall be calcChain.

[Example: Cells D8, E8, and F8 each contain a value that is the result of calculations that shall be performed in the order E8, D8, F8:

end example]

A Calculation Chain part shall be located within the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal).

A Calculation Chain part shall not have implicit or explicit relationships to any part defined by this Standard.

Chartsheet Part

Content Type:

application/vnd.openxmlformats-officedocument.spreadsheetml.chartsheet+xml

Root Namespace:

http://schemas.openxmlformats.org/spreadsheetml/2006/main

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/chartsheet

An instance of this part type represents a chart that is stored in its own sheet.

A package is permitted to contain zero or more Chartsheet parts. Each such part shall be the target of an explicit relationship from the Workbook part (§12.3.23).

[Example: The following Workbook part-relationship item contains three relationships to Chartsheet parts, which are stored in the ZIP items chartsheets/sheetN.xml:

end example]

The root element for a part of this content type shall be chartsheet.

[Example: sheet1.xml refers to a drawing that is the target of a relationship in the Chartsheet part's relationship item:

end example]

A Chartsheet part shall be located within the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal).

A Chartsheet part is permitted to have implicit relationships to the following parts defined by this Standard:

Printer Settings (§15.2.14)

A Chartsheet part is permitted to have explicit relationships to the following parts defined by this Standard:

Drawings (§12.3.8)

A Chartsheet part shall not have implicit or explicit relationships to any other part defined by this Standard.

Comments Part

Content Type:

application/vnd.openxmlformats-officedocument.spreadsheetml.comments+xml

Root Namespace:

http://schemas.openxmlformats.org/spreadsheetml/2006/main

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/comments

An instance of this part type contains all the comments for a given worksheet, as well as the names of the authors of those comments.

A package shall contain exactly one Comments part for each worksheet that contains one or more comments. If a Comments part exists, it shall be the target of an implicit relationship from the Workbook part (§12.3.23).

[Example: The following Worksheet part-relationship item contains a relationship to the Comments part, which is stored in the ZIP item comments2.xml:

end example]

The root element for a part of this content type shall be comments.

[Example: This Comments part results from a workbook that has one or more comments from each of two people: James Jones and Mary Smith:

<comments xmlns:st="…" > <authors> <author>James Jones</author> <author>Mary Smith</author> </authors>

<commentList> <comment r="C7" authorId="0"> <text> <st:r> <st:rPr> … </st:rPr> <st:t>James Jones:</st:t> </st:r>

<st:r> <st:rPr> … </st:rPr> <st:t>Check that this date is correct.</st:t> </st:r> </text> </comment>

end example]

A Comments part shall be located within the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal).

A Comments part shall not implicit or explicit relationships to any part defined by this Standard.

Connections Part

Content Type:

application/vnd.openxmlformats-officedocument.spreadsheetml.connections+xml

Root Namespace:

http://schemas.openxmlformats.org/spreadsheetml/2006/main

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/connections

An instance of this part type describes all of the connections currently established for a workbook.

A package shall contain no more than one Connections part, and that part shall be the target of an implicit relationship from the Workbook part (§12.3.23).

[Example: The following Workbook part-relationship item contains a relationship to the Connections part, which is stored in the ZIP item connections.xml:

end example]

The root element for a part of this content type shall be connections.

[Example: A workbook has three connections, two from one worksheet, and one from another. connections.xml defines these three connections:

end example]

A Connections part shall be located within the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal).

A Connections part shall not have implicit or explicit relationships to any part defined by this Standard..

Custom Property Part

Content Type:

application/vnd.openxmlformats-officedocument.spreadsheetml.customProperty

Root Namespace:

Not applicable

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/customProperty

This binary part supports the storage of arbitrary user-defined data.

A package shall contain at most one Custom Property part, and that part shall be the target of an implicit relationship from the Workbook (§12.3.23) part.

[Example: The following Workbook part-relationship item contains a relationship to the Custom Property part, which is stored in the ZIP item CustomProperty.bin:

end example]

A Custom Property part shall be located within the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal).

A Custom Property part shall not have implicit or explicit relationships to any part defined by this Standard.

Custom XML Mappings Part

Content Type:

application/xml

Root Namespace:

http://schemas.openxmlformats.org/spreadsheetml/2006/main

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/xmlMaps

An instance of this part type contains a schema for an XML file, and information on the behavior that is used when allowing this custom XML schema to be mapped into the spreadsheet.

A package shall contain no more than one Custom XML Mappings part, and that part shall be the target of an implicit relationship from the Workbook part (§12.3.23). The Worksheet part into which this data is imported shall also have a relationship file that targets one or more Table Definition (§12.3.21) parts and/or one or more Single Cell Table Defintions (§12.3.19) parts.

[Example: The following Workbook part-relationship item contains a relationship to the Custom XML Mappings part, which is stored in the ZIP item xmlMaps.xml:

end example]

The root element for a part of this content type shall be mapInfo.

[Example: xmlMaps.xml contains the following:

<xsd:sequence minOccurs="0"> <xsd:element minOccurs="0" maxOccurs="unbounded" nillable="true" name="name" form="unqualified">

<xsd:complexType> <xsd:sequence minOccurs="0"> <xsd:element minOccurs="0" nillable="true" type="xsd:string" name="firstname" form="unqualified"/> <xsd:element minOccurs="0" nillable="true" type="xsd:string" name="initial" form="unqualified"/> <xsd:element minOccurs="0" nillable="true" type="xsd:string" name="lastName" form="unqualified"/> </xsd:sequence> </xsd:complexType>

</xsd:element> </xsd:sequence>

</xsd:complexType> </xsd:element> </xsd:schema> </Schema>

end example]

A Custom XML Mappings part shall be located within the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal).

A Custom XML Mappings part shall not have implicit or explicit relationships to any other part defined by this Standard.

Dialogsheet Part

Content Type:

application/vnd.openxmlformats-officedocument.spreadsheetml.dialogsheet+xml

Root Namespace:

http://schemas.openxmlformats.org/spreadsheetml/2006/main

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/dialogsheet

An instance of this part type contains information about a legacy custom dialog box for a user form.

A package is permitted to contain one or more Dialogsheet parts, and each such part shall be the target of an explicit relationship from the Workbook part (§12.3.23).

[Example: The following Workbook part-relationship item contains relationships to a Dialogsheet part, which is stored in the ZIP item dialogsheets/sheet1.xml:

The Workbook part contains the following:

end example]

The root element for a part of this content type shall be dialogsheet.

[Example: sheet1.xml contains the following:

end example]

A Dialogsheet part shall be located within the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal).

A Dialogsheet part is permitted to have implicit relationships to the following parts defined by this Standard:

Printer Settings (§15.2.14)

A Dialogsheet part is permitted to have explicit relationships to the following parts defined by this Standard:

Embedded Control Persistence (§15.2.8)

Drawings (§12.3.8)

Embedded Object (§15.2.9)

A Dialogsheet part shall not have implicit or explicit relationships to any other part defined by this Standard.

Drawings Part

Content Type:

application/vnd.openxmlformats-officedocument.drawing+xml

Root Namespace:

http://schemas.openxmlformats.org/drawingml/2006/spreadsheetDrawing

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/drawing

An instance of this part type contains the presentation and layout information for one or more drawing elements that are present on this worksheet.

A package is permitted to contain one or more Drawings parts, and each such part shall be the target of an explicit relationship from a Worksheet part (§12.3.24), or a Chartsheet part (§12.3.2). There shall be only one Drawings part per worksheet or chartsheet.

[Example: The following Chartsheet part-relationship item contains a relationship to a Drawings part, which is stored in the ZIP item ../drawings/drawing1.xml:

end example]

The root element for a part of this content type shall be wsDr.

[Example: drawing1.xml refers to a chart that is the target of a relationship in the Drawing part's relationship item:

<xdr:wsDr xmlns:xdr="…" xmlns:a="…"> <xdr:absoluteAnchor> <xdr:pos x="1518046" y="-1443632"/> <xdr:extents cx="8587382" cy="5848945"/> <xdr:graphicFrame macro=""> <xdr:nvGraphicFramePr> <xdr:cNvPr id="24" name="Chart 24" descr=""/> <xdr:cNvGraphicFramePr/> </xdr:nvGraphicFramePr> <xdr:xfrm> <a:off x="0" y="0"/> <a:ext cx="0" cy="0"/> </xdr:xfrm>

<a:graphic> <a:graphicData uri="http://…/chart"> <a:chart relId="rId1"/> </a:graphicData> </a:graphic> </xdr:graphicFrame> <xdr:clientData/> </xdr:absoluteAnchor></xdr:wsDr>

end example]

A Drawings part shall be located within the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal).

A Drawings part is permitted to have explicit relationships to the following parts defined by this Standard:

Chart (§14.2.1)

Diagrams: Diagram Colors(§14.2.3), Diagram Data(§14.2.4), Diagram Layout Definition(§14.2.5) and Diagram Styles (§14.2.6)

Hyperlinks (§15.3)

Images (§15.2.13)

A Drawings part shall not have any implicit or explicit relationships to any other part defined by this Standard.

External Workbook References Part

Content Type:

application/vnd.openxmlformats-officedocument.spreadsheetml.externalLink+xml

Root Namespace:

http://schemas.openxmlformats.org/spreadsheetml/2006/main

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/externalLink

An instance of this part specifies information about data referenced in other SpreadsheetML packages.

[Example: Consider two workbooks, wb1 and wb2, stored in packages called wb1.xlsx and wb2.xlsx, respectively. The value of a cell on a worksheet in wb1 can be computed using the value of one or more cells in wb2. This is done by having wb1 contain an external reference to wb2. end example]

A package is permitted to contain one or more External Workbook References parts, and those parts shall be the target of an explicit relationship in the Workbook part (§12.3.23).

[Example: A Workbook part for wb1 contains the following, which indicates that somewhere in its three worksheets, an external reference is made to a target specified in relationship id rId4 of the part's relationship item:

That part's relationship item contains the following:

end example]

The root element for a part of this content type shall be externalLink.

[Example: externalReference1.xml contains:

This part's relationship item contains the following:

where wb2.xlsx is the workbook in which one or more cells' values are used in calculating the values of a cell in workbook wb1. end example]

An External Workbook References part shall be located within the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal).

An External Workbook References part shall specify an explicit relationship to one or more this StandardExternal Workbooks (§12.4).

An External Workbook References part shall not have any implicit or explicit relationships to other parts defined by this Standard.

Metadata Part

Content Type:

application/vnd.openxmlformats-officedocument.spreadsheetml.sheetMetadata+xml

Root Namespace:

http://schemas.openxmlformats.org/spreadsheetml/2006/main

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/sheetMetadata

An instance of this part type contains information relating to a cell whose value is related to one or more other cells via OnLine Analytical Processing (OLAP) technology.

A package shall contain no more than one Cell Metadata part, and that part shall be the target of an implicit relationship from the Workbook part (§12.3.23).

[Example: The following Workbook part-relationship item contains a relationship to the Metadata part, which is stored in the ZIP item metadata.xml. Cell B3 contains the formula CUBEMEMBER ("externalData", "[Account].[All Account]"):

end example]

The root element for a part of this content type shall be metadata.

[Example: metadata.xml contains the following:

The corresponding Connections part contains the following:

The corresponding Volatile Dependencies part contains the following:

The corresponding Pivot Table Cache Definition part contains the following:

end example]

A Metadata part shall be located within the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal).

A Metadata part shall not have implicit or explicit relationships to any part defined by this Standard.

Pivot Table Part

Content Type:

application/vnd.openxmlformats-officedocument.spreadsheetml.pivotTable+xml

Root Namespace:

http://schemas.openxmlformats.org/spreadsheetml/2006/main

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/pivotTable

An instance of this part type contains a pivot table definition.

A package shall contain exactly one Pivot Table part per pivot table, and each such part shall be the target of an implicit relationship in the relationship part for the Worksheet part (§12.3.24) that corresponds to the worksheet containing the pivot table.

[Example: The following Worksheet part-relationship item contains a relationship to two Pivot Table parts, which are stored in the ZIP items ../pivotTables/pivotTableN.xml:

end example]

The root element for a part of this content type shall be pivotTableDefinition.

[Example: pivotTable1.xml contains the following:

end example]

A Pivot Table part shall be located within the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal).

A Pivot Table part is permitted to have implicit relationships to the following parts defined by this Standard:

Pivot Table Cache Definition (§12.3.12).

A Pivot Table part shall not have any implicit or explicit relationships to other parts defined by this Standard.

Pivot Table Cache Definition Part

Content Type:

application/vnd.openxmlformats-officedocument.spreadsheetml.pivotCacheDefinition+xml

Root Namespace:

http://schemas.openxmlformats.org/spreadsheetml/2006/main

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/pivotCacheDefinition

An instance of this part type contains a cache definition for a pivot table.

A package shall contain exactly one Pivot Table Cache Definition part per pivot table, and each such part shall be the target of an implicit relationship from a Pivot Table (§12.3.11) part as well as an explicit relationship from a Workbook (§12.3.23) part.

[Example: The following Pivot Table part-relationship item contains a relationship to the Pivot Table Cache Definition part, which is stored in the ZIP item ../pivotCache/pivotCacheDefinition2.xml:

end example]

The root element for a part of this content type shall be pivotCacheDefinition.

[Example: pivotCacheDefinition2.xml contains the following:

end example]

A Pivot Table Cache Definition part shall be located within the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal).

A Pivot Table Cache Definition part is permitted to have an explicit relationship to the following part defined by this Standard:

Pivot Table Cache Records (§12.3.13).

A Pivot Table Cache Definition part shall not have any implicit or explicit relationships to other parts defined by this Standard.

Pivot Table Cache Records Part

Content Type:

application/vnd.openxmlformats-officedocument.spreadsheetml.pivotCacheRecords+xml

Root Namespace:

http://schemas.openxmlformats.org/spreadsheetml/2006/main

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/spreadsheetml/pivotCacheRecords

An instance of this part type contains the cache records for a pivot table.

A package shall contain exactly one Pivot Table Cache Records part per pivot table, and each such part shall be the target of an explicit relationship in the Pivot Table Cache Definition (§12.3.12) part for the corresponding pivot table.

[Example: The following Pivot Table Cache Definition part-relationship item contains a relationship to the Pivot Table Cache Records part, which is stored in the ZIP item pivotCacheRecords2.xml:

end example]

The root element for a part of this content type shall be pivotCacheRecords.

[Example: pivotCacheRecords2.xml contains the following:

end example]

A Pivot Table Cache Records part shall be located within the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal).

A Pivot Table Cache Records part shall not have implicit or explicit relationships to any other part defined by this Standard.

Query Table Part

Content Type:

application/vnd.openxmlformats-officedocument.spreadsheetml.queryTable+xml

Root Namespace:

http://schemas.openxmlformats.org/spreadsheetml/2006/main

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/queryTable

An instance of this part type contains information that describes how the source table is connected to an external data source, and defines the properties that is used when this table is refreshed from that source.

A package is permitted to contain one Query Table part per table, and each of those parts shall be the target of an implicit relationship from the corresponding Table Definitions (§12.3.21) part.

[Example: The following Table part-relationship item contains a relationship to the Query Table part corresponding to the connections details for that table. These parts are stored in the ZIP items ../queryTables/queryTablen.xml:

end example]

The root element for a part of this content type shall be queryTable.

[Example: queryTable2.xml deals with a connection to a database file having the seven fields shown:

end example]

A Query Table part shall be located within the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal).

A Query Table part shall not have implicit or explicit relationships to any other part defined by this Standard.

Shared String Table Part

Content Type:

application/vnd.openxmlformats-officedocument.spreadsheetml.sharedStrings+xml

Root Namespace:

http://schemas.openxmlformats.org/spreadsheetml/2006/main

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/sharedStrings

An instance of this part type contains one occurrence of each unique string that occurs on all worksheets in a workbook.

A package shall contain exactly one Shared String Table part, and that part shall be the target of an implicit relationship from the Workbook part (§12.3.23).

[Example: The following Workbook part-relationship item contains a relationship to the Shared String Table part, which is stored in the ZIP item sharedStrings.xml:

end example]

The root element for a part of this content type shall be sst.

[Example: Here are three of the six strings used in the worksheets:

<sst xmlns:st="…" … totalCount="6" uniqueCount="6"> <sstItem> <t>Expenses Log</t> </sstItem>

<sstItem> <t>Period Start</t> </sstItem>

<sstItem> <t>Period End</t> </sstItem> …</sst>

end example]

A Shared String Table part shall be located within the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal).

A Shared String Table part shall not have implicit or explicit relationships to any other part defined by this Standard.

Shared Workbook Revision Headers Part

Content Type:

application/vnd.openxmlformats-officedocument.spreadsheetml.revisionHeaders+xml

Root Namespace:

http://schemas.openxmlformats.org/spreadsheetml/2006/main

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/revisionHeaders

An instance of this part type contains information about each of the editing sessions performed on the parent workbook at the worksheet level (worksheets added and rearranged in each session).

A package shall contain at most one Shared Workbook Revision Headers part. If it exists, that part shall be the target of an implicit relationship from the Workbook (§12.3.23) part.

[Example: The following Workbook part-relationship item contains a relationship to the Shared Workbook Revision Headers part, which is stored in the ZIP item handout revisions/revisionHeaders.xml:

end example]

The root element for a part of this content type shall be headers.

[Example: revisionHeaders.xml contains the following:

…

end example]

A Shared Workbook Revision Headers part shall be located within the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal).

A Shared Workbook Revision Headers part is permitted to have explicit relationships to the following parts defined by this Standard:

Shared Workbook Revision Log (§12.3.17)

A Shared Workbook Revision Headers part shall not have any implicit or explicit relationships to other parts defined by this Standard.

Shared Workbook Revision Log Part

Content Type:

application/vnd.openxmlformats-officedocument.spreadsheetml.revisionLog+xml

Root Namespace:

http://schemas.openxmlformats.org/spreadsheetml/2006/main

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/revisionLog

An instance of this part type contains information about edits performed on individual cells in the parent workbook’s worksheets in each editing session.

A package shall contain one Shared Workbook Revision Log part for each session's set of changes, and those parts shall be the target of an explicit relationship from the Shared Workbook Revision Headers (§12.3.16) part.

[Example: The following Shared Workbook Revision Headers part-relationship item contains a number of relationships to Shared Workbook Revision Log parts, which are stored in the ZIP item revisionLogN.xml:

end example]

The root element for a part of this content type shall be revisions.

[Example: revisionLog2.xml contains the following:

end example]

A Shared Workbook Revision Log part shall be located within the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal).

A Shared Workbook Revision Log part shall not have implicit or explicit relationships to any other part defined by this Standard.

Shared Workbook User Data Part

Content Type:

application/vnd.openxmlformats-officedocument.spreadsheetml.userNames+xml

Root Namespace:

http://schemas.openxmlformats.org/spreadsheetml/2006/main

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/usernames

An instance of this part type contains a list of all the users that are sharing the parent workbook.

A package shall contain at most one Shared Workbook User Data part, and that part shall be the target of an implicit relationship in the Workbook (§12.3.23) part.

[Example: The following Workbook part-relationship item contains a relationship to the Shared Workbook User Data part, which is stored in the ZIP item revisions/userNames.xml:

<Relationships xmlns="…"> Relationship Id="rId8" Type="http://…/usernames" Target="revisions/userNames.xml"/></Relationships>

end example]

The root element for a part of this content type shall be users.

[Example: userNames.xml shows that there are two users sharing this workbook:

end example]

A Shared Workbook User Data part shall be located within the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal).

A Shared Workbook User Data part shall not have implicit or explicit relationships to any other part defined by this Standard.

Single Cell Table Definitions Part

Content Type:

application/vnd.openxmlformats-officedocument.spreadsheetml.tableSingleCells+xml

Root Namespace:

http://schemas.openxmlformats.org/spreadsheetml/2006/main

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/tableSingleCells

An instance of this part type contains information on how to map non-repeating elements from a custom XML file into cells in a worksheet. [Note: Repeating custom XML elements are mapped using a Table (§12.3.21). end note]

A package shall contain at most one Single Cell Table Definitions part per worksheet, and that part shall be the target of an implicit relationship from a Worksheet (§12.3.24) part. A Single Cell Table Definitions part can describe one or more single cell table definitions for any given worksheet.

[Example: The following Worksheet part-relationship item contains a relationship to the Single Cell Table Definitions part, which is stored in the ZIP item ../tables/tableSingleCells1.xml:

end example]

The root element for a part of this content type shall be singleCells.

[Example: A worksheet contains two single cell table definitions; e.g., ../tables/tableSingleCells1.xml contains the following, where the elements id and count are nested inside element names:

end example]

A Single Cell Table Definitions part shall be located within the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal).

A Single Cell Table Definitions part shall not have implicit or explicit relationships to any other part defined by this Standard.

Styles Part

Content Type:

application/vnd.openxmlformats-officedocument.spreadsheetml.styles+xml

Root Namespace:

http://schemas.openxmlformats.org/spreadsheetml/2006/mains

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/styles

An instance of this part type contains all the characteristics for all the cells in the workbook. Such information includes numeric and text formatting, alignment, font, color, and border.

A package shall contain no more than one Styles part, and that part shall be the target of an implicit relationship from the Workbook (§12.3.23) part.

[Example: The following Workbook part-relationship item contains a relationship to the Styles part, which is stored in the ZIP item styles.xml:

end example]

The root element for a part of this content type shall be styleSheet.

[Example:

…

end example]

A Styles part shall be located within the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal).

A Styles part shall not have implicit or explicit relationships to any other part defined by this Standard.

Table Definition Part

Content Type:

application/vnd.openxmlformats-officedocument.spreadsheetml.table+xml

Root Namespace:

http://schemas.openxmlformats.org/spreadsheetml/2006/main

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/table

An instance of this part type contains a description of a single table and its autofilter information. (The data for the table is stored in the corresponding Worksheet part.)

A package shall contain one Table Definition part per table, and each such part shall be the target of an implicit relationship from the Worksheet (§12.3.24) part that corresponds to the worksheet containing that table.

[Example: The following Worksheet part-relationship item contains relationships to two Table Definition parts, which are stored in the ZIP items ../tables/tableN.xml:

end example]

The root element for a part of this content type shall be table.

[Example: table2.xml describes a table that spans a 2-column range of cells, F2:G19:

When the filter "Salesman equal to Smith" is applied, the autoFilter element in table2.xml is extended, as follows:

end example]

A Table Definition part shall be located within the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal).

A Table Definition part is permitted to explicit relationships to the following parts defined by this Standard:

Query Table (§12.3.14)

A Table Definition part shall not have any implicit or explicit relationships to any other part defined by this Standard.

Volatile Dependencies Part

Content Type:

application/vnd.openxmlformats-officedocument.spreadsheetml.volatileDependencies+xml

Root Namespace:

http://schemas.openxmlformats.org/spreadsheetml/2006/main

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/volatileDependencies

An instance of this part type contains information involving real-time data formulas in a workbook.

A package shall contain exactly one Volatile Dependencies part, and that part shall be the target of an implicit relationship from the Workbook (§12.3.23) part.

[Example: The following Workbook part-relationship item contains a relationship to the Volatile Dependencies part, which is stored in the ZIP item volatileDependencies.xml:

end example]

The root element for a part of this content type shall be volTypes.

[Example:

end example]

A Volatile Dependencies part shall be located within the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal).

A Volatile Dependencies part shall not have implicit or explicit relationships to any other part defined by this Standard.

Workbook Part

Content Type(s):

application/vnd.openxmlformats-officedocument.spreadsheetml.main+xmlapplication/vnd.openxmlformats-officedocument.spreadsheetml.template.main+xml

Root Namespace:

http://schemas.openxmlformats.org/spreadsheetml/2006/main

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/officeDocument

An instance of this part type contains workbook data and references to all of its worksheets.

A package shall contain exactly one Workbook part, and that part shall be the target of a relationship in the package-relationship item.

[Example: The following SpreadsheetML package-relationship item contains a relationship to the Workbook part, which is stored in the ZIP item xl/workbook.xml:

end example]

The root element for a part of this content type shall be workbook.

[Example: This workbook has three worksheets, named January, February, and March:

end example]

A Workbook part shall be located within the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal).

A Workbook part is permitted to have implicit relationships to the following parts defined by this Standard:

Additional Characteristics (§15.2.1)

Bibliography (§15.2.3)

Calculation Chain (§12.3.1)

Cell Metadata (§12.3.10)

Connections (§12.3.4)

Custom XML Mappings (§12.3.6)

Custom XML Data Storage (§15.2.4)

Shared String Table (§12.3.15)

Shared Workbook Revision Headers (§12.3.16)

Shared Workbook User Data (§12.3.18)

Styles (§12.3.20)

Theme (§14.2.7)

Thumbnail (§15.2.14)

Volatile Dependencies (§12.3.22)

A Workbook part is permitted to have explicit relationships to the following parts defined by this Standard:

Chartsheet (§12.3.2)

Dialogsheet (§12.3.7)

External Workbook References (§12.3.8)

Pivot Table Cache Definition (§12.3.12)

Worksheet (§12.3.24)

A Workbook part shall not have implicit or explicit relationships to any other part defined by this Standard.

Worksheet Part

Content Type:

application/vnd.openxmlformats-officedocument.spreadsheetml.worksheet+xml

Root Namespace:

http://schemas.openxmlformats.org/spreadsheetml/2006/main

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/worksheet

An instance of this part type contains all the data, formulas, and characteristics associated with a given worksheet.

A package shall contain exactly one Worksheet part per worksheet, and those parts shall be the target of an explicit relationship from the Workbook (§12.3.23) part. Specifically, the id attribute on the sheet element shall reference the desired worksheet part.

[Example: The following Workbook part-relationship item contains three relationships to Worksheet parts, which are stored in the ZIP items worksheets/sheetN.xml:

end example]

The root element for a part of this content type shall be worksheet.

[Example: This worksheet, has cells in the range B1 to F8. Row 8 contains three cells whose values are calculated using the following formulas: D8=SUM(D5:D7), E8=SUM(E5:E7), and F8= D8-E8:

…

…

end example]

A Worksheet part shall be located within the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal).

A Worksheet part is permitted to contain implicit relationships to the following parts defined by this Standard:

Comments (§12.3.3)

Pivot Table Definitions (§12.3.11)

Printer Settings (§15.2.14)

Single Cell Table Definitions (§12.3.19)

Table Definition (§12.3.21)

A Worksheet part is permitted to contain explicit relationships to the following parts defined by this Standard:

Drawings (§12.3.8)

Embedded Control Persistence (§15.2.8)

Embedded Object (§15.2.9)

Embedded Package (§15.2.10)

Hyperlinks (§15.3)

Images (§15.2.13)

VML Drawing (§15.2.17)

A Worksheet part shall not have implicit or explicit relationships to any other part defined by this Standard.

External Workbooks

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/externalLinkPath

An external workbook is a SpreadsheetML package whose contents are being referenced by the current SpreadsheetML package. When a package refers to external workbooks, it shall store the location of those workbooks using this relationship.

A package is permitted to contain one or more External Workbook relationships, and those relationships shall be an explicit relationship from the External Workbook References (§12.3.9) part.

[Example: An External Workbook References part, which references the package c:\sourceData.xlsx would have an External Workbook relationship, which points at that file:

end example]

A external workbook shall be located external to the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be External).

PresentationML

This clause contains specifications for relationship items and parts that are specific to PresentationML. Parts than can occur in a PresentationML document, but are not PresentationML-specific, are specified in §15.2. Unless stated explicitly, all references to relationship items, content-type items, and parts in this clause refer to PresentationML ZIP items.

Glossary of PresentationML-Specific Terms

The following terms are used in the context of a PresentationML document:

handout — A printed set of slides that can be handed out to an audience for future reference.

note — A slide annotation, reminder, or piece of text intended for the presenter or the audience.

presentation — A collection of slides intended to be viewed by an audience.

slide — A frame containing one or more pieces of text and/or images.

slide layout — The organization of elements on a slide.

Package Structure

A PresentationML package shall contain a package-relationship item and a content-type item. The package-relationship item shall contain implicit relationships with targets of the following type:

One Presentation part (§13.3.6).

The package-relationship item is permitted to contain implicit relationships with targets of the following type:

Digital Signature Origin (§15.2.6)

File Property parts (§15.2.11) (Application-Defined File Properties, Core File Properties, and Custom File Properties), as appropriate.

Thumbnail (§15.2.14).

The required and optional relationships between parts are defined in §13.3 and its subordinate clauses.

[Example: The following package represents the minimal conformant PresentationML package as defined by this Standard:

First, the content type for relationship parts and the Main Presentation part (the only required part) must be defined (physically located at /[Content_Types].xml in the package):

Next, the single required relationship (the package-level relationship to the Main Presentation part) must be defined (physically located at /_rels/.rels in the package):

Finally, the minimum content for the Main Presentation part must be defined (physically located at /presentation.xml in the package):

<p:presentation xmlns:p="…"> <p:notesSz cx="913607" cy="913607"/></p:presentation>

end example]

[Example: Consider a simple PresentationML document containing two slides, which both use an image as a template. Here’s an example of the hierarchical folder structure that might be used for the ZIP items in the package for that document. As shown, a number of parts have their own relationship items:

/_rels/.relsPackage-relationship item/[Content_Types].xmlContent-type item

/docProps/app.xmlApplication-Defined File Properties part/docProps/core.xmlCore File Properties part/docProps/custom.xmlCustom File Properties part/docProps/thumbnail.wmfPackage thumbnail image

/ppt/presentation.xml Presentation part/ppt/_rels/presentation.xml.relsPart-relationship item

/ppt/presProps.xmlPresentation Properties part/ppt/tableStyles.xmlTable Styles part/ppt/viewProps.xmlView Properties part

/ppt/handoutMasters/handoutMaster1.xmlHandout Master part/ppt/handoutMasters/_rels/handoutMaster1.xml.rels

Part-relationship item

/ppt/media/image1.jpegSlide template image

/ppt/notesMasters/notesMaster1.xml Notes Master part/ppt/notesMasters/_rels/notesMaster1.xml.rels

Part-relationship item

/ppt/notesSlides/notesSlide1.xml Notes Slide parts/ppt/notesSlides/notesSlide2.xml/ppt/notesSlides/_rels/notesSlide1.xml.relsPart-relationship items/ppt/notesSlides/_rels/notesSlide2.xml.rels

/ppt/slideLayouts/slideLayout1.xmlSlide Layout parts 1–6/ppt/slideLayouts/slideLayout2.xml/ppt/slideLayouts/slideLayout3.xml/ppt/slideLayouts/slideLayout4.xml/ppt/slideLayouts/slideLayout5.xml/ppt/slideLayouts/slideLayout6.xml

/ppt/slideLayouts/_rels/slideLayout1.xml.relsPart-relationship items/ppt/slideLayouts/_rels/slideLayout2.xml.rels/ppt/slideLayouts/_rels/slideLayout3.xml.rels/ppt/slideLayouts/_rels/slideLayout4.xml.rels/ppt/slideLayouts/_rels/slideLayout5.xml.rels/ppt/slideLayouts/_rels/slideLayout6.xml.rels

/ppt/slideMasters/slideMaster1.xml Slide Master part/ppt/slideMasters/_rels/slideMaster1.xml.relsPart-relationship item

/ppt/slides/slide1.xmlSlide parts/ppt/slides/slide2.xml/ppt/slides/_rels/slide1.xml.rels Part-relationship items/ppt/slides/_rels/slide2.xml.rels

/ppt/theme/theme1.xmlTheme parts/ppt/theme/theme2.xml/ppt/theme/theme3.xml

/ppt/theme/themeOverride1.xmlTheme Override parts/ppt/theme/themeOverride2.xml/ppt/theme/themeOverride3.xml/ppt/theme/themeOverride4.xml/ppt/theme/themeOverride5.xml/ppt/theme/themeOverride6.xml/ppt/theme/themeOverride7.xml/ppt/theme/themeOverride8.xml/ppt/theme/themeOverride9.xml/ppt/theme/themeOverride10.xml

The package-relationship item contains the following:

end example]

Part Summary

The subclauses subordinate to this one describe in detail each of the part types specific to PresentationML.

[Note: For convenience, information from those subclauses is summarized in the following table:

Part

Relationship Target of

Root Element

Ref.

Comment Authors

Presentation

cmAuthorLst

§13.3.1

Comments

Slide

cmLst

§13.3.2

Handout Master

Presentation

handoutMaster

§13.3.3

Notes Master

Notes Slide, Presentation

notesMaster

§13.3.4

Notes Slide

Slide

notes

§13.3.5

Presentation

PresentationML package

presentation

§13.3.6

Presentation Properties

Presentation

presentationPr

§13.3.7

Slide

Presentation

sld

§13.3.8

Slide Layout

Slide Master, Notes Slide, Presentation, Slide, Slide Master

sldLayout

§13.3.9

Slide Master

Presentation, Slide Layout

sldMaster

§13.3.10

Slide Synchronization Data

Slide

sldSyncPr

§13.3.11

User-Defined Tags

Presentation, Slide

tagLst

§13.3.12

View Properties

Presentation

viewPr

§13.3.13

end note]

Comment Authors Part

Content Type:

application/vnd.openxmlformats-officedocument.presentationml.commentAuthors+xml

Root Namespace:

http://schemas.openxmlformats.org/presentationml/2006/main

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/commentAuthors

An instance of this part type contains information about each author who has added a comment to the document. That information includes the author's name, initials, a unique author-ID, a last-comment-index-used count, and a display color. (The color can be used when displaying comments to distinguish comments from different authors.)

A package shall contain at most one Comment Authors part. If it exists, that part shall be the target of an implicit relationship from the Presentation (§13.3.6) part.

[Example: The following Presentation part relationship item contains a relationship to the Comment Authors part, which is stored in the ZIP item commentAuthors.xml:

end example]

The root element for a part of this content type shall be cmAuthorLst.

[Example: Two people have authored comments in this document: Mary Smith and Peter Jones. Her initials are "mas", her author-ID is 0, and her comments' display color index is 0. Since Mary's last-comment-index-used value is 3, the next comment-index to be used for her will be 4. His initials are "pjj", his author-ID is 1, and his comments' display color index is 1. Since Peter's last-comment-index-used value is 1, the next comment-index to be used for him will be 2:

<p:cmAuthorLst xmlns:p="…" …> <p:cmAuthor id="0" name="Mary Smith" initials="mas" lastIdx="3" clrIdx="0"/> <p:cmAuthor id="1" name="Peter Jones" initials="pjj" lastIdx="1" clrIdx="1"/></p:cmAuthorLst>

end example]

A Comment Authors part shall be located within the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal).

A Comment Authors part shall not have implicit or explicit relationships to any other part defined by this Standard.

Comments Part

Content Type:

application/vnd.openxmlformats-officedocument.presentationml.comments+xml

Root Namespace:

http://schemas.openxmlformats.org/presentationml/2006/main

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/comments

An instance of this part type contains the comments for a single slide. Each comment is tied to its author via an author-ID. Each comment's index number and author-ID combination are unique.

A package shall contain one Comments part for each slide containing one or more comments, and each of those parts shall be the target of an implicit relationship from its corresponding Slide (§13.3.8) part.

[Example: The following Slide part-relationship item contains a relationship to a Comments part, which is stored in the ZIP item ../comments/comment2.xml:

end example]

The root element for a part of this content type shall be cmLst .

[Example: The Comments part contains three comments, two created by one author, and one created by another, all at the dates and times shown. The index numbers are assigned on a per-author basis, starting at 1 for an author's first comment:

<p:cmLst xmlns:p="…" …> <p:cm authorId="0" dt="2005-11-13T17:00:22.071" idx="1"> <p:pos x="4486" y="1342"/> <p:text>Comment text goes here.</p:text> </p:cm> <p:cm authorId="0" dt="2005-11-13T17:00:34.849" idx="2"> <p:pos x="3607" y="1867"/> <p:text>Another comment's text goes here.</p:text> </p:cm> <p:cm authorId="1" dt="2005-11-15T00:06:46.919" idx="1"> <p:pos x="1493" y="2927"/> <p:text>comment …</p:text> </p:cm></p:cmLst>

end example]

A Comments part shall be located within the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal).

A Comments part shall not have implicit or explicit relationships to any other part defined by this Standard.

Handout Master Part

Content Type:

application/vnd.openxmlformats-officedocument.presentationml.handoutMaster+xml

Root Namespace:

http://schemas.openxmlformats.org/presentationml/2006/main

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/handoutMaster

An instance of this part type contains the look, position, and size of the slides, notes, header and footer text, date, or page number on the presentation's handout.

A package shall contain at most one Handout Master part, and it shall be the target of an explicit relationship from the Presentation (§13.3.6) part.

[Example: The following Presentation part-relationship item contains a relationship to the Handout Master part, which is stored in the ZIP item handoutMasters/handoutMaster1.xml:

end example]

The root element for a part of this content type shall be handoutMaster.

[Example:

<p:handoutMaster xmlns:p="…"> <p:cSld name=""> … </p:cSld> <p:clrMap … /></p:handoutMaster>

end example]

A Handout Master part shall be located within the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal).

A Handout Master part is permitted to have implicit relationships to the following parts defined by this Standard:

Additional Characteristics (§15.2.1)

Bibliography (§15.2.3)

Custom XML Data Storage (§15.2.4)

Theme (§14.2.7)

Thumbnail (§15.2.14)

A Handout Master part is permitted to have explicit relationships to the following parts defined by this Standard:

Audio (§15.2.2)

Chart (§14.2.1)

Diagrams: Diagram Colors(§14.2.3), Diagram Data(§14.2.4), Diagram Layout Definition(§14.2.5) and Diagram Styles (§14.2.6)

Embedded Control Persistence (§15.2.8)

Embedded Object (§15.2.9)

Embedded Package (§15.2.10)

Hyperlink (§15.3)

Image (§15.2.13)

Video (§15.2.14)

VML Drawing (§15.2.17)

A Handout Master part shall not have implicit or explicit relationships to any other part defined by this Standard.

Notes Master Part

Content Type:

application/vnd.openxmlformats-officedocument.presentationml.notesMaster+xml

Root Namespace:

http://schemas.openxmlformats.org/presentationml/2006/main

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/notesMaster

An instance of this part type contains information about the content and formatting of all notes pages.

A package shall contain at most one Notes Master part, and that part shall be the target of an implicit relationship from the Notes Slide (§13.3.5) part, as well as an explicit relationship from the Presentation (§13.3.6) part.

[Example: The following Presentation part-relationship item contains a relationship to the Notes Master part, which is stored in the ZIP item notesMasters/notesMaster1.xml:

end example]

The root element for a part of this content type shall be notesMaster.

[Example:

<p:notesMaster xmlns:p="…"> <p:cSld name=""> … </p:cSld> <p:clrMap … /></p:notesMaster>

end example]

A Notes Master part shall be located within the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal).

A Notes Master part is permitted to have implicit relationships to the following parts defined by this Standard:

Additional Characteristics (§15.2.1)

Bibliography (§15.2.3)

Custom XML Data Storage (§15.2.4)

Theme (§14.2.7)

Thumbnail (§15.2.14)

A Notes Master part is permitted to have explicit relationships to the following parts defined by this Standard:

Audio (§15.2.2)

Chart (§14.2.1)

Diagrams: Diagram Colors(§14.2.3), Diagram Data(§14.2.4), Diagram Layout Definition(§14.2.5) and Diagram Styles (§14.2.6)

Embedded Control Persistence (§15.2.8)

Embedded Object (§15.2.9)

Embedded Package (§15.2.10)

Hyperlink (§15.3).

Image (§15.2.13)

Video (§15.2.14)

VML Drawing (§15.2.17)

The Notes Master part shall not have implicit or explicit relationships to any other part defined by this Standard.

Notes Slide Part

Content Type:

application/vnd.openxmlformats-officedocument.presentationml.notesSlide+xml

Root Namespace:

http://schemas.openxmlformats.org/presentationml/2006/main

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/notesSlide

An instance of this part type contains the notes for a single slide.

A package shall contain one Notes Slide part for each slide that contains notes. If they exist, those parts shall each be the target of an implicit relationship from the Slide (§13.3.8) part.

[Example: The following Slide part-relationship item contains a relationship to a Notes Slide part, which is stored in the ZIP item ../notesSlides/notesSlide1.xml:

end example]

The root element for a part of this content type shall be notes.

[Example:

<p:notes xmlns:p="…"> <p:cSld name=""> … </p:cSld> <p:clrMapOvr> <a:masterClrMapping/> </p:clrMapOvr></p:notes>

end example]

A Notes Slide part shall be located within the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal).

A Notes Slide part is permitted to have implicit relationships to the following parts defined by this Standard:

Additional Characteristics (§15.2.1)

Bibliography (§15.2.3)

Custom XML Data Storage (§15.2.4)

Notes Master (§13.3.4)

Theme Override(§14.2.8)

Thumbnail (§15.2.14)

A Notes Slide part is permitted to have explicit relationships to the following parts defined by this Standard:

Audio (§15.2.2)

Chart (§14.2.1)

Diagrams: Diagram Colors(§14.2.3), Diagram Data(§14.2.4), Diagram Layout Definition(§14.2.5) and Diagram Styles (§14.2.6)

Embedded Control Persistence (§15.2.8)

Embedded Object (§15.2.9)

Embedded Package (§15.2.10)

Hyperlink (§15.3).

Image (§15.2.13)

Video (§15.2.14)

VML Drawing (§15.2.17)

The Notes Slide part shall not have implicit or explicit relationships to any other part defined by this Standard.

Presentation Part

Content Type:

application/vnd.openxmlformats-officedocument.presentationml.presentation.main+xml

application/vnd.openxmlformats-officedocument.presentationml.slideshow.main+xml

application/vnd.openxmlformats-officedocument.presentationml.template.main+xml

Root Namespace:

http://schemas.openxmlformats.org/presentationml/2006/main

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/officeDocument

An instance of this part type contains the definition for a slide presentation.

A package shall contain exactly one Presentation part, and that part shall be the target of a relationship in the package-relationship item.

[Example: The following PresentationML's package-relationship item contains a relationship to the Presentation part, which is stored in the ZIP item ppt/presentation.xml:

end example]

The root element for a part of this content type shall be presentation.

[Example: This presentation contains two slides:

<p:presentation xmlns:p="…" … > <p:sldMasterIdLst> <p:sldMasterId xmlns:rel="http://…/relationships" rel:id="rId1"/> </p:sldMasterIdLst>

<p:notesMasterIdLst> <p:notesMasterId xmlns:rel="http://…/relationships" rel:id="rId4"/> </p:notesMasterIdLst>

<p:handoutMasterIdLst> <p:handoutMasterId xmlns:rel="http://…/relationships" rel:id="rId5"/> </p:handoutMasterIdLst>

<p:sldIdLst> <p:sldId id="267" xmlns:rel="http://…/relationships" rel:id="rId2"/> <p:sldId id="256" xmlns:rel="http://…/relationships" rel:id="rId3"/> </p:sldIdLst>

<p:sldSz cx="9144000" cy="6858000"/> <p:notesSz cx="6858000" cy="9144000"/></p:presentation>

end example]

A Presentation part shall be located within the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal).

A Presentation part is permitted to have implicit relationships to the following parts defined by this Standard:

Additional Characteristics (§15.2.1)

Comments (§13.3.2)

Bibliography (§15.2.3)

Custom XML Data Storage (§15.2.4)

Font (§15.2.12)

Presentation Properties (§13.3.7)

Table Styles (§14.2.9)

Theme (§14.2.7)

Thumbnail (§15.2.14)

View Properties (§13.3.13).

A Presentation part is permitted to have explicit relationships to the following parts defined by this Standard:

Notes Master (§13.3.4)

Handout Master (§13.3.3)

Slide (§13.3.8)

Slide Layout (§13.3.9)

Slide Master (§13.3.10)

User Defined Tags (§13.3.12)

Presentation Properties Part

Content Type:

application/vnd.openxmlformats-officedocument.presentationml.presentationProperties+xml

Root Namespace:

http://schemas.openxmlformats.org/presentationml/2006/main

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/presProps

An instance of this part type contains all the presentation's properties.

A package shall contain exactly one Presentation Properties part, and that part shall be the target of an implicit relationship from the Presentation (§13.3.6) part.

[Example: The following Presentation part-relationship item contains a relationship to the Presentation Properties part, which is stored in the ZIP item presProps.xml:

end example]

The root element for a part of this content type shall be presentationPr.

[Example:

<p:presentationPr xmlns:p="…" …> <p:clrMru> … </p:clrMru> …</p:presentationPr>

end example]

A Presentation Properties part shall be located within the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal).

A Presentation Properties part shall not have implicit or explicit relationships to any other part defined by this Standard.

Slide Part

Content Type:

application/vnd.openxmlformats-officedocument.presentationml.slide+xml

Root Namespace:

http://schemas.openxmlformats.org/presentationml/2006/main

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/slide

A Slide part contains the contents of a single slide.

A package shall contain one Slide part per slide, and each of those parts shall be the target of an explicit relationship from the Presentation (§13.3.6) part.

[Example: Consider a PresentationML document having two slides. The corresponding Presentation part-relationship item contains two relationships to Slide parts, which are stored in the ZIP items slides/slide1.xml and slides/slide2.xml:

end example]

The root element for a part of this content type shall be sld.

[Example: slides/slide1.xml contains:

<p:sld xmlns:p="…"> <p:cSld name=""> … </p:cSld>

<p:clrMapOvr> … </p:clrMapOvr>

<p:timing> <p:tnLst> <p:par> <p:cTn id="1" dur="indefinite" restart="never" nodeType="tmRoot"/> </p:par> </p:tnLst> </p:timing></p:sld>

end example]

A Slide part shall be located within the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal).

A Slide part is permitted to have implicit relationships to the following parts defined by this Standard:

Additional Characteristics (§15.2.1)

Bibliography (§15.2.3)

Comments (§12.3.3)

Custom XML Data Storage (§15.2.4)

Notes Slide (§13.3.5)

Theme Override (§14.2.8)

Thumbnail (§15.2.14)

Slide Layout (§13.3.9)

Slide Synchronization Data (§13.3.11)

A Slide part is permitted to have explicit relationships to the following parts defined by this Standard:

Audio (§15.2.2)

Chart (§14.2.1)

Diagrams: Diagram Colors(§14.2.3), Diagram Data(§14.2.4), Diagram Layout Definition(§14.2.5) and Diagram Styles (§14.2.6)

Embedded Control Persistence (§15.2.8)

Embedded Object (§15.2.9)

Embedded Package (§15.2.10)

Hyperlink (§15.3).

Image (§15.2.13)

User Defined Tags (§13.3.12)

Video (§15.2.14)

VML Drawing (§15.2.17)

A Slide part shall not have implicit or explicit relationships to any other part defined by this Standard.

Slide Layout Part

Content Type:

application/vnd.openxmlformats-officedocument.presentationml.slideLayout+xml

Root Namespace:

http://schemas.openxmlformats.org/presentationml/2006/main

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/slideLayout

An instance of this part type contains the definition for a slide layout template for this presentation. This template defines the default appearance and positioning of drawing objects on this slide type when it is created.

A package shall contain one or more Slide Layout parts, and those parts shall be the target of an explicit relationship in the Presentation (§13.3.6) part, as well as an implicit relationship from the Slide Master (§13.3.10) part associated with this slide layout.

[Example: The following Slide Master part-relationship item contains relationships to several Slide Layout parts, which are stored in the ZIP items ../slideLayouts/slideLayoutN.xml:

end example]

The root element for a part of this content type shall be sldLayout.

[Example:

<p:sldLayout xmlns:p="…" matchingName="" type="title" preserve="1"> <p:cSld name="Title Slide"> … </p:cSld> <p:clrMapOvr> <a:masterClrMapping/> </p:clrMapOvr> <p:timing/> </p:sldLayout></p:sldMaster>

end example]

A Slide Layout part is permitted to have implicit relationships to the following parts defined by this Standard:

Additional Characteristics (§15.2.1)

Bibliography (§15.2.3)

Custom XML Data Storage (§15.2.4)

Slide Master (§13.3.10)

Theme Override (§14.2.8)

Thumbnail (§15.2.14)

A Slide Layout part is permitted to have explicit relationships to the following parts defined by this Standard:

Audio (§15.2.2)

Chart (§14.2.1)

Diagrams: Diagram Colors(§14.2.3), Diagram Data(§14.2.4), Diagram Layout Definition(§14.2.5) and Diagram Styles (§14.2.6)

Embedded Control Persistence (§15.2.8)

Embedded Object (§15.2.9)

Embedded Package (§15.2.10)

Hyperlink (§15.3).

Image (§15.2.13)

Video (§15.2.14)

VML Drawing (§15.2.17)

A Slide Layout part shall not have implicit or explicit relationships to any other part defined by this Standard.

Slide Master Part

Content Type:

application/vnd.openxmlformats-officedocument.presentationml.slideMaster+xml

Root Namespace:

http://schemas.openxmlformats.org/presentationml/2006/main

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/slideMaster

An instance of this part type contains the master definition of formatting, text, and objects that appear on each slide in the presentation that is derived from this slide master.

A package shall contain one or more Slide Master parts, each of which shall be the target of an explicit relationship from the Presentation (§13.3.6) part, as well as an implicit relationship from any Slide Layout (§13.3.9) part where that slide layout is defined based on this slide master. Each can optionally be the target of a relationship in a Slide Layout (§13.3.9) part as well.

[Example: The following Presentation part-relationship item contains a relationship to the Slide Master part, which is stored in the ZIP item slideMasters/slideMaster1.xml:

end example]

The root element for a part of this content type shall be sldMaster.

[Example:

<p:sldMaster xmlns:p="…"> <p:cSld name=""> … </p:cSld> <p:clrMap … /></p:sldMaster>

end example]

A Slide Master part shall be located within the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal).

A Slide Master part is permitted to have implicit relationships to the following parts defined by this Standard:

Additional Characteristics (§15.2.1)

Bibliography (§15.2.3)

Custom XML Data Storage (§15.2.4)

Slide Layout (§13.3.9)

Theme (§14.2.7)

Thumbnail (§15.2.14)

A Slide Master part is permitted to have explicit relationships to the following parts defined by this Standard:

Audio (§15.2.2)

Chart (§14.2.1)

Diagrams: Diagram Colors(§14.2.3), Diagram Data(§14.2.4), Diagram Layout Definition(§14.2.5) and Diagram Styles (§14.2.6)

Embedded Control Persistence (§15.2.8)

Embedded Object (§15.2.9)

Embedded Package (§15.2.10)

Hyperlink (§15.3).

Image (§15.2.13)

Video (§15.2.14)

VML Drawing (§15.2.17)

A Slide Master part shall not have implicit or explicit relationships to any other part defined by this Standard.

Slide Synchronization Data Part

Content Type:

application/vnd.openxmlformats-officedocument.presentationml.slideUpdateInfo+xml

Root Namespace:

http://schemas.openxmlformats.org/presentationml/2006/main

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/slideUpdateInfo

An instance of this part type contains properties specifying the current state of a slide that is being synchronized with a version of that slide stored on a central server.

A package shall contain zero or one Slide Synchronization Data part for each slide stored in the presentation, and that part shall be the target of an implicit relationship from the corresponding Slide (§13.3.8) part.

[Example: The following Slide part-relationship item contains a relationship to the Slide Synchronization Data part, which is stored in the ZIP item slideUpdateInfo/slideUpdateInfo1.xml:

end example]

The root element for a part of this content type shall be sldSyncPr.

[Example:

<p:sldSyncPr xmlns:p="…" serverSldId="1" serverSldModifiedTime="2006-08-12T01:31:08" clientInsertedTime="2006-08-12T01:34:11.227" />

end example]

A Slide Synchronization Data part shall be located within the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal).

A Slide Synchronization Data part is permitted to have implicit relationships to the following parts defined by this Standard:

Slide Synchronization Server Location (§13.4)

A Slide Synchronization Data part shall not have implicit or explicit relationships to any other part defined by this Standard.

User Defined Tags Part

Content Type:

application/vnd.openxmlformats-officedocument.presentationml.tags+xml

Root Namespace:

http://schemas.openxmlformats.org/presentationml/2006/main

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/tags

An instance of this part type contains a set of user-defined properties for an object in a presentation (each property consisting of a name/value pair).

A package shall contain zero or more User Defined Tags parts, zero or one as the target of an explicit relationship from the corresponding Presentation (§13.3.6) or Slide (§13.3.8) part.

[Example: The following Slide part-relationship item contains a relationship to the User Defined Tags part, which is stored in the ZIP item tags/tag1.xml:

end example]

The root element for a part of this content type shall be tagLst.

[Example:

<p:tagLst xmlns:p="…" > <p:tag name="testTagName" val="testTagValue" /></p:tagLst>

end example]

A User Defined Tags part shall be located within the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal).

A User Defined Tags part shall not have implicit or explicit relationships to any other part defined by this Standard.

View Properties Part

Content Type:

application/vnd.openxmlformats-officedocument.presentationml.viewProps+xml

Root Namespace:

http://schemas.openxmlformats.org/presentationml/2006/main

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/viewProps

An instance of this part type contains display properties for this presentation.

A package shall contain zero or one View Properties part, and if it exists, that part shall be the target of an implicit relationship from the Presentation (§13.3.6) part.

[Example: The following Presentation part-relationship item contains a relationship to the View Properties part, which is stored in the ZIP item viewProps.xml:

end example]

The root element for a part of this content type shall be viewPr.

[Example:

<p:viewPr xmlns:p="…" …> <p:normalViewPr showOutlineIcons="0"> … </p:normalViewPr>

<p:slideViewPr> … </p:slideViewPr>

<p:outlineViewPr> … </p:outlineViewPr>

<p:notesTextViewPr> … </p:notesTextViewPr> <p:gridSpacing cx="78028800" cy="78028800"/></p:viewPr>

end example]

A View Properties part shall be located within the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal).

A View Properties part shall not have implicit or explicit relationships to any other part defined by this Standard.

HTML Publish Location

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/ htmlPubSaveAs

When a presentation specifies an external location to which an optional copy might be pushed in the HTML format, this relationship shall be used to target the location where the HTML copy of the presentation is published.

A package shall contain one HTML Publish Location relationship for each slide linked with an HTML publish location, and that relationships shall be an explicit relationship from the corresponding Presentation Properties (§13.3.7) part.

[Example: A Presentation Properties part, which stores an HTML Publish Location of http://www.openxmlformats.org/test.htm will contain the following relationship in that part's relationship part:

end example]

An HTML publish location shall be located external to the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be External).

Slide Synchronization Server Location

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/slideUpdateUrl

When a slide is being synchronized with a copy stored on a remote server, this relationship shall be used to target the location where the server copy of the slide is stored.

A package shall contain one Slide Synchronization Server Location relationship for each slide linked with server data, and that relationships shall be an implicit relationship from the corresponding Slide Synchronization Data (§13.3.11) part.

[Example: A Slide Synchronization Data part that stores information about a slide that is synchronized with a server located at http://www.openxmlformats.org/slides/ will contain the following relationship in that part's relationship part item:

end example]

A slide synchronization server location shall be located external to the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be External).

DrawingML

The relationship items and parts defined in this clause are used by one or more of WordprocessingML (§10), SpreadsheetML (§12), and PresentationML (§13) environments.

Glossary of DrawingML-Specific Terms

diagram — A picture or graphical representation that is displayed using a related set of color, data, layout, and style parts. Examples of diagram types are cycle, organization chart, pyramid, target, and Venn.

Part Summary

The subclauses subordinate to this one describe in detail each of the part types specific to DrawingML.

[Note: For convenience, information from those subclauses is summarized in the following table:

Part

Relationship Target of

Root Element

Ref.

Chart

WordprocessingML: Main Document

SpreadsheetML: Drawings

PresentationML: Handout Master, Notes Master, Notes Slide, Slide Layout, Slide Master, Slide

All: Chart Drawing

chartSpace

§14.2.1

Chart Drawing

All: Chart

userShapes

§14.2.2

Diagram Colors

WordprocessingML: Main Document

SpreadsheetML: Drawings

PresentationML: Handout Master, Notes Master, Notes Slide, Slide Layout, Slide Master, Slide

colorsDef

§14.2.3

Diagram Data

WordprocessingML: Main Document

SpreadsheetML: Drawings

PresentationML: Handout Master, Notes Master, Notes Slide, Slide Layout, Slide Master, Slide

dataModel

§14.2.4

Diagram Layout Definition

WordprocessingML: Main Document

SpreadsheetML: Drawings

PresentationML: Handout Master, Notes Master, Notes Slide, Slide Layout, Slide Master, Slide

layoutDef

§14.2.5

Diagram Style

WordprocessingML: Main Document

SpreadsheetML: Drawings

PresentationML: Handout Master, Notes Master, Notes Slide, Slide Layout, Slide Master, Slide

styleDef

§14.2.6

Theme

WordprocessingML: Main Document

SpreadsheetML: Workbook

PresentationML: Handout Master, Notes Master, Presentation, Slide Master

officeStyleSheet

§14.2.7

Theme Override

PresentationML: Notes Slide, Slide, Slide Layout

themeOverride

§14.2.8

Table Styles

PresentationML: Presentation

tblStyleLst

§14.2.9

end note]

Chart Part

Content Type:

application/vnd.openxmlformats-officedocument.drawingml.chart+xml

Root Namespace:

http://schemas.openxmlformats.org/drawingml/2006/chart

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/chart

An instance of this part type describes a chart.

A package shall contain a Chart part for each chart in the document. In a WordprocessingML document, each such part shall be the target of an explicit relationship in a Main Document (§11.3.10) part. In a SpreadsheetML document, each such part shall be the target of an explicit relationship in a Drawings (§12.3.8) part. In a PresentationML document, each such part shall be the target of an explicit relationship in a Handout Master (§13.3.3), Notes Master (§13.3.4), Notes Slide (§13.3.5), Slide (§13.3.8), Slide Layout (§13.3.9), or Slide Master (§13.3.10) part. This part is permitted to also be the target of an explicit relationship in a Chart Drawing (§14.2.2) part, if the chart that points at this Chart Drawing part is the target of a relationship from a Chartsheet part. In other words, the only time a chart can embed another chart is if the parent chart is part of a chartsheet.

[Example: The following Main Document part-relationship item contains relationships to two Chart parts, which are stored in the ZIP items ../charts/chartN.xml:

The following Drawings part-relationship item contains a relationship to a Chart part, which is stored in the ZIP item ../charts/chart1.xml:

The following Slide part-relationship item contains relationships to two Chart parts, which are stored in the ZIP items ../charts/chartN.xml:

end example]

The root element for a part of this content type shall be chartSpace.

[Example: chart1.xml contains the following clustered bar chart:

<c:chartSpace …> <c:chart> <c:title> … </c:title>

<c:plotArea> <c:layout> … </c:layout> <c:barChart> … </c:barChart> </c:plotArea>

<c:legend> … </c:legend> </c:chart> …</c:chartSpace>

end example]

For WordprocessingML and PresentationML documents, the data for a chart is not stored in the Chart part directly. Instead, it shall be stored in an embedded SpreadsheetML package (§12.2) targeted by an Embedded Package (§15.2.10) part specified by that Chart part. For SpreadsheetML documents, the data for a chart is stored directly in the Drawing’s parent worksheet; no embedded SpreadsheetML package shall be used.

A Chart part shall be located within the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal).

A Chart part is permitted to have explicit relationships to the following parts defined by this Standard:

Chart Drawing (§14.2.2)

Embedded Package (§15.2.10)

A Chart part shall not have any implicit or explicit relationships to any other part defined by this Standard.

Chart Drawing Part

Content Type:

application/vnd.openxmlformats-officedocument.drawingml.chartshapes+xml

Root Namespace:

http://schemas.openxmlformats.org/drawingml/2006/chart

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/chartUserShapes

An instance of this part type contains all basic drawing elements (shapes) which are explicitly associated with this chart. These drawing elements are automatically moved with the chart when it is moved and resized when the chart is resized.

A package is permitted to contain one Chart Drawing part per chart part, and each such part shall be the target of an explicit relationship from a Chart (§14.2.1) part.

[Example: The following Chart part-relationship item contains a relationship to a Chart Drawing part, which is stored in the ZIP item ../drawings/drawing1.xml:

end example]

The root element for a part of this content type shall be userShapes.

[Example:

<c:userShapes xmlns:cdr="…" xmlns:c="…"> <cdr:relSizeAnchor> … </cdr:relSizeAnchor></c:userShapes>

end example]

A Chart Drawing part shall be located within the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal).

A Chart Drawing part is permitted to have explicit relationships to the following parts defined by this Standard:

Chart (§14.2.1)

A Chart Drawing part shall not have any implicit or explicit relationships to any other part defined by this Standard.

Diagram Colors Part

Content Type:

application/vnd.openxmlformats-officedocument.drawingml.diagramColors+xml

Root Namespace:

http://schemas.openxmlformats.org/drawingml/2006/diagram

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/diagramColors

An instance of this part type contains color information for a diagram.

A package shall contain exactly one Diagram Colors part per diagram. Each Diagram Colors part shall be the target of an explicit relationship in a WordprocessingML Main Document (§11.3.10), SpreadsheetML Drawings (§12.3.8), or PresentationML Slide (§13.3.8) part.

[Example: The following SpreadsheetML Drawings part-relationship item contains a relationship to two Diagram Colors parts, which are stored in the ZIP items ../graphics/colorsN.xml.

end example]

The root element for a part of this content type shall be colorsDef.

[Example: colors1.xml contains the following:

<cs:colorsDef xmlns:cs="…" uniqueId="…" minVer="12.0"> <cs:title lang="" val="Primary Accent 2"/> <cs:desc lang="" val="Primary Accent 2"/> <cs:catLst> <cs:cat type="accent1" pri="11200"/> </cs:catLst>

<cs:styleLbl …> … </cs:styleLbl> … <cs:styleLbl …> … </cs:styleLbl></cs:colorsDef>

end example]

A Diagram Colors part shall be located within the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal).

A Diagram Colors part shall not have implicit or explicit relationships to any other part defined by this Standard.

Diagram Data Part

Content Type:

application/vnd.openxmlformats-officedocument.drawingml.diagramData+xml

Root Namespace:

http://schemas.openxmlformats.org/drawingml/2006/diagram

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/diagramData

An instance of this part type contains the semantic data for a diagram.

A package shall contain exactly one Diagram Data part per diagram. Each Diagram Data part shall be the target of an explicit relationship in a WordprocessingML Main Document (§11.3.10); a SpreadsheetML Drawings part (§12.3.8); or a PresentationML Handout Master (§13.3.3), Notes Master (§13.3.4), Notes Slide (§13.3.5), Slide (§13.3.8), Slide Layout (§13.3.9), or Slide Master (§13.3.10) part.

[Example: The following SpreadsheetML Drawings part-relationship item contains a relationship to two Diagram Data parts, which are stored in the ZIP items ../graphics/dataN.xml.

end example]

The root element for a part of this content type shall be dataModel.

[Example: data1.xml contains the following:

<dm:dataModel xmlns:dm="…"> <dm:ptLst> … </dm:ptLst> <dm:cxnLst> … </dm:cxnLst> <dm:bg/> <dm:whole/></dm:dataModel>

end example]

A Diagram Data part shall be located within the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal).

A Diagram Data part is permitted to have explicit relationships to the following parts defined by this Standard:

Image (§15.2.13)

A Diagram Data part shall not have any implicit or explicit relationships to other parts defined by this Standard.

Diagram Layout Definition Part

Content Type:

application/vnd.openxmlformats-officedocument.drawingml.diagramLayout+xml

Root Namespace:

http://schemas.openxmlformats.org/drawingml/2006/diagram

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/diagramLayout

An instance of this part type is a template that describes how diagram-related data is mapped to a shape.

A package shall contain exactly one Diagram Layout Definition part per diagram. Each Layout Definition part shall be the target of an explicit relationship from a WordprocessingML Main Document (§11.3.10); a SpreadsheetML Drawings part (§12.3.8); or a PresentationML Handout Master (§13.3.3), Notes Master (§13.3.4), Notes Slide (§13.3.5), Slide (§13.3.8), Slide Layout (§13.3.9), or Slide Master (§13.3.10) part. If a document contains multiple diagrams having the same graphic layout definition, each of those diagrams shall have its own copy of that Diagram Layout Definition part.

[Example: The following SpreadsheetML Drawings part-relationship item contains a relationship to two Diagram Layout Definition parts, which are stored in the ZIP items ../graphics/layoutN.xml.

end example]

The root element for a part of this content type shall be layoutDef.

[Example: layout1.xml contains the following:

<lo:layoutDef xmlns:lo="…" uniqueId="…2" minVer="12.0" defStyle=""> <lo:title lang="" val="Hierarchy 2"/> <lo:desc lang="" val=""/> <lo:catLst> <lo:cat type="hierarchy" pri="2000"/> </lo:catLst>

<lo:sampData> … </lo:sampData>

<lo:styleData> … </lo:styleData>

<lo:clrData> … </lo:clrData>

<lo:layoutNode name="Name0" styleLbl="" moveWith=""> … </lo:layoutNode></lo:layoutDef>

end example]

A Diagram Layout Definition part shall be located within the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal).

A Diagram Layout Definition part is permitted to have explicit relationships to the following parts and items defined by this Standard:

Image (§15.2.13)

A Diagram Layout Definition part shall not have any implicit or explicit relationships to other parts defined by this Standard.

Diagram Style Part

Content Type:

application/vnd.openxmlformats-officedocument.drawingml.diagramStyle+xml

Root Namespace:

http://schemas.openxmlformats.org/drawingml/2006/diagram

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/diagramQuickStyle

An instance of this part type maps diagram semantic information to a document's theme.

A package shall contain exactly one Diagram Style part per diagram. Each Style part shall be the target of an explicit relationship from a WordprocessingML Main Document (§11.3.10); a SpreadsheetML Drawings part (§12.3.8); or a PresentationML Handout Master (§13.3.3), Notes Master (§13.3.4), Notes Slide (§13.3.5), Slide (§13.3.8), Slide Layout (§13.3.9), or Slide Master (§13.3.10) part.

[Example: The following SpreadsheetML Drawings part-relationship item contains a relationship to two Diagram Style parts, which are stored in the ZIP items ../graphics/quickStyleN.xml.

end example]

The root element for a part of this content type shall be styleDef.

[Example: quickStyle1.xml contains the following:

<qs:styleDef xmlns:qs="…" uniqueId="…" minVer="12.0"> <qs:title lang="" val="Style 2"/> <qs:desc lang="" val="Style 2"/> <qs:catLst> <qs:cat type="simple" pri="10200"/> </qs:catLst> <qs:scene3d> … </qs:scene3d>

<qs:style> … </qs:style>

<qs:styleLbl name="…"> … </qs:styleLbl> … <qs:styleLbl name="…"> … </qs:styleLbl></qs:styleDef>

end example]

A Diagram Style part shall be located within the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal).

A Diagram Style part shall not have implicit or explicit relationships to other parts defined by this Standard.

Theme Part

Content Type:

application/vnd.openxmlformats-officedocument.theme+xml

Root Namespace:

http://schemas.openxmlformats.org/drawingml/2006/main

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/theme

An instance of this part type contains information about a document's theme, which is a combination of color scheme, font scheme, and format scheme (the latter also being referred to as effects). For a WordprocessingML document, the choice of theme affects the color and style of headings, among other things. For a SpreadsheetML document, the choice of theme affects the color and style of cell contents and charts, among other things. For a PresentationML document, the choice of theme affects the formatting of slides, handouts, and notes via the associated master, among other things.

A WordprocessingML or SpreadsheetML package shall contain zero or one Theme part, which shall be the target of an implicit relationship in a Main Document (§11.3.10) or Workbook (§12.3.23) part. A PresentationML package shall contain zero or one Theme part per Handout Master (§13.3.3), Notes Master (§13.3.4), Slide Master (§13.3.10) or Presentation (§13.3.6) part via an implicit relationship.

[Example: The following WordprocessingML Main Document part-relationship item contains a relationship to the Theme part, which is stored in the ZIP item theme/theme1.xml:

end example]

The root element for a part of this content type shall be officeStyleSheet.

[Example: theme1.xml contains the following, where the name attributes of the clrScheme, fontScheme, and fmtScheme elements correspond to the document's color scheme, font scheme, and format scheme, respectively:

<a:officeStyleSheet xmlns:a="…"> <a:baseStyles> <a:clrScheme name="…"> … </a:clrScheme>

<a:fontScheme name="…"> … </a:fontScheme>

<a:fmtScheme name="…"> … </a:fmtScheme> </a:baseStyles> <a:objectDefaults/></a:officeStyleSheet>

end example]

A Theme part shall be located within the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal).

A Theme part is permitted to contain explicit relationships to the following parts defined by this Standard:

Image (§15.2.13)

A Theme part shall not have any implicit or explicit relationships to other parts defined by this Standard.

Theme Override Part

Content Type:

application/vnd.openxmlformats-officedocument.themeOverride+xml

Root Namespace:

http://schemas.openxmlformats.org/drawingml/2006/main

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/themeOverride

An instance of this part type contains information about an object’s theme override, which are overrides to the color scheme, font scheme, and format scheme (the latter also being referred to as effects) for a particular slide, notes slide, or handout.

A PresentationML package shall contain zero or one Theme Override part per Notes Slide (§13.3.5), Slide (§13.3.8), or Slide Layout (§13.3.9) part via an implicit relationship.

[Example: The following WordprocessingML Main Document part-relationship item contains a relationship to the Theme part, which is stored in the ZIP item theme/theme1.xml:

end example]

The root element for a part of this content type shall be ossOverride.

[Example:

<a:ossOverride xmlns:a="…" > …</a:ossOverride>

end example]

A Theme Override part shall be located within the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal).

A Theme Override part shall not contain implicit or explicit relationships to other parts defined by this Standard.

Table Styles Part

Content Type:

application/vnd.openxmlformats-officedocument.presentationml.tableStyles+xml

Root Namespace:

http://schemas.openxmlformats.org/drawingml/2006/main

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/tableStyles

An instance of this part type contains information about the table styles used by tables in this presentation. A table style defines characteristics such as row and column colors, heading row colors, and text.

A PresentationML package shall contain no more than one Table Styles part per Presentation (§13.3.6) part via an implicit relationship.

[Example: The following Presentation part-relationship item contains a relationship to a Table Styles part, which is stored in the ZIP item tableStyles.xml:

end example]

The root element for a part of this content type shall be tblStyleLst.

[Example: tablestyles.xml contains the following:

<a:tblStyleLst xmlns:a="…"> <a:tblStyle> … </a:tblStyle></a:tblStyleLst>

end example]

A Table Styles part shall be located within the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal).

A Table Styles part shall not contain implicit or explicit relationships to other parts defined by this Standard.

Shared

The relationship items and parts defined in this clause are used by one or more of WordprocessingML (§10), SpreadsheetML (§12), and PresentationML (§13) environments.

Glossary of Shared Terms

control — A region of active content within an Office Open XML document.

Part Summary

The subclauses subordinate to this one describe in detail each of the shared part types.

[Note: For convenience, information from those subclauses is summarized in the following table:

Part

Relationship Target of

Root Element

Ref.

Additional Characteristics

Numerous PresentationML, SpreadsheetML, and WordprocessingML parts

Characteristics

§15.2.1

Audio

Numerous PresentationML, SpreadsheetML, and WordprocessingML parts

Not applicable

§15.2.2

Bibliography

Numerous PresentationML, SpreadsheetML, and WordprocessingML parts

Sources

§15.2.3

Custom XML Data Storage

Numerous PresentationML, SpreadsheetML, and WordprocessingML parts

Not applicable

§15.2.4

Custom XML Data Storage Properties

Custom XML Data Storage

datastoreItem

§15.2.5

Digital Signature Origin

WordprocessingML, SpreadsheetML, or PresentationML package

Not applicable

§15.2.6

Digital Signature XML Signature

Digital Signature Origin

Signature

§15.2.7

Embedded Control Persistence

Numerous PresentationML, SpreadsheetML, and WordprocessingML parts

Not applicable

§15.2.8

Embedded Object

Numerous PresentationML, SpreadsheetML, and WordprocessingML parts

Not applicable

§15.2.9

Embedded Package

Numerous PresentationML, SpreadsheetML, and WordprocessingML parts

Not applicable

§15.2.10

File Properties, Extended

WordprocessingML, SpreadsheetML, or PresentationML package

Properties

§ 15.2.11.3

File Properties, Core

WordprocessingML, SpreadsheetML, or PresentationML package

coreProperties

§15.2.11.1

File Properties, Custom

WordprocessingML, SpreadsheetML, or PresentationML package

properties

§15.2.11.2

Font

WordprocessingML Font Table part, PresentationML Presentation part

Not applicable

§15.2.12

Image

Numerous PresentationML, SpreadsheetML, and WordprocessingML parts

Not applicable

§15.2.13

Printer Settings

SpreadsheetML Chartsheet, Dialogsheet, Worksheet parts, WordprocessingML Main Document or Glossary Document parts

Not applicable

§15.2.14

Thumbnail

WordprocessingML, SpreadsheetML, or PresentationML package

Not applicable

§15.2.14

Video part

Numerous PresentationML and WordprocessingML parts

Not applicable

§15.2.16

end note]

Additional Characteristics Part

Content Type:

application/xml

Root Namespace:

http://schemas.openxmlformats.org/officeDocument/2006/additionalCharacteristics

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/customXml

An instance of this part type contains information about additional characteristics of the producer that generated the document, when those characteristics cannot be specified using elements defined by this Standard.

A package is permitted to contain zero or one Additional Characteristics parts, and each such part shall be the target of an implicit relationship from a Main Document (§11.3.10) part in a WordprocessingML package; a Workbook (§12.3.23) part in a SpreadsheetML package; or a Handout Master (§13.3.3) , Notes Master (§13.3.4), Notes Slide (§13.3.5), Presentation (§13.3.6), Slide (§13.3.8), Slide Layout (§13.3.9), or Slide Master (§13.3.10) part in a PresentationML package.

[Example: The following Main Document part-relationship item contains a relationship to an Additional Characteristics part, which is stored in the ZIP item ../customXML/item2.xml:

end example]

An Additional Characteristics part shall be located within the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal).

An Additional Characteristics part is permitted to have implicit relationships to the following parts defined by this Standard:

Custom XML Data Storage Properties (§15.2.5)

An Additional Characteristics part shall not have implicit or explicit relationships to any other part defined by this Standard.

Audio Part

Content Type:

Any supported audio type.

[Note: Some example content types are:

audio/aiff

http://developer.apple.com/documentation/QuickTime/INMAC/SOUND/imsoundmgr.30.htm

audio/midi

http://www.midi.org/about-midi/specinfo.shtml

audio/x-ms-wax

http://msdn.microsoft.com/library/en-us/wmplay10/mmp_sdk/asx_elementsintro.asp

end note]

Root Namespace:

not applicable

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/audio

An instance of this part type contains an audio file.

A PresentationML package is permitted to contain zero or more Sound parts, each of which shall be the target of a relationship in a Handout Master (§13.3.3), Notes Slide (§13.3.5), Notes Master (§13.3.4), Slide (§13.3.8), Slide Layout (§13.3.9), or Slide Master (§13.3.10) part-relationship item. [Example: The following Slide part-relationship item contains a relationship to a Sound part, which is stored as the file E:\Beethoven's Symphony No. 9.wma:

end example]

An Audio part may be located within or external to the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element may be Internal or External).

An Audio part is not stored as XML; instead, it involves a relationship target that is an audio clip.

An Audio part shall not have implicit or explicit relationships to other parts defined by this Standard.

Bibliography Part

Content Type:

application/xml

Root Namespace:

http://schemas.openxmlformats.org/officeDocument/2006/bibliography

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/customXml

An instance of this part type contains bibliographic data for the current package.

A package is permitted to contain zero or one Bibliography part, and each such part shall be the target of an implicit relationship in a Main Document (§11.3.10) part in a WordprocessingML package; a Workbook (§12.3.23) part in a SpreadsheetML package; or a Handout Master (§13.3.3) , Notes Master (§13.3.4), Notes Slide (§13.3.5), Slide (§13.3.8), Slide Layout (§13.3.9), or Slide Master (§13.3.10) part in a PresentationML package.

[Example: The following Main Document part-relationship item contains a relationship to a Bibliography part, which is stored in the ZIP item ../customXML/bib1.xml:

end example]

A Bibliography part shall be located within the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal).

A Bibliography part is permitted to have implicit relationships to the following parts defined by this Standard:

Custom XML Data Storage Properties (§15.2.5)

A Bibliography part shall not have implicit or explicit relationships to any other part defined by this Standard.

Custom XML Data Storage Part

Content Type:

application/xml

Root Namespace:

any XML allowed

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/customXml

An instance of this part type can contain arbitrary XML. As such, an instance of this part can be used to roundtrip arbitrary custom XML data with this package.

A package is permitted to contain one or more Custom XML Data Storage parts, and each such part shall be the target of an implicit relationship in a Main Document (§11.3.10) part in a WordprocessingML package; a Workbook (§12.3.23) part in a SpreadsheetML package; or a Handout Master (§13.3.3) , Notes Master (§13.3.4), Notes Slide (§13.3.5), Presentation (§13.3.6), Slide (§13.3.8), Slide Layout (§13.3.9), or Slide Master (§13.3.10) part in a PresentationML package.

[Example: The following Main Document part-relationship item contains a relationship to a Custom XML Data Storage part, which is stored in the ZIP item ../customXML/item1.xml:

end example]

A Custom XML Data Storage part shall be located within the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal).

A Custom XML Data Storage part is permitted to have implicit relationships to the following parts defined by this Standard:

Custom XML Data Storage Properties (§15.2.5)

A Custom XML Data Storage part shall not have implicit or explicit relationships to any other part defined by this Standard.

Custom XML Data Storage Properties Part

Content Type:

application/vnd.openxmlformats-officedocument.customXmlProperties+xml

Root Namespace:

http://schemas.openxmlformats.org/officeDocument/2006/customXmlDataProps

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/customXmlProps

An instance of this part type contains the set of properties which are specified for this custom XML data. These properties consist of a unique ID for the storage, as well as information on the set of XML schemas used by this custom XML data storage.

A package is permitted to contain zero or more Custom XML Data Storage Properties parts, and each such part shall be the target of an implicit relationship from a Custom XML Data Storage (§15.2.4) part.

[Example: The following Custom XML Data Storage part-relationship item contains a relationship to a Custom XML Data Storage Properties part, which is stored in the ZIP item itemProps1.xml:

end example]

The root element for a part of this content type shall be datastoreItem.

[Example:

<ds:datastoreItem ds:itemID="{D85…53A}" xmlns:ds="…"/> \

end example]

A Custom XML Data Storage Properties part shall be located within the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal).

A Custom XML Data Storage Properties part shall not have implicit or explicit relationships to other parts defined by this Standard.

Digital Signature Origin Part

Content Type:

application/vnd.openxmlformats-package.digital-signature-origin

Root Namespace:

not applicable

Source Relationship:

http://schemas.openxmlformats.org/package/2006/relationships/digital-signature/origin

The Digital Signature Origin part is the starting point for navigating through the signatures in a package.

This part shall have no contents.

A package is permitted to contain zero or one Digital Signature Origin part in a package and it shall the target of a relationship from the package-relationship item for a WordprocessingML, SpreadsheetML, or PresentationML package.

[Example: The following package-relationship item contains a relationship to a Digital Signature Origin part, which is stored in the ZIP item origin.sigs:

end example]

A Digital Signature Origin part shall be located within the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal).

A Digital Signature Origin part is permitted to have implicit relationships to the following parts defined by this Standard:

Digital Signature XML Signature (§15.2.7)

A Digital Signature Origin part shall not have implicit or explicit relationships to any other part defined by this Standard.

Digital Signature XML Signature Part

Content Type:

application/vnd.openxmlformats-package.digital-signature-xmlsignature+xml

Root Namespace:

http://schemas.openxmlformats.org/package/2006/digital-signature

Source Relationship:

http://schemas.openxmlformats.org/package/2006/relationships/digital-signature/signature

The Digital Signature XML Signature part contains digital signature markup.

A package is permitted to contain zero or more Digital Signature XML Signature parts, one for each digital signature in a package, and each of these shall be the target of an implicit relationship from the Digital Signature Origin (§15.2.6) part.

[Example: The following Digital Signature Origin part-relationship item contains a relationship to a Digital Signature XML Signature part, which is stored in the ZIP item sig1.xml:

end example]

The root element for this part shall be Signature.

[Example:

end example]

A Digital Signature XML Signature part shall be located within the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal).

A Digital Signature XML Signature part shall not have implicit or explicit relationships to any part defined by this Standard.

Embedded Control Persistence Part

Content Type:

Any supported control type.

[Note: There are a number of possible control types. One example of a potential control type would be an Active X control, which would use the following content type: application/vnd.ms-office.activeX+xml. end note]

Root Namespace:

not applicable

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/control

An instance of this part contains information about an embedded control in the package. This information is provided by the specified control when asked to persist.

A package is permitted to contain one or more Embedded Control Persistence parts, and each such part shall be the target of an explicit relationship in an Endnotes (§11.3.4), Footer (§11.3.6), Footnotes (§11.3.7), Header (§11.3.9), or Main Document (§11.3.10) part-relationship item in a WordprocessingML package; a Worksheet part (§12.3.24) 15.2.17in a SpreadsheetML package; or a Handout Master (§13.3.3), Notes Slide (§13.3.5), Notes Master (§13.3.4), Slide (§13.3.8), Slide Layout (§13.3.9), Slide Master (§13.3.10) part-relationship item in a PresentationML package.

The content type of this part shall determine the format and contents of the embedded control.

[Example: The following example shows the persistence that could be used for an embedded control which is a Java applet within a WordprocessingML document:

<w:p>

<w:r w:rsidR="005810E1">

<w:object w:dxaOrig="1440" w:dyaOrig="1440">

<v:shapetype id="_x0000_t75" coordsize="21600,21600" o:spt="75" o:preferrelative="t" path="m@4@5l@4@11@9@11@9@5xe" filled="f" stroked="f">

<v:stroke joinstyle="miter" />

<v:formulas>

<v:f eqn="if lineDrawn pixelLineWidth 0" />

<v:f eqn="sum @0 1 0" />

<v:f eqn="sum 0 0 @1" />

<v:f eqn="prod @2 1 2" />

<v:f eqn="prod @3 21600 pixelWidth" />

<v:f eqn="prod @3 21600 pixelHeight" />

<v:f eqn="sum @0 0 1" />

<v:f eqn="prod @6 1 2" />

<v:f eqn="prod @7 21600 pixelWidth" />

<v:f eqn="sum @8 21600 0" />

<v:f eqn="prod @7 21600 pixelHeight" />

<v:f eqn="sum @10 21600 0" />

</v:formulas>

<v:path o:extrusionok="f" gradientshapeok="t" o:connecttype="rect" />

<o:lock v:ext="edit" aspectratio="t" />

</v:shapetype>

<v:shape id="_x0000_i1027" type="#_x0000_t75" style="width:1in;height:24pt" o:ole="">

<v:imagedata r:id="rId4" o:title="" />

</v:shape>

<w:control r:id="rId5" w:name="CommandButton1" w:shapeid="_x0000_i1027" />

</w:object>

</w:r>

</w:p>

The relationship type for rId5 is: http://schemas.openxmlformats.org/officeDocument/2006/relationships/control

The XML content of the part referenced by rId5 could be:

end example]

[Example: The following example shows the persistence that could be used for an embedded control which is an ActiveX control within a WordprocessingML document:

<w:p>

<w:r w:rsidR="005810E1">

<w:object w:dxaOrig="1440" w:dyaOrig="1440">

<v:shapetype id="_x0000_t75" coordsize="21600,21600" o:spt="75" o:preferrelative="t" path="m@4@5l@4@11@9@11@9@5xe" filled="f" stroked="f">

<v:stroke joinstyle="miter" />

<v:formulas>

<v:f eqn="if lineDrawn pixelLineWidth 0" />

<v:f eqn="sum @0 1 0" />

<v:f eqn="sum 0 0 @1" />

<v:f eqn="prod @2 1 2" />

<v:f eqn="prod @3 21600 pixelWidth" />

<v:f eqn="prod @3 21600 pixelHeight" />

<v:f eqn="sum @0 0 1" />

<v:f eqn="prod @6 1 2" />

<v:f eqn="prod @7 21600 pixelWidth" />

<v:f eqn="sum @8 21600 0" />

<v:f eqn="prod @7 21600 pixelHeight" />

<v:f eqn="sum @10 21600 0" />

</v:formulas>

<v:path o:extrusionok="f" gradientshapeok="t" o:connecttype="rect" />

<o:lock v:ext="edit" aspectratio="t" />

</v:shapetype>

<v:shape id="_x0000_i1027" type="#_x0000_t75" style="width:1in;height:24pt" o:ole="">

<v:imagedata r:id="rId4" o:title="" />

</v:shape>

<w:control r:id="rId5" w:name="CommandButton1" w:shapeid="_x0000_i1027" />

</w:object>

</w:r>

</w:p>

The relationship type for rId5 is: http://schemas.openxmlformats.org/officeDocument/2006/relationships/control

The content type of the part referenced by rId5 could be: application/vnd.ms-office.activeX+xml

The XML content of the part referenced by rId5 could be:

<ax:ocx ax:classid="{D7053240-CE69-11CD-A777-00DD01143C57}"

ax:persistence="persistPropertyBag"

xmlns:ax="http://schemas.microsoft.com/office/2006/activeX"> <ax:ocxPr ax:name="Caption" ax:value="CommandButton1" /> <ax:ocxPr ax:name="Size" ax:value="2540;847" /> <ax:ocxPr ax:name="FontName" ax:value="Calibri" /> <ax:ocxPr ax:name="FontHeight" ax:value="225" /> <ax:ocxPr ax:name="FontCharSet" ax:value="0" /> <ax:ocxPr ax:name="FontPitchAndFamily" ax:value="2" /> <ax:ocxPr ax:name="ParagraphAlign" ax:value="3" /> </ax:ocx>

end example]

An Embedded Control Persistence part shall be located within the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal).

An Embedded Control Persistence part shall not have any implicit or explicit relationships to other parts defined by this Standard.

Embedded Object Part

Content Type:

application/vnd.openxmlformats-officedocument.oleObject

Root Namespace:

not applicable

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/oleObject

An instance of this part type can contain an embedded object produced by any embedded object server.

A package is permitted to contain zero or more Embedded Object parts, and each such part shall be the target of an explicit relationship from a Comments (§11.3.2), Endnotes (§11.3.4), Footer (§11.3.6), Footnotes (§11.3.7), Header (§11.3.9), or Main Document (§11.3.10) part in a WordprocessingML package; a Worksheet part (§12.3.24) in a SpreadsheetML package; or a Handout Master (§13.3.3), Notes Slide (§13.3.5), Notes Master (§13.3.4), Slide (§13.3.8), Slide Layout (§13.3.9), Slide Master (§13.3.10) part in a PresentationML package.

A WordprocessingML document package is permitted to contain zero or more Embedded Object parts, each of which shall be the target of a relationship in a Main Document part-relationship item. Each Embedded Object part shall have an associated image, which appears in the document as a placeholder for the corresponding embedded object.

[Example: Consider the case in which a WordprocessingML document has embedded in it one video object and one audio object. The following Main Document part-relationship item contains relationships to two Embedded parts (one each for the video and audio), which are stored in the ZIP items embeddings/embeddedObjectN.bin:

example]

A SpreadsheetML document package is permitted to contain zero or more Embedded Object parts, each of which shall be the target of a relationship in a Worksheet part-relationship item.

[Example: Consider the case in which a SpreadsheetML document has embedded in it one video object and one audio object on one worksheet, and another audio object embedded in another worksheet. The following Worksheet Document part-relationship item contains relationships to two Embedded Object parts (one each for the video and audio), which are stored in the ZIP items ../embeddings/embeddedObjectN.bin:

end example]

A PresentationML document package is permitted to contain zero or more Embedded Object parts, each of which shall be the target of a relationship in a Slide part-relationship item.

[Example: Consider the case in which a PresentationML document has embedded in it one video object and one audio object on one slide, and another audio object embedded on another slide. The following Slide part-relationship item contains relationships to two Embedded Object parts (one each for the video and audio), which are stored in the ZIP items ../embeddings/embeddedObjectN.bin:

end example]

An Embedded Object part may be located within or external to the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element may be Internal or External).

An Embedded Object part is permitted to have an explicit relationship to the following parts defined by this Standard:

Hyperlink (§15.3)

An Embedded Object part shall not have any implicit or explicit relationships to other parts defined by this Standard.

Embedded Package Part

Content Type:

application/vnd.openxmlformats-officedocument.package

Root Namespace:

not applicable

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/package

An instance of this part type contains a complete package. For example, a WordprocessingML document might contain a SpreadsheetML or PresentationML document, in which case, the WordprocessingML document package would contain an embedded package part that defined that SpreadsheetML or PresentationML document.

A package is permitted to contain zero or more Embedded Package parts, and each such part shall be the target of an explicit relationship from a Chart (§14.2.1), Comments (§11.3.2), Endnotes (§11.3.4), Footer (§11.3.6), Footnotes (§11.3.7), Header (§11.3.9), or Main Document (§11.3.10) part in a WordprocessingML package; a Chart (§14.2.1), or Worksheet part (§12.3.24) in a SpreadsheetML package; or a Chart (§14.2.1), Handout Master (§13.3.3), Notes Slide (§13.3.5), Notes Master (§13.3.4), Slide (§13.3.8), Slide Layout (§13.3.9), Slide Master (§13.3.10) part in a PresentationML package.

[Example: The following Presentation part-relationship item contains relationships to two Embedded Package parts: one is a SpreadsheetML package, which is stored in the ZIP item embeddings/Worksheet1.xlsx, the other is a PresentationML package, which is stored in the ZIP item embeddings/Presentation2.pptx. The image files are used as document display placeholders if the consumer cannot handle the embedded package type:

end example]

An Embedded Package part may be located within or external to the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element may be Internal or External).

An Embedded Package part is permitted to have an explicit relationship to the following parts defined by this Standard:

Hyperlink (§15.3)

An Embedded Package part shall not have any implicit or explicit relationships to other parts defined by this Standard.

File Properties

There are three kinds of file properties: , core, custom, and extended. The core file properties of a package enable users to discover, get, and set common sets of properties from within that package, regardless of whether it’s a WordprocessingML, SpreadsheetML, or PresentationML package. Extended file properties are specific to Office Open XML packages, while custom file properties are defined by the user, with each custom file property having a name, a value, and a type.

Core File Properties Part

Content Type:

application/vnd.openxmlformats-package.core-properties+xml

Root Namespace:

http://schemas.openxmlformats.org/package/2006/metadata/core-properties

Source Relationship:

http://schemas.openxmlformats.org/officedocument/2006/relationships/metadata/core-properties

Core file properties enable users to discover, get, and set common sets of properties within packages. (These properties include creator name, creation date, title, and description.) These properties are stored using the appropriate Dublin Core properties whenever possible.

A package shall contain at most one Core File Properties part, and that part shall be the target of a relationship in the package-relationship item for the document.

[Example: The following PresentationML's package-relationship item contains one relationship, for the Core File Properties part stored in the ZIP item core.xml):

end example]

The root element for a part of this content type shall be coreProperties.

[Example:

<cp:coreProperties xmlns:cp="…" xmlns:dc="…" > <dc:title>Example File</dc:title> <dc:creator>Tristan Davis</dc:creator> <cp:lastModifiedBy>Tristan Davis</cp:lastModifiedBy> <cp:revision>1</cp:revision></cp:coreProperties>

end example]

A Core File Properties part shall be located within the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal).

A Core File Properties part shall not have implicit or explicit relationships to other parts defined by this Standard.

Custom File Properties Part

Content Type:

application/vnd.openxmlformats-officedocument.custom-properties+xml

Root Namespace:

http://schemas.openxmlformats.org/officeDocument/2006/custom-properties

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/custom-properties

An instance of this part contains the names of custom file properties that apply to the package, their values, and the types of those values. A custom file property might be the name of the client for whom the document was prepared, a date/time on which some event happened, a document number, or some Boolean status flag.

A package shall contain at most one Custom File Properties part, and that part shall be the target of a relationship in the package-relationship item for the document.

[Example: The following PresentationML's package-relationship item contains a relationship to a Custom File Properties part, stored in the ZIP item docProps/custom.xml:

end example]

The root element for a part of this content type shall be Properties.

[Example: Here's some content markup from a WordprocessingML document, which contains four custom properties: Client, having a text value of "ACME Corp."; Document number, having a numeric value of 1543; Recorded date, having a date/time value of 2005-12-01; and Special processing needed, having a Boolean value of false:

<property fmtid="{D5C…9AE}" pid="5" name="Special processing needed"> <vt:bool>false</vt:bool> </property></Properties>

end example]

A Custom File Properties part shall be located within the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal).

A Custom File Properties part shall not have implicit or explicit relationships to other parts defined by this Standard.

Extended File Properties Part

Content Type:

application/vnd.openxmlformats-officedocument.extended-properties+xml

Root Namespace:

http://schemas.openxmlformats.org/officeDocument/2006/extended-properties

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/extended-properties

An instance of this part contains properties specific to an Office Open XML document.[Example: A PresentationML document specifies the number of slides in this presentation when last saved by a producer. end example]

A package shall contain at most one Extended File Properties part, and that part shall be the target of a relationship in the package-relationship item for the document.

[Example:

end example]

The root element for a part of this content type shall be Properties.

[Example: Here's some content markup from a WordprocessingML document:

<Properties …> <Template>Normal.dotm</Template> <TotalTime>0</TotalTime> <Pages>1</Pages> <Words>3</Words> <Characters>22</Characters>

<Application>Sample Producer</Application> <DocSecurity>0</DocSecurity> <Lines>1</Lines> <Paragraphs>1</Paragraphs> … <AppVersion>12.0000</AppVersion></Properties>

here's some content markup from a SpreadsheetML document:

<Properties …> <Application>Sample Producer</Application> <HeadingPairs> … </HeadingPairs> <TitlesOfParts> … </TitlesOfParts> <Company>Consultant</Company> …</Properties>

and here's some content markup from a PresentationML document:

<Properties …> <Template>ppt_template_sdwest05</Template> <TotalTime>3166</TotalTime> <Words>37</Words> <Application>Sample Producer</Application> <PresentationFormat>On-screen Show</PresentationFormat> <Paragraphs>15</Paragraphs> <Slides>2</Slides> <Notes>2</Notes>

… <HeadingPairs> … </HeadingPairs> <TitlesOfParts> … </TitlesOfParts> …</Properties>

end example]

A Extended File Properties part shall be located within the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal).

An Extended File Properties part shall not have implicit or explicit relationships to any other part defined by this Standard.

Font Part

Content Type:

application/x-fontdataapplication/x-font-ttf

Root Namespace:

not applicable

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/font

An instance of this part type contains a given font embedded directly into the document. (This is useful when using custom fonts or fonts that are not widely distributed.)

Fonts stored in a Font part can be stored in one of two formats, identified by the associated content type:

application/x-fontdata specifies that the font shall be stored as a bitmapped font (each glyph is stored as a raster image)

application/x-font-ttf specifies that the font shall be stored in the TrueType or OpenType format

A package shall contain zero or more Font parts, and for each that exists, that part shall be the target of an explicit relationship in the Font Table (§11.3.5), or Presentation (§13.3.6) part.

A Font part shall be located within the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal).

A Font part shall not have implicit or explicit relationships to other parts defined by this Standard.

Image Part

Content Type:

Any supported image type.

[Note: Some example content types are:

image/gif

http://www.w3.org/Graphics/GIF/spec-gif89a.txt

image/png

ISO/IEC 15948:2003http://www.libpng.org/pub/png/spec/

image/tiff

http://partners.adobe.com/public/developer/tiff/index.html#spec

image/pict

http://developer.apple.com/documentation/mac/QuickDraw/QuickDraw-2.html

image/jpeg

http://www.w3.org/Graphics/JPEG/

end note.]

Root Namespace:

Not applicable

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/image

An image can be stored in a package as a ZIP item. Image ZIP items shall be identified by an image part relationship and the appropriate content type.

A package is permitted to contain zero or more Image parts, and each such part shall be the target of an explicit relationship from a Comments (§11.3.2), Endnotes (§11.3.4), Footer (§11.3.6), Footnotes (§11.3.7), Header (§11.3.9), or Main Document (§11.3.10) part in a WordprocessingML package; a VML Drawing (§15.2.17) part in a SpreadsheetML package; or a Handout Master (§13.3.3), Notes Slide (§13.3.5), Notes Master (§13.3.4), Slide (§13.3.8), Slide Layout (§13.3.9), Slide Master (§13.3.10), or a VML Drawing (§15.2.17) part in a PresentationML package.

[Example: The following PresentationML's package-relationship item contains one relationship, for the slide template jpeg image stored in the ZIP item ../media/image1.jpeg:

end example]

An Image part may be located within or external to the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element may be Internal or External).

An Image part shall not have implicit or explicit relationships to other parts defined by this Standard.

Printer Settings Part

Content Type:

application/vnd.openxmlformats-officedocument.spreadsheetml.printerSettings (in SpreadsheetML documents)application/vnd.openxmlformats-officedocument.wordprocessingml.printerSettings (in WordprocessingML documents)

Root Namespace:

not applicable

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/printerSettings

An instance of this part type contains information about the initialization and environment of a printer or a display device. The layout of this data structure is application-defined. [Example: An Office Open XML producer on Windows might store the DEVMODE structure defined here: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/gdi/prntspol_8nle.asp, while an application on the Mac OS might choose to store the print record defined here: http://developer.apple.com/documentation/Carbon/Reference/CarbonPrintingManager_Ref/Reference/reference.html. end example]

A SpreadsheetML package is permitted to contain at most one Printer Settings part per Chartsheet, Dialogsheet, or Worksheet part, and that part shall be the target of an implicit relationship from a Chartsheet (§12.3.2), Dialogsheet (§12.3.7), or Worksheet (§12.3.24) part. A WordprocessingML package is permitted to contain zero or more Printer Settings parts, one per sectPr element, each a target of an explicit relationship from a Main Document (§11.3.10) or Glossary Document (§11.3.8) part.

[Example: The following SpreadsheetML Worksheet part-relationship item contains a relationship to a Printer Settings part, which is stored in the ZIP item ../printerSettings/printerSettings1.bin:

end example]

A Printer Settings part shall be located within the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal).

A Printer Settings part shall not have implicit or explicit relationships to any other part defined by this Standard.

Thumbnail Part

Content Type:

Any supported image type.

[Note: Some example content types are:

image/gif

http://www.w3.org/Graphics/GIF/spec-gif89a.txt

image/png

ISO/IEC 15948:2003http://www.libpng.org/pub/png/spec/

image/tiff

http://partners.adobe.com/public/developer/tiff/index.html#spec

image/pict

http://developer.apple.com/documentation/mac/QuickDraw/QuickDraw-2.html

image/jpeg

http://www.w3.org/Graphics/JPEG/

end note.]

Root Namespace:

Not applicable

Source Relationship:

http://schemas.openxmlformats.org/package/2006/relationships/metadata/thumbnail

To help end-users identify parts of a package or the package as a whole, images, called thumbnails, may be stored in that package. Each thumbnail image is generated by the package producer and is stored in the package as a ZIP item.

Thumbnail ZIP items shall be identified by either a package-relationship item or a part-relationship item. Packages shall not contain more than one thumbnail relationship associated with the package as a whole, or more than one thumbnail relationship per package part.

[Example: The following PresentationML's package-relationship item contains one relationship, for the metafile image stored in the ZIP item thumbnail.wmf:

end example]

A Thumbnail part shall be located within the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal).

A Thumbnail part shall not have implicit or explicit relationships to other parts defined by this Standard.

Video Part

Content Type:

Any supported video type.

[Note: Some example content types are:

video/x-ms-asf

http://www.microsoft.com/windows/windowsmedia/forpros/format/asfspec.aspx

video/avi

http://www.the-labs.com/Video/odmlff2-avidef.pdf

video/mpg

ISO/IEC 13818

video/mpeg

ISO/IEC 13818

video/x-ms-wm

http://www.microsoft.com/windows/windowsmedia/forpros/format/asfspec.aspx

video/quicktime

http://developer.apple.com/softwarelicensing/agreements/quicktime.html

end note]

Root Namespace:

not applicable

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/video

An instance of this part type contains a video file.

A PresentationML package is permitted to contain zero or more Video parts, each of which shall be the target of an explicit relationship in a Handout Master (§13.3.3), Notes Slide (§13.3.5), Notes Master (§13.3.4), Slide (§13.3.8), Slide Layout (§13.3.9), or Slide Master (§13.3.10) part. A WordprocessingML package is permitted to contain zero or more Video parts, each of which shall be the target of an explicit relationship from a Comments (§11.3.2), Endnotes (§11.3.4), Footer (§11.3.6), Footnotes (§11.3.7), Header (§11.3.9), or Main Document (§11.3.10) part.

[Example: The following Slide part-relationship item contains a relationship to a Video part, which is stored as the file E:\Video demo.avi:

end example]

A Video part is not stored as XML; instead, it involves a relationship target that is a video clip.

A Video part may be located within or external to the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element may be Internal or External).

A Video part shall not have implicit or explicit relationships to other parts defined by this Standard.

VML Drawing Part

Content Type:

application/vnd.openxmlformats-officedocument.vmlDrawing

Root Namespace:

not applicable

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/vmlDrawing

An instance of this part type contains markup in the Vector Markup Language (VML) syntax, which is used to provide an alternative image representation of objects stored in a SpreadsheetML or PresentationML document.

A package is permitted to contain zero or more VML Drawing parts, each of which shall be the target of an explicit relationship in a Handout Master (§13.3.3), Notes Slide (§13.3.5), Notes Master (§13.3.4), Slide (§13.3.8), Slide Layout (§13.3.9), or Slide Master (§13.3.10) part in a PresentationML document; or a Worksheet part (§12.3.24) in a SpreadsheetML document.

[Example: The following SpreadsheetML's package-relationship item contains one relationship, for the VML Drawing part stored in the ZIP item ../drawings/drawing1.vml:

end example]

The root element for a part of this content type shall be xml in the null namespace, encapsulating an arbitrary amount of VML markup as defined by this Standard.

[Example: Consider the following VML Drawing part:

end example]

A VML Drawing part shall be located within the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal).

A VML Drawing part is permitted to have explicit relationships to the following parts defined by this Standard:

Image (§15.2.13)

A VML Drawing part shall not have implicit or explicit relationships to any other part defined by this Standard.

Hyperlinks

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/hyperlink

A hyperlink can be stored in a package as a relationship. Hyperlinks shall be identified by containing a target which specifies the destination of the given hyperlink.

[Example: The following WordprocessingML Footnote part's relationship part contains one relationship, for the hyperlink http://schemas.openxmlformats.org/wordprocessingml/:

end example]

A hyperlink target may be located within or external to the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element may be Internal or External).

Bibliography

This clause is informative.

Character Sets from IANA, as specified at http://www.iana.org/assignments/character-sets

PANOSE Classification Guide, Version 1.2, Hewlett Packard Co., 1992.

RFC 2119, Bradner, Scott, 1997: “Key words for use in RFCs to Indicate Requirement Levels.” http://www.ietf.org/rfc/rfc2119.txt.

RFC 2045, Borenstein, N., and N. Freed. “Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies.” The Internet Society. 1996. http://www.rfc-editor.org

RFC 2616, Berners-Lee, T., R. Fielding, H. Frystyk, J. Gettys, P. Leach, L. Masinter, and J. Mogul. “Hypertext Transfer Protocol—HTTP/1.1.” The Internet Society. 1999. http://www.rfc-editor.org

RFC 3066, Alvestrand, H. “Tags for the Identification of Languages.” The Internet Society. 2001. http://www.rfc-editor.org

RFC 3339, Klyne, G. and C. Newman “Date and Time on the Internet: Timestamps.” The Internet Society. 2002. http://www.rfc-editor.org

RFC 3629, Yergeau, F. “UTF-8, a transformation format of ISO 10646.” The Internet Society. 2003. http://www.rfc-editor.org

RFC 3986, Berners-Lee, T., R. Fielding, and L. Masinter. “Uniform Resource Identifier (URI): Generic Syntax.” The Internet Society. 2005. http://www.rfc-editor.org

The Unicode Consortium. The Unicode Standard, Version 4.0, defined by: The Unicode Standard, Version 4.0 (Reading, MA, Addison-Wesley, 2003. ISBN 0-321-18578-1).

XML, Bray, Tim, Eve Maler, Jean Paoli, C. M. Sperberg-McQueen, and François Yergeau (editors). “Extensible Markup Language (XML) 1.0,” Third Edition. World Wide Web Consortium. 2004. http://www.w3.org/TR/2004/REC-xml-20040204/xml11-20040204/)

XML Base, Marsh, Jonathan. “XML Base.” World Wide Web Consortium. 2001. http://www.w3.org/TR/2001/REC-xmlbase-20010627/

XML Namespaces, Bray, Tim, Dave Hollander, Andrew Layman, and Richard Tobin (editors). “Namespaces in XML 1.1.” World Wide Web Consortium. 2004. http://www.w3.org/TR/2004/REC-xml-names11-20040204/

XML Path Language Specification, Version 1.0, W3C Recommendation 16 November 1999 http://www.w3.org/TR/xpath

XML Schema Part 0: Primer Second Edition, W3C Recommendation 28 October 2004http://www.w3.org/TR/xmlschema-0/

XML Schema Part 1: Structures Second Edition, W3C Recommendation 28 October 2004 http://www.w3.org/TR/xmlschema-1/

XML Schema Part 2: Datatypes Second Edition, W3C Recommendation 28 October 2004http://www.w3.org/TR/xmlschema-2/

.ZIP File Format Specification from PKWARE, Inc., as specified in appnote, the Application Note on the Zip file format, at http://www.pkware.com.

End of informative text.

Index

This annex is informative.

Additional Characteristics part137

Alternative Format Import part28

animation13

annex10

application6

Application-Defined File Properties part152

audience13

audio13

Audio part138

behavior6

implementation-defined6

locale-specific6

unspecified6

Bibliography part139

body11

Calculation Chain part63

cell12, 14, 59

alignment13

border13

color13

font13

formatting13

cell reference13, 59

chart14, 59

Chart Drawing part125

Chart part123

Chartsheet part64

color scheme14, 132, 133

column12, 14, 59

comment13, 24, 59, 98

Comment Authors part102

Comments part

PresentationML103

SpreadsheetML65

WordprocessingML29

conformance2

application3

document3

connection59

Connections part67

consumer11

control136

Core File Properties part149

Custom File Properties part150

custom markup12

Custom Property part68

Custom XML data property15

Custom XML Data Storage part140

Custom XML Data Storage Properties part141

Custom XML Mappings part69

diagram122

diagram color14

Diagram Colors part126

diagram data14

Diagram Data part127

diagram layout14

Diagram Layout Definition part128

diagram style14

Diagram Style part130

Dialogsheet part70

Digital Signature Origin part141

Digital Signature XML Signature part142

document setting24

Document Settings part31

document template53

document type6

DrawingML6, 14

effect14, See format scheme, See format scheme

Embedded Control Persistence part143

Embedded Object part146

Embedded Package part148

Endnotes part33

example10

extension6

External Workbook96

External Workbook References part73

field12

field instruction12

field result12

file property15, 149

application-definedSee Application-Defined File Properties part

core15, 149, See Core File Properties part

custom15, 149, See Custom Properties part

extended15, 149

font14

Font part154

font scheme132, 133

Font Table part35

footer12

Footer part36

Footnotes part38

format scheme132, 133

formula13, 59

frame54

frameset54

function13, 59

glossary document24

Glossary Document part41

handout13, 98

handout master13

Handout Master part104

header12

Header part43

HTML Publish Location119

hyperlink12, 13, 159

IECSee International Electrotechnical Commission

image13, 154

informative text2

International Electrotechnical Commission9

International Organization for Standardization9

ISOSee International Organization for Standardization

ISO/IEC 106465

layout13

mail merge data source56

mail merge header data source57

Main Document part46

master document24, 55

Metadata part75

normative text2, 10

note10, 13, 98

notes master13

Notes Master part106

Notes Slide part107

numbering12

Numbering Definitions part48

Office Open XMLviii, 7

valid7

package7, 11

embedded7

package-relationship ZIP item11

paragraph11

part11

Additional CharacteristicsSee Additional Characteristics part

Alternative Format ImportSee Alternative Format Import part

Application-Defined File PropertiesSee Application-Defined File Properties part

AudioSee Audio part

BibliographySee Bibliography part

Calculation ChainSee Calculation Chain part

ChartSee Chart part

Chart DrawingSee Chart Drawing part

ChartsheetSee Chartsheet part

Comment AuthorsSee Comment Authors part

Comments

PresentationMLSee Comments part, PresentationML

SpreadsheetMLSee Comments part, SpreadsheetML

WordprocessingMLSee Comments part, WordprocessingML

ConnectionsSee Connections part

Core File PropertiesSee Core File Properties part

Custom File PropertiesSee Custom File Properties part

Custom PropertySee Custom Property part

Custom XML Data StorageSee Custom XML Data Storage part

Custom XML Data Storage PropertiesSee Custom XML Data Storage Properties part

Custom XML MappingsSee Custom XML Mappings part

Diagram ColorsSee Diagram Colors part

Diagram DataSee Diagram Data part

Diagram Layout DefinitionSee Diagram Layout Definition part

Diagram StyleSee Diagram Style part

DialogsheetSee Dialogsheet part

Digital Signature OriginSee Digital Signature Origin part

Digital Signature XML SignatureSee Digital Signature XML Signature part

Document SettingsSee Document Settings part

Embedded Control PersistenceSee Embedded Control Persistence part

Embedded ObjectSee Embedded Object part

Embedded PackageSee Embedded Package part

EndnotesSee Endnotes part

External Workbook ReferencesSee External Workbook References part

FontSee Font part

Font TableSee Font Table part

FooterSee Footer part

FootnotesSee Footnotes part

Glossary DocumentSee Glossary Document part

Handout MasterSee Handout Master part

HeaderSee Header part

Main DocumentSee Main Document part

MetadataSee Metadata part

Notes MasterSee Notes Master part

Notes SlideSee Notes Slide part

Numbering DefinitionsSee Numbering Definitions part

Pivot TableSee Pivot Table part

Pivot Table Cache DefinitionSee Pivot Table Cache Definition part

Pivot Table Cache RecordsSee Pivot Table Cache Records part

PresentationSee Presentation part

Presentation PropertiesSee Presentation Properties part

Printer SettingsSee Printer Settings part

Query TableSee Query Table part

Shared String TableSee Shared String Table part

Shared Workbook Revision HeadersSee Shared Workbook Revision Headers part

Shared Workbook Revision LogSee Shared Workbook Revision Log part

Shared Workbook User DataSee Shared Workbook User Data part

Single Cell Table DefinitionsSee Single Cell Table Definitions part

SlideSee Slide part

Slide LayoutSee Slide Layout part

Slide MasterSee Slide Master part

Slide Synchronization DataSee Slide Synchronization Data part

Style DefinitionsSee Style Definitions part

StylesSee Styles part

Table DefinitionSee Table Definition part

Table StylesSee Table Styles part

ThemeSee Theme part

Theme OverrideSee Theme Override part

User Defined TagsSee User Defined Tags part

VideoSee Video part

View PropertiesSee View Properties part

Volatile DependenciesSee Volatile Dependencies part

Web SettingsSee Web Settings part

WorkbookSee Workbook part

WorksheetSee Worksheet part

part-relationship item11

picture14

pivot table59

Pivot Table Cache Definition part79

Pivot Table Cache Records part81

Pivot Table part78

presentation13, 98

custom13

Presentation part109

Presentation Properties part111

PresentationML7, 13

Printer Settings part155

producer11

property11

Query Table part82

rationale10

reference10

relationship7, 11

explicit7, 18

implicit7, 18

relationships part7

row12, 14, 59

run11

section12, 24

shape14

Shared String Table part83

Shared Workbook Revision Headers part84

Shared Workbook Revision Log part85

Shared Workbook User Data part87

Single Cell Table Definitions part87

slide13, 98

slide layout98

Slide Layout part113

slide master13

Slide Master part115

Slide part111

Slide Synchronization Data part116

Slide Synchronization Server Location120

SpreadsheetML7, 12

style12

Style Definitions part51

Styles part89

subdocument24, 55

supplementary document storage location24

table12, 13, 14, 60

Table Definition part90

Table Styles part134

template24

text11

theme14, 132, 133

Theme Override part133

Theme part131

thumbnail156

transition13

trash items17

Unicode standard161

unknown parts17

unknown relationships17

User Defined Tags part117

video13

Video part157

View Properties part118

VML15

Volatile Dependencies part91

W3CSee World Wide Web Consortium

Web Settings part52

WordprocessingML7, 11

workbook12, 60

external96

Workbook part92

worksheet12, 60

Worksheet part94

World Wide Web Consortium9

XSL transformation58