<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Hi all,<br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Am 19.02.20 um 16:34 schrieb Dave Tonge
via Openid-specs-fapi:<br>
</div>
<blockquote type="cite"
cite="mid:CAP-T6TQQZ3_jyEKSL6Mpt-6rwO4UF_nuQ0i2+qAg2a2_gAwZyg@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">1. The current "Financial-grade API - Part 1:
Read-Only API Security Profile" (FAPI Read) spec should be
changed to "<span style="font-family:Arial,Helvetica,sans-serif">Financial-grade
API 1.0 - Part 1: Read-Only API Security Profile (FAPI 1.0
Read)</span>
<div class="gmail_default" style="font-family:trebuchet
ms,sans-serif">2. The current "Financial-grade API - Part 2:
Read and Write API Security Profile" (FAPI Read/Write) spec
should be changed to "<span
style="font-family:Arial,Helvetica,sans-serif">Financial-grade
API 1.0 - Part 2: Read and Write API Security Profile (FAPI
1.0 Read/Write)</span><span
style="font-family:Arial,Helvetica,sans-serif"><br>
</span></div>
<div class="gmail_default" style="font-family:trebuchet
ms,sans-serif"><span
style="font-family:Arial,Helvetica,sans-serif">3. We
introduce two new documents:</span></div>
<div class="gmail_default" style="font-family:trebuchet
ms,sans-serif"><span
style="font-family:Arial,Helvetica,sans-serif"> - </span><span
style="font-family:Arial,Helvetica,sans-serif">Financial-grade
API 2.0 - Basic Security Profile" (FAPI 2.0 Basic)</span></div>
<div class="gmail_default" style="font-family:trebuchet
ms,sans-serif"><span
style="font-family:Arial,Helvetica,sans-serif"> - </span><span
style="font-family:Arial,Helvetica,sans-serif">Financial-grade
API 2.0 - Advanced Security Profile" (FAPI 2.0 Advanced)</span><span
style="font-family:Arial,Helvetica,sans-serif"><br>
</span></div>
</div>
</blockquote>
<p><br>
</p>
<p>I think that it would also make sense to move from
"Financial-grade API" to using just the abbreviation "FAPI" in
newer documents. "Financial" has already become "Financial-grade"
(for good reasons), and "API" has shifted to "API Security
Profile". <br>
</p>
<p>This way, we could preserve the brand "FAPI" while at the same
time taking the focus away from "financial" and "API".</p>
<p>What do you think?</p>
-Daniel<br>
</body>
</html>