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

Excellent point.  

I know that smart people have thought about this a lot. And I am probably treading on well-worn ground, but...

What if:
- identifiers are "reverse domain names" that are just strings and compared as such
- there is a "registry" into which people with such identifiers are allowed to map the identifier to a "locator"
- there is a web service that a payment app (or anyone) could hit to check if there is a mapping for an identifier; and if so retrieve that mapping
- dereferencing the locator returns a document (via conneg) that has the rules you mentioned; stability, persistence, interrogation, evolution, structure

I am sure there are arguments against a list and a non-list, but I don't know what they are.  Is this over complex?  I like applications that are able to discover new information without an update.  Heck, one of the terms in the vocabulary of a document could be the "next update time"; basically an expiration in time certain for the information about the payment method.

Thoughts?

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