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

On 2016-04-21 16:15, Shane McCarron wrote:
> 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?

tricky in this case, i'd say. if you say that the identifiers are just 
that, then i would leave it at that. if you start defining a vocabulary 
that implementations might use *if* they choose to dereference the 
identifiers and *if* the returned representation matches that defined 
vocabulary, then you have to start defining how any metadata gleaned 
from that interacts with metadata from the registry. for example, if the 
registry defines a payment scheme to have the name "Apple Pay" but the 
representation defines a different name, which name wins? i am not sure 
that this added complexity is worth it, but ymmv.


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