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

the current options seem to also consider options where dereferencing identifiers becomes part of the standardized way of using them. whatever is chosen in the end, the spec should be very clear about whether the identifiers are actually identifiers (communicating meaning through their usage), or locators (communicating a way how to extract meaning at runtime). in particular, in a high-volume scenario such as payments the implications of implementations dereferencing payment identifiers should be considered.
it is essential that identifiers have a clear model of either having an assigned and stable meaning, or being opaque addresses that must be dereferenced to obtain the meaning represented by them: https://tools.ietf.org/html/draft-wilde-registries-01#section-3.5

---
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