W3C home > Mailing lists > Public > public-tt@w3.org > January 2003

Re: TT Content Buffering and Timing Scenarios

From: Charles Wiltgen <lists@wiltgen.net>
Date: Wed, 29 Jan 2003 20:34:01 -0800
To: W3C TT Public <public-tt@w3.org>
Message-ID: <BA5DEB39.5D0D1%lists@wiltgen.net>

Glenn A. Adams wrote...

> Well, I hope this will spark a useful discussion, at least one that I can
> learn from.

Normally I like to lurk on new lists, but since nobody's chimed in yet (why,
it's been over three hours!)...   :^)

> In using RealText and QuickText as (potential) examples of non-streaming
> TT content, I did not mean to imply that they were only non-streaming; I
> believe (but am not completely certain) that they also may be delivered
> in streaming mode; perhaps someone can confirm this for me.

I know that QuickTime supports this.

> Given that we are committed to defining an XML based syntax for TT, how
> should we deal with the need to stream TT content?

My main experience with this is related to EventStream, an XML-based
language we created for Cleaner 5 that allows content authors to define
timed text, buttons, timed URL triggers, etc. in a format-agnostic fashion.

EventStream text was encoded very differently depending on the destination
format (QuickTime, RealSystem, Windows Media), and streamed very differently
as well depending on the format and the protocol (HTTP, RTSP, MMS) used.

I guess what I'm asking is, does this group need to define how TT is
streamed using all potential standards-based and proprietary protocols and
distribution formats?  That would be a challenge (he said understatedly),
and doesn't intuitively strike me as the place that a TT standard adds
value.

-- Charles Wiltgen
   <http://playbacktime.com/>
Received on Wednesday, 29 January 2003 23:59:28 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 2 November 2009 22:41:25 GMT