Re: [browser-payment-api] Should Payment Method Identifiers and Messages be expressed using a Linked Data Vocabulary? (#45)

> Could you say more about what requirement(s) you have in mind?

The requirements are at the top of this issue. I'll re-state them again and link the 'keys' and 'values' text above to the requirements stated at the beginning of the issue:

* There should be a list of identifiers for payment methods ('values').
* There should be shared attributes ('keys') across payment apps and methods.
* There should be short names for payment methods ('values').
* We should support distributed extensibility.

We could also extend/refine those with more basic requirements for the payment messages like:

* identifiers (values) should use a universal identifier mechanism (e.g. URLs)
* there should be a way to disambiguate keys shared among different JSON documents (e.g. by mapping them to URLs in some way)
* support linking to data outside of the message (e.g. by using URLs to point to things like offers, images, etc.)
* support internationalization for data values (with the ability to support the expression of the data value in multiple languages in the same message - 'payment request in countries that have more than one "native" language')
* a way to associate datatypes with values (e.g. dates, times, currencies)

I agree that some of these are "nice-to-have"s, but some of them are "must have"s, and it'll be up to the WG to decide where that line is.

---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/browser-payment-api/issues/45#issuecomment-197931196