- From: Giuseppe Pascale <giuseppep@opera.com>
- Date: Mon, 01 Aug 2011 18:28:09 +0200
- To: public-web-and-tv@w3.org, "Russell Berkoff" <r.berkoff@sisa.samsung.com>
- Message-ID: <op.vzjmo7jz6ugkrk@laptop>
Hi Russell, thanks for the putting some effort in producing this summary and the list of requirements! All, I also finally found the time to do some clean up and I updated the wiki with approved/rejected use cases http://www.w3.org/2011/webtv/wiki/HNTF/Home_Network_TF_Discussions and I also updated tracker so that all accepted/rejected usecases are marked as such. http://www.w3.org/2011/webtv/track/products/2/all Unfortunately tracker do not allow to distinguish between CLOSED as in rejected and CLOSED as in approved. So I had to add a resolution comments in the ticket it self (I'm still doing it so some are not updated yet). Other options could be 1) remove the issue from the HNTF product 2) create a new product for rejected issues 3) use one of the states we are not using like POSTPONED. None of them is ideal but it could be a workaround. Unless is possible to add another state like ACCEPTED (Kaz, Francois?). What do people think we should do? We can also ignore the issue since we only have a month left; other TFs may look into this though (Clarke?). Going back to the issues status, there are some differences with Russell document: - I think issue 4, 7 and 10 are accepted. I understand there are possible overlaps and at the end we may decide to merge some use cases, anyway I would leave this as editorial work to be done (soon) while working on the final report. - issue 19 and 24 were approved during last call I also plan to start merging approved Usecases into the requirement document. For the time being I'll merge them as is, but after all the use cases are approved/rejected we may want to modify the requirement document to be consistent and readable. About the requirements: Russell did a great work starting to extract them. So I would like to ask each person with one (or more) approved use cases to add to his own proposal the list or requirements he thinks the use case imply. Of course you can start from Russell suggestion and modify/add/remove. You can add the list at the end of each use case, as a new section "requirements", like in this template http://www.w3.org/2011/webtv/wiki/HNTF/Home_Network_TF_Requirements#UX._.3CTITLE.3E cheers, /g On Tue, 26 Jul 2011 09:50:33 +0200, Russell Berkoff <r.berkoff@sisa.samsung.com> wrote: > > Hello, > > Please find below a summary of HNTF current issues. I extracted a set > of proposed HNTF requirements from the submitted use-cases. > > Regards, > > Russell Berkoff > > Samsung Electronics > 1.1. Submitted Use-Cases > 1.1.1. ISSUE Status Color Codes> >Use-Case closed/merged - (See > References) > >Use-Case accepted > >Use-Case under consideration >1.1.2. ISSUE Summary > > >> ISSUE >Number >> HNTF > > Status >> References >> ISSUE Title >> ISSUE-2 >> CLOSED >> See >ISSUES-4,5,6,7,8 >> Document-level Use Cases >> ISSUE-3 >> OPEN >> >> Security concerns around Home >Networking APIs >> ISSUE-4 >> CLOSED >> See ISSUE-26 >> Use Case: Service User Interface >> ISSUE-5 >> ACCEPTED >> >> Use Case: Discovered Content Host >> ISSUE-6 >> CLOSED >> See ISSUES-13, >14 >> Use Case: Document as a Service Provider >> ISSUE-7 >> CLOSED >> See ISSUE-15 >> Use case: Service Migration >> ISSUE-8 >> ACCEPTED >> >> Use case: Service Distribution >> ISSUE-9 >> OPEN >> >> Implementation Alternatives >> ISSUE-10 >> OPEN? >> See ISSUE-28 >> 3-Box Model >> ISSUE-11 >> OPEN >> >> Requirements Document and other >deliverables >> ISSUE-12 >> ACCEPTED >> See ISSUES-13,14 >> Document Exposing a Service >> ISSUE-13 >> CLOSED >> >> Document Responding to Requests >> ISSUE-14 >> ACCEPTED >> >> Document Discovering a Service >> ISSUE-15 >> ACCEPTED >> See ISSUE-25 >> Document Migration >> ISSUE-16 >> OPEN >> See ISSUE-24 >Web and Device Interworking >> ISSUE-17 >> CLOSED? >> See ISSUES-23, >26, 27, 28, 29, 30 >> Use Case: Home Network Enabled User->Agent >> ISSUE-18 >> OPEN >> Moved to MPTF? >> Video tag support of MPEG2-TS >> ISSUE-19 >> OPEN >> >> Media Identification >> ISSUE-20 >> OPEN >> >> TV Querying and Control >> ISSUE-21 >> OPEN >> >> Time synchronisation >> ISSUE-22 >> OPEN >> >> Lip-sync Accuracy Time Synchronisation >> ISSUE-23 >> OPEN >> >> UPnP/DLNA ecosystem support >> ISSUE-24 >> OPEN >> >> Local Link of web applications >> ISSUE-25 >> ACCEPTED >> >> Application Pull-Migration >> ISSUE-26 >> OPEN >> >> Home Network Enabled User Agent - >Network Media Player >> ISSUE-27 >> OPEN >> >> Home Network Enabled User Agent - >Network Media Server >> ISSUE-28 >> OPEN >> >> Home Network Enabled User-Agent - >Network Media Controller >> ISSUE-29 >> OPEN >> >> Home Network Enabled User-Agent - >Network Record Controller >> ISSUE-30 >> OPEN >> >> Home Network Enabled User-Agent - >Network Device Controller >> >> >> >> > > > >> > 1.2. Derived Requirements > > >> Ecosystem >> ISSUE > > Number >> Requirement >> ALL >> ISSUE-3 >> Allow Home Network Access to only trusted >applications >> ALL >> ISSUE-3 >> Support security mechanisms (such as password, PIN, >etc) >> ALL >> ISSUE-3 >> Enforce privacy controls. Prevent unauthorized transfer >of information >> outside of the home-network. >> DLNA >> ISSUE-5 >> Support display and playback of content from DLNA >Media Servers. >> GENERIC >> ISSUE-8 >> User-Agent supports an application which can create a >service which is >> exposed on the Home Network. >> GENERIC >> ISSUE-8 >> User-Agent supports an application which can discover >created >> services by User-Agents supporting the >previous requirement. >> GENERIC >> ISSUE-9 >> User-Agents provide a generic discovery mechanism >which can be used to >> discover ecosystem specific and >ad-hoc home-network protocols. >> ALL >> ISSUE-11 >> HNTF participant agreement on TF report format >> GENERIC >> ISSUE-12 >> User-Agent supports an application which can create a >service which >> is exposed on the Home Network. > > (See ISSUE-8). >> GENERIC >> ISSUE-14 >> User-Agents provide a generic discovery mechanism >which can be used to >> discover ecosystem specific and >ad-hoc home-network protocols. > > (See ISSUE-9) >> GENERIC >> ISSUE-15 >> User-Agent supports an application request to do a >peer-to-peer >> transfer to different User-Agent without >requiring support of an >> application server. >> GENERIC >> ISSUE-16 >> User-Agent supports an application which can discover >and command >> devices to redirect displayed video >content to a home-network device. >> GENERIC > > >> ISSUE-19 >> User-Agent supports an application which can provide >a URL to which >> provides additional information for a >companion device to display. >> GENERIC(?) > > UC > > UPnP >> ISSUE-19 >> A home-network device can provide additional >information (metadata) >> concerning content currently >being played. >> GENERIC(?) > > UC > > UPnP >> ISSUE-19 >> User-Agent supports an application which can >determine if content is >> suitable to be played on a home->network device >> UC > > UPnP >> ISSUE-20 >> User-Agent supports an application which can control a >home-network >> device receiving broadcast content. >> GENERIC(?) > > UC(?) > > UPnP >> ISSUE-21 >> User-Agent supports an application which can control a >companion >> device to present content related to what is >currently being displayed >> on a home-network device. >> GENERIC(?) > > UPnP >> ISSUE-22 >> A companion device can play an audio track which is >precisely >> synchronized with content being rendered on >the video device. >> UPnP >> ISSUE-23 >> User-Agent supports application access to home->network devices >> equivalent to native UPnP/DLNA >Control Points. >> GENERIC >> ISSUE-24 >> User-Agents support discovery and use of ad-hoc >communications between >> web applications running on >separate User-Agents. >> GENERIC > > CEA-2014 > > >> ISSUE-25 >> User-Agent supports transfer of an application >between devices without >> requiring an application >server. The request is initiated by the >> target User->Agent (destination) for the application. >> GENERIC > > UPnP >> ISSUE-26 >> User-Agent supports an application which can discover >home-network >> devices capable of serving content. >> GENERIC > > UPnP >> ISSUE-26 >> User-Agent supports an application which can list >content available >> on a home-network device, >> GENERIC > > UPnP >> ISSUE-26 >> User-Agent supports an application which can list EPG >data provided by >> a home-network device >> GENERIC > > UPnP >> ISSUE-26 >> User-Agent supports an application which can play >content stored on a >> home-network device. >> GENERIC > > UPnP >> ISSUE-26 >> User-Agent supports an application which can play live >content from a >> home-network device. >> GENERIC > > UPnP >> ISSUE-27 >> User-Agent supports an application which can cause >the User-Agent to >> become a discoverable Media Server >on the home-network. >> GENERIC > > UPnP >> ISSUE-27 >> User-Agent supports an application which can service >requests to >> describe and possibly serve content on the >home network. >> GENERIC > > UPnP >> ISSUE-28 >> User-Agent supports an application which can >command home-network >> Media Rendering devices to >play content from home-network Media >> Servers. >> GENERIC > > UPnP >> ISSUE-28 >> User-Agent supports an application which can control >presentation on >> home-network Media Rendering >devices such as alternate audio track >> selection, Picture->in-Picture, Closed Captioning, brightness, volume, >> etc. >> GENERIC > > UPnP >> ISSUE-29 >> User-Agent supports an application which can control a >home-network >> recording device. Network content to be >recorded shall be selectable >> by various means >including time-of-day, EPG keywords. >> GENERIC > > UPnP >> ISSUE-30 >> User-Agent supports an application which can control >generic >> home-network device whose function may not >be fully standardized. This >> may include new web >applications such as E-Health, Remote Provisioning >> and >Home Energy Management. >> >> >> > > > > -- Giuseppe Pascale TV & Connected Devices Opera Software - Sweden
Received on Monday, 1 August 2011 16:28:55 UTC