Skip to content

Conversation

@gkellogg
Copy link
Member

Remaining issues targeted for the "JSON-LD 1.1 CG" milestone need to be marked as deferred.

@gkellogg gkellogg requested review from azaroth42 and iherman April 28, 2018 16:00
@gkellogg
Copy link
Member Author

I need to update the bibliography which uses https://json-ld.org/spec/latest/ for the location of the specs, which won't be their published locations. I'll change while generating to https://json-ld.org/spec/CG-FINAL/json-ld/20180507/ with variations for the other specs.

@davidlehn
Copy link
Member

There's a markup problem in the generated api and framing docs with whitespace in ids and hrefs. Perhaps a bug with respec not doing proper escaping? For instance, the JsonLdErrorCode section has hrefs and ids like:

<a href="#dom-jsonlderrorcode-colliding keywords" class="idlEnumItem">"colliding keywords"</a>
...
<dt><dfn data-dfn-for="jsonlderrorcode" data-dfn-type="dfn" id="dom-jsonlderrorcode-colliding keywords" ...><code>colliding keywords</code></dfn></dt>

@gkellogg
Copy link
Member Author

gkellogg commented May 2, 2018

Generated ReSpec issue for the whitespace: w3c/respec#1650. I'll fix manually for the snapshot.

@gkellogg
Copy link
Member Author

@azaroth42 these should have been published last week, and need to go on the CG Wiki.

@azaroth42
Copy link
Contributor

Should I merge?

@gkellogg
Copy link
Member Author

gkellogg commented Jun 7, 2018

I'm validating before merge, I'll merge.

@gkellogg gkellogg merged commit 2144b38 into master Jun 7, 2018
@gkellogg gkellogg deleted the final-cg-reports branch June 7, 2018 21:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants