Putting XML fragment into an attribute value is completely unacceptable.
Use nested element instead of gfxdata attribute for storing direct representation of XML. We will not insist on this change if VML is moved into a separate Technical Report as suggested in one of previous comments.
p. 4655 Part 4/6.1.2.19
te
Proposed Disposition of DIS 29500 Comment CZ-0036 (Modified: 2008-01-08) Agreed; this can be changed to improve interoperability. Additionally, in each location where VML is required, VML will be deprecated (but fully documented for legacy purposes) and replaced with an alternative in the DrawingML format. This is addressed in detail within the disposition of the following comments: CA-0076, CL-0025, CL-0206, CO-0076, CO-0223, CZ-0004, CZ-0011, DE-0018, DE-0020, DE-0021, DE-0115, DE-0116, DK-0058, DK-0095, DK-0150, 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, and ZA-0016. The following changes will be made to Part 4, ยง6.1.2.19, page 4,655 to make it clear what format the data should be stored in: Attributes Description gfxdata (Encoded Package) Namespace: urn:schemas-microsoft-com:office:office Specifies a base-64 encoded package as de i fined in Part 2 of this Standard that contains DrawingML content as defined in Part 4 of this standard . The contents of this package are application-defined, but the contents of the package shall use the Parts defined by this Standard whenever possible. [Rationale: This attribute allows an application to use VML to represent graphical content for a legacy document while still persisting DrawingML for consuming applications that support DrawingML. For example, a diagram stored within this attribute would have the four parts defined for a DrawingML diagram, as well as any number of application-defined parts and relationships. end r ationale] [ Example: A DrawingML object is encoded in the gfxdata attribute, leaving VML to handle the visual display: <v:shape id="Diagram 1" o:spid="_x0000_i1025" type="#_x0000_t75" style="width:446.25pt;height:252pt; visibility:visible" o:gfxdata="UEsDBBQABgAIAAAAIQDIu8KcTQE…"> <v:imagedata r:id="rId4" o:title=""/> </v:shape> end example ] The possible values for this attribute are defined by the XML Schema base64Binary datatype. Similar Comments: BR-0056 , CL-0009 , CL-0208 , CO-0226 , DE-0112 , FR-0372 , GB-0484 , GR-0088 , US-0155
Possible dupe of US 155.
Deals with exactly same part of spec