Skip to content

Update spec references. #53

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 5 commits into from
Aug 22, 2018
Merged

Update spec references. #53

merged 5 commits into from
Aug 22, 2018

Conversation

gkellogg
Copy link
Member

@gkellogg gkellogg commented Aug 21, 2018

…ing an external description of the diagram. The diagram is now maintained using Google Drawings.

Fixes #51
@gkellogg gkellogg self-assigned this Aug 21, 2018
@gkellogg gkellogg requested a review from iherman August 21, 2018 22:49
Copy link
Member

@iherman iherman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I find it strange what respec generates into the spec for an IDL reference

  • the 2016 version is the WebIDL 1.0 spec, and McCormack is its sole editor. If all we use is 1.0, that should work for us: https://www.w3.org/TR/WebIDL-1/
  • if we want to refer to the WebIDL 2.0 (I am not sure we can do that on long term, but it is fine in a spec), the URL is indeed https://heycam.github.io/webidl/, then we should call it explicitly webIDL 2.0, but then the date (2016) is incorrect. It is a "living standard", meaning that the date is irrelevant...

@gkellogg
Copy link
Member Author

I tried defining "WebIDL-1" and using it, but ReSpec emits standard references to WebIDL, so can't remove that. But, it sounds like the issue is with SpecRef not having the right definition for WebIDL, and the problem should be fixed there. We could override in our own local bibliography, but that doesn't change what ReSpec emits.

@gkellogg gkellogg merged commit fa14355 into master Aug 22, 2018
@gkellogg gkellogg deleted the update-references branch August 22, 2018 22:47
@iherman
Copy link
Member

iherman commented Aug 23, 2018

If we use our own bibliography with a different key, that should work.

But it is not urgent. These things become important when we get to a final document...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants