tvapi-ACTION-23: recording.series requirement discussion

Hello,

During the February 17 TV Control API conference call, I took an action [1] of starting a clarifying discussion about the recording.series requirement [2]. It is closely related to ACTION-24 [3] which does a comparison of recording.* requirements to that of the MediaStream Recording API draft [4].

The requirement reads as follows:
[recording.series] The API SHALL be able to enable the webapps to record series-linked programs.

This refers to the capability of creating an automated schedule for recording all episodes of a series.

There is at least two minor points to this requirement:


a)      Being able to figure out which episodes belong to a series. This is covered by the EPG requirements.

b)      Paul Higgs raised his concern that the API is required to have some kind of background process on a platform or system level that would be able to start a recording automatically when an episode of a series is airing.

The requirement was originally added by Chris Needham. Chris' motivation was reaching feature parity with OIPF Spec Vol5 DAE [5]. The main question is whether we accept if the series recording can be handled on an application level, e.g. while the application is running it should be able to record a series by managing the schedule itself.

Should the group decide that the MediaStream Recoding API is sufficient (see ACTION-24) then the discussion of this requirement should continue in the Device API WG [6] and Web Real-Time Communications WG [7].

Please chime in with any opinions you have on this topic.

Thanks and best regards
Alex


[1] http://www.w3.org/community/tvapi/track/actions/23
[2] https://www.w3.org/community/tvapi/wiki/Main_Page/Technical_Requirement#Program_Recording_Requirements
[3] http://www.w3.org/community/tvapi/track/actions/24
[4] http://www.w3.org/TR/mediastream-recording/
[5] http://www.oipf.tv/specifications/
[6] http://www.w3.org/2009/dap/
[7] http://www.w3.org/2011/04/webrtc/