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

[HOME_NETWORK_TF] Requirement Draft - Abstract Review (was: Re: New TF on Home Networking - Call for Participants)

From: Giuseppe Pascale <giuseppep@opera.com>
Date: Mon, 28 Mar 2011 12:01:13 +0200
To: "Matt Hammond" <matt.hammond@rd.bbc.co.uk>
Cc: public-web-and-tv@w3.org
Message-ID: <op.vs1ssby36ugkrk@rabdomant-ubuntu>
Matt,
thanks a lot for the contribution,
I started a new thread in order to give it a bit more visibility.


On Wed, 23 Mar 2011 02:28:03 +0100, Matt Hammond  
<matt.hammond@rd.bbc.co.uk> wrote:

> Very happy to make some suggestions and share them on the wiki (and  
> here) as you suggest. Am having a few problems logging into it at the  
> moment with my newly created account.
>
No problem, I'll edit it.
Actually for the time being I would prefer to be the editor (I will  
probably require help to some other people in future).
Remember though that you can still use the wiki to write any proposal you  
like to discuss with other IG participants (when writing into an email is  
not suitable).

To clarify this I split this two sections in two pages:

Requirement Document Draft (EDITOR ONLY):  
http://www.w3.org/2011/webtv/wiki/Home_Network_TF_Requirements
Discussions (EVERYBODY):  
http://www.w3.org/2011/webtv/wiki/Home_Network_TF_Discussions


> As a starting point, here is a suggestion for how I might rephrase the  
> abstract to incorporate some of my ideas/comments:
>
> """
> There is an increasing amount of personal content on devices connected  
> to the home network that users would like to be able to access from any  
> device in teh home (personal computers, tablets, mobile phones, TVs and  
> others).
>
> Growing numbers of TVs and other devices capable of presenting content  
> can be connected to the home network and can access internet based  
> services as well as access content from the home network and receive  
> traditional broadcast services.
>
> There is growing interest in providing richer and novel user experiences  
> that present a cohesive experience across multiple devices including  
> TVs, mobile phones, tablets and others.
>
> This document lists the design goals and requirements that  
> specifications would have to follow in order to enable web and other  
> applications to present user interfaces that facilitate access to the  
> services provided on other devices, including the discovery and playback  
> of content available to those devices, both from services such as  
> traditional broadcast media and internet based services but also from  
> the home network.
> """
>
Sounds fine, I'll incorporate the proposal.

/g

