On Tue, 2008-07-22 at 22:00 +, Ian Hickson wrote:
> On Tue, 22 Jul 2008, Philip Jgenstedt wrote:
> > >
> > > What are the use cases you think are basic? It's unclear to me what
> > > isn't being solved. Here's one use case, a slide deck:
> >
> > The most obvious use case in my mind is displa
On Tue, 22 Jul 2008, Philip J�genstedt wrote:
> >
> > What are the use cases you think are basic? It's unclear to me what
> > isn't being solved. Here's one use case, a slide deck:
>
> The most obvious use case in my mind is displaying captions/subtitles.
I'd much, much ratio subtitles were don
On Tue, 2008-07-22 at 09:58 +, Ian Hickson wrote:
> On Wed, 9 Jul 2008, Dave Singer wrote:
> On Sat, 12 Jul 2008, Philip Jgenstedt wrote:
> >
> > Like Dave, I am not terribly enthusiastic about the current cue ranges
> > spec, which strikes me adding a fair amount of complexity and yet
> > d
On Wed, 9 Jul 2008, Dave Singer wrote:
> >
> > One of the features proposed for the next version of the video API is
> > chapter markers and other embedded timed metadata, with corresponding
> > callbacks for authors to hook into. Would that resolve the problem you
> > mention?
>
> It may be t
Hi Philip, Dave, all,
I agree with Philip and Dave that we need a simple way to include the
cue ranges concept into video for video authors.
As one of the authors of Annodex, I have been meaning to look over the
HTML5 video element for a while and examine how it's details works -
sorry for my lat
Just to add some of my thought on cue ranges.
Like Dave, I am not terribly enthusiastic about the current cue ranges
spec, which strikes me adding a fair amount of complexity and yet
doesn't solve the basic use case in straightforward manner.
If I were a content author and looked at the available
OK, some comments back on the cue range design. Sorry for the
summer-vacation-induced delay in response!
At 1:00 + 12/06/08, Ian Hickson wrote:
> In the current HTML5 draft cue ranges are available using a DOM API.
This way of doing ranges is less than ideal.
First of all, it is ha
At 14:20 +1000 23/05/08, Silvia Pfeiffer wrote:
Hi Dave,
If the W3C standardises time ranges through a URI approach, would
there still be a need to have a specification in the DOM or the HTML
code?
I think the two have different purposes and use-cases, don't they?
I am talking about this p
Hi Dave,
If the W3C standardises time ranges through a URI approach, would
there still be a need to have a specification in the DOM or the HTML
code?
I am talking about this planned activity
http://www.w3.org/2008/01/media-fragments-wg.html and a scheme akin to
the one mentioned here
http://www.w
