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: Thu, 30 Jan 2003 08:39:05 -0800
To: W3C TT Public <public-tt@w3.org>
Message-ID: <BA5E9529.5D1AC%lists@wiltgen.net>

Glenn A. Adams wrote...

>> 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 think you must mean RTP, not RTSP, correct? Since RTSP is just a
> command/control protocol.

Yes, finger slip.   :^)   My point was that the importance of EventStream
was that content developers could author once and deploy any which way, and
So it wasn't necessary to dictate how EventStream text should be streamed.
(Thank goodness!)

> Of course we can't define all possible distribution formats; however, our
> charter does explicitly charge us to "develop an XML based format used for the
> representation of streamable text synchronized with some other timed media".
> So we need to address this at some level.

So if I'm understanding you correctly, the charter (1) requires that TT be
streamable, but (2) doesn't require that this group dictate how to stream
TT.  If so, excellent!

-- Charles Wiltgen
Received on Thursday, 30 January 2003 11:39:14 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 5 October 2017 18:23:58 UTC