It is against the described best practice of ECMA-376 Office Open XML to adopt VML functionality within the WordprocessingML. As described in part 4 Section 6.1 page 4343 line 12, the VML is considered "deprecated"
This could raise confusion, since the specification state one thing ( don’t use VML), but actually do the oppesit itself ( applying VML to construct, which could be done using DrawingML)
This could raise confusion, since the specification state one thing ( don’t use VML), but actually do the oppesit itself ( applying VML to construct, which could be done using DrawingML)
VML should be maintained in the specification solely for backwards compatibility reasons and it should be maintained that the usage of VML is "deprecated". We strongly suggest that future versions of DrawingML should be extended to become a full superset of VML and subsequently no distinct parts of the specification should rely VML, but instead utilize this extended DrawingML.
Page 1615
line 16 Part 4
Section 2.17.1.1
Te
Proposed Disposition of DIS 29500 Comment DK-0022 (Modified: 2008-01-03) Agreed; deprecated markup should not be required in Part 4, §2.3.3.19 and §2.3.3.21 (or at any other location within WordprocessingML). At each location where VML is required, VML will be deprecated 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. Similar Comments: CA-0016 , CL-0140 , CO-0085 , CO-0086 , DE-0019 , DE-0022 , DE-0109 , DK-0006 , DK-0007 , DK-0008 , DK- 0009 , FR-0049 , GB-0174 , GB-0178 , GR-0069 , IN-0049 , KE-0048 , KE-0053 , MY-0001 , US-0119 , US-0124 , VE-0014
