W3C home > Mailing lists > Public > public-web-and-tv@w3.org > September 2011

webtv-ISSUE-54 (HNTF_Report_Issues_2): Missing use-case for ISSUE-23 (Action-61) [HOME_NETWORK_TF]

From: Web and TV Interest Group Issue Tracker <sysbot+tracker@w3.org>
Date: Mon, 19 Sep 2011 00:16:58 +0000
To: public-web-and-tv@w3.org
Message-Id: <E1R5RXe-0001km-Rc@barney.w3.org>

webtv-ISSUE-54 (HNTF_Report_Issues_2): Missing use-case for ISSUE-23 (Action-61) [HOME_NETWORK_TF]

http://www.w3.org/2011/webtv/track/issues/54

Raised by: Russell Berkoff
On product: HOME_NETWORK_TF

Action-61 incomplete since use case text is missing from report:

Suggested use-case text follows:

--------------------------------
	[edit] U15-0. UPnP / DLNA ecosystem support 
Original Proposal: ISSUE-23 
Description: 
·	Use Cases U15, U16, U16, U18, and U1 describe functionality implemented by existing UPnP/DLNA home network devices in general terms. However, there is an existing install base of UPnP/DLNA compliant devices and the associated SDOs (UPnP Forum, DLNA) continue actively develop additional device related specifications. 
It would be beneficial to the end-user community if W3C User-Agents provided access to UPnP/DLNA devices without requiring any modification to the existing install base of UPnP/DLNA compliant devices.
Scenarios 
·	W3C user agents support applications which can discover UPnP/DLNA compliant devices.
·	W3C user agents support applications retrieving UPnP Device and Service Description XML documents.
·	W3C user agents support application issuing of SOAP actions to control UPnP/DLNA devices.
·	W3C user agents support applications subscribing to UPnP Service Events.
·	W3C user agents support applications inspection of UPnP Service State Variables.
·	W3C user agents support applications including DLNA specified HTTP transport headers to obtain DLNA content metadata and to control playback features (such as trick-play, time-based positioning).
A summary of UPnP specifications relevant to this use case is provided in the “UPnP Reference” #xxxxx section.
-----------------------------
Received on Monday, 19 September 2011 00:17:00 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 19 September 2011 00:17:00 GMT