Second Screen Working Group - Activity in 2018
No matches.
GitHub
w3c/openscreenprotocol
-
3 issues opened.
-
Is a Presentation close/terminate from a controller a request/response or event? w3c/openscreenprotocol#124, by @pthatcherg.
-
Define a capabilities mechanism w3c/openscreenprotocol#123, by @pthatcherg.
-
[Auth] Challenge/Response over TLS w3c/openscreenprotocol#122, by @nigelcearnshaw.
-
-
3 issues received 3 new comments.
-
Is a Presentation close/terminate from a controller a request/response or event? w3c/openscreenprotocol#124 (1 comment by @btolsch)
-
[QUIC] Define suspend and resume behavior for connection protocol w3c/openscreenprotocol#108 (1 comment by @btolsch)
-
-
4 pull requests opened.
-
Remove unused urls in availability event w3c/openscreenprotocol#128, by @btolsch.
-
Replace GitHub issue relative URLs with absolute URLs w3c/openscreenprotocol#127, by @takumif.
-
Add challenge/response mechanism for authentication w3c/openscreenprotocol#126, by @pthatcherg.
-
Add CDDL minimum occurrence specification w3c/openscreenprotocol#125, by @btolsch.
-
-
5 pull requests merged.
-
Remove unused urls in availability event w3c/openscreenprotocol#128.
-
Replace GitHub issue relative URLs with absolute URLs w3c/openscreenprotocol#127.
-
Add CDDL minimum occurrence specification w3c/openscreenprotocol#125.
-
Specify use of mDNS, QUIC, and CBOR w3c/openscreenprotocol#119.
-
Add messages and protocol for Presentation API w3c/openscreenprotocol#120.
-
-
1 pull request reopened.
-
Specify use of mDNS, QUIC, and CBOR w3c/openscreenprotocol#119, by @markafoltz.
-
-
3 pull requests received 151 new comments.
-
Specify use of mDNS, QUIC, and CBOR w3c/openscreenprotocol#119 (72 comments by @markafoltz, @pthatcherg)
-
Add messages and protocol for Presentation API w3c/openscreenprotocol#120 (56 comments by @btolsch, @chrisn, @markafoltz, @pthatcherg, @tidoust)
-
Add challenge/response mechanism for authentication w3c/openscreenprotocol#126 (23 comments by @markafoltz, @pthatcherg)
-
GitHub
w3c/openscreenprotocol
-
1 issue opened.
-
[mDNS] Investigate compatibility with DNS-SD sleep proxy spec w3c/openscreenprotocol#121, by @markafoltz.
-
-
1 issue received 1 new comment.
-
Incorporate wake-on-lan into discovery protocol w3c/openscreenprotocol#51 (1 comment by @markafoltz)
-
-
2 pull requests opened.
-
Add messages and protocol for Presentation API w3c/openscreenprotocol#120, by @pthatcherg.
-
Specify use of mDNS, QUIC, and CBOR w3c/openscreenprotocol#119, by @pthatcherg.
-
-
2 pull requests received 42 new comments.
-
Add messages and protocol for Presentation API w3c/openscreenprotocol#120 (15 comments by @pthatcherg, @tidoust)
GitHub
w3c/openscreenprotocol
-
8 issues opened.
-
[Security] UI guidelines for pairing and trusted/untrusted data w3c/openscreenprotocol#118, by @markafoltz.
-
[Protocol] Support establishment of a streaming session the control protocol w3c/openscreenprotocol#117, by @markafoltz.
-
Investigate alternative discovery mechanisms w3c/openscreenprotocol#116, by @markafoltz.
-
[Auth] Trusted Displays w3c/openscreenprotocol#114, by @nigelcearnshaw.
-
[Auth] Certificates and devices w3c/openscreenprotocol#113, by @nigelcearnshaw.
-
[Auth] Revisiting a previously established session w3c/openscreenprotocol#112, by @nigelcearnshaw.
-
[Auth] Length of Password w3c/openscreenprotocol#111, by @nigelcearnshaw.
-
[Auth] Symmetric vs Asymmetric w3c/openscreenprotocol#110, by @nigelcearnshaw.
-
-
2 issues received 3 new comments.
-
[SSDP] Investigate mechanisms to pre-filter devices by Presentation URL w3c/openscreenprotocol#21 (1 comment by @markafoltz)
-
1 pull request opened.
-
Fix links to GitHub issues in schema.md w3c/openscreenprotocol#115, by @chrisn.
-
-
1 pull request merged.
-
Fix links to GitHub issues in schema.md w3c/openscreenprotocol#115.
-
-
2 pull requests received 2 new comments.
GitHub
w3c/openscreenprotocol
-
3 issues opened.
-
[QUIC] Define suspend and resume behavior for connection protocol w3c/openscreenprotocol#108, by @markafoltz.
-
[mDNS] Define suspend and resume behavior for discovery protocol w3c/openscreenprotocol#107, by @markafoltz.
-
[mDNS] Minimum TXT record length limit w3c/openscreenprotocol#105, by @markafoltz.
-
-
2 issues closed.
-
[DataChannel] Investigate use of DataChannel without all of WebRTC w3c/openscreenprotocol#83.
-
[Spec] Complete introduction and requirements section. w3c/openscreenprotocol#99.
-
-
2 issues received 2 new comments.
-
[DataChannel] Investigate use of DataChannel without all of WebRTC w3c/openscreenprotocol#83 (1 comment by @markafoltz)
-
-
2 pull requests opened.
-
Add link to Open Screen Protocol draft spec w3c/openscreenprotocol#109, by @chrisn.
-
Merge PR #103 to gh-pages. w3c/openscreenprotocol#106, by @markafoltz.
-
-
3 pull requests merged.
-
Add link to Open Screen Protocol draft spec w3c/openscreenprotocol#109.
-
Merge PR #103 to gh-pages. w3c/openscreenprotocol#106.
-
Adds terminology and requirements to spec. w3c/openscreenprotocol#103.
-
-
3 pull requests received 4 new comments.
-
Add link to Open Screen Protocol draft spec w3c/openscreenprotocol#109 (2 comments by @anssiko, @markafoltz)
-
GitHub
w3c/openscreenprotocol
-
5 issues opened.
-
[Spec] Complete Authentication section. w3c/openscreenprotocol#102, by @markafoltz.
-
[Spec] Complete Transport Establishment section. w3c/openscreenprotocol#101, by @markafoltz.
-
[Spec] Complete Receiver Discovery section. w3c/openscreenprotocol#100, by @markafoltz.
-
[Spec] Complete introduction and requirements section. w3c/openscreenprotocol#99, by @markafoltz.
-
[Meta] Open Screen Protocol 1.0 Specification w3c/openscreenprotocol#98, by @markafoltz.
-
-
1 issue received 1 new comment.
-
[QUIC] Find out timeline for TLS 1.3 and QUIC v1 w3c/openscreenprotocol#82 (1 comment by @tomoyukilabs)
-
-
3 pull requests opened.
-
Adjust copyright and SOTD sections to mention CLA w3c/openscreenprotocol#104, by @tidoust.
-
Adds terminology and requirements to spec. w3c/openscreenprotocol#103, by @markafoltz.
-
Outline for a combined specification document. w3c/openscreenprotocol#97, by @markafoltz.
-
-
2 pull requests merged.
-
Adjust copyright and SOTD sections to mention CLA w3c/openscreenprotocol#104.
-
Outline for a combined specification document. w3c/openscreenprotocol#97.
-
-
3 pull requests received 8 new comments.
-
Adjust copyright and SOTD sections to mention CLA w3c/openscreenprotocol#104 (3 comments by @markafoltz, @tidoust)
-
Outline for a combined specification document. w3c/openscreenprotocol#97 (3 comments by @markafoltz, @tidoust)
-
Adds terminology and requirements to spec. w3c/openscreenprotocol#103 (2 comments by @markafoltz, @tidoust)
-
w3c/presentation-api
-
1 issue opened.
-
BinaryType enum is already defined in HTML w3c/presentation-api#456, by @foolip.
-
-
1 issue closed.
-
BinaryType enum is already defined in HTML w3c/presentation-api#456.
-
-
1 issue received 4 new comments.
-
BinaryType enum is already defined in HTML w3c/presentation-api#456 (4 comments by @foolip, @markafoltz, @tidoust)
-
-
3 pull requests opened.
-
Revert "Remove BinaryType enum (already in HTML) (#457)" w3c/presentation-api#459, by @markafoltz.
-
Fix respec errors. w3c/presentation-api#458, by @markafoltz.
-
Remove BinaryType enum (already in HTML) w3c/presentation-api#457, by @foolip.
-
-
3 pull requests merged.
-
Revert "Remove BinaryType enum (already in HTML) (#457)" w3c/presentation-api#459.
-
Fix respec errors. w3c/presentation-api#458.
-
Remove BinaryType enum (already in HTML) w3c/presentation-api#457.
-
-
2 pull requests received 2 new comments.
Participants
-
1 organization left.
-
VIGOUR left.
-
GitHub
w3c/openscreenprotocol
-
2 issues opened.
-
[HbbTV] Semantics of hbbtv: URLs w3c/openscreenprotocol#94, by @markafoltz.
-
[Meta] Add note to schemes.md about custom schemes and interop w3c/openscreenprotocol#93, by @markafoltz.
-
-
1 issue closed.
-
[SSDP] Update proposed use of SSDP to specifically prevent SSDP amplification attacks w3c/openscreenprotocol#57.
-
-
4 issues received 4 new comments.
-
[SSDP] Update proposed use of SSDP to specifically prevent SSDP amplification attacks w3c/openscreenprotocol#57 (1 comment by @markafoltz)
-
[Meta] Performance data for discovery protocols w3c/openscreenprotocol#69 (1 comment by @markafoltz)
-
2 pull requests opened.
-
Prevent SSDP amplification attacks w3c/openscreenprotocol#96, by @markafoltz.
-
Update schemes.md w3c/openscreenprotocol#95, by @markafoltz.
-
-
3 pull requests merged.
-
Update schemes.md w3c/openscreenprotocol#95.
-
Prevent SSDP amplification attacks w3c/openscreenprotocol#96.
-
add schemes.md w3c/openscreenprotocol#90.
-
-
3 pull requests received 4 new comments.
w3c/presentation-api
-
1 issue opened.
-
Clarify behavior when the receiving page attempts to navigate itself w3c/presentation-api#455, by @tidoust.
-
-
3 issues closed.
-
Add sample code for single controller to multiple presentations w3c/presentation-api#451.
-
Multiple presentation URLs including non-http/https URL w3c/presentation-api#446.
-
Receiver does not receive the initial message w3c/presentation-api#450.
-
-
5 issues received 8 new comments.
-
Behavior of window.reload() on presentation receiver page w3c/presentation-api#449 (4 comments by @markafoltz, @tidoust)
-
Add sample code for single controller to multiple presentations w3c/presentation-api#451 (1 comment by @markafoltz)
-
Multiple presentation URLs including non-http/https URL w3c/presentation-api#446 (1 comment by @markafoltz)
-
Local Presentation API to enable child-window presentation documents w3c/presentation-api#347 (1 comment by @anssiko)
-
-
3 pull requests opened.
-
Address issue #449. w3c/presentation-api#454, by @markafoltz.
-
Adds sample code for starting a 2nd presentation. w3c/presentation-api#453, by @markafoltz.
-
Update web-platform-tests URLs w3c/presentation-api#452, by @foolip.
-
-
2 pull requests merged.
-
Adds sample code for starting a 2nd presentation. w3c/presentation-api#453.
-
Update web-platform-tests URLs w3c/presentation-api#452.
-
-
1 pull request received 1 new comment.
-
Adds sample code for starting a 2nd presentation. w3c/presentation-api#453 (1 comment by @tomoyukilabs)
-
w3c/remote-playback
-
1 pull request opened.
-
Update web-platform-tests URL w3c/remote-playback#122, by @foolip.
-
-
1 pull request merged.
-
Update web-platform-tests URL w3c/remote-playback#122.
-
GitHub
w3c/remote-playback
-
4 issues opened.
-
Support for TTML and IMSC captions w3c/remote-playback#120, by @chrisn.
-
Explore polyfilling Remote Playback API on top of Presentation API w3c/remote-playback#119, by @markafoltz.
-
Define remote playback interaction with background playback policies w3c/remote-playback#118, by @markafoltz.
-
Chromecast TV not detected w3c/remote-playback#117, by @Mathieu-R.
-
-
2 issues closed.
-
Compatibility of Remote Playback API with AirPlay mirroring w3c/remote-playback#114.
-
Chromecast TV not detected w3c/remote-playback#117.
-
-
3 issues received 7 new comments.
-
Define remote playback interaction with background playback policies w3c/remote-playback#118 (1 comment by @markafoltz)
-
Compatibility of Remote Playback API with AirPlay mirroring w3c/remote-playback#114 (1 comment by @markafoltz)
-
1 pull request opened.
-
Minor editorial changes w3c/remote-playback#121, by @chrisn.
-
-
1 pull request merged.
-
Minor editorial changes w3c/remote-playback#121.
-
-
1 pull request received 5 new comments.
w3c/openscreenprotocol
-
3 issues opened.
-
[Control protocol] Forward compatibility with presentation page advertisement w3c/openscreenprotocol#92, by @markafoltz.
-
Disconnect/Reconnect of RemotePlayback API w3c/openscreenprotocol#89, by @igarashi50.
-
Why a custom binary control protocol? w3c/openscreenprotocol#86, by @rektide.
-
-
4 issues closed.
-
[SSDP] Update implementation information w3c/openscreenprotocol#81.
-
Representation of BCP-47 language tags w3c/openscreenprotocol#54.
-
[QUIC] Investigate and propose use of DataChannel framing on top of QUIC w3c/openscreenprotocol#84.
-
Why a custom binary control protocol? w3c/openscreenprotocol#86.
-
-
10 issues received 18 new comments.
-
[QUIC] Find out timeline for TLS 1.3 and QUIC v1 w3c/openscreenprotocol#82 (4 comments by @anssiko, @chrisn, @tomoyukilabs)
-
[Meta] Propose security mechanisms for Open Screen protocol w3c/openscreenprotocol#13 (3 comments by @anssiko, @tomoyukilabs)
-
[Protocol] Hand-rolled binary protocol? w3c/openscreenprotocol#77 (3 comments by @avayvod, @markafoltz, @rektide)
-
Investigate message latency requirements for media sync w3c/openscreenprotocol#80 (1 comment by @chrisn)
-
[DataChannel] Define bootstrap mechanism for QUIC (or RTCDataChannel) w3c/openscreenprotocol#73 (1 comment by @anssiko)
-
[QUIC] Investigate and propose use of DataChannel framing on top of QUIC w3c/openscreenprotocol#84 (1 comment by @anssiko)
-
-
4 pull requests opened.
-
Add TV device specs w3c/openscreenprotocol#91, by @chrisn.
-
add schemes.md w3c/openscreenprotocol#90, by @louaybassbouss.
-
Update implementation information for SSDP w3c/openscreenprotocol#88, by @louaybassbouss.
-
Update j-pake.md w3c/openscreenprotocol#87, by @tomoyukilabs.
-
-
4 pull requests merged.
-
Update implementation information for SSDP w3c/openscreenprotocol#88.
-
Add TV device specs w3c/openscreenprotocol#91.
-
Update j-pake.md w3c/openscreenprotocol#87.
-
Add a document about details on J-PAKE w3c/openscreenprotocol#85.
-
-
5 pull requests received 14 new comments.
w3c/presentation-api
-
4 issues opened.
-
Add sample code for single controller to multiple presentations w3c/presentation-api#451, by @markafoltz.
-
Receiver does not receive the initial message w3c/presentation-api#450, by @Mathieu-R.
-
Behavior of window.reload() on presentation receiver page w3c/presentation-api#449, by @markafoltz.
-
Present a page that's only available to authenticated users. w3c/presentation-api#448, by @Mathieu-R.
-
-
1 issue closed.
-
Present a page that's only available to authenticated users. w3c/presentation-api#448.
-
-
1 issue reopened.
-
Presentation display capability detection w3c/presentation-api#348, by @markafoltz.
-
-
7 issues received 24 new comments.
-
Behavior of window.reload() on presentation receiver page w3c/presentation-api#449 (7 comments by @ebidel, @louaybassbouss, @markafoltz, @tomoyukilabs)
-
Receiver does not receive the initial message w3c/presentation-api#450 (6 comments by @imcheng2, @louaybassbouss, @markafoltz, @Mathieu-R, @tomoyukilabs)
-
Local Presentation API to enable child-window presentation documents w3c/presentation-api#347 (3 comments by @anssiko, @markafoltz)
-
Presentation display capability detection w3c/presentation-api#348 (3 comments by @louaybassbouss, @markafoltz)
-
Present a page that's only available to authenticated users. w3c/presentation-api#448 (3 comments by @louaybassbouss, @Mathieu-R)
-
Allow page to turn itself into a presentation session w3c/presentation-api#32 (1 comment by @markafoltz)
-
Add sample code for single controller to multiple presentations w3c/presentation-api#451 (1 comment by @markafoltz)
-
Participants
-
1 organization joined.
-
SPORTTOTAL AG joined.
-
GitHub
w3c/presentation-api
-
1 issue received 4 new comments.
-
Multiple presentation URLs including non-http/https URL w3c/presentation-api#446 (4 comments by @markafoltz, @tidoust, @tomoyukilabs)
-
-
1 pull request opened.
-
Ignore a URL with an unsupported scheme w3c/presentation-api#447, by @tomoyukilabs.
-
-
1 pull request merged.
-
Ignore a URL with an unsupported scheme w3c/presentation-api#447.
-
-
1 pull request received 6 new comments.
-
Ignore a URL with an unsupported scheme w3c/presentation-api#447 (6 comments by @markafoltz, @tomoyukilabs)
-
w3c/remote-playback
-
1 issue opened.
-
[Chrome 64] The RemotePlayback API is disabled on this platform w3c/remote-playback#116, by @Mathieu-R.
-
-
1 issue closed.
-
[Chrome 64] The RemotePlayback API is disabled on this platform w3c/remote-playback#116.
-
-
1 issue received 4 new comments.
-
[Chrome 64] The RemotePlayback API is disabled on this platform w3c/remote-playback#116 (4 comments by @markafoltz, @Mathieu-R, @mounirlamouri)
-
-
1 pull request merged.
-
Addresses Issue #114 w3c/remote-playback#115.
-
-
1 pull request received 1 new comment.
Lifecycle
-
1 charter started.
-
Chartered until 31 December 2019.
-
GitHub
w3c/openscreenprotocol
-
2 issues closed.
-
[Editorial] Use compact and readable syntax for protocol messages w3c/openscreenprotocol#60.
-
[Protocol] Investigate variable length encodings for integer header values w3c/openscreenprotocol#45.
-
-
4 issues received 5 new comments.
-
[QUIC] Investigate WebSocket layering onto QUIC w3c/openscreenprotocol#62 (2 comments by @pthatcherg, @tomoyukilabs)
-
[Editorial] Use compact and readable syntax for protocol messages w3c/openscreenprotocol#60 (1 comment by @markafoltz)
-
[Protocol] Investigate variable length encodings for integer header values w3c/openscreenprotocol#45 (1 comment by @markafoltz)
-
[DataChannel] Define bootstrap mechanism for QUIC (or RTCDataChannel) w3c/openscreenprotocol#73 (1 comment by @tomoyukilabs)
-
-
1 pull request opened.
-
Add a document about details on J-PAKE w3c/openscreenprotocol#85, by @tomoyukilabs.
-
w3c/presentation-api
-
1 issue received 1 new comment.
-
Multiple presentation URLs including non-http/https URL w3c/presentation-api#446 (1 comment by @anssiko)
-
w3c/remote-playback
-
1 issue received 1 new comment.
-
Compatibility of Remote Playback API with AirPlay mirroring w3c/remote-playback#114 (1 comment by @markafoltz)
-
-
1 pull request received 2 new comments.
GitHub
w3c/remote-playback
-
1 issue opened.
-
Compatibility of Remote Playback API with AirPlay mirroring w3c/remote-playback#114, by @markafoltz.
-
-
1 issue closed.
-
Should rendering behavior of the remote-d media element be specified? w3c/remote-playback#46.
-
-
1 issue received 1 new comment.
-
Should rendering behavior of the remote-d media element be specified? w3c/remote-playback#46 (1 comment by @markafoltz)
-
-
2 pull requests opened.
-
Addresses Issue #114 w3c/remote-playback#115, by @markafoltz.
-
Adds informative note about UI during remote playback. w3c/remote-playback#113, by @markafoltz.
-
-
1 pull request merged.
-
Adds informative note about UI during remote playback. w3c/remote-playback#113.
-
w3c/secondscreen-charter
-
2 pull requests opened.
-
Address more editorial review comments w3c/secondscreen-charter#9, by @tidoust.
-
Revisions in response to Mozilla. w3c/secondscreen-charter#8, by @markafoltz.
-
-
2 pull requests merged.
-
Address more editorial review comments w3c/secondscreen-charter#9.
-
Revisions in response to Mozilla. w3c/secondscreen-charter#8.
-
-
2 pull requests received 16 new comments.
-
Revisions in response to Mozilla. w3c/secondscreen-charter#8 (14 comments by @anssiko, @dbaron, @markafoltz, @schien, @tidoust)
-
w3c/presentation-api
-
1 issue opened.
-
Multiple presentation URLs including non-http/https URL w3c/presentation-api#446, by @tomoyukilabs.
-
-
1 issue closed.
-
Consider use cases for Presentation API v2 with VR capable displays w3c/presentation-api#444.
-
-
3 issues received 6 new comments.
-
Multiple presentation URLs including non-http/https URL w3c/presentation-api#446 (2 comments by @tidoust, @tomoyukilabs)
-
Consider use cases for Presentation API v2 with VR capable displays w3c/presentation-api#444 (1 comment by @anssiko)