Re: [w3c/browser-payment-api] Identifiers or Locators (#150)

I also agree it should not be mandatory.  However, can we also agree that there is a way to craft the optional language to assist in ensuring that even optional things are predictable?  For example:

> A payment method MAY provide a machine readable definition.  When it does so, it MUST be done using one of the following formats [some list]. When using one of those formats, the following terms MAY be used [term list]

I am not saying we need to even develop this today.  Just that having this mechanism and a well defined set of terms (with associated data types) means payment method owners are able to inform payment applications of the sorts of things discussed earlier in this thread with a minimum of hassle.  Interoperability and Portability are the most important tools we can provide to a payment app developer.

---
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/150#issuecomment-213154775