Re: [apis] Cross-review of HNReq document and current list of use cases

Thank you for your comments.
We have our reply inline.

2013. 7. 5., 오전 1:23, Olivier Thereaux <<>> 작성:

** From Media APIs/Use Cases
  ( )

6. "Use Case Six – Tuner Control thru EPG Application"

This looks very similar to "Use Case Three – Tablet EPG". I would encourage the Use Case authors to detail how the use cases differ.

The use case 6 of Media API is focus in enabling the Web application to directly control the TV tuner with the information from the EPG data.
The use case 15 of HNReq is about an interface between the home network media player and terminal device that use the EPG data to view the live streaming contents.
This content is delivered through the home network. The HNReq does not cover control of broadcast streams from digital cable.
In the Use case 6 of Media API, the web application can provide description of the programs that are provided by digital broadcasting service provider and helps the user to search and select the channel to watch through the control of the TV tuner.
It will be useful for the web application to use the URI in expressing the channel/program. The IETF RFC 2838 (“Uniform Resource Identifiers for Television Broadcasts”) defines TV URI, however, it does not include local tuner identifier. We need to identify the form of URI for local tuner identifier (Channel ID).
Thus, this use case is not limited to the use of EPG for controlling TV tuner. However, we think that controlling the TV tuner with the use of EPG data would be much simpler to convey the needed information such as local tuner identifier.
The web application will need to express the channel ID in form of URI to control the TV tuner. Also, the broadcast media stream from the tuner can be embedded into a video tag in the web-application.
To avoid further confusion, I think we will change the title and texts to the use case six indicating the relation with the TV broadcast service.

7. "Use Case Seven – Channel Bounded Applications"

This use case shares some similarities with the following HNReq use case:
 - U12. Time Synchronization

However, there seem to be some unique characteristics to this use case which I do not find in HNReq, such as the switching of applications on the "slave" device based on channel change in the "master" device. This could be an additional requirement worth exploring.

U12 of HNReq (Time synchronization) is about using secondary device such as Laptop, tablet, media rendering device while watching TV. It uses the playback time index to interwork between timeline of a program being played on a TV or other home media rendering device.

The Use Case 7 of Media API (Channel Bounded Applications) describes the use case of execution and termination of channel bounded application which can show TV broadcasting contents and related contents(supplementary contents) in a single platform with a tuner (i.e., STB). Although it is possible to show the related contents in a different screen as in U12 of HNReq, however, this use case does not cover how the web application operates, such as method of time synchronization between the two content devices.
The Use Case 7 of Media API does not use the concept of master/slave. The TV broadcasting contents and web application act together as a group which can be shown in a single device..
Even through current use case contains some features relating to time synchronization; it is more focused on describing concept of channel bounded application. Is there any suggestion or comments on modifying the Use case 7 to show the readers of this intension?

** From Media APIs/Terminal Use Cases
  ( )

7. TV Applications

This use case looks like a collection of use cases. I would encourage its authors to split it into more atomic use cases which we could then analyse for gaps.


We have made the text for “7. TV Applications”. We will see if we can make any use case for media API on this topic, next time.



Received on Tuesday, 9 July 2013 09:40:36 UTC