API Spec Alignment with Commonalities and ICM - Release 1.1#69
Conversation
tanjadegroot
left a comment
There was a problem hiding this comment.
This looks good.
please ensure to check all updates in the changelog of Commonalities and of ICM for applicable items.
There was a problem hiding this comment.
General comment: for a developer who does not know what a BlockchainPublicAddress can be used for, maybe add an additional paragraph on what this API is about.
There was a problem hiding this comment.
Have added clarifications to the term BlockChain Public Address
|
Please @grgpapadopoulos, @tanjadegroot take a look. |
| # Authorization and authentication | ||
|
|
||
| The "Camara Security and Interoperability Profile" provides details on how a client requests an access token. Please refer to Identify and Consent Management (https://github.com/camaraproject/IdentityAndConsentManagement/) for the released version of the Profile. | ||
| The "Camara Security and Interoperability Profile" provides details of how an API consumer requests an access token. Please refer to Identity and Consent Management (https://github.com/camaraproject/IdentityAndConsentManagement/) for the released version of the profile. |
There was a problem hiding this comment.
Identity and Consent Management (https://github.com/camaraproject/IdentityAndConsentManagement/)
-->
Identity and Consent Management
so that it show as a nicer link.
There was a problem hiding this comment.
reviewing this to get latest text
There was a problem hiding this comment.
What type of PR is this?
What this PR does / why we need it:
API Spec alignement with Current Commonalities and ICM (Spring 25)
Which issue(s) this PR fixes:
Fixes #63
Special notes for reviewers:
Changelog input
Additional documentation
This section can be blank.