Re: [w3c/browser-payment-api] Should a payment method identifier (URL) resolve to a machine readable resource that describes it? (#46)

This text was proposed as a set of requirements for content from resolved payment method identifiers:

```html
      <section>
        <h2>Content at Payment Method Identifier URLs</h2>
        <p>
          Payment method identifier URLs that resolve to content:
        </p>
        <ol>
          <li>MUST be served over HTTPS,</li>
          <li>SHOULD support HTTP Content Negotiation,</li>
          <li>SHOULD provide a human-readable document that describes the
          payment method when <code>text/html</code> is requested, and</li>
          <li>SHOULD provide a machine-readable document that describes the
          payment method when <code>application/ld+json</code> is requested.
          </li>
        </ol>
      </section>
```

---
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/46#issuecomment-218808573