[w3c/browser-payment-api] Registry Access/Handling Registry Change (#151)

why is the model that "registry snapshots" are created at odd URIs such as v1 and v2 and v3? it seems more logical, in case the idea is to allow machine-based access to the registry (which in itself is a tough design issue https://tools.ietf.org/html/draft-wilde-registries-01#section-5.5), that registry contents can always be retrieved, and represent the current status of the registry.
the registry should be designed in a way that (a) identifier semantics never change, and (b) there is a way to mark identifiers as being deprecated, so that in the worst case scenario, snapshots fail to correctly reflect a deprecated value.
this would allow developers to at least easily check if and how the registry has changed, and they would have an easy way how to review those changes, and possibly update their implementations to support the changes in the registry.

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