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

[github at oidf.org]

openid/sharedsignals event

Issue Comment created on issue 241
Issue Title: Support for advertising Transmitter metadata for multiple versions of spec
https://github.com/openid/sharedsignals/issues/241

Comment: > We launched the ID1 transmitter and have seamlessly supported ID1, ID2, and ID3 without needing this, so I'm curious about the ask! The usual guidance for the new implementers is to use the latest version; what use cases are you thinking of? ID1 transmitter configuration endpoint is completely different `/.well-known/sse-configuration` from later versions `/.well-known/ssf-configuration` . How were you able to support multiple versions at the same time? What is the metadata url and response for supporting multiple versions would look like? > This would change the API response from a JSON object to a list of objects, breaking backward compatibility, and should be avoided at this phase of the spec lifecycle. The one I proposed would be JSON object not list.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-risc/attachments/20250318/587656c7/attachment.htm>