Extension to application/oipfRecordingScheduler for control of recordings
The OITF SHALL support the following extensions to the application/oipfRecordingScheduler object defined in section 7.10.1.
This subsection SHALL apply for OITFs that have indicated support for the extended PVR management functionality by adding the attribute ‘manageRecordings = true’ to the <recording> element in the client capability description as defined in section 9.3.3.
The functionality as described in this section is subject to the security model of section 10.
|readonly ScheduledRecordingCollection recordings
|Provides a list of scheduled and recorded programmes in the system. This property may only provide access to a subset of the full list of recordings, as determined by the value of the manageRecordings attribute of the <recording> element in the client capability description (see section 9.3.3).
|readonly DiscInfo discInfo
|Get information about the status of the local storage device. The DiscInfo class is defined in section 7.16.4.
function onPVREvent( Integer state, ScheduledRecording recording )
This function is the DOM 0 event handler for notification of changes in the state of recordings. The specified function is called with the following arguments:
· Integer state – The current state of the recording. One of:
· ScheduledRecording recording – The recording to which this event refers.
void stop( Recording recording )
Stop an in-progress recording. The recording SHALL NOT be deleted.
The recording to be stopped.
Update the recordings property to show the current status of all recordings.
For the intrinsic events listed in the table below, a corresponding DOM event SHALL be generated in the following manner:
|Corresponding DOM event
|DOM Event properties
|Bubbles: No Cancellable: No Context Info: state, recording
Note: the DOM events are directly dispatched to the event target, and will not bubble nor capture. Remote UIs SHOULD NOT rely on receiving these events during the bubbling or the capturing phase. Remote UIs that use DOM event handlers SHALL call the addEventListener() method on the application/oipfScheduledRecording object itself. The third parameter of addEventListener, i.e. “useCapture”, will be ignored.