[Openid-specs-fapi] Issue #140: New name for FAPI (openid/fapi)
ve7jtb at ve7jtb.com
Thu May 10 20:30:38 UTC 2018
I think that the remaining things with FAPI in the name can be explained in the spec.
Changing the WG name is probably the most important part.
I don’t have a problem with calling the specs Enhanced OpenID profile or something like that while still having a X-FAPI header if we need to.
> On May 2, 2018, at 1:12 AM, Nat Sakimura via Openid-specs-fapi <openid-specs-fapi at lists.openid.net> wrote:
> New issue 140: New name for FAPI
> Nat Sakimura:
> In March Board meeting, the board requested the name for FAPI to be generalized so that it will match the wider applicability of the security profiles.
> This is a fair request but the catch is that the string 'fapi' is already used in the protocol parameters and we do not want to change it.
> Thus we have a constrained name search: the new name should have an acronym that would result in **FAPI**.
> This ticket collects some candidates on it.
> Some of the initial ideas:
> * Fully Assured Protection Interoperable
> * Fair Assurance Protection Interface
> Openid-specs-fapi mailing list
> Openid-specs-fapi at lists.openid.net
More information about the Openid-specs-fapi