All subsections of Section 6 describe deprecated only material, making Section 6 deprecated as a whole. A new standard should not contain deprecated parts.

Change Section 6 to an "Informative" Annex or separate document.

To go to the end Part 4, Section 6.

TE

Proposed Disposition of DIS 29500 Comment CA-0076 (Modified: 2008-01-13) Agreed to deprecate use of VML; we will remove VML from its current location in the specification (Part 4, §6, pages 4,343­4,960), and place it into a new annex for deprecated features. Deprecated features should not be used in newly created Office Open XML documents. Following the precedent set by other ISO standards (such as SQL’s ISO 9075:2003 Part 1 and C++’s ISO/IEC 14882:1998), we will make use of a new Annex that contains normative descriptions of all deprecated features. The intent of this Annex is to enable a transitional period during which existing binary documents being migrated to DIS 29500 can make use of those deprecated features to preserve their fidelity, while noting that new documents should not use them. Accordingly, the Conformance clause will also be changed to state that newly created documents (those not created by migrating existing binary documents) should not use deprecated features. All deprecated features will be removed from their current locations in the standard, but will be fully defined in this new Annex. DrawingML is the appropriate replacement of VML. In the current specification, it is already the suggested format to be used almost everywhere VML was formerly used. In conjunction with removing VML, we will extend the usage of DrawingML in any area where it did not already replace VML. The following summarizes the changes that will be made: General A new annex in Part 4 will be created as follows: Annex - Selected Transitional Migration Features (normative) (deprecated) The features described in this Annex should only be used by documents that are created as part of a migration of existing binary documents to DIS 29500. The intent of this Annex is to enable a transitional period during which existing binary documents being migrated to DIS 29500 can make use of those deprecated features to preserve their fidelity, while noting that new documents should not use them. The Conformance clause states that newly created documents (those not created by migrating existing binary documents) should not use deprecated features.All deprecated features are fully defined in this Annex. Deprecated is defined as: Normative for the current edition of the Standard, but not guaranteed to be part of the Standard in future revisions. The intent is to enable the future DIS 29500 maintenance group to choose, at a later date, to remove this set of features from a revised version of DIS 29500. [Description of each Deprecated Feature ­ e.g. VML &WordprocessingML Compatibility Settings] Note that deprecated elements and attributes remain in the schemas so that documents migrated from binary format will properly validate against the Office Open XML schemas. They will appear in the Parent Elements tables, Child Elements tables and XML schema fragments, but not in the description text. All associated subclause references (e.g., §2.x.x) will be updated to correspond to the changes described in this document. Part 1 Deprecate the following and move them to the new annex for deprecated features: §8.6.2 (VML), page 15 §15.2.17 (VML Drawing Part), pages 158­159 In §15.2.8, pages 143­146: Remove the VML from the two examples. For example, in §15.2.8, pages 144­145: [Example:The following example shows the persistence that could be used for an embedded control which is a Java applet within a WordprocessingML document . Note that the shape which provides the visible thumbnail representation of the control is omitted for brevity : <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:drawing> … </w:drawing> <w:control r:id="rId5" w:name="CommandButton1" w:shapeid=" _x0000_i 1027" /> </w:object> </w:r> </w:p> Remove references to VML from the following text: §12.3.24 (Worksheet Part), page 96 §13.3.3 (Handout Master Part), page 106 §13.3.4 (Notes Master Part), page 107 §13.3.5 (Notes Slide Part), page 109 §13.3.8 (Slide Part), page 113 §13.3.9 (Slide Layout Part), page 115 §13.3.10 (Slide Master Part), page 116 §15.2.13 (Image Part), page 154 For example, in §12.3.24 (Worksheet Part), page 96, lines 10­17: 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) Part 4, §2 ­ WordprocessingML Deprecate the following and move them to the new annex for deprecated features: §2.3.3.17 (movie), pages 259­260 o Describe an alternate means for providing a movie object in a WordprocessingML diagram using DrawingML. §2.15.1.50 (hdrShapeDefaults), pages 1199­1200 §2.15.1.79 (shapeDefaults), page 1244 §2.17.1 (Text Box Content), pages 1615­1618 o Note that DrawingML already provides a means to include text in shapes. In §2.2.1 (background), pages 27­31: Add §2.3.3.9 (drawing) as a valid child element. In §2.3.3.19 (object), pages 261­263, §2.3.3.21 (pict), pages 264­265 and §2.9.23 (pict), pages 804­805: Add §2.3.3.9 (drawing) as a valid child element. Add new child elements to contain properties of object or pict that were previously stored in VML. For an example, consider the structure of the following isolated XML fragments that demonstrate the use of new and extended element structures to replace VML usage: <w:r> … <w:object … > <w:drawing> … </w:drawing> <w:objectEmbed drawAspect="content" r:id="rId3" progId="…" shapeId="…"/> </w:object> </w:r> <w:r> <w:pict … > <w:drawing> … </w:drawing> <w:control … /> </w:pict> </w:r> The following XML Schema fragments define the changes that will be made: The following change will be made to §2.3.3.19 (object): <complexType name="CT_Object"> <complexContent> <extension base="CT_PictureBase"> <sequence> <element name="control" type="CT_Control" minOccurs="0"/> <element name="objectEmbed" type="CT_OleObject" minOccurs="0"/> <element name="objectLink" type="CT_OleObjectLink" minOccurs="0"/> <element name="drawing" type="CT_Drawing" minOccurs="0"/> </sequence> <attribute name="dxaOrig" type="ST_TwipsMeasure" use="optional"/> <attribute name="dyaOrig" type="ST_TwipsMeasure" use="optional"/> </extension> </complexContent> </complexType> The following change will be made to §2.3.3.21 (pict) and §2.9.23 (pict): <complexType name="CT_Picture"> <complexContent> <extension base="CT_PictureBase"> <sequence maxOccurs="1"> <element name="movie" type="CT_Rel" minOccurs="0"/> <element name="control" type="CT_Control" minOccurs="0"/> <element name="objectEmbed" type="CT_OleObject" minOccurs="0"/> <element name="objectLink" type="CT_OleObjectLink" minOccurs="0"/> <element name="drawing" type="CT_Drawing" minOccurs="0"/> </sequence> </extension> </complexContent> </complexType> The following new elements will be added: <complexType name="CT_ObjectEmbed"> <attribute name="drawAspect" type="ST_ObjectDrawAspect" use="optional"/> <attribute ref="r:id" use="required"/> <attribute name="progId" type="ST_String" use="optional"/> <attribute name="shapeId" type="ST_String" use="optional"/> <attribute name="fieldCodes" type="ST_String" use="optional"/> </complexType> <complexType name="CT_ObjectLink"> <complexContent> <extension base="CT_ObjectEmbed"> <attribute name="updateMode" type="ST_OleObjectUpdateMode" use="required"/> <attribute name="serverFormat" type="ST_OleObjectServerFormat" use="required"/> <attribute name="lockedField" type="ST_OnOff" use="optional"/> </extension> </complexContent> </complexType> <simpleType name="ST_ObjectDrawAspect"> <restriction base="xsd:string"> <enumeration value="content"/> <enumeration value="icon"/> </restriction> </simpleType> <simpleType name="ST_ObjectUpdateMode"> <restriction base="xsd:string"> <enumeration value="always"/> <enumeration value="onCall"/> </restriction> </simpleType> <simpleType name="ST_ObjectLinkType"> <restriction base="xsd:string"> <enumeration value="bitmap"/> <enumeration value="picture"/> <enumeration value="metaFile"/> </restriction> </simpleType> <simpleType name="ST_ObjectServerFormat"> <union memberTypes="ST_String ST_ObjectLinkType"/> </simpleType> In §2.3.3.21 (pict), pages 264­265 and §2.9.23 (pict), pages 804­805: Rename §2.3.3.21 (pict) from “VML Object” to “Drawing Object” Remove references to VML from the following text: §2.3.3 (Run Content), page 241 ­ line 1 §2.3.3.2 (control), pages 243­245 ­ explanatory text, example markup, shapeid attribute §2.3.3.3 (control), pages 245­247 ­ examples, shapeid attribute §2.3.3.19 (object), pages 261­263 ­ explanatory text, example markup §2.3.3.21 (pict), pages 264­265 ­ explanatory text, example markup §2.5.2.23 (picture), page 565 ­ explanatory text §2.9.10 (lvlPicBulletId), pages 785-786 ­ example markup §2.9.23 (pict), pages 804­805 ­ explanatory text, example markup §2.15.1.69 (revisionView), page 1226 ­ inkAnnotations attribute §2.15.3.17 (doNotSnapToGridInCell), pages 1398­1400 ­ explanatory text §2.15.3.18 (doNotSuppressIndentation), pages 1400­1402 ­ explanatory text §2.15.3.23 (doNotVertAlignCellWithSp), pages 1410­1413 ­ explanatory text §2.15.3.24 (doNotVertAlignInTxbx), pages 1413­1415 ­ explanatory text §2.15.3.29 (layoutRawTableWidth), pages 1422­1424 ­ explanatory text §2.15.3.30 (layoutTableRowsApart), pages 1424­1426 ­ explanatory text §2.15.3.41 (shapeLayoutLikeWW8), pages 1442­1443 ­ explanatory text §2.16.5.8 (AUTOTEXT), page 1515 ­ explanatory text For example, in §2.3.3.2 (control), pages 243­245: 2.3.3.2 control (Floating Embedded Control) This element specifies that the parent VML object associated shape is a representation of an embedded control at the current location in the document. This element shall be used to associate the VML data shape with the appropriate embedded control settings and properties when the document is displayed. If the embedded control is not present, cannot be loaded due to application settings, or is not supported, then the VML data shape shall be used to provide an image representation of the control at the appropriate location in the document. [Example: Consider a run which consists of an embedded control. That run would be specified using the following WordprocessingML: <w:r> <w:pict> … <w:control r:id="rId99" w:shapeid=" shape01 1025 " … /> </w:pict> </w:r> The control element indicates that the parent VML shape object contains the positioning and last known image representation of an embedded control, whose settings and properties are stored on this element. end example] … Attributes Description shapeid (Associated VML Data Shape Reference) Specifies the shape ID for a shape which shall be used to define the presentation and location of this embedded control within the document if the control is floating using the VML syntax . [Note: This positioning data is sufficient to display the control in any case where: The embedded control is not on the current machine Embedded controls are disabled Embedded controls of this type are not supported end note] This shape ID reference is resolved by looking for a VML shapeelement (§6.1.2.19) whose id attribute shape whose ID matches the value specified within this attribute. If no such shape exists, then the control shall be rendered inline in the document content at the current run content location. If this attribute is omitted, then this embedded control shall be displayed inline in the current location in the parent run. [Example: Consider the following WordprocessingML markup for an embedded control in a document: <w:control r:id="rId5" w:id="CheckBox1" w:name="CheckBox1" w:shapeid=" _x0000_s 1027" w:class="shape" w:w="145" w:h="28" w:align="left" /> The shapeidattribute specifies that the VML shape element with a shape id attribute value with an ID of _x0000_s 1027 shall contain the VML positioning data for this embedded control. end example] The possible values for this attribute are defined by the ST_String simple type (§2.18.89). The following do not impact VML in Office Open XML and will not be changed. They are settings that describe whether VML should be used when exporting the document to HTML for consumption by a web browser. §2.15.2.32 (optimizeForBrowser), pages 1337­1339 §2.15.2.34 (relyOnVML), pages 1340­1341 Part 4, §3 ­ SpreadsheetML Deprecate the following and move them to the new annex for deprecated features: §3.3.1.51 (legacyDrawing), page 1980 §3.3.1.52 (legacyDrawingHF), pages 1980­1981 In §3.3.1 (Worksheets): Add a new element to contain shape references to images in the worksheet header or footer. These were previously stored in VML. For example, a drawingHF element that mirrors the structure of legacyDrawingHF. The following XML Schema fragments define the changes that will be made: The following new element will be added and made a valid child element of §3.3.1.11 (chartsheet), §3.3.1.32 (dialogsheet) and §3.3.1.96 (worksheet): <complexType name="drawingHF"> <attribute ref="r:id" use="required"> <attribute name="lho" type="unsignedInt"/> <attribute name="lhe" type="unsignedInt"/> <attribute name="lhf" type="unsignedInt"/> <attribute name="cho" type="unsignedInt"/> <attribute name="che" type="unsignedInt"/> <attribute name="chf" type="unsignedInt"/> <attribute name="rho" type="unsignedInt"/> <attribute name="rhe" type="unsignedInt"/> <attribute name="rhf" type="unsignedInt"/> <attribute name="lfo" type="unsignedInt"/> <attribute name="lfe" type="unsignedInt"/> <attribute name="lff" type="unsignedInt"/> <attribute name="cfo" type="unsignedInt"/> <attribute name="cfe" type="unsignedInt"/> <attribute name="cff" type="unsignedInt"/> <attribute name="rfo" type="unsignedInt"/> <attribute name="rfe" type="unsignedInt"/> <attribute name="rff" type="unsignedInt"/> </complexType> Each letter in the attribute names above correspond to the position and pages the drawing applies to. 1. Position of the drawing (l = left, c = center, r = right) 2. Is the drawing in the header or footer (h = header, f = footer) 3. Which pages the drawing applies to (o = odd pages only, e = even pages only, f = first page only) For example, the lhe attribute corresponds to a drawing on the left side of the header for even pages only. In the headerFooter element (§3.3.1.43) that corresponds to the header or footer drawing, if the differentOddEven attribute is true, then the attributes that correspond to even pages, such as lhe and rfe, are used. If differentOddEven is false, then the odd page attributes, such as lho and rfo, are used. If the differentFirst attribute is true, then the first page attributes, such as lhf and rff, are used. If differentFirst is false, then the odd page attributes are used. The values of these attributes contain the ID of the corresponding shape in the DrawingML part that is referenced by the r:id attribute. In §3.3.1.57 (oleObject) and §3.3.1.18 (control): Allow the shapeid attribute to point to a DrawingML shape. Add a new child element to contain properties of the object. These were previously stored in VML. Since VML is deprecated, specifying an object or control will not use VML and will instead use the new schema additions described below. For an example, consider the structure of the following isolated XML fragments: <oleObjects> <oleObject … > <objectPr cf="Pict"> <anchor sizeWithCells="true"> <from> <col>0</col> <colOff>0</colOff> <row>0</row> <rowOff>0</rowOff> </from> <to> <col>4</col> <colOff>182880</colOff> <row>10</row> <rowOff>0</rowOff> </to> <anchor> </objectPr> </oleObject> </oleObjects> <controls> <control … > <controlPr autoLine="false" cf="Pict"> <anchor sizeWithCells="true"> <from> <col>1</col> <colOff>497305</colOff> <row>0</row> <rowOff>176463</rowOff> </from> <to> <col>3</col> <colOff>898358</colOff> <row>2</row> <rowOff>224589</rowOff> </to> <anchor> </controlPr> </control> </controls> The following XML Schema fragments define the changes that will be made: The following change will be made to §3.3.1.57 (oleObject): <complexType name="CT_OleObject"> <sequence> <element name="objectPr" type="CT_ObjectPr" minOccurs="0" maxOccurs="1" /> </sequence> <attribute name="progId" type="xsd:string" use="optional"/> <attribute name="dvAspect" type="ST_DvAspect" use="optional" default="DVASPECT_CONTENT"/> <attribute name="link" type="ST_Xstring" use="optional"/> <attribute name="oleUpdate" type="ST_OleUpdate" use="optional"/> <attribute name="autoLoad" type="xsd:boolean" use="optional" default="false"/> <attribute name="shapeId" type="xsd:unsignedInt" use="required"/> <attribute ref="r:id" use="optional"/> </complexType> The following change will be made to §3.3.1.18 (control): <complexType name="CT_Control"> <sequence> <element name="controlPr" type="CT_ControlPr" minOccurs="0" maxOccurs="1"/> </sequence> <attribute name="shapeId" type="xsd:unsignedInt" use="required"/> <attribute ref="r:id" use="required"/> <attribute name="name" type="xsd:string" use="optional"/> </complexType> The following new elements will be added: <complexType name="CT_ObjectPr"> <sequence> <element name="anchor" type="CT_ObjectAnchor" minOccurs="1" maxOccurs="1"/> </sequence> <attribute name="locked" type="boolean" use="optional" default="true"/> <attribute name="defaultSize" type="boolean" use="optional" default="true"/> <attribute name="print" type="boolean" use="optional" default="true"/> <attribute name="disabled" type="boolean" use="optional" default="false"/> <attribute name="uiObject" type="boolean" use="optional" default="false"/> <attribute name="autoFill" type="boolean" use="optional" default="true"/> <attribute name="autoLine" type="boolean" use="optional" default="true"/> <attribute name="macro" type="ST_Formula" use="optional"/> <attribute name="altText" type="ST_XString" use="optional"/> <attribute name="cf" type="ST_String" use="optional" default="pict"/> <attribute name="autoPict" type="boolean" use="optional" default="true"/> <attribute name="dde" type="boolean" use="optional" default="false"/> <attribute ref="r:id"/> </complexType> <complexType name="CT_ControlPr"> <sequence> <element name="anchor" type="CT_ObjectAnchor" minOccurs="1" maxOccurs="1"/> </sequence> <attribute name="locked" type="boolean" use="optional" default="true"/> <attribute name="defaultSize" type="boolean" use="optional" default="true"/> <attribute name="print" type="boolean" use="optional" default="true"/> <attribute name="disabled" type="boolean" use="optional" default="false"/> <attribute name="uiObject" type="boolean" use="optional" default="false"/> <attribute name="recalcAlways" type="boolean" use="optional" default="false"/> <attribute name="autoFill" type="boolean" use="optional" default="true"/> <attribute name="autoLine" type="boolean" use="optional" default="true"/> <attribute name="macro" type="ST_Formula" use="optional"/> <attribute name="altText" type="ST_XString" use="optional"/> <attribute name="linkedCell" type="ST_Formula" use="optional"/> <attribute name="listFillRange" type="ST_Formula" use="optional"/> <attribute name="cf" type="ST_String" use="optional" default="pict"/> <attribute name="autoPict" type="boolean" use="optional" default="true"/> <attribute ref="r:id"/> </complexType> <complexType name="CT_ObjectAnchor"> <sequence> <element name="from" type="CT_Marker" minOccurs="1" maxOccurs="1"/> <element name="to" type="CT_Marker" minOccurs="1" maxOccurs="1"/> </sequence> <attribute name="moveWithCells" type="boolean" use="optional" default="false"/> <attribute name="sizeWithCells" type="boolean" use="optional" default="false"/> <attribute name="z-order" type="unsignedint" use="optional"/> </complexType> Note that CT_Marker is already defined in the dml-chart schema. In §3.7 (Comments): Add a new element to contain comment properties. These were previously stored in VML. Since VML is deprecated, specifying a comment will not use VML and will instead use the new schema additions described below. For an example, consider the structure of the following isolated XML fragment: <comments> <authors> … </authors> <commentList> <comment … > <text> … </text> <commentPr autoFill="false"> <anchor moveWithCells="true" sizeWithCells="true"> <from> <col>1</col> <colOff>240630</colOff> <row>0</row> <rowOff>2</rowOff> </from> <to> <col>3</col> <colOff>240630</colOff> <row>3</row> <rowOff>256674</rowOff> </to> <anchor> </commentPr> </comment> </commentList> </comments> The following XML Schema fragments define the changes that will be made: The following change will be made to §3.7.3 (comment): <complexType name="CT_Comment"> <sequence> <element name="text" type="CT_Rst" minOccurs="1" maxOccurs="1"/> <element name="commentPr" type="CT_CommentPr" minOccurs="0" maxOccurs="1"/> </sequence> <attribute name="ref" type="ST_Ref" use="required"/> <attribute name="authorId" type="xsd:unsignedInt" use="required"/> <attribute name="guid" type="ST_Guid" use="optional"/> <attribute name="shapeId" type="unsignedInt" use="required"/> </complexType> The following new elements will be added (note that CT_ObjectAnchor is a new element defined above): <complexType name="CT_CommentPr"> <sequence> <element name="anchor" type="CT_ObjectAnchor" minOccurs="1" maxOccurs="1"/> </sequence> <attribute name="locked" type="boolean" use="optional" default="true"/> <attribute name="defaultSize" type="boolean" use="optional" default="true"/> <attribute name="print" type="boolean" use="optional" default="true"/> <attribute name="disabled" type="boolean" use="optional" default="false"/> <attribute name="uiObject" type="boolean" use="optional" default="false"/> <attribute name="autoFill" type="boolean" use="optional" default="true"/> <attribute name="autoLine" type="boolean" use="optional" default="true"/> <attribute name="altText" type="ST_XString" use="optional"/> <attribute name="textHAlign" type="ST_TextHAlign" use="optional" default="left"/> <attribute name="textVAlign" type="ST_TextVAlign" use="optional" default="top"/> <attribute name="lockText" type="boolean" use="optional" default="true"/> <attribute name="justLastX" type="boolean" use="optional" default="false"/> <attribute name="secretEdit" type="boolean" use="optional" default="false"/> <attribute name="autoScale" type="boolean" use="optional" default="false"/> <attribute name="rowHidden" type="boolean" use="optional" default="false"/> <attribute name="colHidden" type="boolean" use="optional" default="false"/> </complexType> <simpleType name="ST_TextHAlign"> <enumeration value="left"/> <enumeration value="center"/> <enumeration value="right"/> <enumeration value="justify"/> <enumeration value="distributed"/> </simpleType> <simpleType name="ST_TextVAlign"> <enumeration value="top"/> <enumeration value="center"/> <enumeration value="bottom"/> <enumeration value="justify"/> <enumeration value="distributed"/> </simpleType> In §3.7.3 (comment): Add the comment properties element as a valid child element. Add an attribute to point to a DrawingML shape. Remove references to VML from the following text: §3.3.1.18 (control) ­ shapeid attribute The following does not impact VML in Office Open XML and will not be changed. It is a setting that describes whether VML should be used when exporting the document to HTML for consumption by a web browser. §3.2.24 (webPublishing), pages 1904­1906 Part 4, §4 ­ PresentationML Deprecate the following and move them to the new annex for deprecated features: §4.4.2.1 (control), pages 3060­3061 ­ spid attribute §4.4.2.4 (oleObj), pages 3063­3064 ­ spid attribute In §4.4.2.1 (control), pages 3060-3061 and §4.4.2.4 (oleObj), pages 3063-3064: Add §4.4.1.34 (pic) as a valid child element. For example, in §4.4.2.1 (control), pages 3060­3061: Child Elements Subclause extLst (Extension List) §4.2.5 pic (Picture) §4.4.1.34 The following does not impact VML in Office Open XML and will not be changed. It is a setting that describes whether VML should be used when exporting the document to HTML for consumption by a web browser. §4.3.1.36 (webPr), pages 2994-2995 Part 4, §5 ­ DrawingML Deprecate the following and move them to the new annex for deprecated features: §5.3 (DrawingML - Legacy Compatibility), pages 3895-3896 §5.7.2.93 (legacyDrawingHF), pages 4041–4042 Remove references to VML from the following text: §5.7.2.26 (chart), page 4004 ­ id attribute §5.7.2.222 (userShapes), page 4115 ­ id attribute For example, in §5.7.2.26 (chart), page 4004: Attributes Description id (Relationship Reference) Namespace: …/officeDocument /2006/relationships Specifies the relationship ID for the relationship for this Chart , or Chart Drawing , or VML Drawing part. The type of relationship needed is specified by the parent element. The possible values for this attribute are defined by the ST_RelationshipId simple type (§7.8.2.1). Part 4, §6 ­ VML Deprecate the following and move them to the new annex for deprecated features: 1. §6 (VML Reference Material), pages 4,343–4,960 Similar Comments: CO-0076 , CO-0223 , CZ-0004 , CZ-0011 , DE-0018 , DE-0020 , DE-0021 , DE-0115 , DE-0116 , DK-0058 , DK- 0095 , DK-0155 , FI-0008 , GB-0177 , GB-0190 , GB-0476 , GB-0477 , GR-0087 , IE-0009 , JP-0030 , KE-0047 , KE-0064 , MX-0006 , US- 0092 , US-0152 , UY-0002 , VE-0013 , ZA-0016