[draft charter] Changes to Dependencies and Liaison section

Hi,

While you discuss the exact scope of this working group to be, I thought 
I'd try to advance less problematic sections of the draft charter. I 
completed the dependencies and liaison section and just sent in a pull 
request with proposed changes:

   https://github.com/webscreens/charter/pull/5

See below for a text version of the proposed section.

The goal of the Dependencies and Liaison section is to explicit 
dependencies, formal and informal liaisons with existing groups within 
W3C and with external bodies that develop related technologies. 
Regardless of the group's final decision on protocols, it seems 
important to list main external bodies that work on protocols that 
implementors could support.

The initial draft charter has the SysApps WG as internal group to liaise 
with. I didn't see why and dropped it. What did i miss? :)

I let you review and apply or discard the changes as needed. Although I 
tried to review all the discussions the group had so far, it's not the 
same thing as being part of these discussions from the ground up, so I 
may well have missed a few key points.

Thanks,
Francois.


Proposed text:
-----

Dependencies

The initial draft of the Presentation API was prepared by the Second 
Screen Presentation Community Group. Upon approval of the Working Group, 
the Community Group will publish a W3C Community Group Final Report of 
its Presentation API specification and will cease its work on the 
deliverable. The Community Group may recharter to work on other related 
deliverables that are not yet ready for the Working Group, or disband 
when the Working Group is formed.

The specifications produced by this Working Group adhere to the Web's 
security model defined in the HTML specification published by the HTML 
Working Group.

Common web technologies that this Working Group could refer to for 
messaging purpose include HTML5 Web Messaging and the Web Socket API 
defined by the Web Applications Working Group.

Some of the use cases that this Working Group aims to address, in 
particular the discovery and control of a display service connected on 
the local network, are also in scope of the Network Service Discovery 
API worked upon by the Device APIs Working Group. This Working Group 
will liaise with the Device APIs Working Group to avoid duplication of 
efforts and of solutions in this space.

This Working Group is not aware of any dependencies other Working 
Groups’ specifications have on this Working Group’s specifications.


Liaisons

The Working Group expects to maintain contacts with at least the 
following groups and Activities within W3C (in alphabetical order) and 
ask for reviews of deliverables in Last Call, and where appropriate:

Device APIs Working Group
The Device APIs Working Group defines the Network Service Discovery API 
that addresses some of the use cases that are in scope of the Second 
Screen Presentation Working Group.

HTML Working Group
The HTML Working Group’s deliverables cover the security model 
implemented in Web Browsers; this security model imposes limitations on 
what an extended model for Web Applications can achieve.

Web Accessibility Initiative Protocols and Formats Working Group
To ensure the Presentation API supports accessibility requirements, 
particularly with regard to interoperability with assistive 
technologies, and inclusion in the deliverable of guidance for 
implementing the group’s deliverables in ways that support accessibility 
requirements.

Web Applications Working Group
This group defines relevant or potentially relevant specifications 
including Web IDL, HTML5 Web Messaging and The Web Socket API.

Web and TV Interest Group
This group provides use cases and requirements for second screen 
scenarios and thus important input on the Presentation API developed by 
the Second Screen Presentation Working Group.


External Groups

The Presentation API does not have strong dependencies on any given set 
of protocols. The following is a tentative list of external bodies the 
Working Group should collaborate with to ensure that the Presentation 
API can be implemented on top of widely deployed attachment methods for 
connected displays:

DLNA
The Digital Living Network Alliance references home network protocols 
that secondary displays may support.

IETF
The IETF develops home network protocols that secondary displays may 
support.

UPnP Forum
The UPnP Forum develops home network protocols that secondary displays 
may support.

Wi-Fi Alliance
The Wi-Fi Alliance develops home network protocols that secondary 
displays may support.

Received on Wednesday, 28 May 2014 06:45:47 UTC