Wednesday, 31 March 2010
- Re: ACTION-158: Exhaustive list of Test Cases for the temporal dimension in the Media Fragment URI
- Re: Media Fragments Working Group: Agenda 31 March, Telecon 0900 UTC
- Re: short report of 2010-03-31 teleconference
- Re: ACTION-158: Exhaustive list of Test Cases for the temporal dimension in the Media Fragment URI
- short report of 2010-03-31 teleconference
- 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
- Re: Media Fragments Working Group: Agenda 31 March, Telecon 0900 UTC
- Media Fragments Working Group: Agenda 31 March, Telecon 0900 UTC
Tuesday, 30 March 2010
Monday, 29 March 2010
- Re: ACTION-220 to Investigate into the "wttjs" tool to transform WebIDL example into testsuite
- Re: ACTION-220 to Investigate into the "wttjs" tool to transform WebIDL example into testsuite
- ACTION-220 to Investigate into the "wttjs" tool to transform WebIDL example into testsuite
Thursday, 25 March 2010
- Re: CANCEL: Media Fragments Working Group 24 March, Telecon 0900 UTC
- Re: publication of Media Fragments URI 1.0 as a WD
- Re: publication of Media Fragments URI 1.0 as a WD
- publication of Media Fragments URI 1.0 as a WD
- Re: ACTION-155: Figures illustrating URI fragment Resolution in HTTP
- RE: ACTION-155: Figures illustrating URI fragment Resolution in HTTP
Wednesday, 24 March 2010
- Re: CANCEL: Media Fragments Working Group 24 March, Telecon 0900 UTC
- Re: ACTION-155: Figures illustrating URI fragment Resolution in HTTP
- Re: ACTION-155: Figures illustrating URI fragment Resolution in HTTP
- Re: CANCEL: Media Fragments Working Group 24 March, Telecon 0900 UTC
- RE: ACTION-155: Figures illustrating URI fragment Resolution in HTTP
- Re: CANCEL: Media Fragments Working Group 24 March, Telecon 0900 UTC
Tuesday, 23 March 2010
- Re: ACTION-155: Figures illustrating URI fragment Resolution in HTTP
- CANCEL: Media Fragments Working Group 24 March, Telecon 0900 UTC
- RE: ACTION-155: Figures illustrating URI fragment Resolution in HTTP
- RE: Media Fragments Working Group: availability this week?
- Re: Media Fragments Working Group: availability this week?
- Media Fragments Working Group: availability this week?
Monday, 22 March 2010
- Re: ACTION-155: Figures illustrating URI fragment Resolution in HTTP
- ACTION-155: Figures illustrating URI fragment Resolution in HTTP
Friday, 19 March 2010
- Re: Update your stylesheet before generating a new HTML version of the spec
- Update your stylesheet before generating a new HTML version of the spec
Wednesday, 17 March 2010
- 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
- Re: Media Fragments Working Group: Agenda 17 March, Telecon 1000 UTC
- ACTION-158: Exhaustive list of Test Cases for the temporal dimension in the Media Fragment URI
- CANCEL: Media Fragments Working Group: Agenda 17 March, Telecon 1000 UTC
Tuesday, 16 March 2010
- Re: Media Fragments Working Group: Agenda 17 March, Telecon 1000 UTC
- Re: Range equivalence (was Re: 5th F2F meeting: second day summary)
- RE: Media Fragments Working Group: Agenda 17 March, Telecon 1000 UTC
- Re: Range equivalence (was Re: 5th F2F meeting: second day summary)
- Re: Media Fragments Working Group: Agenda 17 March, Telecon 1000 UTC
- RE: Media Fragments Working Group: Agenda 17 March, Telecon 1000 UTC
- Re: [ERRATA] Media Fragments Working Group: Agenda 17 March, Telecon *0900 UTC*
- Range equivalence (was Re: 5th F2F meeting: second day summary)
- Re: Media Fragments Working Group: Agenda 17 March, Telecon 1000 UTC
- Re: [ERRATA] Media Fragments Working Group: Agenda 17 March, Telecon *0900 UTC*
- Re: Media Fragments Working Group: Agenda 17 March, Telecon 1000 UTC
- [ERRATA] Media Fragments Working Group: Agenda 17 March, Telecon *0900 UTC*
- Media Fragments Working Group: Agenda 17 March, Telecon 1000 UTC
Wednesday, 10 March 2010
- Re: 5th F2F meeting: second day summary
- Re: 5th F2F meeting: second day summary
- Re: Spec layering: name-value pairs and beyond
- Re: Segment production rule
- Issue of combining multiple dimensions
Tuesday, 9 March 2010
- Re: 5th F2F meeting: second day summary
- Re: Spec layering: name-value pairs and beyond
- Re: Media Fragment validation service
- Re: Spec layering: name-value pairs and beyond
- Re: Spec layering: name-value pairs and beyond
- 5th F2F meeting: second day summary
- Re: Segment production rule
- Re: Spec layering: name-value pairs and beyond
- Re: Segment production rule
- Re: Segment production rule
- Re: Spec layering: name-value pairs and beyond
- 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: Ran into a problem with corrib...
- 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
- Spec layering: name-value pairs and beyond
- Re: minutes from yesterday and some fixes
- Re: minutes from yesterday and some fixes
- Re: minutes from yesterday and some fixes
- Re: minutes from yesterday and some fixes
- Re: minutes from yesterday and some fixes
- Re: minutes from yesterday and some fixes
- Re: minutes from yesterday and some fixes
- 5th F2F meeting: first day summary
- Re: minutes from yesterday and some fixes
- Re: Media Fragment validation service
- Re: Objection to use of Range for non-byte sections (from Conrad)
- Re: minutes from yesterday and some fixes
- Re: Media Fragment validation service
- Re: minutes from yesterday and some fixes
- Objection to use of Range for non-byte sections (from Conrad)
- Re: minutes from yesterday and some fixes
- Re: bandwidth conservation use case, objection to use of Range for non-byte sections
- Re: minutes from yesterday and some fixes
- Re: bandwidth conservation use case, objection to use of Range for non-byte sections
- Re: minutes from yesterday and some fixes
Monday, 8 March 2010
- bandwidth conservation use case, objection to use of Range for non-byte sections
- 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
- Re: Track fragments
- ACTION-144 done
Sunday, 7 March 2010
- Re: W3C TPAC2010 Meeting Schedule: 1-5 November, Lyon, France
- W3C TPAC2010 Meeting Schedule: 1-5 November, Lyon, France
- 5th F2F Meeting Agenda
- ACTION-143 done
Saturday, 6 March 2010
Friday, 5 March 2010
- 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
Thursday, 4 March 2010
- 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: Percent encoding
- Re: The problem of having multiple Content-Range headers in HTTP response
- Re: Percent encoding
- 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
Wednesday, 3 March 2010
- Re: Percent encoding
- Re: The problem of having multiple Content-Range headers in HTTP response
- 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
- 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
- RE: Media Fragments Working Group: Agenda 03 March, Telecon 1000 UTC
- Re: Formatting of the minutes
Tuesday, 2 March 2010
- Re: Percent encoding
- Re: Percent encoding
- Media Fragments Home page updated
- Re: Percent encoding
- Re: Percent encoding
- Re: Media Fragments Working Group: Agenda 03 March, Telecon 1000 UTC
- Re: Formatting of the minutes
- Re: Percent encoding
- Media Fragments Working Group: Agenda 03 March, Telecon 1000 UTC
- Re: Percent encoding
- Re: Formatting of the minutes