>
> Matt
>
> To addres my comments, I would suggest a general refactoring
>
> On Tue, 22 Mar 2011 11:54:09 -0000, Giuseppe Pascale  
> <giuseppep@opera.com> wrote:
>
>>> Broadcast style TV services/content should be included when  
>>> considering the kinds of content to be accessed by a device. It is  
>>> still a popular medium :-)
>>>
>> Agree :)
>>
>> May I ask you to suggest some specific re-wording of the current  
>> requirement draft[1]?
>> Just to be sure your comment is correctly reflected and to let people  
>> react on what you propose
>> Feel free to post it here.
>>
>>> The 2-box / 3-box distinction and the assumption of a need for content  
>>> type negotiation assume a particular structure/model for interaction  
>>> and a particular level of abstraction. Does this implicitly pre-select  
>>> particular solutions (eg. UPnP) for the inter-device application layer  
>>> protocols?
>>>
>>
>> That was not the intention, but I agree that this is misleading.
>> We need to generalize it a little more and probably use a more  
>> "neutral" terminology.
>>
>> To be honest, the use of 2-box/3-box model terms was good at start to  
>> let people understand at a glance what we are talking about.
>> But I agree on a reworking of this part. As said above, if you have a  
>> proposal, feel free to share.
>>
>>> I also feel it may be too limiting, at this stage, to confine the  
>>> scope to just JavaScript APIs. This assumes the existence of suitable  
>>> inter-device application layer protocols. The existence of JavaScript  
>>> APIs is the (or at least a major) desirable end-goal, but we might  
>>> identify other elements that are required.
>>>
>> partially agree, in fact the current draft mention JS API only in few  
>> places, while it usually says "User agents should provide a means for  
>> ...".
>> We can generalize even more and remove any specific mention to JS API.
>>
>> On the other hand we need to have this discussion at some point. Not  
>> only if we need an API but also which kind of granularity we need for  
>> these API.
>>
>>> Arguably content discovery and playback are the two most important  
>>> elements, but devices such as connected TVs have many other functions  
>>> - eg. apps, recording capabilities etc. Many of these functions may  
>>> also be useful to access from other devices within the home. There is  
>>> also the opportunity to comprehensively improve accessibility if most  
>>> key functions of such a device can be exposed through suitable APIs.
>>>
>> maybe we should use the term "Service Discovery and Control"?
>>
>> /g
>>
>>
>> [1] http://www.w3.org/2011/webtv/wiki/Home_Network_TF_Requirements
>>
>>
>>>
>>> On Thu, 17 Mar 2011 22:58:27 -0000, Giuseppe Pascale  
>>> <giuseppep@opera.com> wrote:
>>>
>>>> Dear all,
>>>> during the last Web & TV workshop in Berlin, device and content  
>>>> discovery
>>>> and control in the home network was identified as a prerequisite for  
>>>> most
>>>> multiple
>>>> screen scenarios and some of the participants expressed interested in
>>>> outlining requirements
>>>> and make a gap analysis with currently available technologies in  
>>>> order to
>>>> identify areas where some specification effort may be needed.
>>>>
>>>> In order to handle this discussion, we are issuing a call for  
>>>> participants
>>>> for a Task Force on Home Network Content Discovery and Control.
>>>>
>>>> Since this is the first TF created in the IG, below you will find
>>>> more information about what a TF is and how it works (in the context  
>>>> of
>>>> the Web & TV IG).
>>>> Information below are tailored for this particular TF but in the next
>>>> weeks a more generic and extended version of the same information  
>>>> will be
>>>> published on the IG wiki and/or home page.
>>>>
>>>> We apologize if we didn't manage yet to finalize and publish all
>>>> information
>>>> and tools but we are working on it and they will be available soon.
>>>>
>>>> If you have any comment/question on this CfP feel free to reply to  
>>>> this
>>>> email.
>>>>
>>>> Home Network TF (of the Web & TV IG)
>>>> ------------------------------------
>>>>
>>>> * How to join the TF
>>>> The TF is open to all members of the Web & TV IG.
>>>> Proceedings of the TF will be public so will be
>>>> also available e.g. to the subscribers of the
>>>> Web & TV Mailing list.
>>>>
>>>> Note though that some actions may require to be an official
>>>> member of the IG (i.e. a w3c member); one example is editing
>>>> the requirement document produced by the IG (see below)
>>>>
>>>> In order to be able to evaluate the interest among IG participants,
>>>> interested parties are required to send a simple statement of
>>>> interest (in form of a short reply to this email).
>>>>
>>>>
>>>> * Goals and deliverables of the TF
>>>> In a first phase, the goal of the TF will be to identify usecases
>>>> for device and content discovery and control in the home network,
>>>> gaps in the existing technologies to address these usecases and
>>>> requirements that specifications need to address in order to cover  
>>>> such
>>>> gaps.
>>>>
>>>> Another goal for this first phase is also to identify
>>>> - if the requirements can be addressed by one ore more existing W3C  
>>>> WGs, OR
>>>> - if a new WG is required, OR
>>>> - if the work is out of scope for W3C
>>>>
>>>> Deliverables for this first phase are a requirement document that an
>>>> existing or new group can use to begin the specification work.
>>>>
>>>> In a (optional) second phase, the TF can be used to monitor and
>>>> provide feedbacks or new inputs to the WG working on the  
>>>> specification.
>>>>
>>>> * How is the TF work organized?
>>>> - Wiki
>>>> In order to enable collaborative work, the TF will use the web & TV  
>>>> wiki.
>>>> The wiki will be used both to maintain the requirement document draft  
>>>> and
>>>> to keep information about any other relevant discussion raised.
>>>> All IG participants (i.e. w3c members) have write access to the wiki.
>>>> We may consider having one or more editors to avoid confusion.
>>>>
>>>> - Phone calls
>>>> If/when needed, the TF can schedule regular phone calls in order to
>>>> discuss relevant topics. Frequency of the phone calls
>>>> is a decision for TF participants to make.
>>>>
>>>> - Email discussion
>>>> For email discussion, the general Web & TV IG mailing list will be  
>>>> used.
>>>> In order to make easy to identify the mail related to the TF
>>>> (and allow people to filter email they are not interested to)
>>>> each mail thread MUST contain the tag [HOME_NETWORK_TF]
>>>>
>>>> * Relevant links
>>>> Wiki: http://www.w3.org/2011/webtv/wiki/Main_Page
>>>> IG Home: http://www.w3.org/2011/webtv/
>>>>
>>>> P.S. attached to this mail an initial draft of a requirement document.
>>>> This is just intended as a starting point for our discussion.
>>>> Thanks to Bob Lund and Clarke Stevens for providing this initial
>>>> contribution.
>>>>
>>>>
>>>> Best Regards,
>>>> Giuseppe Pascale on Behalf of the Web & TV IG co-chairs
>>>>
>>>
>>>
>>
>>
>
>

-- 
Giuseppe Pascale
TV & Connected Devices
Opera Software - Sweden
Received on Monday, 28 March 2011 10:02:38 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:44:02 UTC