Re: [apis] ACTION-128 Drafting Use-Case/Requirements Cross-Reference Table

Hi JC,
My AI from the July 24 meeting was to create this table that essentially is another way to looking at the current Requirements<http://www.w3.org/2011/webtv/wiki/Media_APIs/Requirements> document, including the derivation of requirements from the current list of Use Cases<http://www.w3.org/2011/webtv/wiki/Media_APIs/Use_Cases>. Detail descriptions of all the Use Cases are to be found in the group's Use Cases<http://www.w3.org/2011/webtv/wiki/Media_APIs/Use_Cases> site.
All of the "X's were directly copied from the "Derived From" sub-sections for the corresponding Requirement headings. The only exceptions are those marked "X?" and colored red, which are the ones I thought might deserve further discussions in this group.

I believe you have identified additional ones, including some that were apparently discussed and concluded from prior meetings.

Just to be clear, "X" means, according to my understanding of the current Requirement document, that the particular requirement is derived from the corresponding use cases.

My motivation for putting the requirement vs UC in this cross-reference table is to precisely allow us to have a larger view of the UC and the requirements so that issues such as the ones raised in your email can now be discussed in the group.

----
Sheau Ng | NBCUniversal | P: +1.609.759.0819


From: JC Verdié <jc.verdie@mstarsemi.com<mailto:jc.verdie@mstarsemi.com>>
Date: Friday, July 26, 2013 5:04 AM
To: Sheau Ng <sheau.ng@nbcuni.com<mailto:sheau.ng@nbcuni.com>>
Cc: "public-web-and-tv@w3.org<mailto:public-web-and-tv@w3.org>" <public-web-and-tv@w3.org<mailto:public-web-and-tv@w3.org>>
Subject: Re: [apis] ACTION-128 Drafting Use-Case/Requirements Cross-Reference Table

Hi Sheau,

Let's play battleship :)

7-G : 1.5 Device Authentication mechanism  / UC 6 : Tuner control thru web app
IMHO it's X! more than X? It's a tricky point: the device controlling the tuner absolutely needs to be authenticated and granted access, but it's not enough. Even if a device is generally allowed to perform this action it doesn't mean it can do it at this specific time. A good example is when another allowed device is currently connected and interacting with the main screen.

Which lead to many derivative questions:
- how can we consider a 2nd device is "currently interacting"? e.g. if i change channel, or modify volume. How long before my device is not considered as "locking the main screen"?
- is it, anyway, a good idea to consider this "locking"? but if not, what about two devices interacting at the same time. it can happen with a device in another room, and user unknowingly interacting with the main screen..
- do we want to address this now? Do we want to address this at all?


22-E : 1.20 content protection / UC4:  Content Sharing

I would vote "X"

22-F : 1.20 / UC5: Content Search

I would vote "not X": it's a good idea to let people discover content, even if it means they will need to acquire certain rights to view it. I'm confident movie studios would agree with this ;)

22-H : 1.20 / UC7: Channel Bounded Applications

Not sure what you mean? Is your question "If an app is bounded to a channel, viewing this app implicitely means you have access to the channel" ? If I understood your question correctly, my answer would be "it depends"
- content provider might want to provide protected apps because they're strongly related to the protected content and providing them for free reduces the perceived value of the content
- content provider might also want to provide unprotected apps to tease non-subscribers. These apps would be considered as generic trailers, or informative apps about the protected channel ("what are your benefits if you subscribe", or any other stuff content providers' imagination can birth.
- they might even want to provide both apps: if a user is subscribed, give him app X, if he isn't, give him app Y.

Regards,
JC

Ng, Sheau (NBCUniversal) wrote:
Per my action item ACTION-128 to draft a use-case/requirements
cross-reference table on Google Doc:

https://docs.google.com/spreadsheet/ccc?key=0Ancbh-cL3L9YdE81MFpFVWxsY1dyUmhZMmZIdzZxVnc&usp=sharing
<https://docs.google.com/spreadsheet/ccc?key=0Ancbh-cL3L9YdE81MFpFVWxsY1dyUmhZMmZIdzZxVnc&usp=sharing>


I have included a few "X?" in red to indicate my questions regarding
possible requirements that pertain to some use cases.

Thanks!


----
Sheau Ng | NBCUniversal | P: +1.609.759.0819