Re: [paymentrequest] Should well-known identifiers be used for ubiquitous payment methods (#35)

Here's an example of how we could do the registry for all terms, short strings, etc. that would go in payment messages (human readable and machine-readable as RDFa) - the link is live, go to it:

https://w3id.org/payments

and the machine-readable version of the registry (as JSON-LD), again, live link:

https://w3id.org/payments/v1

The example registry above:
 * Uses the w3id.org redirect service as a best practice - the final redirect location for the registry may change from time to time, but the links above could be used for the next 50+ years due to the w3id.org site's continuity plan.
 * Resolves to the Editor's Draft for the human-readable spec and web-payments.org for the machine-readable one. We'd update these once we hit production with v1 of the vocabulary and context.

These rules could be used for updating the human-readable vocabulary:
 * Adding new terms can be done by consensus in the WPWG and then the WPIG (if the WPWG dissolves). Terms would start at 'unstable', moving to 'proposed', then 'stable', and if terms fall out of favor 'deprecated'. We would probably never remove terms.

The machine-readable context would be updated like so:
 * The context is versioned by major number (v1, v2, v3, etc.)
 * Adding terms requires consensus and a 'stable' marker in the human-readable vocabulary.
 * Terms are never changed or removed once they are added to a particular context version (doing so would break deployed systems). 
 * Terms may be removed as you move from v1 to v2, etc.
 * Nothing would prevent developers from using full URLs where terms, like "Visa" are used.

None of what's said above wrt. the management of these registries should be controversial. They reflect best practices that have been refined over the past 10+ years in the Linked Data realm at W3C. As Shane said, we used many of these rules to manage the RDFa initial context and that's worked out pretty well so far (as far as managing the registry is concerned).

---
Reply to this email directly or view it on GitHub:
https://github.com/WICG/paymentrequest/issues/35#issuecomment-169543697