-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PROPOSAL: Adopt developer friendly-terminology for WG deliverables but root this in ISO20022 data dictionary through our published glossary. #67
Comments
Sounds good. One extra bullet point to add to the proposal that makes it clear how these proposals get implemented in the specifications:
|
+1 to this proposal now |
This looks fine to me. It's not totally clear to me how this will map to roles in a Web API interaction, but I suppose that will become clearer as the API solidifies. |
@msporny - edited to include your additonal bullet |
This proposal was RESOLVED during the 28 January meeting with the following addition as proposed by @msporny:
The group also noted that all WG specs SHOULD reference the IG glossary but elected to not include this as an explicit dependency in the proposal. The final resolution was: The WG will adopt the following terms for use in its deliverables:
@mountainhippo took an action to liaise with the IG and ensure the terms are part of their glossary |
Follows discussion of the question at #59.
PROPOSAL (from @mattsaxon )
In keeping with the WG resolution to try and root our terminology in the ISO20022 data dictionary the WG will adopt the following terms for use in its deliverables:
The text was updated successfully, but these errors were encountered: