Make other Payments-drafts refs be absolute URLs #115
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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).