W3C home > Mailing lists > Public > public-media-fragment@w3.org > November 2008

News from the HTML5 WG

From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
Date: Fri, 14 Nov 2008 17:02:58 +1100
Message-ID: <2c0e02830811132202p2e28260dp8d7b12286bf12a1e@mail.gmail.com>
To: "Media Fragment" <public-media-fragment@w3.org>

For those of you not subscribed to the WHATWG mailing list, here is some new:

Ian just proposed to use media fragment URIs to control time offset
playback (use case 3 below) instead of other mechanism so far
discussed in HTML5.

Let's get a simple spec out asap if we can! :-)

Cheers,
Silvia.


---------- Forwarded message ----------
From: Ian Hickson <ian@hixie.ch>
Date: Fri, Nov 14, 2008 at 1:56 PM
Subject: Re: [whatwg] video tag : loop for ever
To: WHAT Working Group Mailing List <whatwg@whatwg.org>



There were 81 e-mails on the topic of looping audio and video.

I haven't included them here because they were mostly redundant. However,
I read them all, and it seems that the use cases and feedback boiled down
to these points:

 1. Feedback: Simplify the API where possible; in particular start/end/
   loopStart/loopEnd and so on.

 2. Use case: looping complete tracks of background audio or video without
   glitches.

 3. Use case: playing a track starting at a particular location without
   using script that waits for the media to load.

 4. Use case: playing different media segments with only one HTTP request.

To address point 1 I've removed all those attributes and related APIs.

To address point 2 I've added a single attribute "loop", which, when
set, causes the UA to loop back to time=0 when the clip ends.

To address point 3 I would like us to consider using recently begun
work relating to fragment identifiers for media content. I have edited
the spec so that it defers to the fragment identifier or any metadata
in the resource, but I expect we will have to further tweak this.

To address point 4 I would like to rely on a more generic solution
that also addresses this for CSS, images, etc. This could be jar:, or
it could me a MIME multipart solution, or offline caching, or data:
URLs, or something else. However, I think this transcends the media
API and therefore I haven't added anything specifically in this API to
deal with it.

If I have missed a key point, please do let me know. It's quite
possible that I missed something when reading this thread as it was
quite long and had a lot of repetition.

--
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Friday, 14 November 2008 06:03:38 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 21 September 2011 12:13:31 GMT