future of the XHTML Role Module (PF agenda addendum request 2009-11-11)

as discussed at today's XHTML2 Working Group teleconference

http://www.w3.org/2009/11/11-xhtml-minutes.html#item04

since the XHTML2 working group's deliverables under continued 
development are being farmed out to WGs without an expiration date, 
it would be optimal for WAI if PF or the WAI in general takes 
ownership of the XHTML Role Module

why?

1.1. currently the only way that the XHTML2 WG can get the Role Module 
through W3C process before it expires is to change it from Rec status to 
Note status, which means that ARIA would not be able to normatively point 
to the Role Module, as it would only be a note.

1.2. the XHTML Role Module was a deliverable which PF asked the XHTML2 WG 
to draft and publish; since the XHTML2 activity is being dismantled, the
most logical place for the Role Module to find a home and keep in Rec
track is within WAI/PF

which brings me to the next question:

should WAI/PF absorb the Role Module into ARIA or should it continue to 
develop the Role Module as a distinct deliverable?

2.1. the Role Module has great utility outside the realm of accessibility;
it can be used to perform repairs upon mash-ups so that users -- and their
equipment -- can make sense of them, either directly or through a 
server or client-side script in the manner that GreaseMonkey and 
AccessMonkey currently operate.

2.2. as ARIA grows and changes, it would be useful to keep the core of 
the concept of Role as its own document, so that it is neither 
sublimated by nor obscured by the rest of the ARIA spec, which is 
already massive enough; moreover, maintaining the Role Module in 
addition to ARIA would enable WAI/PF to control both the general 
mechanism for extensibility and landmarking (the Role Module) and its 
application in ARIA

i have, therefore, been asked by the XHTML2 WG to ask PF/WAI if it would
take ownership of the XHTML Role Module; the module's main author, Shane
McCarron has explictly expressed his willingness to continue as the 
document's main editor, a burden he has shouldered since Role's inception,
so we need not worry that the Role Module will land in PF/WAI's lap 
without clear and firm guidance of the type that Shane is capable of 
providing.  in addition, one of our own -- RichS -- is listed as an 
editor of the Role Module, since it was his initial negotiations with the
XHTML2 WG that led to the XHTML2 WG taking ownership of the Role Module

i eagerly anticipate discussion of this proposal/request,
gregory.
-----------------------------------------------------------------
Accessibility, Internationalization, and Interoperability are not
"features", "overlays" or "add-ons".  Rather, they are core 
components of any architecture -- programmatic or otherwise.
-----------------------------------------------------------------
     Gregory J. Rosmaita, gregory@linux-foundation.org
Vice-Chair, WebMaster & Listmaster, Open Accessibility Workgroup
http://a11y.org/                                http://a11y/specs
-----------------------------------------------------------------

Received on Wednesday, 11 November 2009 15:57:21 UTC