- From: Igarashi, Tatsuya <Tatsuya.Igarashi@jp.sony.com>
- Date: Tue, 14 Jun 2011 19:53:17 +0900
- To: Giuseppe Pascale <giuseppep@opera.com>, "public-web-and-tv@w3.org" <public-web-and-tv@w3.org>, Jan Lindquist <jan.lindquist@ericsson.com>
Hi Jan and Giuseppe, As I understood the implementation example of the ISSUE-16, the different between ISSUE-16 and ISSUE-24 would be about payload format of message exchange. If the ISSUE-16 also supports the application/service agnostic message exchange, the use case (system interactions) can be the same as the ISSUE24. Otherwise, the use case of the ISSUE-16 would be different. For example, 1. An User-Agent discovers other users agent on the same IP-sub network 2. Via API, the User-Agent provides the list of discovered applications which support the media rendering function. 3. The application invokes the play command with the content id via the API 4. The user-agent invokes the message of the play command to the target application. Jan, would you clarify whether do you think of the application/service agnostic message format or application/service specific message format in the ISSUE-16 ? Thank you. -***---***---***---***---***---***---***---***---***--***---***---***- Tatsuya Igarashi (Tatsuya.Igarashi@jp.sony.com) NS Development Dept. Technology Development Group Sony Corporation (Voice) +81-3-5435-3252 (Fax) +81-3-5435-3274 > -----Original Message----- > From: public-web-and-tv-request@w3.org > [mailto:public-web-and-tv-request@w3.org] On Behalf Of Giuseppe Pascale > Sent: Tuesday, June 14, 2011 6:35 PM > To: public-web-and-tv@w3.org; Jan Lindquist > Subject: Re: [HOME_NETWORK_TF] New use case Web and Device Interworking > (Issue-16) > > Hi Jan, > some comments on this usecase: > > * I don't think that, for this particular usecase, the "implementation" > section mentioning UPnP/DLNA is strictly needed. I would suggest to remove > it. Actually I would suggest to turn that section in a step-by-step > description, similar to what Igarashi-san has done for ISSUE-24 > * The part where you reference a "brokering service" is a bit vague (just > looking at the text). I think you should either expand it a little bit or > remove it. Actually that could be even a separate use case since it seems > to me to require a slightly different architecture and scenarios. > * I think this usecase partially overlaps with ISSUE-24 actually; do you > think would be possible to merge them? (or do you think they are different > instead?) > > Thanks, > /g > > On Mon, 13 Jun 2011 09:10:34 +0200, Jan Lindquist > <jan.lindquist@ericsson.com> wrote: > > > Hello, > > > > The Issue-16 has been updated. The following changes were made: > > > > - Some terms were modified in order to align with agreed terms. > > - An example of bookmarklets for loading additional scripts on a web > > page was added. > > - The text surrounding dependency was moved to implmentation. > > > > Best Regards, > > JanL > > > > ________________________________ > > From: public-web-and-tv-request@w3.org > > [mailto:public-web-and-tv-request@w3.org] On Behalf Of Jan Lindquist > > Sent: den 20 maj 2011 10:28 > > To: public-web-and-tv@w3.org > > Subject: [HOME_NETWORK_TF] New use case Web and Device Interworking > > (Issue-16) > > > > Hello, > > > > I have submitted a new use case for consideration by HNTF called web and > > device interworking (issue-16) . > > > > > http://www.w3.org/2011/webtv/wiki/HNTF/Home_Network_TF_Discussions/Web > DeviceInterworking > > > > The use case describes a how a personal device list available in the > > home is invoked on any web page and devices in the list can be used for > > consuming the contents on a web page, e.g. video clip on a page can be > > redirected to a TV or recorded on a network attached storage. > > > > The use case is actually supported by Ericsson Labs and is called Web > > Device Connectivity > > (https://labs.ericsson.com/apis/web-device-connectivity/). While the > Web > > Device Connectivity project is broader in nature the focus of this use > > case is to address the "implementation" list as described in issue-16. > > Note there is a reference API that addresses the implementation list > > which can be found under Documentation Tab (section 3) under Web Device > > Connectivity. > > > > Best regards, > > JanL > > > > > -- > Giuseppe Pascale > TV & Connected Devices > Opera Software - Sweden >
Received on Tuesday, 14 June 2011 10:53:50 UTC