- From: <sysbot+notifier@w3.org>
- Date: Thu, 21 Nov 2024 15:04:51 +0000
- To: public-transition-announce@w3.org
Split / FPWD Request for Open Screen Protocol specs - openscreen-application, openscreen-network from https://github.com/w3c/transitions/issues/678 # Document title, URLs, estimated publication date The [Open Screen Protocol](https://www.w3.org/TR/openscreenprotocol/) spec was published as FPWD in 2021 (see #322). As described in its [charter](https://www.w3.org/2024/05/charter-secondscreen-wg.html#normative), the Second Screen WG worked on splitting the protocol into two parts: - "discovery and authentication", now known as [Open Screen Network Protocol](https://w3c.github.io/openscreenprotocol/network.html); - the "actual control protocol", now known as [Open Screen Application Protocol](https://w3c.github.io/openscreenprotocol/application.html) The W3C Process document does not say much about splitting a spec. Back in 2010, when a few specs got split out of HTML, they got published as FPWD. This request proposes to take the same approach and: - publish the two new specs as FPWD; - supersede the previous Open Screen Protocol spec. Relevant info for the two FPWDs: Application: - Title: Open Screen Application Protocol - URL: https://w3c.github.io/openscreenprotocol/application.html - Shortname: `openscreen-application`... or `osp-app` if we're looking for something shorter? Network: - Title: Open Screen Network Protocol - URL: https://w3c.github.io/openscreenprotocol/network.html - Shortname: `openscreen-network`... or `osp-net` Note: [Patent disclosures](https://www.w3.org/groups/wg/secondscreen/ipr/#current-disclosures) were made against the Open Screen Protocol specification. According to the [Patent Policy FAQ](https://www.w3.org/2003/12/22-pp-faq#doc-split), these disclosures need to be carried forward to the two new specs. # Abstract - Open Screen Application Protocol: The Open Screen Application Protocol allows user agents to implement the [Presentation API](https://w3c.github.io/openscreenprotocol/application.html#biblio-presentation-api) and the [Remote Playback API](https://w3c.github.io/openscreenprotocol/application.html#biblio-remote-playback) in an interoperable fashion. - Open Screen Network Protocol: The Open Screen Network Protocol is a network protocol that allows two Open Screen agents to establish a secure network transport in an interoperable fashion. # Status - Open Screen Application Protocol, see ED version of the [Status of This Document section](https://w3c.github.io/openscreenprotocol/application.html#sotd) - Open Screen Network Protocol, see ED version of the [Status of This Document section](https://w3c.github.io/openscreenprotocol/network.html#sotd) On top of adjusting the boilerplate text for publication as FPWD. If a paragraph to note the history seems warranted, the following text could be used: - Open Screen Application Protocol: "This document is the result of splitting the [Open Screen Protocol](https://www.w3.org/TR/openscreenprotocol/) document into two independent parts: the Open Screen Network Protocol provides a baseline set of network protocols for browsers and devices to discover each other and establish a secure network connection, and this document allows user agents to implement the [Presentation API](https://w3c.github.io/openscreenprotocol/application.html#biblio-presentation-api) and the [Remote Playback API](https://w3c.github.io/openscreenprotocol/application.html#biblio-remote-playback) in an interoperable fashion." - Open Screen Network Protocol: "This document is the result of splitting the [Open Screen Protocol](https://www.w3.org/TR/openscreenprotocol/) document into two independent parts: the Open Screen Application Protocol allows user agents to implement the [Presentation API](https://w3c.github.io/openscreenprotocol/application.html#biblio-presentation-api) and the [Remote Playback API](https://w3c.github.io/openscreenprotocol/application.html#biblio-remote-playback) in an interoperable fashion, and this document provides a baseline set of network protocols for browsers and devices to discover each other and establish a secure network connection." # Is it a delta specification intended to become a W3C Recommendation? No # Link to group's decision to request transition https://lists.w3.org/Archives/Public/public-secondscreen/2024Nov/0000.html # Issues https://github.com/w3c/openscreenprotocol/issues/ # Information about implementations known to the Working Group Google develops an open source [Open Screen Library](https://chromium.googlesource.com/openscreen/). -- This email was generated automatically using https://github.com/w3c/transition-issues-bot
Received on Thursday, 21 November 2024 15:04:56 UTC