W3C home > Mailing lists > Public > public-html-a11y@w3.org > June 2014

Re: Acronym corrections: CAAM -> Core-AAM, etc. (Was: Accessibility API Mappings - location in Github?)

From: James Craig <jcraig@apple.com>
Date: Wed, 11 Jun 2014 23:42:45 -0700
Cc: W3C WAI Protocols & Formats <public-pfwg@w3.org>, HTML Accessibility Task Force <public-html-a11y@w3.org>, 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>
Message-id: <3814ED8D-E0D8-4653-8BCD-6637C3566C93@apple.com>
To: Jason Kiss <jason@accessibleculture.org>
I think the main benefit is readability and understandability for others outside the working groups. No one will know what HAAM is, but HTML-AAM and SVG-AAM are generally understandable without much additional context. Once people understand that "AAM" means Accessibility API Mapping, all of the acronyms are understandable without any additional context. 

As an example, would MAAM refer to MathML, MML, Media, or something else entirely? Who knows? Changing that to MathML-AAM removes that ambiguity immediately.


On Jun 11, 2014, at 9:23 PM, Jason Kiss <jason@accessibleculture.org> wrote:

> Disambiguation acknowledged. It's certainly not as fun a naming
> convention, but it is more than reasonable.
> 
> Jason
> 
> On Thu, Jun 12, 2014 at 9:14 AM, James Craig <jcraig@apple.com> wrote:
>> 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 Thursday, 12 June 2014 06:44:04 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:05:39 UTC