[Openid-specs-risc] openid/sharedsignals: Comment created on issue 289

[github at oidf.org]

openid/sharedsignals event

Issue Comment created on issue 289
Issue Title: Guidelines for Adding Subjects to a Stream
https://github.com/openid/sharedsignals/issues/289

Comment: The `add_subjects` endpoint allows the Receiver to express the subjects that it is interested in receiving. It is up to the Transmitter whether or not to actually send an event with that subject. The authentication between the Transmitter and Receiver that is sent during stream configuration API calls should be enough to indicate to the Transmitter who the Receiver is, which should give the Transmitter enough info to determine what subjects and event types should be allowed to flow over that stream. Some things to note in the spec: - A Transmitter can [choose to default to sending all subjects](https://openid.github.io/sharedsignals/openid-sharedsignals-framework-1_0.html#section-7.1-25). `"ALL" indicates that any subjects that *are appropriate* for the stream are added to the stream by default.` (emphasis added by me) - In [Subject Probing](https://openid.github.io/sharedsignals/openid-sharedsignals-framework-1_0.html#section-9.1), it states that `Event Transmitters MAY return a "204" response even if they will not actually send any events related to the subject, and Event Receivers MUST NOT assume that a 204 response means that they will receive events related to the subject.` - In [Subject Matching](https://openid.github.io/sharedsignals/openid-sharedsignals-framework-1_0.html#name-subject-matching) the spec says `If a Receiver adds a subject to a stream defined in Section 8.1.3.2, the Transmitter SHOULD send any events relating to the subject which have event_types that the Receiver has subscribed to...` Note the keyword SHOULD, not MUST.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-risc/attachments/20250829/f3e5e2e2/attachment.htm>