openscreenprotocol
openscreenprotocol copied to clipboard
w3c
Open Screen Protocol
This will begin as everything omitted from the Open Screen Application Protocol (#341) but may evolve over time into one or more specifications. The motivations for doing so are listed...
The existing spec checks for consistency between metadata obtained through DNS-SD (instance name) and CBOR (agent-info) and considers inconsistency a reason to flag the agent as not trustworthy. https://www.w3.org/TR/openscreenprotocol/#instance-names If...
Following TPAC 2023, we agreed to investigate splitting the current specification into two or more specifications, for several reasons. Three main factors were: - Simplifying the specification and making it...
The application protocol needs abstract discovery and transport requirements, not specific to DNS-SD or QUIC.
The message delivery/ordering semantics depend on QUIC streams. Rewrite to be less specific, but in a way that can be mapped to QUIC easily. Related: #334