Renaming Operations ‘ participants’ resource

[NicoDuvenage]

Request:

Renaming Operations ‘participants’ resource to something better (anything other than participants - may be '/fsproviders', '/serviceProviders', ‘ /fsps ’ ?) that would lead to less confusion [I think right now, someone may ask - "What does this participants do and what does that participants do?", "Why do we have two participants end-points?", "Can we use both or either?"]. This request is just to give some clarity to this issue.

Description of the issue:

• In the Operations/Admin API for a Mojaloop Hub/Switch we have a ‘ /participants ’ resource for on-boarding FSPs to the Mojaloop system. There is a POST method (details in the API) for registering FSPs, only after which FSPs can register endpoints, set limits and perform funds-in, etc. (There are other on-boarding steps as well, which is another topic of discussion).
• However, there is another /participants resource, that is actually in the Mojaloop Specification, that is part of account-lookup. This resource is intended to be used to register (using POST) parties (end-users) of FSPs to an ALS (thats either part of the Switch or separately hosted) and to find out - to which FSP a party belongs to (using GET /participants/{Type}/{ID} or using SubId). And this was rolled out with the v1.0 of the Spec, so it was there before the operations endpoint was drafted.
• The current proposal is to rename the operations (or admin) 'participants' resource to something else (may be ‘ fsps ’) (or something better - anything other than participants) to avoid confusion since both resources have POST methods. [While also understanding that this is not incorrect technically.]
• Another reason is that the Mojaloop FSPIOP API is relatively standardized and published whereas the Operations / Admin API is not there, yet and so there is still some flexibility here.

Artifacts:

• [ ] Artifact to consider [@Contributor]

Decision(s):

• [ ] Actual decision made as a result of discussion

Follow-up:

• [ ] Alternative actions

Dependencies:

• [ ] If Applicable

Accountability:

• Owner:

Notes:

[elnyry-sam-k]

Not a fan of saying "I told you so", but below is in fact the reason why I brought this up - a year ago.