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

github at oidf.org github at oidf.org
Tue Apr 23 22:36:22 UTC 2024


openid/sharedsignals event

Issue Comment created on issue 152
Issue Title: Removing transmitter supplied fields from stream config PUT and PATCH…
https://github.com/openid/sharedsignals/pull/152

Comment: > The existing language already clarifies - > > > Transmitter-Supplied properties beside the stream_id MAY be present, > > but they MUST match the expected value. Missing Transmitter-Supplied > > properties MUST be ignored by the Transmitter. > > There may be reasons for the receiver to send the same values to make sure it's info matches the Tx info (and expect to receive error message, on mismatch) > > I don't think this PR is needed. Please let me know your thoughts The issue addressed by this PR is not if the fields can or can't be in the request but the fact that having a the fields in the **examples** is confusing. Having transmitter-supplied fields in an update request is an edge case and while it is allowed, it doesn't make sense to do so.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-risc/attachments/20240423/36fb3f14/attachment.html>


More information about the Openid-specs-risc mailing list