RE: spec. updates.

>-----Original Message-----
>From: Richard Schwerdtfeger []
>Regarding categorizing SVG elements in the SVG-AAM I think the better place
>to do this would be in the authoring practices and not the browser mapping
>spec. which is targeted at user agent developers responsible for SVG
>accessibility support. I also find it easier to keep up an alphabetical list of
>elements and their mappings with the SVG spec. itself by looking at the
>element cross reference. So, I would rather not refactor this right now.

One approach might be (though not for the first working draft) to write a non-normative explanation of the rationale that points out the common mappings of various elements. This wouldn't necessitate changing the table of mappings, but it would help to explain the design (albeit concisely).

I think this would address at least part of what was discussed at the meeting on this point.


This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited.

Thank you for your compliance.


Received on Monday, 26 January 2015 23:54:26 UTC