Skip to content
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

Closed
adrianhopebailie opened this issue Jan 23, 2016 · 5 comments

Comments

@adrianhopebailie
Copy link
Collaborator

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:

W3C Web Payments Term Common Terms ISO 20022 definition
Payee Merchant Creditor, Beneficiary
Payee PSP Acquirer, Gateway Acquirer, Intermediary
Payer Shopper, Consumer, User Debtor, Initiator
Payer PSP Wallet Intermediary
  • We will use the W3C Payments Terms in the W3C specifications (to avoid writing out in detail).
  • In the flows we would use the complete terms, however it should be realised that Common terms and ISO 20022 definitions may change between flows, for example for Direct Debit the ISO20022 term is Beneficiary, whilst for Credit Transfer it is Creditor.
  • We will endeavour to have the W3C Terms added to the ISO repository as reserved words or ideally as specific mappings, e.g. a Payee is the superclass of both the subclasses of Creditors and Beneficiary.
@msporny
Copy link
Member

msporny commented Jan 26, 2016

Sounds good. One extra bullet point to add to the proposal that makes it clear how these proposals get implemented in the specifications:

  • The W3C Web Payments Terms and their respective mappings to common terms and ISO20022 will be implemented in the Web Payments IG Glossary, which will be dynamically pulled into all WPWG specifications.

@dlongley
Copy link
Contributor

+1 to this proposal now

@bifurcation
Copy link

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.

@adrianhopebailie
Copy link
Collaborator Author

@msporny - edited to include your additonal bullet
@bifurcation - have you had a look at the high-level architecture?
https://github.com/w3c/webpayments/wiki/A-Payments-Initiation-Architecture-for-the-Web

@adrianhopebailie
Copy link
Collaborator Author

This proposal was RESOLVED during the 28 January meeting with the following addition as proposed by @msporny:

  • The W3C Web Payments Terms and their respective mappings to common terms and ISO20022 will be implemented in the Web Payments IG Glossary

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:

W3C Web Payments Term Common Terms ISO 20022 definition
Payee Merchant Creditor, Beneficiary
Payee PSP Acquirer, Gateway Acquirer, Intermediary
Payer Shopper, Consumer, User Debtor, Initiator
Payer PSP Wallet Intermediary
  • We will use the W3C Payments Terms in the W3C specifications (to avoid writing out in detail).
  • In the flows we will use the complete terms, however it should be realised that Common terms and ISO 20022 definitions may change between flows, for example for Direct Debit the ISO20022 term is Beneficiary, whilst for Credit Transfer it is Creditor.
  • We will endeavour to have the W3C Terms added to the ISO repository as reserved words or ideally as specific mappings, e.g. a Payee is the superclass of both the subclasses of Creditors and Beneficiary.
  • The W3C Web Payments Terms and their respective mappings to common terms and ISO20022 will be implemented in the Web Payments IG Glossary

@mountainhippo took an action to liaise with the IG and ensure the terms are part of their glossary
https://www.w3.org/Payments/WG/track/actions/12

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants