Re: Call for consensus - transcript extension

I'm not clear what 1) entails.

If you're asking me whether the spec is ready to be used as an
extension spec or Working Draft, then I have to object.

If you're asking me whether this task force should continue improving
this spec as an unofficial document, then I'm ok with it.

To be clear:
* The document is a discussion paper and not a specification at this
stage, because it contains use cases and requirements that are not met
by the proposed specification and it contains alternative linking
approaches that are not prescriptive which one should be specified. It
would be unclear to an implementer what to implement.
* Also, from a more technical approach, I don't agree that
"delineation" requires introduction of a new element - I've expressed
this before.
* I also object to several of the linking approaches.

As for 2) - that only applies to WD of WG documents, so I'm not sure
why that would be relevant to an unofficial document.

In short: I am supportive of this group continuing work on
transcripts, but I don't believe the work is ready for prime time yet.

Cheers,
Silvia.


On Sat, Jun 20, 2015 at 10:56 AM,  <chaals@yandex-team.ru> wrote:
> Hello, this is a call for consensus on each of the following proposals:
>
> 1) The HTML Accessibility Task Force should adopt the draft specification at http://chaals.github.io/html-transcript/html-transcript-src.html as its initial draft for the transcript work item.
>
> 2) If the work continues toward recommendation, it should be managed under the 2014 Process Document
>
> Yes/no responses on each proposal are requested in reply to this email thread, and will be accepted up to midnight Hawaii Time on Friday 26 June. Lack of response will be considered assent without endorsement.
>
> cheers
>
> Chaals - TF co-coordinator.
>
> --
> Charles McCathie Nevile - web standards - CTO Office, Yandex
> chaals@yandex-team.ru - - - Find more at http://yandex.com
>

Received on Saturday, 20 June 2015 01:20:29 UTC