W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > October 2013

[Bug 23421] HTML-AAPI doc should be a living document

From: <bugzilla@jessica.w3.org>
Date: Wed, 02 Oct 2013 17:28:04 +0000
To: public-html-bugzilla@w3.org
Message-ID: <bug-23421-2486-QUax8kpaop@http.www.w3.org/Bugs/Public/>

--- Comment #2 from James Craig <jcraig@apple.com> ---
(In reply to steve faulkner from comment #1)
> (In reply to James Craig from comment #0)
> > All of the Accessibility APIs have changed somewhat since the first draft of
> > the ARIA implementation guide. I worry that using the spec-track approach
> > for external API mappings while only ensure that the document is immediately
> > out of date at the time it is published. I'd recommend making this a living
> > document rather than a spec-track document.
> Hi james, this is not something that the editors can decide, it needs to be
> brought up with the PF/HTML wg's.
> Am unclear as to how a living document concpet fits in with the current
> document track options available in the W3C, any ideas?
> Also sounds like the ARIA implementation guide should changed to use a
> similar approach right?

I agree, and have proposed the same to the PFWG.

> FWIW as i mentioned to you in another place, the always latest and publicly
> available editors draft [1] is a 'living document' and I would expect
> implementers to be using it over the periodic WD snapshots
> [1] http://rawgithub.com/w3c/html-api-map/master/index.html

This is the workaround I've been recommending.

You are receiving this mail because:
You are on the CC list for the bug.
Received on Wednesday, 2 October 2013 17:28:06 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:31:44 UTC