[w3c/browser-payment-api] Make other Payments-drafts refs be absolute URLs (#115)

I don’t think we’re going to be allowed to publish the API FPWD with relative URLs in the References section. The URLs need to absolute. And when we publish the FPWDs of the specs, they are not going to be relative to one other in the same way but instead will each of their own shortname under `www.w3.org/TR/`

We’re allowed to list EDs in the References section, so I suggest we just put the ED URLs and keep them until the point in the W3C process where we need to reference the `www.w3.org/TR/` equivalents (which I think will not be strictly necessary until the specs go to Rec). 
You can view, comment on, or merge this pull request online at:

  https://github.com/w3c/browser-payment-api/pull/115

-- Commit Summary --

  * Make other Payments-drafts refs be absolute URLs

-- File Changes --

    M specs/paymentrequest.html (4)

-- Patch Links --

https://github.com/w3c/browser-payment-api/pull/115.patch
https://github.com/w3c/browser-payment-api/pull/115.diff

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