(ed) Need to add JARM in the introductions

[Nat Sakimura]

Currently, it goes like:

Financial-grade API consists of the following parts:

• Part 1: Read-Only API Security Profile
• Part 2: Read and Write API Security Profile
• Client Initiated Backchannel Authentication Profile

Future parts may follow.

We need to add JARM. It does not have to be in this round, but we need to remember to update.

[Nat Sakimura]

Currently, it goes like:

Financial-grade API consists of the following parts:

• Part 1: Read-Only API Security Profile
• Part 2: Read and Write API Security Profile
• Client Initiated Backchannel Authentication Profile

Future parts may follow.

We need to add JARM. It does not have to be in this round, but we need to remember to update.

[Dave Tonge]

Dave to update intros

[Joseph Heenan]

pull request opened: https://bitbucket.org/openid/fapi/pull-requests/185/update-intros-to-mention-jarm/diff

[Dave Tonge]

Merged in update-intros (pull request #185)

Update intros to mention JARM

• Update intros to mention JARM

Generally made them consistent, and removed references to Pushed Request Object as that's now PAR in the IETF OAuth WG.

closes #166

• Update README.md

Remove Pushed Request Object, add Implementation & Deployment advice.

Approved-by: Dave Tonge

→ <<cset fa3159bca357>>