FifthF2FAgenda

From Media Fragments Working Group Wiki
Revision as of 08:26, 8 March 2010 by Jjansen2 (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Agenda Preparation

  • The main objective of this 5th F2F meeting is to get another document to PUBLISH and be closest as possible to LCWD!

Participants

  • Confirmed: Erik, Davy, Jack, Yves, Raphaël
  • Remotes: Silvia, Michael, Conrad, Philip
  • Observers: Franck
  • Unknown: Guillaume

Remotes Details

  • Zakim:
    • Bridge US: +1-617-761-6200 | FR: +33.4.89.06.34.99 | UK: +44.117.370.6152
    • Conference code: 3724# (spells "FRAG")
    • IRC channel: #mediafrag on irc.w3.org:6665

Monday 2010-03-08, 09:00-18:00

09:00 - 09:30 Administrative: coffee, agenda, etc.
09:30 - 11:00 Yves/Silvia/Conrad/Jack/Philip: Media Fragments syntax
  1. WG decision for expressing wall-clock time code (Yves)
    • Brief description: Two ways for representing wall-clock time code: ISO way followed by HTML5 and RTSP (RFC2326) or RFC3339 (subset of ISO 8601). Which one to re-use and reference ? See also section 4.2.1.3
    • Estimate time of discussion: 10 min
    • Concrete objectives to reach: WG decision
  2. WG decision: having quotes or not for name and id dimensions (Erik)
    • Brief description / URL: see ACTION-150
    • Estimate time of discussion: 20 min
    • Concrete objectives to reach: WG decision
  3. Multiple tracks (Raphael)
    • Brief description / URL: What is the media fragment URI that correspond to a selection of 2 tracks of a media file? What is the HTTP request and HTTP response generated?
    • Estimate time of discussion: 30 min
    • Concrete objectives to reach: get the syntax worked out and done
  4. Multiple but equivalent Content-Range headers (Silvia)
    • Brief description / URL: long thread at http://lists.w3.org/Archives/Public/public-media-fragment/2010Mar/0020.html
      • Multiple header fields with the same field name MUST NOT be sent in a message unless the entire field value for that header field is defined as a comma-separated list (i.e., #(values)). Multiple header fields with the same field name can be combined into one "field-name: field-value" pair, without changing the semantics of the message, by appending each subsequent field value to the combined field value in order, separated by a comma ref.
      • We cannot use several Content-Range headers for different things
    • Estimate time of discussion: 30 min ... but also related to the general objective of defining ABNF syntax for HTTP headers
    • Concrete objectives to reach: decide how media fragments request with server help should be answered
11:00 - 11:30 Refreshment Break
11:30 - 13:00 ALL: Protocol Handling
  1. ABNF syntax for HTTP headers (request and response) ( Yves)
    • Brief description / URL: Discuss and decide the formal syntax for the headers (including the new ones introduced if any)
    • Estimate time of discussion: 1,5 hour max
    • Concrete objectives to reach: bits of syntax included in the spec document
13:00 - 14:00 Lunch
14:00 - 15:30 ALL: Protocol Handling (cont.)
  1. Progress each of the dimensions towards LCWD (Silvia)
    • Brief description: the spatial, track and named dimensions have not been progressed as much as the temporal dimension. The main aim of this meeting should be to progress those as far as possible towards LCWD.
    • Estimate time of discussion: As much as possible, at least 3 hours each.
    • Concrete objectives to reach: development of subsections for these dimensions similar to temporal dimension.
15:30 - 16:00 Refreshment Break
16:00 - 18:00 ALL: Protocol Handling (cont.)
  1. Progress each of the dimensions towards LCWD (Silvia)
    • Brief description: the spatial, track and named dimensions have not been progressed as much as the temporal dimension. The main aim of this meeting should be to progress those as far as possible towards LCWD.
    • Estimate time of discussion: As much as possible, at least 3 hours each.
    • Concrete objectives to reach: development of subsections for these dimensions similar to temporal dimension.

Tuesday 2010-03-09, 09:00-15:30

09:00 - 09:30 Administrative: coffee, agenda, etc.
09:30 - 11:00 Michael: Test Cases
  1. Review all Test Cases entered into Corrib (Michael)
    • Brief description / URL: Go through and review all test cases, Behavior for over-specified dimension: error or not?
    • Estimate time of discussion: 1,5 hours max
    • Concrete objectives to reach: TC are marked up as validated and data is updated into corrib
11:00 - 11:30 Refreshment Break
11:30 - 13:00 Davy: Implementation Reports
  1. Rendering Media Fragments in UA (Davy)
    • Brief description / URL: How to render media fragments in UA? See also ACTION-135
    • Estimate time of discussion: 45 min max (including demo)
    • Concrete objectives to reach: identify implementation difficulties, provide input for spatial and track fragment discussion
  2. Other implementations in the pipeline (ALL)
    • Estimate time of discussion: 45 min max
    • Concrete objectives to reach: planning for upcoming experiments and implementations
13:00 - 14:00 Lunch
14:00 - 15:30 Raphael: Actions/Issues Discussion/Wrap up
  1. Review all actions and issues and discuss / close as appropriate
    • Estimate time of discussion: 1,5 hours max
    • Concrete objectives to reach: concrete common view of what is left to be discussed
  2. Should we split the spec document (Raphael)
    • Brief description: the temporal dimension starts to be very stable and could soon be push forward to the rec track. We should discuss whether dealing with all the other dimensions into the same document does or does not slow down the process given the pressure to get some documents out quickly!
    • Estimate time of discussion: 1/2 hour max
    • Concrete objectives to reach: take a formal resolution, hopefully by consensus.
  3. Go through the spec document and mark up the stable sections (Raphael)
    • Brief description: Go through the Sections 4 and 5 of the spec draft and mark whether they are stable or not for web developers
    • Estimate time: 1/2 hour max
    • Concrete objective: a new colored document containing the stable sections marked up

Venue Details

Hotel

IBIS Cathedral Hotel (on Google Maps)

  • Limburgstraat 2, 9000 Ghent
  • price per night: +/- 90 € (single room)
  • Reservations can be made online

Meeting venue

IBBT (on Google Maps)

  • Gaston Crommenlaan 8, 9050 Ghent-Ledeberg, bus 102
  • Floor 1 (lefthandside of elevator, meeting room BeBox)

How to get to ... Ghent from Brussels Airport

The closest airport to Ghent is Zaventem National Airport.

  • The easiest way getting to Ghent is by taxi (+32 9 222 22 22): prices for transport between Ghent and Zavemtem National Airport vary from 90€ (standard car, up to 4 people) to 110€ (minibus, up tot 8 people), ordering during office hour is recommended.
  • The cheapest way getting to Ghent is by railway from Zaventem National Airport to Gent Sint-Pieters. Railway Company Info: time tables and other information can be found when entering from ‘BRUXELLES NAT AIRPORT’ to ‘GENT SINT PIETERS’. The ride takes approximately 1 hour, "one way" costs about 10€ and there are trains almost every 10 minutes.

How to get to ... Ghent from Amsterdam Airport

The cheapest way getting to Ghent from Holland is by railway from Schiphol Airport to Gent Sint-Pieters. Railway Company Info: time tables and other information can be found when entering from ‘SCHIPHOL AIRPORT’ to ‘GENT SINT PIETERS’ using the 'international' option. The ride takes approximately 3 hours, "one way" costs about 40€ and the latest train arriving the same day departs around 20:00.

How to get to ... IBIS Hotel

With public transportation from railway station Gent Sint-Pieters to IBIS Cathedral hotel: by taxi (+32 9 222 22 22) or by trolley (number 4 to stop Belfort or to stop Korenmarkt, followed by a 0.4 km walk to the hotel)

(Google Maps: From Train station to Hotel)

How to get to ... IBBT

The meeting will be held in the IBBT-headquarters at Gaston Crommenlaan 8, bus 102 at Ghent-Ledeberg. Again trolley line 4 is the most suitable: drive till stop Ledeberg, Hundelgemsesteemweg, Jacques Eggermontstraat. You are now in walking distance from IBBT.

(Google Maps: From Hotel to IBBT)

Social event

'Surprise' on Monday Evening :)