W3C home > Mailing lists > Public > public-html-a11y@w3.org > September 2012

What's in a name?

From: Laura Carlson <laura.lee.carlson@gmail.com>
Date: Wed, 19 Sep 2012 07:39:34 -0500
Message-ID: <CAOavpvcfy51Bnvq8O=vJUk_u1w4hvm_t-dY+896nMZSYfV3Cpg@mail.gmail.com>
To: James Craig <jcraig@apple.com>, Cynthia Shelly <cyns@microsoft.com>, David Bolter <david.bolter@gmail.com>, Ian Hickson <ian@hixie.ch>
Cc: public-html-a11y@w3.org, Sam Ruby <rubys@intertwingly.net>
Hi James, Cynthia, David, and Ian,

Sam wrote to Leif in another thread:

> And (recognizing that I do NOT work for a
> browser vendor), I do believe that a solution for these problems can be
> specified in a matter of months and demonstrably conforming public
> implementations could be produced in a matter of months after that.
>
> As to whether or not that attribute should be spelled "longdesc"

One question to our task force browser reps: would you implement a
change proposal with the exact same verbiage as the instatelongdesc
proposal [1] if the HTML5 attribute name @longdesc was changed to
@desc or @describedat something similar [2]? Does the name make a
difference to your company implementing it?

Best Regards,
Laura
[1] http://www.w3.org/html/wg/wiki/ChangeProposals/InstateLongdesc
[2] https://www.w3.org/Bugs/Public/show_bug.cgi?id=10455
Related Ref "New HTML Attribute":
[3] http://www.d.umn.edu/~lcarlson/research/constriants/newattribute.html
-- 
Laura L. Carlson
Received on Wednesday, 19 September 2012 12:40:06 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 19 September 2012 12:40:07 GMT