[Openid-specs-fapi] Issue #479: Change to the naming of FAPI (openid/fapi)

[M V]

New issue 479: Change to the naming of FAPI
https://bitbucket.org/openid/fapi/issues/479/change-to-the-naming-of-fapi

Mark Verstege:

There has previously been a discussion [here](https://bitbucket.org/openid/fapi/issues/140/new-name-for-fapi) and [here](https://bitbucket.org/openid/fapi/issues/432/fapi2-trust-framework-structure) around the naming of FAPI. Originally standing for Financial APIs, it was renamed to Financial-grade APIs, to reflect the fact that its security profiles are suitable for APIs in other verticals beyond finance services. Whilst this indicates the security of the profile for financial services, it has created confusion in other industries that are considering the adoption of FAPI as the baseline security profile \(e.g. utility sectors such as energy and telecommunications\). Beyond this there are emerging global health care and government use cases where continuing usage of “financial-grade” may continue to cause contention.

With the FAPI 2.0 profile specification developing there seems an opportunity for broader alignment to a whole-of-economy name change that indicates its utility and suitability to all secure open data use cases.

Given the prevalence of use of the FAPI acronym, any change away from the “financial-grade” terminology would need to retain the acronym. This ticket seeks input on the merits of a name change at this stage in the profile’s evolution and future uptake to industries beyond financial services.  
  
This ticket is seeking candidates and offers “Fortified APIs” as a potential option.

“Fortified” by definition seems suitably broad and applicable:

[\(1\)](https://www.merriam-webster.com/dictionary/fortified) made stronger or more secure  
[\(2\)](https://www.merriam-webster.com/dictionary/fortified) improved or enhanced  
[\(3\)](https://dictionary.cambridge.org/dictionary/english/fortify) to make something stronger, especially in order to protect it