ISO 3611-2 vs. CLDR #34
Comments
|
Note that I'm filing the issue on this spec, but that doesn't necessarily mean that this is the one that needs to change -- this may well be something that requires a change in the Payment API instead. What's important is consistency. |
ianbjacobs
added a commit
to ianbjacobs/webpayments-methods-credit-transfer-direct-debit
that referenced
this issue
Feb 7, 2017
ianbjacobs
added a commit
that referenced
this issue
Feb 7, 2017
* Added back supportedNetworks per issue 33 #33 And 2 Feb 2017 discussin https://www.w3.org/2017/02/02-wpay-minutes.html * Change ISO to CLDR to solve issue 34 #34
|
Changed to CLDR for consistency with PR API |
ianbjacobs
added a commit
that referenced
this issue
Mar 1, 2017
* Added back supportedNetworks per issue 33 #33 And 2 Feb 2017 discussin https://www.w3.org/2017/02/02-wpay-minutes.html * Change ISO to CLDR to solve issue 34 #34 * - Created new appendix for mappings - Moved SEPA mappings there - Added design note about authentication - Added note to supported networks that we are still working on how and whether to create a database.
ianbjacobs
added a commit
that referenced
this issue
Mar 1, 2017
* Added back supportedNetworks per issue 33 #33 And 2 Feb 2017 discussin https://www.w3.org/2017/02/02-wpay-minutes.html * Change ISO to CLDR to solve issue 34 #34 * - Created new appendix for mappings - Moved SEPA mappings there - Added design note about authentication - Added note to supported networks that we are still working on how and whether to create a database. * typo fix
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The
PaymentAddressinterface defined in the Payment API has acountryattribute that is defined as being the "the CLDR (Common Locale Data Repository) region code."This specification proposes using ISO3166-2 for the
CreditTransferRequest.supportedCountriesfield. While these are largely harmonized, they technically are different authorities, and I'm concerned about the prospect of having to deal with two different databases of largely the same information within a single body of specification.I don't have enough background to know whether there is a single specification that is favored for W3C specs. If so, we should ensure that all the payments work uses that. In the absence of such precedent, we should at least use only one authority within the payments-related specifications.
The text was updated successfully, but these errors were encountered: