sharedsignals
sharedsignals copied to clipboard
openid
OpenID Shared Signals Working Group Repository
In the description of [stream_id](https://openid.github.io/sharedsignals/openid-sharedsignals-framework-1_0.html#section-8.1.1-2) we say that it's: > A string that uniquely identifies the stream. A Transmitter MUST generate a unique ID for each of its non-deleted streams...
Once v1 is finalized, we can add "invalid_state" to the official SET error codes recognized in the IANA registry here: https://www.iana.org/assignments/secevent/secevent.xhtml#secevent-error-codes
Once v1 is finalized, we can add our new subject types to the IANA subject identifier formats registry: https://www.iana.org/assignments/secevent/secevent.xhtml#subject-identifier-formats
Right now, RISC profile is defined in xml. This makes it hard to edit/maintain. We use markdown instead. Not required for v1. Just an dev experience thing.
The SSF well known uri is currently marked as "provisional". Once the spec gets voted in for version 1, we can move it to permanent. This issue is just a...
In the [Transmitter section](https://openid.net/specs/openid-sharedsignals-framework-1_0-ID3.html#name-authorization-scheme) we have > SSF is an HTTP based signals sharing framework and is agnostic to the authentication and authorization schemes used to secure stream configuration APIs....