Re: [webpayments] How do organizations layer additional information in the core messages? (#18)

>From [Payment Request Architecture](http://wicg.github.io/paymentrequest/specs/architecture.html#payment-transaction-message-specifications)
> For example, we expect multiple different payment apps to support returning credit card PANs and **they should all do so using the same field names**.

This seems to imply either:

a) A registry of JSON field names, or
b) A JSON-LD context and Linked Data vocabulary that specifies those field names, their expected types, usage, etc.

Strong +1 for the latter, since there are many other considerations when attempting to create common registries and do decentralized extensibility other than just the names of the fields themselves. Lots of people have put a great deal of thought into **b)** after failing (to various degrees) at **a)**.


---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webpayments/issues/18#issuecomment-162345847