W3C home > Mailing lists > Public > public-html-a11y@w3.org > May 2011

Re: [media] issue-152: documents for further discussion

From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
Date: Tue, 17 May 2011 21:23:12 +1000
Message-ID: <BANLkTi=jgnktrY6-1RrXo5OH8W7XFLV7FA@mail.gmail.com>
To: Bob Lund <B.Lund@cablelabs.com>
Cc: HTML Accessibility Task Force <public-html-a11y@w3.org>, "Mark Vickers @ Comcast" <mark_vickers@cable.comcast.com>, Eric Winkelman <E.Winkelman@cablelabs.com>, David Agranoff <d.agranoff@cablelabs.com>
Hi Bob,

Ah, sorry, I misunderstood.

Actually, I think what you are trying to do should be done with an
application-specific tag, because the tracks that are @kind=metadata
will really be interpreted by local script applications only - there
doesn't need to be standardized names.

So, I suggest you use an @data-xxx attribute, such as @data-content or
@data-type on the track elements to solve this. I really don't think
we need anything more specialized than that.

Regards,
Silvia.

On Tue, May 17, 2011 at 9:00 AM, Bob Lund <B.Lund@cablelabs.com> wrote:
> Hi Silvia,
>
> No, these are two separate issues. Issue 1 addresses multiple file formats, i.e metadata tracks can come as ttml, vtt, etc. Issue 8 addresses the need to identify what kind of metadata is in a file of a specific format, e.g. does the vtt file contain a content advisory or an ad insertion message.
>
> Bob
>
>> -----Original Message-----
>> From: Silvia Pfeiffer [mailto:silviapfeiffer1@gmail.com]
>> Sent: Monday, May 16, 2011 4:04 PM
>> To: Bob Lund
>> Cc: HTML Accessibility Task Force; Mark Vickers @ Comcast; Eric
>> Winkelman; David Agranoff
>> Subject: Re: [media] issue-152: documents for further discussion
>>
>> Hi Bob,
>>
>> that issue is now present twice on that page: both as a first and a last
>> issue. :-)
>>
>> Cheers,
>> Silvia.
>>
>>
>> On Tue, May 17, 2011 at 5:20 AM, Bob Lund <B.Lund@cablelabs.com> wrote:
>> > All,
>> >
>> > I've added a new issue "8 Support for multiple metadata track types"
>> to the Media TextTrack Issues wiki page
>> http://www.w3.org/WAI/PF/HTML/wiki/Media_TextTrack_Issues. The issue is
>> described, along with some implementation alternatives and a preferred
>> implementation.
>> >
>> > I'm very interested in all feedback on the issue and proposed
>> alternatives. On a related note, will we be discussing all of the issues
>> raised on this wiki page in a upcoming media subgroup call?
>> >
>> > Thanks,
>> > Bob Lund
>> >
>> >
>> >
>> >> -----Original Message-----
>> >> From: public-html-a11y-request@w3.org [mailto:public-html-a11y-
>> >> request@w3.org] On Behalf Of Silvia Pfeiffer
>> >> Sent: Sunday, April 10, 2011 9:42 PM
>> >> To: HTML Accessibility Task Force
>> >> Subject: [media] issue-152: documents for further discussion
>> >>
>> >> Hi all,
>> >>
>> >> As agreed in the last media subgroup meeting, I have put together a
>> >> wiki page that summarizes the different proposals under discussion
>> >> for issue- 152.
>> >>
>> >> You can find it at
>> >> http://www.w3.org/WAI/PF/HTML/wiki/Media_Multitrack_Change_Proposals_
>> >> Sum
>> >> mary
>> >> .
>> >>
>> >> As I was adding in the key changes that Ian's Controller-based
>> >> approach provides, I also noticed some issues with it and took note.
>> >> None of them are major issues and I would have found similar things
>> >> on the other proposals.
>> >>
>> >> Also note that I have pulled out all the discussions that
>> >> intermingled with the multitrack issues, but really related to the
>> >> TextTrack API into a new page at
>> >> http://www.w3.org/WAI/PF/HTML/wiki/Media_TextTrack_Issues
>> >> . We should keep the discussion of these issues for after we've
>> >> finalized what we want to do about issue-152.
>> >>
>> >> Cheers,
>> >> Silvia.
>> >
>> >
>
Received on Tuesday, 17 May 2011 11:24:05 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 04:42:38 GMT