short report of 2010-03-31 teleconference
Media Fragments Working Group: Agenda 31 March, Telecon 0900 UTC
user of media fragments
ACTION-220 to Investigate into the "wttjs" tool to transform WebIDL example into testsuite
Media Fragments Working Group: availability this week?
- Re: Media Fragments Working Group: availability this week?
- RE: Media Fragments Working Group: availability this week?
- CANCEL: Media Fragments Working Group 24 March, Telecon 0900 UTC
ACTION-155: Figures illustrating URI fragment Resolution in HTTP
- Re: ACTION-155: Figures illustrating URI fragment Resolution in HTTP
- Re: ACTION-155: Figures illustrating URI fragment Resolution in HTTP
- Re: ACTION-155: Figures illustrating URI fragment Resolution in HTTP
- Re: ACTION-155: Figures illustrating URI fragment Resolution in HTTP
- Re: ACTION-155: Figures illustrating URI fragment Resolution in HTTP
Update your stylesheet before generating a new HTML version of the spec
ACTION-158: Exhaustive list of Test Cases for the temporal dimension in the Media Fragment URI
- Re: ACTION-158: Exhaustive list of Test Cases for the temporal dimension in the Media Fragment URI
- Re: ACTION-158: Exhaustive list of Test Cases for the temporal dimension in the Media Fragment URI
Media Fragments Working Group: Agenda 17 March, Telecon 1000 UTC
- [ERRATA] Media Fragments Working Group: Agenda 17 March, Telecon *0900 UTC*
- Re: Media Fragments Working Group: Agenda 17 March, Telecon 1000 UTC
- Re: Media Fragments Working Group: Agenda 17 March, Telecon 1000 UTC
- RE: Media Fragments Working Group: Agenda 17 March, Telecon 1000 UTC
- RE: Media Fragments Working Group: Agenda 17 March, Telecon 1000 UTC
Issue of combining multiple dimensions
5th F2F meeting: second day summary
- Re: 5th F2F meeting: second day summary
- Range equivalence (was Re: 5th F2F meeting: second day summary)
Re: Segment production rule
Spec layering: name-value pairs and beyond
5th F2F meeting: first day summary
bandwidth conservation use case, objection to use of Range for non-byte sections
- Re: bandwidth conservation use case, objection to use of Range for non-byte sections
- Re: bandwidth conservation use case, objection to use of Range for non-byte sections
- Re: bandwidth conservation use case, objection to use of Range for non-byte sections
minutes from yesterday and some fixes
- Re: minutes from yesterday and some fixes
Ran into a problem with corrib...
ISSUE-16: Combining axis is probably not going to be done by LC, but we should write somewhere that this is doable
RE: Media Fragment validation service
ACTION-141 done: clarify the role of the UA for rendering a media fragment
Re: Track fragments
ACTION-144 done
W3C TPAC2010 Meeting Schedule: 1-5 November, Lyon, France
5th F2F Meeting Agenda
ACTION-143 done
The problem of having multiple Content-Range headers in HTTP response
- Re: The problem of having multiple Content-Range headers in HTTP response
- Re: The problem of having multiple Content-Range headers in HTTP response
- Re: The problem of having multiple Content-Range headers in HTTP response
- Re: The problem of having multiple Content-Range headers in HTTP response
- Re: The problem of having multiple Content-Range headers in HTTP response
- Re: The problem of having multiple Content-Range headers in HTTP response
- Re: The problem of having multiple Content-Range headers in HTTP response
- Re: The problem of having multiple Content-Range headers in HTTP response
- Re: The problem of having multiple Content-Range headers in HTTP response
- Re: The problem of having multiple Content-Range headers in HTTP response
- Re: The problem of having multiple Content-Range headers in HTTP response
- Re: The problem of having multiple Content-Range headers in HTTP response
- Re: The problem of having multiple Content-Range headers in HTTP response
- Re: The problem of having multiple Content-Range headers in HTTP response
- Re: The problem of having multiple Content-Range headers in HTTP response
- Re: The problem of having multiple Content-Range headers in HTTP response
- Re: The problem of having multiple Content-Range headers in HTTP response
- Re: The problem of having multiple Content-Range headers in HTTP response
- Re: The problem of having multiple Content-Range headers in HTTP response
- Re: The problem of having multiple Content-Range headers in HTTP response
minutes of 2010-03-03 teleconference
ISSUE-15: Which def should we take?
Re: Media Fragments Working Group: Agenda 03 March, Telecon 1000 UTC
Media Fragments Home page updated
Media Fragments Working Group: Agenda 03 March, Telecon 1000 UTC
- Re: Media Fragments Working Group: Agenda 03 March, Telecon 1000 UTC
- RE: Media Fragments Working Group: Agenda 03 March, Telecon 1000 UTC
- Re: Media Fragments Working Group: Agenda 03 March, Telecon 1000 UTC