[browser-payment-api] Should Payment Method Identifiers and Messages be expressed using a Linked Data Vocabulary? (#45)

The [Payment Method Identifiers](http://wicg.github.io/paymentrequest/specs/method-identifiers.html) spec states:
> The PaymentRequest API requires that merchants supply a list identifiers for supported payment methods. This document defines those identifier strings and how they are created.

The [Payment Request Architecture](http://wicg.github.io/paymentrequest/specs/architecture.html) spec states:
> we expect some message definitions to be shared amongst different payment apps.

The two sets of spec proposals agree that:

* There should be a list of identifiers for payment methods.
* There should be shared attributes across payment apps and methods.
* There should be short names for payment methods.
* We should support distributed extensibility.

This sounds an awful lot like a Linked Data vocabulary. Is it?

This is related to #11.

Spec refs:
http://wicg.github.io/paymentrequest/specs/method-identifiers.html#introduction
http://web-payments.github.io/web-payments-messaging/#payment-instrument-registration

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/browser-payment-api/issues/45