[Openid-specs-fapi] Renaming FAPI

[Mike Schwartz]

Ok, the just "Plus"

And we could say the "OpenID Plus" profile or "OpenID Plus Working 
Group"

- Mike


On 2018-04-10 15:02, Tom Jones wrote:
> its is a profile for an open id spec - why repeat openid over and over
> and over again this dance is going to be a drag.
> 
> openID protection provided for openID connect on top of openID OAuth?
> 
> Peace ..tom
> On Tue, Apr 10, 2018 at 12:33 PM, Mike Schwartz via Openid-specs-fapi
> <openid-specs-fapi at lists.openid.net> wrote:
> 
>> FAPI WG,
>> 
>> Putting "user" in the name might cause confusion with "User Managed
>> Access" (UMA).
>> 
>> Why wouldn't you want to leverage the existing "OpenID" Branding?
>> 
>> If not "OpenID Plus" then "OpenID ____"?
>> 
>> What strikes me about FAPI is that it's the most secure profile of
>> OpenID Connect, and can be used by the OP to increase assurance, and
>> the RP to increase protection. So "OpenID Plus" says it's basically
>> OpenID... with some extra stuff to make it extra secure.
>> 
>> - Mike
>> 
>> On 2018-04-10 14:16, Brian Campbell via Openid-specs-fapi wrote:
>> 
>> I also think a more broadly applicable term like "user" is
>> preferable
>> to "consumer".
>> 
>> Spitballing a few:
>> 
>> User Resource Protection
>> User Resource Protection Profiles
>> Enhanced User Resource Protection Profiles
>> 
>> On Tue, Apr 10, 2018 at 10:08 AM, Tom Jones via Openid-specs-fapi
>> <openid-specs-fapi at lists.openid.net> wrote:
>> 
>> i prefer the term "user" as it is broader.
>> 
>> How about
>> User Protection Profiles
>> 
>> Peace ..tom
>> 
>> On Tue, Apr 10, 2018 at 8:30 AM, Sarah Squire via Openid-specs-fapi
>> <openid-specs-fapi at lists.openid.net> wrote:
>> 
>> Hey Folks,
>> 
>> At the last OpenID Foundation Board meeting, the board agreed that
>> since FAPI is not limited to the financial sector and does not
>> proscribe API designs, it should be renamed.
>> 
>> The fundamental thing that differentiates the OpenID Foundation's
>> OpenAPI working groups is that they focus on consumer-facing
>> ecosystems as opposed to enterprise, so we could focus it in that
>> direction.
>> 
>> Instead of saying API, we could say something like resource or
>> protected resource.
>> 
>> How about
>> 
>> Consumer Resource Protection (CRP)
>> 
>> Delegated Resource Access for Consumer-facing Operators (DRACO)
>> 
>> Delegated Protection of Consumer Resources (DPCR)
>> 
>> Thoughts?
>> 
>> Sarah
>> 
>> PS I work for Ping Identity. Sending this from an old email
>> address because of IPR/mailing list issues.
>> 
>> _______________________________________________
>> Openid-specs-fapi mailing list
>> Openid-specs-fapi at lists.openid.net
>> http://lists.openid.net/mailman/listinfo/openid-specs-fapi [1] [1]
>> 
>> _______________________________________________
>> Openid-specs-fapi mailing list
>> Openid-specs-fapi at lists.openid.net
>> http://lists.openid.net/mailman/listinfo/openid-specs-fapi [1] [1]
> 
> _CONFIDENTIALITY NOTICE: This email may contain confidential and
> privileged material for the sole use of the intended recipient(s). Any
> review, use, distribution or disclosure by others is strictly
> prohibited.  If you have received this communication in error, please
> notify the sender immediately by e-mail and delete the message and any
>  file attachments from your computer. Thank you._
> 
> Links:
> ------
> [1] http://lists.openid.net/mailman/listinfo/openid-specs-fapi [1]
> _______________________________________________
> Openid-specs-fapi mailing list
> Openid-specs-fapi at lists.openid.net
> http://lists.openid.net/mailman/listinfo/openid-specs-fapi [1]
> 
>  _______________________________________________
> Openid-specs-fapi mailing list
> Openid-specs-fapi at lists.openid.net
> http://lists.openid.net/mailman/listinfo/openid-specs-fapi [1]
> 
> 
> 
> Links:
> ------
> [1] http://lists.openid.net/mailman/listinfo/openid-specs-fapi