DR-17-0010: VML: Attribute examples

MURATA Makoto eb2m-mrt at asahi-net.or.jp
Sat Apr 8 00:16:11 CEST 2017


I think that the remaining task for option #3 is very small, and I
presume that new implementations cannot always avoid

29500-4 repeats attributes too often.  I think that this repetition
makes the standard less readable.  Note that no other attributes
are repeated in OOXML.  It is only VML attributes that are

Which part of the remaining task for option #3
needs big efforts?


2017-04-08 3:15 GMT+09:00 Rex Jaeschke <rex at rexjaeschke.com>:

> In private mail to Murata-san back in January, I identified the following
> three options for addressing this DR, listed here in increasing amount of
> effort:
> 1.      Do nothing. [No effort]
> 2.      Look at each of the 300+ examples and change them to have the
> appropriate parent element. [Some effort]
> 3.      Look at removing the duplicate specification of all these
> attributes, by putting them in their own subclause and having the parent
> elements point there. (As I think there are other attribute groups used in
> multiple contexts, this option wouldn't make sense unless one
> rearranged/consolidated all such groups.) [A big effort]
> As indicated in the DR log, Murata-san supports Option #3.
> After considerable discussion with MS experts, I and MS favor Option #1. As
> is, the spec is good enough even if it's not strictly correct; in any
> event,
> examples are informative, not normative. No implementer has reported this
> as
> a problem, so it's not holding up anyone w.r.t conformance, and we presume
> new implementers aren't implementing Transitional stuff. We have more
> important issues to deal with, so we propose closing this DR without
> action.
> Rex


Praying for the victims of the Japan Tohoku earthquake

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.vse.cz/pipermail/sc34wg4/attachments/20170408/003c226b/attachment.html>

More information about the sc34wg4 mailing list