- From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
- Date: Wed, 10 Feb 2010 20:52:20 +1100
- To: erik mannens <erik.mannens@ugent.be>
- Cc: public-media-fragment@w3.org
Looking good to me, but then, you painted exactly my examples. :-) Can somebody confirm that it would be the same with MPEG files? Then there is the point that Conrad made that a client may need an auxiliary file to resolve the actual resource and byte ranges to request. I am not even sure we need to mention that, since the specifications for retrieving byte ranges on such resources exist elsewhere, and thus could be applied by logical deduction. Also, neither Apple's scheme nor Microsoft's scheme are "open standards", though Apple is trying to publish its spec as a RFC through IETF, but with "no derivative works" attached and further restrictive rights. So, I'm not sure how much we really want to address such formats. I guess, I am keen to explain the main use case and maybe mention further use cases, but not go into too much detail there. Cheers, Silvia. On Wed, Feb 10, 2010 at 7:45 PM, erik mannens <erik.mannens@ugent.be> wrote: > Dear all, > > > > > > On the wiki [1] I welcome comments on the draft time-sequence diagrams. When > uploading a new version, I will scale the images more appropriate. For now, > this should do. > > > > [1]: > http://www.w3.org/2008/WebVideo/Fragments/wiki/Protocol_Time-Sequence_Diagrams > > > > > > Sincere greetings, > > > > Erik Mannens > > > > Project Manager > > > > Gaston Crommenlaan 8 bus 201 > > B-9050 Ledeberg-Ghent, Belgium > > > > T: +32 9 331 49 93 > > F: +32 9 331 48 96 > > M: +32 473 27 44 17 > > E: erik.mannens@ugent.be > > W: http://www.mmlab.be/emannens > > > > > > http://multimedialab.elis.ugent.be > >
Received on Wednesday, 10 February 2010 09:53:13 UTC