PF's proposed document naming convention re API mappings

Colleagues:

During our last CG telecon I was asked to summarize PF's new proposed
convention on document naming for a complex of documents which we expect
to publish in the coming years growing out of our ARIA.Next activities.


The proposed naming scheme is as follows, where X stands for a
particular markup technology:

"The X Accessibility APIs Mapping Guide"

As of this writing we expect a minimum of 3 documents will bear this
title in the next two years:

The Core ARIA Accessibility APIs Mapping Guide, will be the partial
successor to the recently published ARIA 1.0 User Agent Guide. This
"core" guide will specify normative requirements on any user agent
implementing ARIA 1.1 (and above).

The above normative requirements are seen as pertaining to any user
agent implementing ARIA. Added to that will be a series of optional
markup technology specific normative requirements on user agents
implementing particular markup technologyes. Two such are expected in
the next 2 years.

The HTML5 Accessibility APIs Mapping Guide, also a partial successor to
the ARIA 1.0 User Agent Guide, will map additional ARIA markup as well
as all HTML elements to the various accessibility APIs.

The SVG2 Accessibility APIs Mapping Guide will map additional ARIA
markup particular to SVG as well as all SVG elements to the various accessibility APIs.

There may be additional guides, e.g. for Epub.

These additional guides are "optional" only in the sense that only user
agents implementing the particular markup technology need implement the
normative requirements specified in these guides.

It is our desire that our document naming convention help indicate these
documents are related one to another.

Is this scheme sufficient? Or should we also seek to indicate the
parent/child relationship by perhaps using an additional term in the
title, i.e.

The Supplamentary X Accessibility APIs Mapping Guide

... so that it's clear there's a "Core" guide, as well as "Supplamentary"
guides?

This last notion is new in this email, not previously discussed.

Please give us your thoughts. We want to get this naming scheme right,
as we will likely live with our decision for many years to come.

Janina

-- 

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 Tuesday, 6 May 2014 12:29:36 UTC