- From: James Craig <jcraig@apple.com>
- Date: Wed, 11 Jun 2014 14:14:35 -0700
- To: Jason Kiss <jason@accessibleculture.org>, W3C WAI Protocols & Formats <public-pfwg@w3.org>, HTML Accessibility Task Force <public-html-a11y@w3.org>
- Cc: Michael Cooper <cooper@w3.org>, Joseph Scheuhammer <clown@alum.mit.edu>, Steve Faulkner <faulkner.steve@gmail.com>, "public-html-admin@w3.org" <public-html-admin@w3.org>, Robin Berjon <robin@w3.org>
We had discussed disambiguating these acronyms by calling them:
Core-AAM instead of CAAM.
HTML-AAM instead of HAAM.
SVG-AAM instead of SAAM.
This would allow continued use of the same -AAM suffix ("accessibility API mapping") for other specs that start with the same letter, like CSS.
CSS-AAM (for example useful when we need to map CSS generated list markers to APIs like AXListMarker).
Thanks,
James
On Jun 10, 2014, at 10:49 PM, jason@accessibleculture.org wrote:
> Thanks, Robin.
>
> So, am I right in thinking that this leaves Michael, Joseph, James, and myself to sort out changes to the directory structure in that repo to accommodate the CAAM, HAAM, and SAAM so that they easily use any shared resources?
>
>
>
> Jason Kiss
> jason@accessibleculture.org
> http://www.accessibleculture.org
>
>
>
>
> On 10/06/2014, at 8:36 pm, Robin Berjon <robin@w3.org> wrote:
>
>> Hi Jason,
>>
>> On 09/06/2014 00:26 , jason@accessibleculture.org wrote:
>>> Robin, just following up: Any objections to the HTML Accessibility API
>>> Mappings (HAAM) doc going in the ARIA repo?
>>
>> None that I can think of!
>>
>> --
>> Robin Berjon - http://berjon.com/ - @robinberjon
>
>
Received on Wednesday, 11 June 2014 21:15:12 UTC