Re: Call for consensus - transcript extension

I support the proposal. I'd go with developing example 1. I'm expecting
we'll eventually whittle the options down to one, once we put our finger to
see what way the wind will blow with the HTML5 team.

Cheers,

David MacDonald



*Can**Adapt* *Solutions Inc.*

Tel:  613.235.4902

LinkedIn <http://www.linkedin.com/in/davidmacdonald100>

www.Can-Adapt.com



*  Adapting the web to all users*
*            Including those with disabilities*

If you are not the intended recipient, please review our privacy policy
<http://www.davidmacd.com/disclaimer.html>

On Sat, Jun 20, 2015 at 5:12 AM, <chaals@yandex-team.ru> wrote:

> Hi,
>
> 20.06.2015, 04:25, "Silvia Pfeiffer" <silviapfeiffer1@gmail.com>:
> > On Sat, Jun 20, 2015 at 11:57 AM, <chaals@yandex-team.ru> wrote:
> >>  Hi Silvia, all,
> >>
> >>  20.06.2015, 03:20, "Silvia Pfeiffer" <silviapfeiffer1@gmail.com>:
> >>>  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.
> >>
> >>  It is obviously not ready to be used as an extension spec. It could be
> an early working draft or editors' draft.
> >
> > If I've not been clear: I'm against it being a working draft. Anything
> > else is an unofficial document from a spec status. It already is an
> > editor draft and can continue to stay that way while you and the task
> > force improve it.
> >
> >>>  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.
> >>
> >>  If we are going to continue the work, and if we get a document ready
> for Publication while the group is still under its old charter, it would be
> nice (but not essential) to have already determined whether we are going to
> shift it immediately to the new Process.
> >
> > This is about setting the process version in the respec document then.
> > I agree with this.
>
> OK
>
> >>>  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.
> >>
> >>  Subject to you stating otherwise, I read that as support for making
> the draft into the TF's editors' draft, and not answering the second
> question.
> >
> > I don't see a difference in having it a editor draft of yours or of
> > the task force - it doesn't change the official standing of the
> > document. I just wanted to make sure this is understood and this is
> > not regarded as an agreement on a WD or an extension spec.
> >
> > Also, if an alternative spec should emerge (however unlikely), I don't
> > see this decision as a decision that excludes the possibility of
> > taking on another draft as a working draft for the transcript issue. I
> > just wanted to be clear on that.
>
> Yeah, I don't know of any reason why we would exclude that possibility.
> The current draft explicitly anticipates it by including a number of the
> possible alternative strategies - effectively it is a compound of several
> possible specs, of which I hope we end up with fewer than two…
>
> > Given these reservations, I'm ok with both.
>
> OK, thanks.
>
> cheers
>
> Chaals
>
> > Cheers,
> > Silvia.
> >
> >>  cheers
> >>
> >>  Chaals
> >>
> >>>  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
> >>
> >>  --
> >>  Charles McCathie Nevile - web standards - CTO Office, Yandex
> >>  chaals@yandex-team.ru - - - Find more at http://yandex.com
>
> --
> Charles McCathie Nevile - web standards - CTO Office, Yandex
> chaals@yandex-team.ru - - - Find more at http://yandex.com
>
>
>