[Openid-specs-risc] Backwards compat language in a pre-1.0 spec

[Atul Tulshibagwale]

Thanks Tim,
I can make this change to the pull request, and it should be agreeable to
everyone.

One question: Do we know of any other Transmitters that use the previous
draft of the RISC profile? If so, the language would need to include those
too (i.e. it cannot say "Google implementation").

Atul


On Fri, Jan 7, 2022 at 10:34 AM Tim Cappalli via Openid-specs-risc <
openid-specs-risc at lists.openid.net> wrote:

> Hey all,
>
> Sending this here since we didn't meet this week.
>
> I spoke to the OpenID Foundation and there is precedent for not including
> inline normative backwards compatibility text in a 1.0 spec, but instead
> adding text under a Compatibility Notes section.
>
> https://openid.net/specs/openid-connect-core-1_0.html#CompatibilityNotes
>
>
> This happened with OpenID Connect Core with the iss​ value:
> https://openid.net/specs/openid-connect-core-1_0.html#GoogleIss
>
> It was recommended that we follow this approach.
>
> Tim
>
>
>
>
> _______________________________________________
> Openid-specs-risc mailing list
> Openid-specs-risc at lists.openid.net
> http://lists.openid.net/mailman/listinfo/openid-specs-risc
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-risc/attachments/20220107/fc0340fc/attachment-0001.html>