Re: [w3c/browser-payment-api] Update to method identifiers spec to use absolute URLs (#183)

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

This section on information for payment method identifiers that do happen to resolve to content shouldn't be completely removed just because we settled on using absolute URLs. This is still an additional option under consideration.

---
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/pull/183/files/f025f4153504c821a07e03745ea0b9900f64ecbe#r63029809