This describes an "ink" element which stores "ink annotations in an application-defined format." This is apparently intended to store annotations, used with tablet input devices to add hand-written annotations to documents. These annotations are often a vital part of documents and their specification is undefined in OOXML. We are opposed to standardizing placeholder elements for entirely application-dependent proprietary formats without also specifying an interoperable format for those who with to create interoperable formats.

Specify the "ink" format or remove the element from OOXML and make this an application extension using the extensibility mechanisms of OOXML.

- Part 4, Section 6.2.2.14

te

Proposed Disposition of DIS 29500 Comment CL-0209 (Modified: 2008-01-04) Agreed; this can be changed to improve interoperability. The following changes will be made to Part 4, §6.2.2.14, pages 4,813­4,814 to allow any content to be stored in the i attribute and to add a contentType attribute to specify the format of the value of the i attribute. Part 4, §6.2.2.14, page 4,813, lines 7­13 This element specifies the presence of an ink object. An ink object is a VML object which allows applications to store data for ink annotations in an application-defined format . [Note: Applications are encouraged to use an open-ink format, such as the Ink Markup Language (InkML), a Working Draft specification of the World Wide Web Consortium, available at http://www.w3.org/TR/InkML/. end note] [Example: <v:shape … > <o:ink i="…" annotation="t" contentType="application/inkml+xml"/> </v:shape> <v:shape … > <o:ink i="AMgFHQSWC+YFASAAaAwAAAAAAMA…" annotation="t" contentType="application/x-ms-ink" /> </v:shape> end example] Part 4, §6.2.2.14, page 4,813, line 14 and page 4,814, top Attributes Description contentType (Content Type) Specifies the format of the ink content stored in the i attribute. The syntax is a content type as defined in IETF RFC 2616, available at http://www.ietf.org/rfc/rfc2616.txt . If this attribute is omitted, application should attempt to determine the content type by reading the contents of the i element. The possible values for this attribute are defined by the ST_ContentType simple type. i (Ink Data) Specifies additional ink object information which shall be associated with the parent VML shape. The VML shape specifies the information necessary to render the ink, and this attribute may be used to store additional application-specific data about the VML shape(s) representing ink. This attribute’s contents are formatted as specified by the contentType attribute, but are optional and may be ignored if not recognized. [Example: <o:ink … i=" AMgFHQSWC+YFASAAaAwAAAAAAMA …"> </o:ink> end example] The possible values for this attribute are defined by the XML Schema base64Binary string datatype. Part 4, §6.2.2.14, page 4,814, line 4 and after line 5 The following XML Schema fragment defines the contents of this element: <complexType name="CT_Ink"> <sequence/> <attribute name="i" type="xsd: base64Binary string "> <attribute name="annotation" type="ST_TrueFalse"/> <attribute name="contentType" type="ST_ContentType"> </simpleType> The following new subclause will be added, and existing subclauses §6.2.3.8­§6.2.3.24 will be renumbered. The corresponding schema definition files will be updated accordingly. 6.2.3.8 ST_ContentType (Content Type) This simple type specifies a content type. This simple type’s contents are a restriction of the XML Schema string datatype. Referenced By contentType@ink (§6.2.2.14); The following XML Schema fragment defines the contents of this element: <simpleType name="ST_ContentType"> <restriction base="xsd:string"/> </simpleType> Similar Comments: BR-0057 , FR-0373 , GB-0485 , PT-0111 , US-0157