14.2.4 Diagram Data Part

Content Type:

application/vnd.openxmlformats-officedocument.drawingml.diagramData+xml

Root Namespace:

http://purl.oclc.org/ooxml/drawingml/diagram

Source Relationship:

http://purl.oclc.org/ooxml/officeDocument/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.

<Relationships xmlns="…">
  <Relationship Id="rId1"
    Type="http://…/diagramData" Target="../graphics/data1.xml"/>
  <Relationship Id="rId5"
    Type="http://…/diagramData" Target="../graphics/data2.xml"/>
</Relationships>

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 relationships part (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 ISO/IEC 29500:

• Image (15.2.14)

A Diagram Data part shall not have any implicit or explicit relationships to other parts defined by ISO/IEC 29500.