Re: PF's proposed document naming convention re API mappings

Hello Steve, All:

Two comments:

1.)	I agree, and the just concluded PF telecon and PF-Editors
telecon also agree, that the word "Guide" is unhelpful and inappropriate
for a normative specification. We now propose to drop that word.

2.)	I erred in representing the core mapping document as the "Core
ARIA" document. The correct proposed title is:

Core Accessibility API Mappings

As was pointed out on the PF call, this helps with the parent-child
relationship to our other identified documents:

HTML Accessibility API Mappings
SVG Accessibility API Mappings

Janina

Steven Faulkner writes:
> On 6 May 2014 13:28, Janina Sajka <janina@rednote.net> wrote:
> 
> > The X Accessibility APIs Mapping Guide
> 
> 
> given that they are going to be normative documents using the term "guide"
> seems like a misnomer.
> 
> suggest 'specification'
> --
> 
> Regards
> 
> SteveF
> HTML 5.1 <http://www.w3.org/html/wg/drafts/html/master/>

-- 

Janina Sajka,	Phone:	+1.443.300.2200
			sip:janina@asterisk.rednote.net
		Email:	janina@rednote.net

Linux Foundation Fellow
Executive Chair, Accessibility Workgroup:	http://a11y.org

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Chair,	Protocols & Formats	http://www.w3.org/wai/pf
	Indie UI			http://www.w3.org/WAI/IndieUI/

Received on Wednesday, 7 May 2014 17:52:19 UTC