Action-4: Consolidated Technical Requirement

Hello team,

I have an open action item to consolidate input contributions of technical use cases to technical requirements. Here you are [1].

Basically, what I did are:

(1)    Categorized them into 11 functional groups according to original input

(2)    Re-worded the requirements with more normalized language, e.g. "SHALL be" instead of "is", wherever appropriate

(3)    Re-worded the requirements to focus on API's v.s. the webapps development instead of app function / user interaction

(4)    A few duplicates from different inputs were consolidated

(5)    A few webapps requirement (e.g. app functions or UI functions) were not captured because those are not directly related to APIs

Regarding (4) above, here are highlighted specifics:

-          "The API is able to let the user scan (or stop scanning) the channels that are available on the air" (Mozilla, Channel) is duplicate and consolidated into "Tuner Channel Scan Requirements" category

-          The ETRI / Program requirements were consolidated into "General Program Requirements"

-          The ETRI / Source requirements were consolidated into "General Channel Requirements"

-          Re "The API is able to let the user retrieve data from the broadcaster's remote servers to provide more program-/content-related information. To do this, we need to define a universal way to identify the program on the web" (Mozilla, Others), essential functional requirements were consolidated into "General Program Requirements", while app functions were not captured.

Regarding to (5) above, here are highlighted specifics:

-          "The API is able to let the user watch multiple programs concurrently on the screen (e.g., Picture-in-Picture)" (Mozilla, Others) seems an application function (UI related), thus it was not captured.

-          "The API is able to let the user navigate through the EPG and directly select a program to watch" (Mozilla, EPG) seems an application function (UI related), thus it was not captured.

-          "The API is able to let the user browse through the list of other programs while (s)he is watching a program" (Mozilla, EPG) seems an application function (UI related), thus it was not captured.

-          The ETRI / Channel requirements seems an application function (UI related), thus it was not captured.

-          Note: If certain API functions are indeed needed for any of above, e.g. events and/or triggers, we can add it.

Let me know if there is any question, and we can discuss it in the mailing list and the conference call next Tuesday.
Thank you

Bin
[1] https://www.w3.org/community/tvapi/wiki/Main_Page/Technical_Requirement