JSON-LD Working Group - Activity in 2019
No matches.
TR publications
-
3 documents published.
-
JSON-LD 1.1 published as a Candidate Recommendation Snapshot. History of JSON-LD 1.1
-
JSON-LD 1.1 Framing published as a Candidate Recommendation Snapshot. History of JSON-LD 1.1 Framing
-
JSON-LD 1.1 Processing Algorithms and API published as a Candidate Recommendation Snapshot. History of JSON-LD 1.1 Processing Algorithms and API
-
GitHub
w3c/json-ld-api
-
28 issues opened.
-
Issue with expansion of null @value values. w3c/json-ld-api#292, by @kasei.
-
Wrong variable use in Expansion handling of @index maps w3c/json-ld-api#290, by @kasei.
-
Issue with dropping @language-only objects during expansion w3c/json-ld-api#284, by @kasei.
-
Improve Object to RDF Conversion language regarding datatype well-formedness w3c/json-ld-api#282, by @kasei.
-
Accidental variable override in Deserialize JSON-LD to RDF Algorithm 1.2 w3c/json-ld-api#281, by @kasei.
-
Typo in Node Map Generation 6.11 w3c/json-ld-api#280, by @kasei.
-
Extraneous step in Deserialize JSON-LD to RDF Algorithm? w3c/json-ld-api#278, by @kasei.
-
Missing variable definition in Object to RDF Conversion w3c/json-ld-api#277, by @kasei.
-
Undefined variable in Node Map Generation w3c/json-ld-api#276, by @kasei.
-
Possible bug in Expansion Algorithm step 13.4.16 w3c/json-ld-api#270, by @kasei.
-
Problem testing non-expanded value in Expansion algorithm 13.4.7.1 w3c/json-ld-api#269, by @kasei.
-
Problematic/confusing algorithm text re: the handling of URL @context values w3c/json-ld-api#265, by @kasei.
-
Issue with Expansion handling of type maps and @none w3c/json-ld-api#264, by @kasei.
-
Possible error in Expansion Algorithm handling of nesting values (13.15) w3c/json-ld-api#262, by @kasei.
-
Incomplete conditional when determining error case in Create Term Definition w3c/json-ld-api#261, by @kasei.
-
Markup missing for variable in Create Term Definition w3c/json-ld-api#260, by @kasei.
-
Error in Create Term Definition relating to test ttn02 and handling of @none w3c/json-ld-api#259, by @kasei.
-
Expand test manifest typo for tin01 w3c/json-ld-api#254, by @kasei.
-
Expand test manifest typos for tm015 and tm016 w3c/json-ld-api#253, by @kasei.
-
Issue with type-scoped contexts propagation w3c/json-ld-api#246, by @kasei.
-
Possible problem with Create Term Definition algorithm on compact IRI terms w3c/json-ld-api#245, by @kasei.
-
XHTML support in HTML script extraction w3c/json-ld-api#244, by @ByteEater-pl.
-
Duplicated content in Expansion algorithm steps w3c/json-ld-api#243, by @kasei.
-
Issue with @container arrays w3c/json-ld-api#242, by @kasei.
-
Branching logic issue in Create Term Definition step 16 w3c/json-ld-api#241, by @kasei.
-
Add test for JSON-LD inside a JSON literal. w3c/json-ld-api#237, by @davidlehn.
-
The propagate option to Create Term Definition is unused. w3c/json-ld-api#233, by @gkellogg.
-
-
14 issues closed.
-
Possible error in Expansion Algorithm handling of nesting values (13.15) w3c/json-ld-api#262.
-
Typo in Node Map Generation 6.11 w3c/json-ld-api#280.
-
Error in Create Term Definition relating to test ttn02 and handling of @none w3c/json-ld-api#259.
-
Incomplete conditional when determining error case in Create Term Definition w3c/json-ld-api#261.
-
Markup missing for variable in Create Term Definition w3c/json-ld-api#260.
-
Add test for JSON-LD inside a JSON literal. w3c/json-ld-api#237.
-
Issue with type-scoped contexts propagation w3c/json-ld-api#246.
-
Possible problem with Create Term Definition algorithm on compact IRI terms w3c/json-ld-api#245.
-
XHTML support in HTML script extraction w3c/json-ld-api#244.
-
Duplicated content in Expansion algorithm steps w3c/json-ld-api#243.
-
Issue with @container arrays w3c/json-ld-api#242.
-
Expand test manifest typos for tm015 and tm016 w3c/json-ld-api#253.
-
Expand test manifest typo for tin01 w3c/json-ld-api#254.
-
The propagate option to Create Term Definition is unused. w3c/json-ld-api#233.
-
-
2 issues reopened.
-
Add test for JSON-LD inside a JSON literal. w3c/json-ld-api#237, by @gkellogg.
-
XHTML support in HTML script extraction w3c/json-ld-api#244, by @iherman.
-
-
26 issues received 134 new comments.
-
Branching logic issue in Create Term Definition step 16 w3c/json-ld-api#241 (13 comments by @gkellogg, @iherman, @kasei)
-
Possible bug in Expansion Algorithm step 13.4.16 w3c/json-ld-api#270 (10 comments by @gkellogg, @kasei)
-
Possible error in Expansion Algorithm handling of nesting values (13.15) w3c/json-ld-api#262 (10 comments by @gkellogg, @iherman, @kasei)
-
Problematic/confusing algorithm text re: the handling of URL @context values w3c/json-ld-api#265 (9 comments by @dlongley, @gkellogg, @kasei)
-
XHTML support in HTML script extraction w3c/json-ld-api#244 (8 comments by @azaroth42, @ByteEater-pl, @gkellogg, @iherman)
-
Issue with @container arrays w3c/json-ld-api#242 (8 comments by @gkellogg, @iherman, @kasei, @pchampin)
-
Problem testing non-expanded value in Expansion algorithm 13.4.7.1 w3c/json-ld-api#269 (7 comments by @gkellogg, @kasei)
-
Add test for JSON-LD inside a JSON literal. w3c/json-ld-api#237 (6 comments by @davidlehn, @dlongley, @gkellogg, @iherman)
-
Issue with Expansion handling of type maps and @none w3c/json-ld-api#264 (5 comments by @gkellogg, @kasei)
-
Error in Create Term Definition relating to test ttn02 and handling of @none w3c/json-ld-api#259 (5 comments by @gkellogg, @iherman, @kasei)
-
Issue with type-scoped contexts propagation w3c/json-ld-api#246 (5 comments by @gkellogg, @iherman, @kasei)
-
Possible problem with Create Term Definition algorithm on compact IRI terms w3c/json-ld-api#245 (5 comments by @gkellogg, @iherman, @kasei)
-
Markup missing for variable in Create Term Definition w3c/json-ld-api#260 (5 comments by @gkellogg, @iherman, @kasei)
-
Missing variable definition in Object to RDF Conversion w3c/json-ld-api#277 (4 comments by @gkellogg, @kasei)
-
Duplicated content in Expansion algorithm steps w3c/json-ld-api#243 (4 comments by @gkellogg, @iherman, @kasei)
-
Wrong variable use in Expansion handling of @index maps w3c/json-ld-api#290 (3 comments by @gkellogg, @kasei)
-
Extraneous step in Deserialize JSON-LD to RDF Algorithm? w3c/json-ld-api#278 (3 comments by @gkellogg, @kasei)
-
Incomplete conditional when determining error case in Create Term Definition w3c/json-ld-api#261 (3 comments by @gkellogg, @iherman, @kasei)
-
Accidental variable override in Deserialize JSON-LD to RDF Algorithm 1.2 w3c/json-ld-api#281 (2 comments by @gkellogg, @kasei)
-
Improve Object to RDF Conversion language regarding datatype well-formedness w3c/json-ld-api#282 (2 comments by @gkellogg, @kasei)
-
Mixed use of "append" and "add" in reference to an RdfGraph in Deserialize JSON-LD to RDF Algorithm w3c/json-ld-api#279 (2 comments by @gkellogg, @kasei)
-
Issue with dropping @language-only objects during expansion w3c/json-ld-api#284 (2 comments by @gkellogg, @kasei)
-
The propagate option to Create Term Definition is unused. w3c/json-ld-api#233 (1 comment by @iherman)
-
-
33 pull requests opened.
-
Return early in step 15.3 of expansion algorithm. w3c/json-ld-api#293, by @gkellogg.
-
Update expansion of property indexes. w3c/json-ld-api#291, by @gkellogg.
-
Add some notes to Context Processing algorithm for strings. w3c/json-ld-api#289, by @gkellogg.
-
Rework Create Term Definition step 16 (again) w3c/json-ld-api#288, by @gkellogg.
-
Changed step 18 of the Expansion algorithm to return `null` w3c/json-ld-api#287, by @gkellogg.
-
To RDF improvements w3c/json-ld-api#286, by @gkellogg.
-
Improve step 3 of the node map generation algorithm. w3c/json-ld-api#285, by @gkellogg.
-
Adds tests for null json literals, and fixes one expected result w3c/json-ld-api#283, by @gkellogg.
-
Update expansion to expand _input type_ before comparing with `@type`. w3c/json-ld-api#275, by @gkellogg.
-
Improve wording in Expansion on type-maps. w3c/json-ld-api#274, by @gkellogg.
-
Change inline note to block note in Create Term Definition step 16. w3c/json-ld-api#273, by @gkellogg.
-
Move expansion step 13.15 to out of the loop to step 14. w3c/json-ld-api#272, by @gkellogg.
-
"the value" => "_value_". w3c/json-ld-api#271, by @gkellogg.
-
add missing `@none` in step 13.4, addressing #259 w3c/json-ld-api#268, by @pchampin.
-
added missing keywords in step 28 (Create Term Definition) w3c/json-ld-api#267, by @pchampin.
-
Improve fix to #241 w3c/json-ld-api#266, by @pchampin.
-
Add test for JSON literal with a context. w3c/json-ld-api#263, by @gkellogg.
-
Add test for JSON literal with a context. w3c/json-ld-api#257, by @davidlehn.
-
Align expand and toRdf js tests. w3c/json-ld-api#256, by @davidlehn.
-
Manifest typos w3c/json-ld-api#255, by @gkellogg.
-
Pass `false` for _propagate_ when expanding and adding a type-scoped context w3c/json-ld-api#252, by @gkellogg.
-
Update Create Term Definition to set defined[term] to true in 16.5. w3c/json-ld-api#251, by @gkellogg.
-
Add text on handling application/xhtml+xml. w3c/json-ld-api#250, by @gkellogg.
-
Remove duplicated text in the expansion algorithm. w3c/json-ld-api#249, by @gkellogg.
-
Clarify that `@graph` may be used with `@set` … w3c/json-ld-api#248, by @gkellogg.
-
Clarify 16.1 in Create Term Definition to satisfy #241. w3c/json-ld-api#247, by @gkellogg.
-
Add toRdf JSON literal alias tests. w3c/json-ld-api#240, by @davidlehn.
-
Add value alias test similar to e029. w3c/json-ld-api#239, by @davidlehn.
-
Add JSON literal alias tests. w3c/json-ld-api#238, by @davidlehn.
-
Remove unused _propagate_ argument to Create Term Definition w3c/json-ld-api#236, by @gkellogg.
-
Add paragraph to abstract on 1.0 compatibility. w3c/json-ld-api#235, by @gkellogg.
-
Fix typos in tests/manifest.html and template.haml w3c/json-ld-api#234, by @fsteeg.
-
Add missing mention of `@json` in create term definitions w3c/json-ld-api#232, by @fsteeg.
-
-
33 pull requests merged.
-
Rework Create Term Definition step 16 (again) w3c/json-ld-api#288.
-
Update expansion of property indexes. w3c/json-ld-api#291.
-
Return early in step 15.3 of expansion algorithm. w3c/json-ld-api#293.
-
Improve step 3 of the node map generation algorithm. w3c/json-ld-api#285.
-
Add some notes to Context Processing algorithm for strings. w3c/json-ld-api#289.
-
Adds tests for null json literals, and fixes one expected result w3c/json-ld-api#283.
-
Changed step 18 of the Expansion algorithm to return `null` w3c/json-ld-api#287.
-
To RDF improvements w3c/json-ld-api#286.
-
Update expansion to expand _input type_ before comparing with `@type`. w3c/json-ld-api#275.
-
Move expansion step 13.15 to out of the loop to step 14. w3c/json-ld-api#272.
-
Change inline note to block note in Create Term Definition step 16. w3c/json-ld-api#273.
-
Improve wording in Expansion on type-maps. w3c/json-ld-api#274.
-
"the value" => "_value_". w3c/json-ld-api#271.
-
add missing `@none` in step 13.4, addressing #259 w3c/json-ld-api#268.
-
added missing keywords in step 28 (Create Term Definition) w3c/json-ld-api#267.
-
Improve fix to #241 w3c/json-ld-api#266.
-
Add test for JSON literal with a context. w3c/json-ld-api#263.
-
Pass `false` for _propagate_ when expanding and adding a type-scoped context w3c/json-ld-api#252.
-
Add text on handling application/xhtml+xml. w3c/json-ld-api#250.
-
Align expand and toRdf js tests. w3c/json-ld-api#256.
-
Update Create Term Definition to set defined[term] to true in 16.5. w3c/json-ld-api#251.
-
Manifest typos w3c/json-ld-api#255.
-
Remove duplicated text in the expansion algorithm. w3c/json-ld-api#249.
-
Clarify that `@graph` may be used with `@set` … w3c/json-ld-api#248.
-
Clarify 16.1 in Create Term Definition to satisfy #241. w3c/json-ld-api#247.
-
Add toRdf JSON literal alias tests. w3c/json-ld-api#240.
-
Add value alias test similar to e029. w3c/json-ld-api#239.
-
Add JSON literal alias tests. w3c/json-ld-api#238.
-
Remove unused _propagate_ argument to Create Term Definition w3c/json-ld-api#236.
-
Add paragraph to abstract on 1.0 compatibility. w3c/json-ld-api#235.
-
Fix typos in tests/manifest.html and template.haml w3c/json-ld-api#234.
-
Add missing mention of `@json` in create term definitions w3c/json-ld-api#232.
-
Context resolution w3c/json-ld-api#230.
-
-
1 pull request closed.
-
Add test for JSON literal with a context. w3c/json-ld-api#257.
-
-
20 pull requests received 44 new comments.
-
Clarify 16.1 in Create Term Definition to satisfy #241. w3c/json-ld-api#247 (6 comments by @davidlehn, @gkellogg, @iherman, @kasei)
-
added missing keywords in step 28 (Create Term Definition) w3c/json-ld-api#267 (5 comments by @davidlehn, @gkellogg)
-
add missing `@none` in step 13.4, addressing #259 w3c/json-ld-api#268 (2 comments by @davidlehn, @gkellogg)
-
w3c/json-ld-api#258 (2 comments by @gkellogg)
-
Update Create Term Definition to set defined[term] to true in 16.5. w3c/json-ld-api#251 (2 comments by @davidlehn, @gkellogg)
-
Remove duplicated text in the expansion algorithm. w3c/json-ld-api#249 (2 comments by @iherman, @kasei)
-
Clarify that `@graph` may be used with `@set` … w3c/json-ld-api#248 (2 comments by @iherman, @kasei)
-
Adds tests for null json literals, and fixes one expected result w3c/json-ld-api#283 (1 comment by @davidlehn)
-
Change inline note to block note in Create Term Definition step 16. w3c/json-ld-api#273 (1 comment by @kasei)
-
Pass `false` for _propagate_ when expanding and adding a type-scoped context w3c/json-ld-api#252 (1 comment by @pchampin)
-
Add missing mention of `@json` in create term definitions w3c/json-ld-api#232 (1 comment by @fsteeg)
-
w3c/json-ld-framing
-
1 issue opened.
-
Clarify example for omit graph flag w3c/json-ld-framing#88, by @Fak3.
-
-
1 issue received 4 new comments.
-
Clarify example for omit graph flag w3c/json-ld-framing#88 (4 comments by @Fak3, @gkellogg, @iherman)
-
-
3 pull requests opened.
-
Improve omit graph flag example discussion w3c/json-ld-framing#91, by @gkellogg.
-
Update baseIri to json-ld-framing w3c/json-ld-framing#89, by @fsteeg.
-
Add paragraph to abstract on 1.0 compatibility. w3c/json-ld-framing#87, by @gkellogg.
-
-
3 pull requests merged.
-
Improve omit graph flag example discussion w3c/json-ld-framing#91.
-
Update baseIri to json-ld-framing w3c/json-ld-framing#89.
-
Add paragraph to abstract on 1.0 compatibility. w3c/json-ld-framing#87.
-
-
3 pull requests received 3 new comments.
-
w3c/json-ld-framing#90 (1 comment by @gkellogg)
-
w3c/json-ld-wg
-
3 issues opened.
-
2019-12-20-action1: update json-ld vocabulary at ns/json-ld (Gregg Kellogg) w3c/json-ld-wg#134, by @iherman.
-
2019-12-13-action1: make google doc to co-edit, to be posted next week (Benjamin Young) w3c/json-ld-wg#133, by @iherman.
-
2019-12-06-action1: add values discussion to BP#19 (Rob Sanderson) w3c/json-ld-wg#132, by @iherman.
-
-
3 issues closed.
-
"Contributing" sections. w3c/json-ld-wg#131.
-
2019-12-06-action1: add values discussion to BP#19 (Rob Sanderson) w3c/json-ld-wg#132.
-
3 issues received 4 new comments.
-
2019-12-13-action1: make google doc to co-edit, to be posted next week (Benjamin Young) w3c/json-ld-wg#133 (2 comments by @azaroth42, @gkellogg)
-
2019-12-06-action1: add values discussion to BP#19 (Rob Sanderson) w3c/json-ld-wg#132 (1 comment by @azaroth42)
-
-
1 pull request opened.
-
Update JSON-LD vocabulary. w3c/json-ld-wg#135, by @gkellogg.
-
w3c/json-ld-syntax
-
1 issue opened.
-
Why xsd:double? Why not xsd:decimal? w3c/json-ld-syntax#318, by @dr-shorthair.
-
-
3 issues closed.
-
Why xsd:double? Why not xsd:decimal? w3c/json-ld-syntax#318.
-
Flagging an action for CR (RDF vocabulary file update) w3c/json-ld-syntax#263.
-
@context as relative IRI w3c/json-ld-syntax#311.
-
-
4 issues received 24 new comments.
-
Why xsd:double? Why not xsd:decimal? w3c/json-ld-syntax#318 (10 comments by @dr-shorthair, @gkellogg, @iherman, @pchampin)
-
Flagging an action for CR (RDF vocabulary file update) w3c/json-ld-syntax#263 (10 comments by @davidlehn, @gkellogg, @iherman, @swickr, @TallTed)
-
-
3 pull requests opened.
-
proposed note to address #318 w3c/json-ld-syntax#319, by @pchampin.
-
Describe resolution of remote context documents using relative URLs. w3c/json-ld-syntax#317, by @gkellogg.
-
Add paragraph to abstract on 1.0 compatibility. w3c/json-ld-syntax#316, by @gkellogg.
-
-
3 pull requests merged.
-
proposed note to address #318 w3c/json-ld-syntax#319.
-
Describe resolution of remote context documents using relative URLs. w3c/json-ld-syntax#317.
-
Add paragraph to abstract on 1.0 compatibility. w3c/json-ld-syntax#316.
-
-
3 pull requests received 5 new comments.
-
Describe resolution of remote context documents using relative URLs. w3c/json-ld-syntax#317 (2 comments by @pchampin)
-
w3c/json-ld-syntax#320 (1 comment by @gkellogg)
w3c/json-ld-bp
-
7 issues opened.
-
Example for cache control (§6.1) w3c/json-ld-bp#24, by @iherman.
-
Example 5? w3c/json-ld-bp#23, by @iherman.
-
Name in the example w3c/json-ld-bp#22, by @iherman.
-
References to other documents w3c/json-ld-bp#21, by @iherman.
-
Best practices for maintaining list order w/o collections. w3c/json-ld-bp#20, by @hsolbrig.
-
Avoid CURIEs in the data w3c/json-ld-bp#19, by @dlongley.
-
Semantic lifting tutorial w3c/json-ld-bp#18, by @ajs6f.
-
-
1 issue closed.
-
Question about good practice for @id w3c/json-ld-bp#7.
-
-
1 issue reopened.
-
Add example on order impact on @protected w3c/json-ld-bp#2, by @ajs6f.
-
-
10 issues received 36 new comments.
-
Best practices for maintaining list order w/o collections. w3c/json-ld-bp#20 (10 comments by @ajs6f, @hsolbrig, @iherman)
-
Avoid CURIEs in the data w3c/json-ld-bp#19 (6 comments by @ajs6f, @azaroth42, @BigBlueHat, @dlongley)
-
Question about good practice for @id w3c/json-ld-bp#7 (3 comments by @cristianvasquez, @iherman, @pchampin)
-
-
2 pull requests opened.
-
Emphasize JSON instead of data publishing w3c/json-ld-bp#26, by @ajs6f.
-
Minor editorial thingies w3c/json-ld-bp#25, by @iherman.
-
-
1 pull request merged.
-
Emphasize JSON instead of data publishing w3c/json-ld-bp#26.
-
-
2 pull requests received 4 new comments.
TR publications
-
3 documents published.
-
JSON-LD 1.1 Framing published as a Working Draft. History of JSON-LD 1.1 Framing
-
JSON-LD 1.1 published as a Working Draft. History of JSON-LD 1.1
-
JSON-LD 1.1 Processing Algorithms and API published as a Working Draft. History of JSON-LD 1.1 Processing Algorithms and API
-
Participants
-
1 participant joined.
-
Eric Prud'hommeaux (W3C) joined.
-
GitHub
w3c/json-ld-api
-
20 issues opened.
-
Meaning of tests with only specVersion w3c/json-ld-api#227, by @rubensworks.
-
Tests with invalid keyword expect error w3c/json-ld-api#226, by @rubensworks.
-
Test input file `expand/e051-in.jsonld` is missing w3c/json-ld-api#225, by @lo48576.
-
Confusing links for definition of "IRI" w3c/json-ld-api#222, by @kasei.
-
Unclear IRI Expansion of blank-node-mapped prefixes w3c/json-ld-api#219, by @kasei.
-
Unused variable defined for property-scoped contexts in expansion algorithm w3c/json-ld-api#216, by @kasei.
-
Clarify text in Expansion Algorithm step 12 regarding variable initialization w3c/json-ld-api#215, by @kasei.
-
Undefined use of property-scoped context variable in expansion algorithm w3c/json-ld-api#214, by @kasei.
-
Missing text in expansion algorithm w3c/json-ld-api#213, by @kasei.
-
Clarify language in JsonLdProcessor API w3c/json-ld-api#212, by @kasei.
-
Clarification in algorithms w3c/json-ld-api#206, by @pchampin.
-
toRdf/0118 fails in JSON-LD 1.1 w3c/json-ld-api#205, by @gkellogg.
-
Confusing language used in Context Processing Algorithm w3c/json-ld-api#199, by @kasei.
-
Ambiguous use of "unless" in expansion algorithm w3c/json-ld-api#198, by @kasei.
-
Ambiguous use of "otherwise" in expansion algorithm w3c/json-ld-api#197, by @kasei.
-
Missing fragment anchor for default base direction w3c/json-ld-api#196, by @kasei.
-
Containing a colon does not mean an IRI is absolute or blank node identifier w3c/json-ld-api#195, by @lo48576.
-
Markup regarding local contexts in Create Term Definition is confusing w3c/json-ld-api#193, by @kasei.
-
Incorrect variable name in expansion 13.4.7.3? w3c/json-ld-api#192, by @kasei.
-
Dealing with other people's `@` prefixed terms w3c/json-ld-api#191, by @BigBlueHat.
-
-
24 issues closed.
-
Meaning of tests with only specVersion w3c/json-ld-api#227.
-
Tests with invalid keyword expect error w3c/json-ld-api#226.
-
Clarify language in JsonLdProcessor API w3c/json-ld-api#212.
-
toRdf/0118 fails in JSON-LD 1.1 w3c/json-ld-api#205.
-
Confusing links for definition of "IRI" w3c/json-ld-api#222.
-
Test input file `expand/e051-in.jsonld` is missing w3c/json-ld-api#225.
-
Unclear IRI Expansion of blank-node-mapped prefixes w3c/json-ld-api#219.
-
Missing text in expansion algorithm w3c/json-ld-api#213.
-
Undefined use of property-scoped context variable in expansion algorithm w3c/json-ld-api#214.
-
Clarify text in Expansion Algorithm step 12 regarding variable initialization w3c/json-ld-api#215.
-
Unused variable defined for property-scoped contexts in expansion algorithm w3c/json-ld-api#216.
-
Clarification in algorithms w3c/json-ld-api#206.
-
Processing terms starting with : w3c/json-ld-api#189.
-
Dealing with other people's `@` prefixed terms w3c/json-ld-api#191.
-
Containing a colon does not mean an IRI is absolute or blank node identifier w3c/json-ld-api#195.
-
Ambiguous use of "otherwise" in expansion algorithm w3c/json-ld-api#197.
-
Ambiguous use of "unless" in expansion algorithm w3c/json-ld-api#198.
-
Confusing language used in Context Processing Algorithm w3c/json-ld-api#199.
-
Fix/clarify use of "otherwise" steps in expansion algorithms w3c/json-ld-api#176.
-
Missing fragment anchor for default base direction w3c/json-ld-api#196.
-
Incorrect variable name in expansion 13.4.7.3? w3c/json-ld-api#192.
-
Markup regarding local contexts in Create Term Definition is confusing w3c/json-ld-api#193.
-
Clarify text regarding container mappings in algorithms w3c/json-ld-api#181.
-
FIx Create Term Definition algorithm for terms starting with `@` w3c/json-ld-api#188.
-
-
2 issues reopened.
-
toRdf/0118 fails in JSON-LD 1.1 w3c/json-ld-api#205, by @pchampin.
-
Processing terms starting with : w3c/json-ld-api#189, by @gkellogg.
-
-
14 issues received 55 new comments.
-
Dealing with other people's `@` prefixed terms w3c/json-ld-api#191 (15 comments by @akuckartz, @BigBlueHat, @dlongley, @gkellogg, @iherman)
-
Containing a colon does not mean an IRI is absolute or blank node identifier w3c/json-ld-api#195 (10 comments by @akuckartz, @gkellogg, @iherman, @msporny, @pchampin)
-
Clarify language in JsonLdProcessor API w3c/json-ld-api#212 (6 comments by @azaroth42, @gkellogg, @kasei)
-
Meaning of tests with only specVersion w3c/json-ld-api#227 (4 comments by @azaroth42, @gkellogg, @rubensworks)
-
Unclear IRI Expansion of blank-node-mapped prefixes w3c/json-ld-api#219 (4 comments by @gkellogg, @pchampin)
-
Clarify text in Expansion Algorithm step 12 regarding variable initialization w3c/json-ld-api#215 (2 comments by @gkellogg)
-
Unused variable defined for property-scoped contexts in expansion algorithm w3c/json-ld-api#216 (1 comment by @gkellogg)
-
Undefined use of property-scoped context variable in expansion algorithm w3c/json-ld-api#214 (1 comment by @gkellogg)
-
Markup regarding local contexts in Create Term Definition is confusing w3c/json-ld-api#193 (1 comment by @gkellogg)
-
-
21 pull requests opened.
-
Update index.html w3c/json-ld-api#231, by @TallTed.
-
Context resolution w3c/json-ld-api#230, by @gkellogg.
-
chore: fix link to commits being wrong w3c/json-ld-api#229, by @sidvishnoi.
-
@context resolution respects relative URLs w3c/json-ld-api#228, by @ericprud.
-
Update section reference for IRI. w3c/json-ld-api#224, by @gkellogg.
-
Qualify that a potential prefix term must end with a gen-delim w3c/json-ld-api#223, by @gkellogg.
-
Use "deferred" instead of "asynchronous" in API section w3c/json-ld-api#221, by @gkellogg.
-
Fix typos. w3c/json-ld-api#220, by @davidlehn.
-
Add note on `@version` being `1.1` not being semantic versioning. w3c/json-ld-api#218, by @gkellogg.
-
Kasei updates w3c/json-ld-api#217, by @gkellogg.
-
Preparation for CR. w3c/json-ld-api#211, by @gkellogg.
-
Regenerated the acknowledgement file (status of 2019-11-16) w3c/json-ld-api#210, by @iherman.
-
Update to make terms that have the form of a keyword errors. w3c/json-ld-api#209, by @gkellogg.
-
Algorithm clarifications w3c/json-ld-api#208, by @gkellogg.
-
Make toRdf/0118 1.0 only. w3c/json-ld-api#207, by @gkellogg.
-
Keyword space w3c/json-ld-api#204, by @gkellogg.
-
Terms with colon w3c/json-ld-api#203, by @gkellogg.
-
Add control to highlight/de-highlight changes w3c/json-ld-api#202, by @gkellogg.
-
Kasei clarifications w3c/json-ld-api#201, by @gkellogg.
-
Update common files. w3c/json-ld-api#200, by @gkellogg.
-
Variable confusion w3c/json-ld-api#194, by @gkellogg.
-
-
20 pull requests merged.
-
Update index.html w3c/json-ld-api#231.
-
Qualify that a potential prefix term must end with a gen-delim w3c/json-ld-api#223.
-
Update section reference for IRI. w3c/json-ld-api#224.
-
chore: fix link to commits being wrong w3c/json-ld-api#229.
-
Add note on `@version` being `1.1` not being semantic versioning. w3c/json-ld-api#218.
-
Use "deferred" instead of "asynchronous" in API section w3c/json-ld-api#221.
-
Fix typos. w3c/json-ld-api#220.
-
Kasei updates w3c/json-ld-api#217.
-
Preparation for CR. w3c/json-ld-api#211.
-
Regenerated the acknowledgement file (status of 2019-11-16) w3c/json-ld-api#210.
-
Algorithm clarifications w3c/json-ld-api#208.
-
Make toRdf/0118 1.0 only. w3c/json-ld-api#207.
-
Keyword space w3c/json-ld-api#204.
-
Terms with colon w3c/json-ld-api#203.
-
Kasei clarifications w3c/json-ld-api#201.
-
Add control to highlight/de-highlight changes w3c/json-ld-api#202.
-
Update common files. w3c/json-ld-api#200.
-
Variable confusion w3c/json-ld-api#194.
-
Clarifications on _container mapping_ w3c/json-ld-api#186.
-
For warnings, change to "return" rather than "abort". w3c/json-ld-api#190.
-
-
2 pull requests closed.
-
@context resolution respects relative URLs w3c/json-ld-api#228.
-
Update to make terms that have the form of a keyword errors. w3c/json-ld-api#209.
-
-
8 pull requests received 15 new comments.
-
Update to make terms that have the form of a keyword errors. w3c/json-ld-api#209 (5 comments by @gkellogg, @pchampin)
-
Qualify that a potential prefix term must end with a gen-delim w3c/json-ld-api#223 (1 comment by @gkellogg)
-
Use "deferred" instead of "asynchronous" in API section w3c/json-ld-api#221 (1 comment by @davidlehn)
-
w3c/json-ld-syntax
-
11 issues opened.
-
@context as relative IRI w3c/json-ld-syntax#311, by @hsolbrig.
-
URI Schemes term restriction is fairly draconian w3c/json-ld-syntax#310, by @hsolbrig.
-
Alias statements about `@base` are inconsistent w3c/json-ld-syntax#309, by @hsolbrig.
-
Confusing statement on aliasing keywords w3c/json-ld-syntax#308, by @hsolbrig.
-
Example 28 lacks conversion tabs w3c/json-ld-syntax#305, by @hsolbrig.
-
Stars on type on example 13 w3c/json-ld-syntax#303, by @hsolbrig.
-
Named Graphs: confusing "embedding doesn't work as each node object references the other" w3c/json-ld-syntax#300, by @Fak3.
-
Keyword pattern should error when used as a term w3c/json-ld-syntax#297, by @gkellogg.
-
Avoid floating-point number for `@version` w3c/json-ld-syntax#296, by @lo48576.
-
Consistent use of the 'informative' class w3c/json-ld-syntax#294, by @pchampin.
-
Expanded containers. w3c/json-ld-syntax#292, by @davidlehn.
-
-
14 issues closed.
-
URI Schemes term restriction is fairly draconian w3c/json-ld-syntax#310.
-
Alias statements about `@base` are inconsistent w3c/json-ld-syntax#309.
-
Confusing statement on aliasing keywords w3c/json-ld-syntax#308.
-
Avoid floating-point number for `@version` w3c/json-ld-syntax#296.
-
Example 28 lacks conversion tabs w3c/json-ld-syntax#305.
-
Named Graphs: confusing "embedding doesn't work as each node object references the other" w3c/json-ld-syntax#300.
-
Stars on type on example 13 w3c/json-ld-syntax#303.
-
Keyword pattern should error when used as a term w3c/json-ld-syntax#297.
-
Consistent use of the 'informative' class w3c/json-ld-syntax#294.
-
Expanded containers. w3c/json-ld-syntax#292.
-
Better styling on example buttons w3c/json-ld-syntax#82.
-
Terminology of "absolute IRI" differs from RFC 3986 / 3987? w3c/json-ld-syntax#288.
-
Better styling of changes w3c/json-ld-syntax#81.
-
Register application/jsonld alongside application/ld+json? w3c/json-ld-syntax#287.
-
-
1 issue reopened.
-
Keyword pattern should error when used as a term w3c/json-ld-syntax#297, by @pchampin.
-
-
13 issues received 54 new comments.
-
Avoid floating-point number for `@version` w3c/json-ld-syntax#296 (13 comments by @azaroth42, @davidlehn, @gkellogg, @iherman, @lo48576, @pchampin, @TallTed)
-
Alias statements about `@base` are inconsistent w3c/json-ld-syntax#309 (5 comments by @azaroth42, @gkellogg, @hsolbrig)
-
URI Schemes term restriction is fairly draconian w3c/json-ld-syntax#310 (4 comments by @azaroth42, @gkellogg, @TallTed)
-
Keyword pattern should error when used as a term w3c/json-ld-syntax#297 (4 comments by @azaroth42, @iherman, @pchampin)
-
Consistent use of the 'informative' class w3c/json-ld-syntax#294 (4 comments by @gkellogg, @iherman, @pchampin)
-
Confusing statement on aliasing keywords w3c/json-ld-syntax#308 (3 comments by @azaroth42, @gkellogg)
-
Named Graphs: confusing "embedding doesn't work as each node object references the other" w3c/json-ld-syntax#300 (3 comments by @azaroth42, @Fak3, @pchampin)
-
Register application/jsonld alongside application/ld+json? w3c/json-ld-syntax#287 (2 comments by @iherman)
-
-
15 pull requests opened.
-
MUST NOT => SHOULD NOT on URI schemes. w3c/json-ld-syntax#315, by @gkellogg.
-
Fix Note for example 65 w3c/json-ld-syntax#314, by @Fak3.
-
Update index.html w3c/json-ld-syntax#313, by @TallTed.
-
Keyword aliases w3c/json-ld-syntax#312, by @gkellogg.
-
Update example to actually require `@graph`. w3c/json-ld-syntax#307, by @gkellogg.
-
Fix typos. w3c/json-ld-syntax#306, by @davidlehn.
-
Address issue #303 w3c/json-ld-syntax#304, by @pchampin.
-
Address issue #300 w3c/json-ld-syntax#302, by @pchampin.
-
Add note on `@version` being `1.1` not being semantic versioning. w3c/json-ld-syntax#301, by @gkellogg.
-
Preparation for CR w3c/json-ld-syntax#299, by @gkellogg.
-
Regenerated the acknowledgement file (status of 2019-11-16) w3c/json-ld-syntax#298, by @iherman.
-
Clean informative sections w3c/json-ld-syntax#295, by @pchampin.
-
Describe forward-compatibility issues with terms starting with `@` w3c/json-ld-syntax#293, by @gkellogg.
-
Add additional wording to the IANA considerations w3c/json-ld-syntax#291, by @gkellogg.
-
-
16 pull requests merged.
-
MUST NOT => SHOULD NOT on URI schemes. w3c/json-ld-syntax#315.
-
Fix Note for example 65 w3c/json-ld-syntax#314.
-
Keyword aliases w3c/json-ld-syntax#312.
-
Update index.html w3c/json-ld-syntax#313.
-
Add note on `@version` being `1.1` not being semantic versioning. w3c/json-ld-syntax#301.
-
Update example to actually require `@graph`. w3c/json-ld-syntax#307.
-
Fix typos. w3c/json-ld-syntax#306.
-
Address issue #300 w3c/json-ld-syntax#302.
-
Preparation for CR w3c/json-ld-syntax#299.
-
Regenerated the acknowledgement file (status of 2019-11-16) w3c/json-ld-syntax#298.
-
Clean informative sections w3c/json-ld-syntax#295.
-
Describe forward-compatibility issues with terms starting with `@` w3c/json-ld-syntax#293.
-
Add additional wording to the IANA considerations w3c/json-ld-syntax#291.
-
Add control to highlight/de-highlight changes w3c/json-ld-syntax#285.
-
Fix links w3c/json-ld-syntax#290.
-
Update use of _IRI_ to obviate _absolute IRI_ w3c/json-ld-syntax#289.
-
-
1 pull request closed.
-
Address issue #303 w3c/json-ld-syntax#304.
-
-
8 pull requests received 24 new comments.
-
Update use of _IRI_ to obviate _absolute IRI_ w3c/json-ld-syntax#289 (9 comments by @BigBlueHat, @gkellogg, @iherman, @pchampin, @TallTed)
-
Describe forward-compatibility issues with terms starting with `@` w3c/json-ld-syntax#293 (1 comment by @TallTed)
-
w3c/json-ld-wg
-
5 issues opened.
-
"Contributing" sections. w3c/json-ld-wg#131, by @davidlehn.
-
Bogus automatic "Commit history" field in "Participate" spec headers. w3c/json-ld-wg#130, by @davidlehn.
-
2019-11-15-action2: fill out requirements on wiki page (Rob Sanderson) w3c/json-ld-wg#128, by @iherman.
-
-
7 issues closed.
-
Bogus automatic "Commit history" field in "Participate" spec headers. w3c/json-ld-wg#130.
-
2019-11-15-action2: fill out requirements on wiki page (Rob Sanderson) w3c/json-ld-wg#128.
-
-
7 issues received 10 new comments.
-
2019-10-26-action3: find reference to file extensions for profiles re annotation (Rob Sanderson) w3c/json-ld-wg#123 (3 comments by @azaroth42, @BigBlueHat, @iherman)
-
Bogus automatic "Commit history" field in "Participate" spec headers. w3c/json-ld-wg#130 (2 comments by @gkellogg)
-
2019-10-18-action2: find CG issues and reference in CR request wiki page (Rob Sanderson) w3c/json-ld-wg#120 (1 comment by @azaroth42)
-
2019-11-15-action2: fill out requirements on wiki page (Rob Sanderson) w3c/json-ld-wg#128 (1 comment by @azaroth42)
-
2019-11-01-action1: contact IETF about the multiple pluses in the JSON-LD registration (Rob Sanderson) w3c/json-ld-wg#126 (1 comment by @azaroth42)
-
2019-10-26-action1: register profiles with IANA (Benjamin Young) w3c/json-ld-wg#124 (1 comment by @BigBlueHat)
-
-
1 pull request opened.
-
Fix typo. w3c/json-ld-wg#129, by @davidlehn.
-
-
1 pull request merged.
-
Fix typo. w3c/json-ld-wg#129.
-
w3c/json-ld-bp
-
2 issues closed.
-
Bring in existing Best Practices w3c/json-ld-bp#1.
-
Proposed renaming and sectioning w3c/json-ld-bp#15.
-
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Fix 15 - Restructuring w3c/json-ld-bp#17, by @BigBlueHat.
-
-
1 pull request merged.
-
Fix 15 - Restructuring w3c/json-ld-bp#17.
-
w3c/json-ld-framing
-
1 issue opened.
-
Consistent use of the 'informative' class w3c/json-ld-framing#83, by @pchampin.
-
-
1 issue closed.
-
Consistent use of the 'informative' class w3c/json-ld-framing#83.
-
-
1 issue received 1 new comment.
-
4 pull requests opened.
-
Fix typos. w3c/json-ld-framing#86, by @davidlehn.
-
Preparation for CR w3c/json-ld-framing#85, by @gkellogg.
-
Regenerated the acknowledgement file (status of 2019-11-16) w3c/json-ld-framing#84, by @iherman.
-
Add control to highlight/de-highlight changes w3c/json-ld-framing#82, by @gkellogg.
-
-
4 pull requests merged.
-
Fix typos. w3c/json-ld-framing#86.
-
Preparation for CR w3c/json-ld-framing#85.
-
Regenerated the acknowledgement file (status of 2019-11-16) w3c/json-ld-framing#84.
-
Add control to highlight/de-highlight changes w3c/json-ld-framing#82.
-
-
1 pull request received 1 new comment.
TR publications
-
3 documents published.
-
JSON-LD 1.1 published as a Working Draft. History of JSON-LD 1.1
-
JSON-LD 1.1 Framing published as a Working Draft. History of JSON-LD 1.1 Framing
-
JSON-LD 1.1 Processing Algorithms and API published as a Working Draft. History of JSON-LD 1.1 Processing Algorithms and API
-
Participants
-
1 organization left.
-
Mayo Clinic left.
-
GitHub
w3c/json-ld-api
-
13 issues opened.
-
Processing terms starting with : w3c/json-ld-api#189, by @azaroth42.
-
FIx Create Term Definition algorithm for terms starting with `@` w3c/json-ld-api#188, by @kasei.
-
Remove redundant conditional statements in expansion algorithm step 13.11 w3c/json-ld-api#185, by @kasei.
-
Clarify type expectations for the result of expansion w3c/json-ld-api#183, by @kasei.
-
Clarify text regarding container mappings in algorithms w3c/json-ld-api#181, by @kasei.
-
Clarify use of base IRI in IRI expansion algorithm w3c/json-ld-api#180, by @kasei.
-
Fix wording in expansion w3c/json-ld-api#178, by @kasei.
-
Fix/clarify use of "otherwise" steps in expansion algorithms w3c/json-ld-api#176, by @kasei.
-
Clarify trailing text in expansion algorithm w3c/json-ld-api#175, by @kasei.
-
Typo: "Step 9" for "Step 13" in Expansion w3c/json-ld-api#172, by @azaroth42.
-
Wrong reference text in the expansion algorithm property nesting w3c/json-ld-api#171, by @kasei.
-
Require valid language tags w3c/json-ld-api#167, by @gkellogg.
-
Relationship to the RDF/JS Dataset interface(s) w3c/json-ld-api#166, by @iherman.
-
-
14 issues closed.
-
Clarify trailing text in expansion algorithm w3c/json-ld-api#175.
-
Clarify type expectations for the result of expansion w3c/json-ld-api#183.
-
Clarify use of base IRI in IRI expansion algorithm w3c/json-ld-api#180.
-
Remove redundant conditional statements in expansion algorithm step 13.11 w3c/json-ld-api#185.
-
Fix wording in expansion w3c/json-ld-api#178.
-
id-maps don't apply scoped context before expanding keys w3c/json-ld-api#159.
-
lazy-evaluation of 1.1 mode w3c/json-ld-api#161.
-
Require valid language tags w3c/json-ld-api#167.
-
Error code for invalid JSON literal? w3c/json-ld-api#149.
-
How to handle [Exposed=Windows] w3c/json-ld-api#160.
-
keyword alias with `"@prefix"=true` ? w3c/json-ld-api#153.
-
IRI spoofing is still possible w3c/json-ld-api#157.
-
Typo: "Step 9" for "Step 13" in Expansion w3c/json-ld-api#172.
-
Wrong reference text in the expansion algorithm property nesting w3c/json-ld-api#171.
-
-
2 issues reopened.
-
id-maps don't apply scoped context before expanding keys w3c/json-ld-api#159, by @gkellogg.
-
How to handle [Exposed=Windows] w3c/json-ld-api#160, by @gkellogg.
-
-
15 issues received 30 new comments.
-
FIx Create Term Definition algorithm for terms starting with `@` w3c/json-ld-api#188 (3 comments by @azaroth42, @gkellogg, @kasei)
-
Clarify text regarding container mappings in algorithms w3c/json-ld-api#181 (3 comments by @gkellogg, @kasei)
-
Remove redundant conditional statements in expansion algorithm step 13.11 w3c/json-ld-api#185 (2 comments by @kasei, @pchampin)
-
Fix/clarify use of "otherwise" steps in expansion algorithms w3c/json-ld-api#176 (2 comments by @gkellogg, @pchampin)
-
Relationship to the RDF/JS Dataset interface(s) w3c/json-ld-api#166 (2 comments by @iherman, @rubensworks)
-
16 pull requests opened.
-
For warnings, change to "return" rather than "abort". w3c/json-ld-api#190, by @gkellogg.
-
Clarify that IRI expansion uses _base IRI_ from _active context_ w3c/json-ld-api#187, by @gkellogg.
-
Clarifications on _container mapping_ w3c/json-ld-api#186, by @gkellogg.
-
Clarify that expansion steps looking for entries w3c/json-ld-api#184, by @gkellogg.
-
Addresses issue #176 w3c/json-ld-api#182, by @pchampin.
-
Remove incomplete and redundant step for `@type` and `@included` w3c/json-ld-api#179, by @gkellogg.
-
Fix error codes in tests being emitted as IRIs w3c/json-ld-api#177, by @rubensworks.
-
Add wording to allow a default object w3c/json-ld-api#174, by @gkellogg.
-
Expand contexts when processing keys in id-map. w3c/json-ld-api#173, by @gkellogg.
-
Lazy eval version w3c/json-ld-api#170, by @gkellogg.
-
Fix expansion of link template variable json_file, regenerate html. w3c/json-ld-api#169, by @ratmice.
-
Language tags w3c/json-ld-api#168, by @gkellogg.
-
Base direction w3c/json-ld-api#165, by @gkellogg.
-
Add tests for checking lowercasing of @language w3c/json-ld-api#164, by @rubensworks.
-
Fix IDL markup issues. w3c/json-ld-api#163, by @davidlehn.
-
Fix typos. w3c/json-ld-api#162, by @davidlehn.
-
-
14 pull requests merged.
-
Clarify that expansion steps looking for entries w3c/json-ld-api#184.
-
Clarify that IRI expansion uses _base IRI_ from _active context_ w3c/json-ld-api#187.
-
Addresses issue #176 w3c/json-ld-api#182.
-
Remove incomplete and redundant step for `@type` and `@included` w3c/json-ld-api#179.
-
Expand contexts when processing keys in id-map. w3c/json-ld-api#173.
-
Add wording to allow a default object w3c/json-ld-api#174.
-
Fix error codes in tests being emitted as IRIs w3c/json-ld-api#177.
-
Lazy eval version w3c/json-ld-api#170.
-
Fix expansion of link template variable json_file, regenerate html. w3c/json-ld-api#169.
-
Language tags w3c/json-ld-api#168.
-
Fix IDL markup issues. w3c/json-ld-api#163.
-
Base direction w3c/json-ld-api#165.
-
Fix typos. w3c/json-ld-api#162.
-
Add tests to check for keyword redefinition allowing `@protected`. w3c/json-ld-api#158.
-
-
1 pull request closed.
-
Add tests for checking lowercasing of @language w3c/json-ld-api#164.
-
-
12 pull requests received 109 new comments.
-
Base direction w3c/json-ld-api#165 (61 comments by @davidlehn, @dlongley, @gkellogg, @iherman, @pchampin, @rubensworks)
-
Add tests for checking lowercasing of @language w3c/json-ld-api#164 (9 comments by @davidlehn, @dlongley, @gkellogg, @rubensworks)
-
Fix error codes in tests being emitted as IRIs w3c/json-ld-api#177 (3 comments by @gkellogg, @rubensworks)
-
Add tests to check for keyword redefinition allowing `@protected`. w3c/json-ld-api#158 (3 comments by @dlongley, @gkellogg, @pchampin)
-
Fix expansion of link template variable json_file, regenerate html. w3c/json-ld-api#169 (1 comment by @gkellogg)
-
w3c/json-ld-syntax
-
5 issues opened.
-
Terminology of "absolute IRI" differs from RFC 3986 / 3987? w3c/json-ld-syntax#288, by @lo48576.
-
Register application/jsonld alongside application/ld+json? w3c/json-ld-syntax#287, by @iherman.
-
language-maps don't allow separate base direction w3c/json-ld-syntax#280, by @gkellogg.
-
JSON literal term definition markup. w3c/json-ld-syntax#278, by @davidlehn.
-
Flattening doc with node references instead of node object? w3c/json-ld-syntax#277, by @zaliqarosli.
-
-
9 issues closed.
-
Description of `@type` in 9.16 should mention its use as a key on context w3c/json-ld-syntax#269.
-
Example 16 - navigation unclear w3c/json-ld-syntax#273.
-
Missing keywords in 9.15 & 9.16 w3c/json-ld-syntax#262.
-
keyword aliases for @id and @type cannot be singly @protected? w3c/json-ld-syntax#246.
-
Introducing @dir w3c/json-ld-syntax#11.
-
JSON literal term definition markup. w3c/json-ld-syntax#278.
-
Warn or error if non-keyword strings having "@" are encountered w3c/json-ld-syntax#16.
-
Use of null value with JSON literals w3c/json-ld-syntax#258.
-
Flattening doc with node references instead of node object? w3c/json-ld-syntax#277.
-
-
1 issue reopened.
-
Description of `@type` in 9.16 should mention its use as a key on context w3c/json-ld-syntax#269, by @gkellogg.
-
-
10 issues received 23 new comments.
-
Terminology of "absolute IRI" differs from RFC 3986 / 3987? w3c/json-ld-syntax#288 (4 comments by @gkellogg, @pchampin)
-
Flattening doc with node references instead of node object? w3c/json-ld-syntax#277 (3 comments by @pchampin, @zaliqarosli)
-
Register application/jsonld alongside application/ld+json? w3c/json-ld-syntax#287 (2 comments by @gkellogg, @iherman)
-
Description of `@type` in 9.16 should mention its use as a key on context w3c/json-ld-syntax#269 (2 comments by @azaroth42, @pchampin)
-
keyword aliases for @id and @type cannot be singly @protected? w3c/json-ld-syntax#246 (1 comment by @gkellogg)
-
-
9 pull requests opened.
-
Update use of _IRI_ to obviate _absolute IRI_ w3c/json-ld-syntax#289, by @gkellogg.
-
Improve normative definition of `@type`. w3c/json-ld-syntax#286, by @gkellogg.
-
Add control to highlight/de-highlight changes w3c/json-ld-syntax#285, by @gkellogg.
-
Lazy eval version w3c/json-ld-syntax#284, by @gkellogg.
-
Language tag w3c/json-ld-syntax#283, by @gkellogg.
-
Weaken requirement to normalize language tags w3c/json-ld-syntax#282, by @rubensworks.
-
Add link to the API test suite. w3c/json-ld-syntax#281, by @gkellogg.
-
Fix typos. w3c/json-ld-syntax#279, by @davidlehn.
-
Describing `@direction` w3c/json-ld-syntax#276, by @gkellogg.
-
-
7 pull requests merged.
-
Improve normative definition of `@type`. w3c/json-ld-syntax#286.
-
Lazy eval version w3c/json-ld-syntax#284.
-
Language tag w3c/json-ld-syntax#283.
-
Describing `@direction` w3c/json-ld-syntax#276.
-
Add link to the API test suite. w3c/json-ld-syntax#281.
-
Fix typos. w3c/json-ld-syntax#279.
-
Add note that `null` is preserved in JSON literals. w3c/json-ld-syntax#275.
-
-
1 pull request closed.
-
Weaken requirement to normalize language tags w3c/json-ld-syntax#282.
-
-
5 pull requests received 49 new comments.
-
Describing `@direction` w3c/json-ld-syntax#276 (37 comments by @aphillips, @dlongley, @gkellogg, @iherman, @pchampin)
-
Improve description of keyword aliases using `@protected` w3c/json-ld-syntax#272 (5 comments by @gkellogg, @pchampin)
-
Add control to highlight/de-highlight changes w3c/json-ld-syntax#285 (2 comments by @gkellogg, @iherman)
-
Weaken requirement to normalize language tags w3c/json-ld-syntax#282 (2 comments by @gkellogg, @rubensworks)
-
w3c/json-ld-wg
-
10 issues opened.
-
2019-10-26-action2: check with plh if he is the right contact person (Ivan Herman) w3c/json-ld-wg#125, by @iherman.
-
2019-10-26-action1: register profiles with IANA (Benjamin Young) w3c/json-ld-wg#124, by @iherman.
-
2019-10-18-action2: find CG issues and reference in CR request wiki page (Rob Sanderson) w3c/json-ld-wg#120, by @iherman.
-
2019-10-18-action1: add links to changes to CR request wiki page (Gregg Kellogg) w3c/json-ld-wg#121, by @iherman.
-
2019-10-11-action1: update docs regarding lazy evaluation of processing mode (Gregg Kellogg) w3c/json-ld-wg#119, by @iherman.
-
2019-10-04-action1: add test suite links to syntax doc (Gregg Kellogg) w3c/json-ld-wg#116, by @iherman.
-
-
4 issues closed.
-
2019-10-18-action1: add links to changes to CR request wiki page (Gregg Kellogg) w3c/json-ld-wg#121.
-
2019-10-04-action1: add test suite links to syntax doc (Gregg Kellogg) w3c/json-ld-wg#116.
-
7 issues received 14 new comments.
-
2019-10-26-action3: find reference to file extensions for profiles re annotation (Rob Sanderson) w3c/json-ld-wg#123 (8 comments by @azaroth42, @BigBlueHat, @gkellogg, @iherman, @TallTed)
-
2019-10-26-action1: register profiles with IANA (Benjamin Young) w3c/json-ld-wg#124 (1 comment by @iherman)
-
2019-10-26-action4: comment in issue inviting DID WG to JSON-LD WG regular call next week to discuss (Rob Sanderson) w3c/json-ld-wg#122 (1 comment by @azaroth42)
-
2019-10-26-action2: check with plh if he is the right contact person (Ivan Herman) w3c/json-ld-wg#125 (1 comment by @iherman)
-
2019-10-18-action1: add links to changes to CR request wiki page (Gregg Kellogg) w3c/json-ld-wg#121 (1 comment by @gkellogg)
-
2019-10-04-action2: run down where best to host JSON-LD tests with a proper HTTP server going forward (Benjamin Young) w3c/json-ld-wg#118 (1 comment by @BigBlueHat)
-
2019-10-04-action3: create issue on values of language maps not including `@direction` (Gregg Kellogg) w3c/json-ld-wg#117 (1 comment by @gkellogg)
-
w3c/json-ld-framing
-
3 issues opened.
-
Default value for @type w3c/json-ld-framing#74, by @AtesComp.
-
Reframing Relationships w3c/json-ld-framing#73, by @AtesComp.
-
Correction for 2.3.2 Explicit inclusion flag w3c/json-ld-framing#72, by @AtesComp.
-
-
3 issues closed.
-
Add more framing examples w3c/json-ld-framing#69.
-
Default value for @type w3c/json-ld-framing#74.
-
Correction for 2.3.2 Explicit inclusion flag w3c/json-ld-framing#72.
-
-
3 issues received 5 new comments.
-
8 pull requests opened.
-
Small document reorganization w3c/json-ld-framing#81, by @gkellogg.
-
Use expectErrorCode instead of expect for negative tests. w3c/json-ld-framing#80, by @gkellogg.
-
More examples w3c/json-ld-framing#79, by @gkellogg.
-
Text and tests for default values of `@type`. w3c/json-ld-framing#78, by @gkellogg.
-
Fix expansion of link template variable json_file, regenerate html. w3c/json-ld-framing#77, by @ratmice.
-
Lazy-Eval processingMode. w3c/json-ld-framing#76, by @gkellogg.
-
Ignore language case when framing w3c/json-ld-framing#75, by @gkellogg.
-
Fix typos. w3c/json-ld-framing#71, by @davidlehn.
-
-
8 pull requests merged.
-
More examples w3c/json-ld-framing#79.
-
Small document reorganization w3c/json-ld-framing#81.
-
Use expectErrorCode instead of expect for negative tests. w3c/json-ld-framing#80.
-
Text and tests for default values of `@type`. w3c/json-ld-framing#78.
-
Lazy-Eval processingMode. w3c/json-ld-framing#76.
-
Fix expansion of link template variable json_file, regenerate html. w3c/json-ld-framing#77.
-
Ignore language case when framing w3c/json-ld-framing#75.
-
Fix typos. w3c/json-ld-framing#71.
-
-
3 pull requests received 11 new comments.
-
Fix expansion of link template variable json_file, regenerate html. w3c/json-ld-framing#77 (1 comment by @gkellogg)
w3c/json-ld-bp
-
1 pull request opened.
-
Switch to section/h3 markup w3c/json-ld-bp#16, by @BigBlueHat.
-
-
1 pull request merged.
-
Switch to section/h3 markup w3c/json-ld-bp#16.
-
-
1 pull request received 5 new comments.
TR publications
-
3 documents published.
-
JSON-LD 1.1 published as a Working Draft. History of JSON-LD 1.1
-
JSON-LD 1.1 Framing published as a Working Draft. History of JSON-LD 1.1 Framing
-
JSON-LD 1.1 Processing Algorithms and API published as a Working Draft. History of JSON-LD 1.1 Processing Algorithms and API
-
GitHub
w3c/json-ld-syntax
-
48 issues opened.
-
Example 16 - navigation unclear w3c/json-ld-syntax#273, by @hrennau.
-
Description of `@type` in 9.16 should mention its use as a key on context w3c/json-ld-syntax#269, by @pchampin.
-
Flagging an action for CR (RDF vocabulary file update) w3c/json-ld-syntax#263, by @iherman.
-
Missing keywords in 9.15 & 9.16 w3c/json-ld-syntax#262, by @iherman.
-
Mixing graph id-s and node id-s in the example No. 155 w3c/json-ld-syntax#261, by @iherman.
-
Can terms start with '@'? w3c/json-ld-syntax#260, by @azaroth42.
-
@vocab's presence causes @foo in a value object to fail, otherwise it doesn't w3c/json-ld-syntax#259, by @azaroth42.
-
Use of null value with JSON literals w3c/json-ld-syntax#258, by @azaroth42.
-
What's the use of 7.3? w3c/json-ld-syntax#256, by @azaroth42.
-
Better example for included blocks w3c/json-ld-syntax#255, by @azaroth42.
-
Describe scoped context with @base for id map? w3c/json-ld-syntax#254, by @azaroth42.
-
Examples 91 & 92 very confusing, especially given language maps w3c/json-ld-syntax#253, by @azaroth42.
-
Delete type coercion reference from 4.5 w3c/json-ld-syntax#252, by @azaroth42.
-
4.2.4 or 4.6.2 to note challenge of "en-us" and dot-property notation code w3c/json-ld-syntax#251, by @azaroth42.
-
example 67 uses not best practice of node embedded context w3c/json-ld-syntax#250, by @azaroth42.
-
Note at end of 4.2.3 is out of date w3c/json-ld-syntax#249, by @azaroth42.
-
Example 63 is still hard to understand w3c/json-ld-syntax#248, by @azaroth42.
-
Note in 4.2.1 should clarify not setting node type via context w3c/json-ld-syntax#247, by @azaroth42.
-
keyword aliases for @id and @type cannot be singly @protected? w3c/json-ld-syntax#246, by @azaroth42.
-
Typo: effect -> affect after example 50 w3c/json-ld-syntax#245, by @azaroth42.
-
Typo and confusion in 4.1.9 intro w3c/json-ld-syntax#244, by @azaroth42.
-
Grammar in 4.1.8 w3c/json-ld-syntax#243, by @azaroth42.
-
redefine / redefinition doesn't need hyphen w3c/json-ld-syntax#242, by @azaroth42.
-
Move text inside example 46 to immediately before it w3c/json-ld-syntax#241, by @azaroth42.
-
Bad grammar in intro to 4.1.7 w3c/json-ld-syntax#240, by @azaroth42.
-
Typo: it's --> its in 4.1.4 w3c/json-ld-syntax#239, by @azaroth42.
-
4.1.2.1 should come after 4.1.3 w3c/json-ld-syntax#238, by @azaroth42.
-
Text before example 25 should describe the result w3c/json-ld-syntax#237, by @azaroth42.
-
Forward ref in 4.1 to 4.1.7-10 ? w3c/json-ld-syntax#236, by @azaroth42.
-
Nested properties in section 4 w3c/json-ld-syntax#235, by @azaroth42.
-
"List Objects and Set objects" ... ? w3c/json-ld-syntax#234, by @azaroth42.
-
Links in TR/ refer to github.io version not internal anchors w3c/json-ld-syntax#233, by @azaroth42.
-
Refer to privacy / security concern of context deref in 3.1? w3c/json-ld-syntax#232, by @azaroth42.
-
3.1 - Can any string can be a term? w3c/json-ld-syntax#231, by @azaroth42.
-
Potential for confusion of @version syntax? w3c/json-ld-syntax#230, by @azaroth42.
-
Typo: sccope for scope in definition of @propagate w3c/json-ld-syntax#229, by @azaroth42.
-
Definition of @none could be more specific w3c/json-ld-syntax#228, by @azaroth42.
-
@nested keyword definition does not describe what it does w3c/json-ld-syntax#227, by @azaroth42.
-
Overview implies literals are blank nodes w3c/json-ld-syntax#226, by @azaroth42.
-
Data Model Overview is misleading? w3c/json-ld-syntax#225, by @azaroth42.
-
Simplicity design goal can be even simpler! w3c/json-ld-syntax#224, by @azaroth42.
-
Typo: it's --> its in type map definition w3c/json-ld-syntax#223, by @azaroth42.
-
Typo: ore --> or in included block definition w3c/json-ld-syntax#222, by @azaroth42.
-
Typo: it's --> its in id map definition w3c/json-ld-syntax#221, by @azaroth42.
-
Move 9.3 and "default object" to Framing only? w3c/json-ld-syntax#220, by @azaroth42.
-
default language is described rather than defined in 1.4 w3c/json-ld-syntax#219, by @azaroth42.
-
Remove somewhat passive-aggressive "if desired" from Introduction w3c/json-ld-syntax#218, by @azaroth42.
-
Should abstract refer to 1.1 version? w3c/json-ld-syntax#217, by @azaroth42.
-
-
42 issues closed.
-
What's the use of 7.3? w3c/json-ld-syntax#256.
-
Examples 91 & 92 very confusing, especially given language maps w3c/json-ld-syntax#253.
-
Describe scoped context with @base for id map? w3c/json-ld-syntax#254.
-
Mixing graph id-s and node id-s in the example No. 155 w3c/json-ld-syntax#261.
-
Data Model Overview is misleading? w3c/json-ld-syntax#225.
-
3.1 - Can any string can be a term? w3c/json-ld-syntax#231.
-
Note at end of 4.2.3 is out of date w3c/json-ld-syntax#249.
-
example 67 uses not best practice of node embedded context w3c/json-ld-syntax#250.
-
4.2.4 or 4.6.2 to note challenge of "en-us" and dot-property notation code w3c/json-ld-syntax#251.
-
Delete type coercion reference from 4.5 w3c/json-ld-syntax#252.
-
Forward ref in 4.1 to 4.1.7-10 ? w3c/json-ld-syntax#236.
-
Text before example 25 should describe the result w3c/json-ld-syntax#237.
-
4.1.2.1 should come after 4.1.3 w3c/json-ld-syntax#238.
-
Bad grammar in intro to 4.1.7 w3c/json-ld-syntax#240.
-
Move text inside example 46 to immediately before it w3c/json-ld-syntax#241.
-
redefine / redefinition doesn't need hyphen w3c/json-ld-syntax#242.
-
Grammar in 4.1.8 w3c/json-ld-syntax#243.
-
Typo and confusion in 4.1.9 intro w3c/json-ld-syntax#244.
-
Typo: effect -> affect after example 50 w3c/json-ld-syntax#245.
-
Note in 4.2.1 should clarify not setting node type via context w3c/json-ld-syntax#247.
-
Example 63 is still hard to understand w3c/json-ld-syntax#248.
-
Overview implies literals are blank nodes w3c/json-ld-syntax#226.
-
@nested keyword definition does not describe what it does w3c/json-ld-syntax#227.
-
Definition of @none could be more specific w3c/json-ld-syntax#228.
-
Typo: sccope for scope in definition of @propagate w3c/json-ld-syntax#229.
-
Potential for confusion of @version syntax? w3c/json-ld-syntax#230.
-
Refer to privacy / security concern of context deref in 3.1? w3c/json-ld-syntax#232.
-
Links in TR/ refer to github.io version not internal anchors w3c/json-ld-syntax#233.
-
"List Objects and Set objects" ... ? w3c/json-ld-syntax#234.
-
Nested properties in section 4 w3c/json-ld-syntax#235.
-
Should abstract refer to 1.1 version? w3c/json-ld-syntax#217.
-
Remove somewhat passive-aggressive "if desired" from Introduction w3c/json-ld-syntax#218.
-
default language is described rather than defined in 1.4 w3c/json-ld-syntax#219.
-
Typo: it's --> its in id map definition w3c/json-ld-syntax#221.
-
Typo: ore --> or in included block definition w3c/json-ld-syntax#222.
-
Typo: it's --> its in type map definition w3c/json-ld-syntax#223.
-
Simplicity design goal can be even simpler! w3c/json-ld-syntax#224.
-
Typo: it's --> its in 4.1.4 w3c/json-ld-syntax#239.
-
@vocab's presence causes @foo in a value object to fail, otherwise it doesn't w3c/json-ld-syntax#259.
-
Can terms start with '@'? w3c/json-ld-syntax#260.
-
Move 9.3 and "default object" to Framing only? w3c/json-ld-syntax#220.
-
Specs have references to themselves. w3c/json-ld-syntax#186.
-
-
3 issues reopened.
-
Describe scoped context with @base for id map? w3c/json-ld-syntax#254, by @gkellogg.
-
Warn or error if non-keyword strings having "@" are encountered w3c/json-ld-syntax#16, by @azaroth42.
-
Introducing @dir w3c/json-ld-syntax#11, by @azaroth42.
-
-
21 issues received 44 new comments.
-
Use of null value with JSON literals w3c/json-ld-syntax#258 (8 comments by @azaroth42, @gkellogg, @iddan, @iherman, @rubensworks)
-
keyword aliases for @id and @type cannot be singly @protected? w3c/json-ld-syntax#246 (7 comments by @azaroth42, @gkellogg, @iherman)
-
Describe scoped context with @base for id map? w3c/json-ld-syntax#254 (5 comments by @azaroth42, @gkellogg)
-
Warn or error if non-keyword strings having "@" are encountered w3c/json-ld-syntax#16 (2 comments by @azaroth42, @iherman)
-
Description of `@type` in 9.16 should mention its use as a key on context w3c/json-ld-syntax#269 (1 comment by @gkellogg)
-
Mixing graph id-s and node id-s in the example No. 155 w3c/json-ld-syntax#261 (1 comment by @gkellogg)
-
example 67 uses not best practice of node embedded context w3c/json-ld-syntax#250 (1 comment by @gkellogg)
-
Links in TR/ refer to github.io version not internal anchors w3c/json-ld-syntax#233 (1 comment by @gkellogg)
-
@vocab's presence causes @foo in a value object to fail, otherwise it doesn't w3c/json-ld-syntax#259 (1 comment by @iherman)
-
Note in 4.2.1 should clarify not setting node type via context w3c/json-ld-syntax#247 (1 comment by @ajs6f)
-
-
10 pull requests opened.
-
Add note that `null` is preserved in JSON literals. w3c/json-ld-syntax#275, by @gkellogg.
-
Update fragment used in 7.3 w3c/json-ld-syntax#274, by @gkellogg.
-
Improve description of keyword aliases using `@protected` w3c/json-ld-syntax#272, by @gkellogg.
-
More azaroth fixes w3c/json-ld-syntax#271, by @gkellogg.
-
proposed solution to #261 w3c/json-ld-syntax#270, by @pchampin.
-
added missing keywords in sections 1.7, 9.15 and 9.16, addressing #262 w3c/json-ld-syntax#268, by @pchampin.
-
typos and minor improvements w3c/json-ld-syntax#267, by @pchampin.
-
Update some attributions. w3c/json-ld-syntax#266, by @gkellogg.
-
Azaroth suggestions w3c/json-ld-syntax#265, by @gkellogg.
-
Minor editorial issues w3c/json-ld-syntax#264, by @iherman.
-
-
9 pull requests merged.
-
Update fragment used in 7.3 w3c/json-ld-syntax#274.
-
Improve description of keyword aliases using `@protected` w3c/json-ld-syntax#272.
-
More azaroth fixes w3c/json-ld-syntax#271.
-
added missing keywords in sections 1.7, 9.15 and 9.16, addressing #262 w3c/json-ld-syntax#268.
-
proposed solution to #261 w3c/json-ld-syntax#270.
-
typos and minor improvements w3c/json-ld-syntax#267.
-
Azaroth suggestions w3c/json-ld-syntax#265.
-
Update some attributions. w3c/json-ld-syntax#266.
-
Minor editorial issues w3c/json-ld-syntax#264.
-
-
3 pull requests received 11 new comments.
w3c/json-ld-api
-
7 issues opened.
-
lazy-evaluation of 1.1 mode w3c/json-ld-api#161, by @gkellogg.
-
How to handle [Exposed=Windows] w3c/json-ld-api#160, by @gkellogg.
-
id-maps don't apply scoped context before expanding keys w3c/json-ld-api#159, by @gkellogg.
-
IRI spoofing is still possible w3c/json-ld-api#157, by @pchampin.
-
keyword alias with `"@prefix"=true` ? w3c/json-ld-api#153, by @pchampin.
-
Cut/paste typos in definitions w3c/json-ld-api#151, by @azaroth42.
-
Error code for invalid JSON literal? w3c/json-ld-api#149, by @davidlehn.
-
-
3 issues closed.
-
Cut/paste typos in definitions w3c/json-ld-api#151.
-
Compacting graph container with multiple nodes broken w3c/json-ld-api#143.
-
Node map generation seems to miss anonymous graph name w3c/json-ld-api#144.
-
-
2 issues reopened.
-
Error code for invalid JSON literal? w3c/json-ld-api#149, by @gkellogg.
-
Compacting graph container with multiple nodes broken w3c/json-ld-api#143, by @azaroth42.
-
-
4 issues received 12 new comments.
-
Compacting graph container with multiple nodes broken w3c/json-ld-api#143 (5 comments by @dlongley, @gkellogg, @iherman)
-
keyword alias with `"@prefix"=true` ? w3c/json-ld-api#153 (3 comments by @azaroth42, @iherman, @pchampin)
-
-
10 pull requests opened.
-
Add tests to check for keyword redefinition allowing `@protected`. w3c/json-ld-api#158, by @gkellogg.
-
Update acknowledgements and editors. w3c/json-ld-api#156, by @gkellogg.
-
Add minor spec update and tests for JSON literal string and null values. w3c/json-ld-api#155, by @gkellogg.
-
Prevent keyword alias to be declared as prefix w3c/json-ld-api#154, by @pchampin.
-
Mark tests that use relative `@vocab` as JSON-LD 1.1 tests w3c/json-ld-api#152, by @rubensworks.
-
Add invalid JSON literal error and tests. w3c/json-ld-api#150, by @gkellogg.
-
Fix ReSpec errors w3c/json-ld-api#148, by @marcoscaceres.
-
Implementation report template and initial seed. w3c/json-ld-api#147, by @gkellogg.
-
Wrap multiple object values of a term which is a graph container w3c/json-ld-api#146, by @gkellogg.
-
Remove caveat about expanding values of terms which are graph contain… w3c/json-ld-api#145, by @gkellogg.
-
-
9 pull requests merged.
-
Prevent keyword alias to be declared as prefix w3c/json-ld-api#154.
-
Mark tests that use relative `@vocab` as JSON-LD 1.1 tests w3c/json-ld-api#152.
-
Update acknowledgements and editors. w3c/json-ld-api#156.
-
Add minor spec update and tests for JSON literal string and null values. w3c/json-ld-api#155.
-
Add invalid JSON literal error and tests. w3c/json-ld-api#150.
-
Implementation report template and initial seed. w3c/json-ld-api#147.
-
Fix ReSpec errors w3c/json-ld-api#148.
-
Wrap multiple object values of a term which is a graph container w3c/json-ld-api#146.
-
Remove caveat about expanding values of terms which are graph contain… w3c/json-ld-api#145.
-
-
8 pull requests received 29 new comments.
-
Mark tests that use relative `@vocab` as JSON-LD 1.1 tests w3c/json-ld-api#152 (16 comments by @davidlehn, @gkellogg, @rubensworks)
-
Remove caveat about expanding values of terms which are graph contain… w3c/json-ld-api#145 (1 comment by @iherman)
-
Wrap multiple object values of a term which is a graph container w3c/json-ld-api#146 (1 comment by @iherman)
-
w3c/json-ld-framing
-
1 issue opened.
-
Add more framing examples w3c/json-ld-framing#69, by @gkellogg.
-
-
1 issue closed.
-
Framing blank node unnamed graphs w3c/json-ld-framing#27.
-
-
1 issue reopened.
-
Framing blank node unnamed graphs w3c/json-ld-framing#27, by @azaroth42.
-
-
2 issues received 12 new comments.
-
Confusion regarding @default and @embed in JSON-LD 1.1? w3c/json-ld-framing#58 (10 comments by @cboettig, @davidlehn, @gkellogg, @jeroen)
-
-
3 pull requests opened.
-
Update editors and acknowledgements. w3c/json-ld-framing#70, by @gkellogg.
-
HTML versions of manifests. w3c/json-ld-framing#68, by @gkellogg.
-
Fix ReSpec error w3c/json-ld-framing#67, by @marcoscaceres.
-
-
4 pull requests merged.
-
Update editors and acknowledgements. w3c/json-ld-framing#70.
-
HTML versions of manifests. w3c/json-ld-framing#68.
-
Fix ReSpec error w3c/json-ld-framing#67.
-
Update framing algorithm to use `embedded flag` in _framing state_ w3c/json-ld-framing#66.
-
-
2 pull requests received 2 new comments.
w3c/json-ld-bp
-
2 issues opened.
-
Proposed renaming and sectioning w3c/json-ld-bp#15, by @BigBlueHat.
-
Unexpected typed value experience w3c/json-ld-bp#14, by @BigBlueHat.
-
-
2 issues received 9 new comments.
-
Unexpected typed value experience w3c/json-ld-bp#14 (4 comments by @BigBlueHat, @gkellogg, @iherman)
-
1 pull request merged.
-
Import from CG BP draft w3c/json-ld-bp#12.
-
-
1 pull request received 2 new comments.
w3c/json-ld-wg
-
9 issues opened.
-
2019-09-20-action3: send email to schema earlier (Rob Sanderson) w3c/json-ld-wg#114, by @iherman.
-
2019-09-06-action2: add software version DOAP property to report template (Gregg Kellogg) w3c/json-ld-wg#109, by @iherman.
-
2019-09-06-action1: send to -chairs example CR request (Ivan Herman) w3c/json-ld-wg#108, by @iherman.
-
13 issues closed.
-
2019-09-20-action3: send email to schema earlier (Rob Sanderson) w3c/json-ld-wg#114.
-
2019-09-06-action1: send to -chairs example CR request (Ivan Herman) w3c/json-ld-wg#108.
-
Communication with OGC w3c/json-ld-wg#82.
-
2019-08-23-action3: chase a11y HR (Benjamin Young) w3c/json-ld-wg#101.
-
2019-08-30-action3: email Coralie regarding announcement at TPAC (Rob Sanderson) w3c/json-ld-wg#104.
-
16 issues received 22 new comments.
-
2019-09-20-action3: send email to schema earlier (Rob Sanderson) w3c/json-ld-wg#114 (3 comments by @akuckartz, @azaroth42, @iherman)
-
2019-04-19-action4: check a11y questionnaire against specs (Rob Sanderson) w3c/json-ld-wg#77 (2 comments by @BigBlueHat)
-
2019-08-30-action1: contact w3 team to determine possibility of json-ld shortname pointing to latest version (Ivan Herman) w3c/json-ld-wg#105 (2 comments by @iherman)
-
2019-09-20-action2: send email to schema.org CG when final WD pre CR is available for review (Rob Sanderson) w3c/json-ld-wg#113 (1 comment by @azaroth42)
-
2019-09-20-action4: set up empty wiki page with template for transition request to collect information (Ivan Herman) w3c/json-ld-wg#115 (1 comment by @iherman)
-
2019-09-06-action3: look at taking out test definitions and replacing with links to test manifests (Gregg Kellogg) w3c/json-ld-wg#107 (1 comment by @gkellogg)
-
2019-09-06-action2: add software version DOAP property to report template (Gregg Kellogg) w3c/json-ld-wg#109 (1 comment by @gkellogg)
-
2019-09-06-action1: send to -chairs example CR request (Ivan Herman) w3c/json-ld-wg#108 (1 comment by @iherman)
-
2018-10-25-action1: add privacy and horizontal review to guiding principles (Rob Sanderson) w3c/json-ld-wg#63 (1 comment by @azaroth42)
-
2019-08-30-action3: email Coralie regarding announcement at TPAC (Rob Sanderson) w3c/json-ld-wg#104 (1 comment by @azaroth42)
-
TR publications
-
5 documents published.
-
JSON-LD 1.1 published 3 times as a Working Draft. History of JSON-LD 1.1
-
JSON-LD 1.1 Framing published as a Working Draft. History of JSON-LD 1.1 Framing
-
JSON-LD 1.1 Processing Algorithms and API published as a Working Draft. History of JSON-LD 1.1 Processing Algorithms and API
-
GitHub
w3c/json-ld-api
-
4 issues opened.
-
Node map generation seems to miss anonymous graph name w3c/json-ld-api#144, by @gkellogg.
-
Compacting graph container with multiple nodes broken w3c/json-ld-api#143, by @gkellogg.
-
Should rel="alternate" keep the base IRI of the original document? w3c/json-ld-api#139, by @pchampin.
-
Discuss `rel="alternate"` approach to preemptive content negotation w3c/json-ld-api#138, by @BigBlueHat.
-
-
2 issues closed.
-
Should rel="alternate" keep the base IRI of the original document? w3c/json-ld-api#139.
-
Discuss `rel="alternate"` approach to preemptive content negotation w3c/json-ld-api#138.
-
-
4 issues received 23 new comments.
-
Compacting graph container with multiple nodes broken w3c/json-ld-api#143 (14 comments by @dlongley, @gkellogg)
-
Should rel="alternate" keep the base IRI of the original document? w3c/json-ld-api#139 (5 comments by @BigBlueHat, @iherman, @pchampin, @rubensworks)
-
Discuss `rel="alternate"` approach to preemptive content negotation w3c/json-ld-api#138 (3 comments by @iherman, @pchampin)
-
-
12 pull requests opened.
-
Base URL for rel=alternate is the alternate URL w3c/json-ld-api#142, by @gkellogg.
-
Make expandContext option in tests a URI instead of a string w3c/json-ld-api#141, by @rubensworks.
-
Enable generalized RDF in expansion test 75 for toRdf w3c/json-ld-api#140, by @rubensworks.
-
Html base atrisk w3c/json-ld-api#136, by @gkellogg.
-
Encapsulate HTML processing w3c/json-ld-api#135, by @gkellogg.
-
Remove requirement for extracting a context from HTML. w3c/json-ld-api#134, by @gkellogg.
-
Add support for the `alternate` link relation w3c/json-ld-api#133, by @gkellogg.
-
A proposal to make algorithms easier to read using foldable sections. w3c/json-ld-api#132, by @pchampin.
-
add missing parameter w3c/json-ld-api#131, by @pchampin.
-
Review terms pchampin w3c/json-ld-api#130, by @pchampin.
-
verify that compact IRIs and terms as `@vocab` expand properly w3c/json-ld-api#129, by @pchampin.
-
-
10 pull requests merged.
-
Base URL for rel=alternate is the alternate URL w3c/json-ld-api#142.
-
Enable generalized RDF in expansion test 75 for toRdf w3c/json-ld-api#140.
-
Encapsulate HTML processing w3c/json-ld-api#135.
-
atrisk w3c/json-ld-api#137.
-
Remove requirement for extracting a context from HTML. w3c/json-ld-api#134.
-
Add support for the `alternate` link relation w3c/json-ld-api#133.
-
add missing parameter w3c/json-ld-api#131.
-
verify that compact IRIs and terms as `@vocab` expand properly w3c/json-ld-api#129.
-
Review terms pchampin w3c/json-ld-api#130.
-
Updates and tests for `@included` as an array of node objects. w3c/json-ld-api#128.
-
-
2 pull requests closed.
-
Make expandContext option in tests a URI instead of a string w3c/json-ld-api#141.
-
Html base atrisk w3c/json-ld-api#136.
-
-
9 pull requests received 57 new comments.
-
Add support for the `alternate` link relation w3c/json-ld-api#133 (21 comments by @BigBlueHat, @dlongley, @gkellogg, @pchampin)
-
Encapsulate HTML processing w3c/json-ld-api#135 (17 comments by @BigBlueHat, @gkellogg, @iherman, @pchampin, @rubensworks)
-
A proposal to make algorithms easier to read using foldable sections. w3c/json-ld-api#132 (7 comments by @BigBlueHat, @dlongley, @gkellogg, @iherman, @pchampin)
-
Make expandContext option in tests a URI instead of a string w3c/json-ld-api#141 (6 comments by @dlongley, @gkellogg, @iherman, @rubensworks)
-
verify that compact IRIs and terms as `@vocab` expand properly w3c/json-ld-api#129 (1 comment by @pchampin)
-
w3c/json-ld-framing
-
1 issue opened.
-
Framing and @container:@set for scoped contexts w3c/json-ld-framing#64, by @azaroth42.
-
-
2 issues closed.
-
Framing and @container:@set for scoped contexts w3c/json-ld-framing#64.
-
Confusion regarding @default and @embed in JSON-LD 1.1? w3c/json-ld-framing#58.
-
-
1 issue reopened.
-
Framing blank node unnamed graphs w3c/json-ld-framing#27, by @gkellogg.
-
-
3 issues received 19 new comments.
-
Framing blank node unnamed graphs w3c/json-ld-framing#27 (13 comments by @dlongley, @gkellogg, @iherman)
-
Framing and @container:@set for scoped contexts w3c/json-ld-framing#64 (4 comments by @gkellogg, @iherman)
-
Confusion regarding @default and @embed in JSON-LD 1.1? w3c/json-ld-framing#58 (2 comments by @cboettig, @gkellogg)
-
-
5 pull requests opened.
-
Update framing algorithm to use `embedded flag` in _framing state_ w3c/json-ld-framing#66, by @gkellogg.
-
Fix lost array with container: set w3c/json-ld-framing#65, by @gkellogg.
-
Test case for credentials framing. w3c/json-ld-framing#63, by @gkellogg.
-
Add test for issue found in #58. w3c/json-ld-framing#62, by @gkellogg.
-
Text and tests for framing `@included` w3c/json-ld-framing#61, by @gkellogg.
-
-
4 pull requests merged.
-
Test case for credentials framing. w3c/json-ld-framing#63.
-
Fix lost array with container: set w3c/json-ld-framing#65.
-
Add test for issue found in #58. w3c/json-ld-framing#62.
-
Text and tests for framing `@included` w3c/json-ld-framing#61.
-
-
3 pull requests received 4 new comments.
-
Update framing algorithm to use `embedded flag` in _framing state_ w3c/json-ld-framing#66 (1 comment by @gkellogg)
w3c/json-ld-wg
-
12 issues opened.
-
2019-08-30-action3: email Coralie regarding announcement at TPAC (Rob Sanderson) w3c/json-ld-wg#104, by @iherman.
-
2019-08-30-action2: contact Avneesh Singh regarding a11y of fold/unfold button (Ivan Herman) w3c/json-ld-wg#106, by @iherman.
-
Final fate of the json-ld short names? w3c/json-ld-wg#103, by @iherman.
-
2019-08-23-action3: chase a11y HR (Benjamin Young) w3c/json-ld-wg#101, by @iherman.
-
2019-08-23-action5: add use absolute URIs to BPs (Adam Soroka) w3c/json-ld-wg#98, by @iherman.
-
2019-08-23-action4: add use absolute URIs to BPs (Benjamin Young) w3c/json-ld-wg#100, by @iherman.
-
2019-08-16-action2: put [https://w3ctag.github.io/security-questionnaire/](https://w3ctag.github.io/security-questionnaire/) into [https://github.com/w3c/json-ld-wg/issues/89](https://github.com/w3c/json-ld-wg/issues/89) and request comments from security (Rob Sanderson) w3c/json-ld-wg#96, by @iherman.
-
2019-08-16-action2: put [https://w3ctag.github.io/security-questionnaire/](https://w3ctag.github.io/security-questionnaire/) into [https://github.com/w3c/json-ld-wg/issues/89](https://github.com/w3c/json-ld-wg/issues/89) and request comments from security (Rob Sanderson) w3c/json-ld-wg#94, by @iherman.
-
-
11 issues closed.
-
2019-08-23-action5: add use absolute URIs to BPs (Adam Soroka) w3c/json-ld-wg#98.
-
2019-08-23-action4: add use absolute URIs to BPs (Benjamin Young) w3c/json-ld-wg#100.
-
2019-04-19-action5: check with kaz about review of WoT (Rob Sanderson) w3c/json-ld-wg#76.
-
11 issues received 23 new comments.
-
Final fate of the json-ld short names? w3c/json-ld-wg#103 (9 comments by @akuckartz, @azaroth42, @gkellogg, @iherman)
-
2019-08-23-action5: add use absolute URIs to BPs (Adam Soroka) w3c/json-ld-wg#98 (4 comments by @ajs6f, @BigBlueHat, @iherman)
-
2019-08-30-action2: contact Avneesh Singh regarding a11y of fold/unfold button (Ivan Herman) w3c/json-ld-wg#106 (1 comment by @iherman)
-
2019-08-23-action2: alert privacy as to response and intend to keep going (Rob Sanderson) w3c/json-ld-wg#99 (1 comment by @azaroth42)
-
2019-08-23-action1: alert security as to the questionnaire responses (#89) and intend to keep going (Rob Sanderson) w3c/json-ld-wg#102 (1 comment by @azaroth42)
-
2019-08-23-action4: add use absolute URIs to BPs (Benjamin Young) w3c/json-ld-wg#100 (1 comment by @BigBlueHat)
-
2019-08-16-action2: put [https://w3ctag.github.io/security-questionnaire/](https://w3ctag.github.io/security-questionnaire/) into [https://github.com/w3c/json-ld-wg/issues/89](https://github.com/w3c/json-ld-wg/issues/89) and request comments from security (Rob Sanderson) w3c/json-ld-wg#96 (1 comment by @iherman)
-
2019-04-19-action5: check with kaz about review of WoT (Rob Sanderson) w3c/json-ld-wg#76 (1 comment by @azaroth42)
-
2019-08-16-action2: put [https://w3ctag.github.io/security-questionnaire/](https://w3ctag.github.io/security-questionnaire/) into [https://github.com/w3c/json-ld-wg/issues/89](https://github.com/w3c/json-ld-wg/issues/89) and request comments from security (Rob Sanderson) w3c/json-ld-wg#94 (1 comment by @azaroth42)
-
-
1 pull request opened.
-
Fix typo during scribing on 2019-08-16 w3c/json-ld-wg#97, by @rubensworks.
-
-
1 pull request merged.
-
Fix typo during scribing on 2019-08-16 w3c/json-ld-wg#97.
-
w3c/json-ld-bp
-
1 issue opened.
-
Recommend using absolute URIs when possible w3c/json-ld-bp#11, by @ajs6f.
-
-
3 issues received 10 new comments.
-
Bring in existing Best Practices w3c/json-ld-bp#1 (8 comments by @ajs6f, @BigBlueHat, @gkellogg, @iherman)
-
-
1 pull request opened.
-
Import from CG BP draft w3c/json-ld-bp#12, by @ajs6f.
-
w3c/json-ld-syntax
-
1 issue opened.
-
Reconsider Processing Levels w3c/json-ld-syntax#213, by @BigBlueHat.
-
-
8 issues closed.
-
Reconsider Processing Levels w3c/json-ld-syntax#213.
-
JSON-LD Context processing in HTML Documents w3c/json-ld-syntax#172.
-
Link header for HTML and JSON-LD w3c/json-ld-syntax#204.
-
Consider obsoleting use of blank nodes for properties and "generalized RDF" w3c/json-ld-syntax#37.
-
what is null base URL for an embedded json-ld? w3c/json-ld-syntax#103.
-
Inconsistencies in how @vocab is specified w3c/json-ld-syntax#184.
-
Indexing without a predicate w3c/json-ld-syntax#19.
-
TriG graphs in JSON-LD w3c/json-ld-syntax#128.
-
-
1 issue reopened.
-
Consider context by reference with metadata w3c/json-ld-syntax#108, by @gkellogg.
-
-
10 issues received 30 new comments.
-
Consider obsoleting use of blank nodes for properties and "generalized RDF" w3c/json-ld-syntax#37 (8 comments by @ClearlyClaire, @gkellogg, @iherman, @nightpool, @pchampin)
-
Reconsider Processing Levels w3c/json-ld-syntax#213 (7 comments by @ajs6f, @azaroth42, @gkellogg, @iherman)
-
Consider context by reference with metadata w3c/json-ld-syntax#108 (2 comments by @gkellogg, @iherman)
-
Use of `"@vocab": "_:"` in ActivityStreams 2.0 (at least) w3c/json-ld-syntax#183 (1 comment by @BigBlueHat)
-
-
6 pull requests opened.
-
Update restrictReferences logic for removing unused definitions. w3c/json-ld-syntax#215, by @gkellogg.
-
Encapsulate HTML processing w3c/json-ld-syntax#214, by @gkellogg.
-
Remove "Using an HTML document as a Context section. w3c/json-ld-syntax#212, by @gkellogg.
-
Add containing section on Modifying Behavior with Link Relationships w3c/json-ld-syntax#211, by @gkellogg.
-
Update definition for _vocabulary mapping_ w3c/json-ld-syntax#210, by @gkellogg.
-
Added the example for bushes w3c/json-ld-syntax#209, by @iherman.
-
-
7 pull requests merged.
-
Update restrictReferences logic for removing unused definitions. w3c/json-ld-syntax#215.
-
Encapsulate HTML processing w3c/json-ld-syntax#214.
-
Remove "Using an HTML document as a Context section. w3c/json-ld-syntax#212.
-
Add containing section on Modifying Behavior with Link Relationships w3c/json-ld-syntax#211.
-
Update definition for _vocabulary mapping_ w3c/json-ld-syntax#210.
-
Describe included blocks. w3c/json-ld-syntax#208.
-
Added the example for bushes w3c/json-ld-syntax#209.
-
-
5 pull requests received 28 new comments.
-
Added the example for bushes w3c/json-ld-syntax#209 (14 comments by @azaroth42, @BigBlueHat, @dlongley, @gkellogg, @iherman)
-
Remove "Using an HTML document as a Context section. w3c/json-ld-syntax#212 (6 comments by @BigBlueHat, @gkellogg, @pchampin)
-
Add containing section on Modifying Behavior with Link Relationships w3c/json-ld-syntax#211 (5 comments by @gkellogg, @pchampin, @rubensworks)
-
w3c/json-ld-rc
-
1 pull request opened.
-
Include changes made in RDFa JSON-LD context w3c/json-ld-rc#2, by @rubensworks.
-
-
1 pull request merged.
-
Include changes made in RDFa JSON-LD context w3c/json-ld-rc#2.
-
TR publications
-
4 documents published.
-
JSON-LD 1.1 published as a Working Draft. History of JSON-LD 1.1
-
JSON-LD 1.1 Framing published as a Working Draft. History of JSON-LD 1.1 Framing
-
JSON-LD 1.1 Processing Algorithms and API published twice as a Working Draft. History of JSON-LD 1.1 Processing Algorithms and API
-
GitHub
w3c/json-ld-syntax
-
2 issues opened.
-
Link header for HTML and JSON-LD w3c/json-ld-syntax#204, by @gkellogg.
-
Consider Infra spec for describing primitive types w3c/json-ld-syntax#199, by @gkellogg.
-
-
7 issues closed.
-
Misleading introductory text in "Terminology" subsection w3c/json-ld-syntax#185.
-
Unexpected @type scope behavior (term definitions persist throughout JSON tree) w3c/json-ld-syntax#174.
-
IRIs are terms can be misdefined w3c/json-ld-syntax#155.
-
Add security considerations section for URI schemes w3c/json-ld-syntax#148.
-
Add security consideration about IRI concatenation w3c/json-ld-syntax#147.
-
Content addressable contexts w3c/json-ld-syntax#9.
-
Consider Infra spec for describing primitive types w3c/json-ld-syntax#199.
-
-
1 issue reopened.
-
Consider obsoleting use of blank nodes for properties and "generalized RDF" w3c/json-ld-syntax#37, by @azaroth42.
-
-
12 issues received 50 new comments.
-
Unexpected @type scope behavior (term definitions persist throughout JSON tree) w3c/json-ld-syntax#174 (13 comments by @azaroth42, @dlongley, @gkellogg)
-
Consider obsoleting use of blank nodes for properties and "generalized RDF" w3c/json-ld-syntax#37 (5 comments by @ajs6f, @azaroth42, @gkellogg, @kaniini, @nightpool)
-
Link header for HTML and JSON-LD w3c/json-ld-syntax#204 (5 comments by @azaroth42, @BigBlueHat, @dlongley, @gkellogg, @pchampin)
-
Consider Infra spec for describing primitive types w3c/json-ld-syntax#199 (5 comments by @dlongley, @gkellogg, @iherman)
-
Misleading introductory text in "Terminology" subsection w3c/json-ld-syntax#185 (1 comment by @gkellogg)
-
Add security considerations section for URI schemes w3c/json-ld-syntax#148 (1 comment by @azaroth42)
-
-
9 pull requests opened.
-
Describe included blocks. w3c/json-ld-syntax#208, by @gkellogg.
-
Describe included maps with examples. w3c/json-ld-syntax#207, by @gkellogg.
-
Terms update w3c/json-ld-syntax#206, by @gkellogg.
-
Example of using xref w3c/json-ld-syntax#205, by @marcoscaceres.
-
Context definitions w3c/json-ld-syntax#203, by @gkellogg.
-
Add Dave Longley as an editor. w3c/json-ld-syntax#202, by @dlongley.
-
Add sourced context section. w3c/json-ld-syntax#201, by @dlongley.
-
Add section for `@propagate` and stub for `@import`. w3c/json-ld-syntax#200, by @gkellogg.
-
Respec updates w3c/json-ld-syntax#198, by @gkellogg.
-
-
6 pull requests merged.
-
Terms update w3c/json-ld-syntax#206.
-
Context definitions w3c/json-ld-syntax#203.
-
Add section for `@propagate` and stub for `@import`. w3c/json-ld-syntax#200.
-
Add Dave Longley as an editor. w3c/json-ld-syntax#202.
-
Add sourced context section. w3c/json-ld-syntax#201.
-
Respec updates w3c/json-ld-syntax#198.
-
-
2 pull requests closed.
-
Describe included maps with examples. w3c/json-ld-syntax#207.
-
Example of using xref w3c/json-ld-syntax#205.
-
-
1 pull request reopened.
-
Describe included blocks. w3c/json-ld-syntax#208, by @azaroth42.
-
-
6 pull requests received 40 new comments.
-
Describe included blocks. w3c/json-ld-syntax#208 (12 comments by @azaroth42, @dlongley, @gkellogg, @iherman)
-
Add section for `@propagate` and stub for `@import`. w3c/json-ld-syntax#200 (1 comment by @gkellogg)
-
w3c/json-ld-api
-
3 issues opened.
-
Setting @prefix false should prohibit the term from being used to expand a compact IRI w3c/json-ld-api#122, by @gkellogg.
-
Inconsistency about type maps between API and SYNTAX document. w3c/json-ld-api#121, by @pchampin.
-
Create Term Definition algorithm should not be invoked for @import w3c/json-ld-api#120, by @lutzhelm.
-
-
5 issues closed.
-
Inconsistency about type maps between API and SYNTAX document. w3c/json-ld-api#121.
-
Create Term Definition algorithm should not be invoked for @import w3c/json-ld-api#120.
-
What if a @context URL response is HTML? w3c/json-ld-api#66.
-
-
4 issues received 4 new comments.
-
Setting @prefix false should prohibit the term from being used to expand a compact IRI w3c/json-ld-api#122 (1 comment by @gkellogg)
-
Inconsistency about type maps between API and SYNTAX document. w3c/json-ld-api#121 (1 comment by @gkellogg)
-
"Create term definition" algorithm expands schema part of an absolute IRI as if it is a compact IRI w3c/json-ld-api#96 (1 comment by @azaroth42)
-
-
11 pull requests opened.
-
Updates and tests for `@included` as an array of node objects. w3c/json-ld-api#128, by @gkellogg.
-
Allow `@type` to be duplicated, either through aliasing, or nesting. w3c/json-ld-api#127, by @gkellogg.
-
Tests and algorithm updates to support included maps. w3c/json-ld-api#126, by @gkellogg.
-
Term updates w3c/json-ld-api#125, by @gkellogg.
-
Fix latest WebIDL issues. w3c/json-ld-api#124, by @gkellogg.
-
`@container: @type` implies and requires that `@type` not be a literal. w3c/json-ld-api#123, by @gkellogg.
-
Update toRdf tests w3c/json-ld-api#119, by @gkellogg.
-
Don't define _promise_ but use {{Promise}} reference. w3c/json-ld-api#118, by @gkellogg.
-
Context definitions w3c/json-ld-api#117, by @gkellogg.
-
Update terms to use INFRA in place of WebIDL where reasonable. w3c/json-ld-api#116, by @gkellogg.
-
Respec issues w3c/json-ld-api#115, by @gkellogg.
-
-
10 pull requests merged.
-
Allow `@type` to be duplicated, either through aliasing, or nesting. w3c/json-ld-api#127.
-
Fix latest WebIDL issues. w3c/json-ld-api#124.
-
`@container: @type` implies and requires that `@type` not be a literal. w3c/json-ld-api#123.
-
Term updates w3c/json-ld-api#125.
-
Update toRdf tests w3c/json-ld-api#119.
-
Don't define _promise_ but use {{Promise}} reference. w3c/json-ld-api#118.
-
Context definitions w3c/json-ld-api#117.
-
Updates to add @propagate and @import w3c/json-ld-api#112.
-
Update terms to use INFRA in place of WebIDL where reasonable. w3c/json-ld-api#116.
-
Respec issues w3c/json-ld-api#115.
-
-
2 pull requests closed.
-
Tests and algorithm updates to support included maps. w3c/json-ld-api#126.
-
toRdf tests for @prefix w3c/json-ld-api#77.
-
-
6 pull requests received 22 new comments.
-
Updates and tests for `@included` as an array of node objects. w3c/json-ld-api#128 (4 comments by @dlongley, @gkellogg)
w3c/json-ld-wg
-
3 issues received 7 new comments.
-
2019-04-19-action4: check a11y questionnaire against specs (Rob Sanderson) w3c/json-ld-wg#77 (3 comments by @azaroth42, @BigBlueHat)
w3c/json-ld-framing
-
1 issue opened.
-
Confusion regarding @default and @embed in JSON-LD 1.1? w3c/json-ld-framing#58, by @cboettig.
-
-
1 issue closed.
-
2 issues received 2 new comments.
-
Confusion regarding @default and @embed in JSON-LD 1.1? w3c/json-ld-framing#58 (1 comment by @dlongley)
-
Or ... can `@graph` be used in a frame document to dictate the presence of `@graph` in the resulting JSON-LD document? w3c/json-ld-framing#56 (1 comment by @azaroth42)
-
-
3 pull requests opened.
-
Term updates w3c/json-ld-framing#60, by @gkellogg.
-
Use updated term definitions. w3c/json-ld-framing#59, by @gkellogg.
-
Update test README w3c/json-ld-framing#57, by @gkellogg.
-
-
3 pull requests merged.
-
Term updates w3c/json-ld-framing#60.
-
Use updated term definitions. w3c/json-ld-framing#59.
-
Update test README w3c/json-ld-framing#57.
-
w3c/json-ld-bp
-
2 issues received 2 new comments.
GitHub
w3c/json-ld-api
-
3 issues opened.
-
Tests page no longer links clearly to tests w3c/json-ld-api#113, by @cwebber.
-
Expansion test e005 should require `specVersion` to be `json-ld-1.1` w3c/json-ld-api#107, by @lo48576.
-
compaction changes the meaning of absolute IRIs in some cases w3c/json-ld-api#104, by @pchampin.
-
-
6 issues closed.
-
Tests page no longer links clearly to tests w3c/json-ld-api#113.
-
Update documentLoader to return parsed document w3c/json-ld-api#85.
-
Handling of @type in Expansion Algorithm w3c/json-ld-api#100.
-
compaction changes the meaning of absolute IRIs in some cases w3c/json-ld-api#104.
-
Expansion test e005 should require `specVersion` to be `json-ld-1.1` w3c/json-ld-api#107.
-
Tweak `@protected` algorithm to allow reuse of existing contexts w/o conflicts w3c/json-ld-api#90.
-
-
8 issues received 10 new comments.
-
Tests page no longer links clearly to tests w3c/json-ld-api#113 (2 comments by @gkellogg, @rubensworks)
-
Expansion concept "key's term definition" is unclear with compact IRI keys w3c/json-ld-api#94 (2 comments by @azaroth42, @iherman)
-
"Create term definition" algorithm expands schema part of an absolute IRI as if it is a compact IRI w3c/json-ld-api#96 (1 comment by @gkellogg)
-
Expansion test e005 should require `specVersion` to be `json-ld-1.1` w3c/json-ld-api#107 (1 comment by @gkellogg)
-
compaction changes the meaning of absolute IRIs in some cases w3c/json-ld-api#104 (1 comment by @iherman)
-
Tweak `@protected` algorithm to allow reuse of existing contexts w/o conflicts w3c/json-ld-api#90 (1 comment by @gkellogg)
-
-
9 pull requests opened.
-
Update test README w3c/json-ld-api#114, by @gkellogg.
-
Updates to add @propagate and @import w3c/json-ld-api#112, by @gkellogg.
-
Address @kasei's concerns on `@type` expansion. w3c/json-ld-api#111, by @gkellogg.
-
Detect an attempt to compact an IRI which results in an absolute IRI w3c/json-ld-api#110, by @gkellogg.
-
Compact IRI expansion with prefix flag false w3c/json-ld-api#109, by @gkellogg.
-
Only test expansion e005 with specVersion 1.1. w3c/json-ld-api#108, by @gkellogg.
-
Update example formatting. w3c/json-ld-api#106, by @gkellogg.
-
Add feature freeze note w3c/json-ld-api#105, by @BigBlueHat.
-
Add toRdf tests for merging rootless base paths w3c/json-ld-api#103, by @fsteeg.
-
-
9 pull requests merged.
-
Update test README w3c/json-ld-api#114.
-
Address @kasei's concerns on `@type` expansion. w3c/json-ld-api#111.
-
Detect an attempt to compact an IRI which results in an absolute IRI w3c/json-ld-api#110.
-
Compact IRI expansion with prefix flag false w3c/json-ld-api#109.
-
Only test expansion e005 with specVersion 1.1. w3c/json-ld-api#108.
-
Add protected term redefinition tests. w3c/json-ld-api#92.
-
Update example formatting. w3c/json-ld-api#106.
-
Add feature freeze note w3c/json-ld-api#105.
-
Add toRdf tests for merging rootless base paths w3c/json-ld-api#103.
-
-
7 pull requests received 41 new comments.
-
Detect an attempt to compact an IRI which results in an absolute IRI w3c/json-ld-api#110 (19 comments by @davidlehn, @gkellogg, @iherman, @pchampin)
-
Updates to add @propagate and @import w3c/json-ld-api#112 (8 comments by @dlongley, @gkellogg, @iherman, @pchampin)
-
Add toRdf tests for merging rootless base paths w3c/json-ld-api#103 (4 comments by @davidlehn, @fsteeg, @iherman)
-
w3c/json-ld-wg
-
9 issues opened.
-
I18N Review w3c/json-ld-wg#93, by @iherman.
-
Complete Security Horizontal Review w3c/json-ld-wg#89, by @BigBlueHat.
-
Complete Privacy Horizontal Review w3c/json-ld-wg#88, by @BigBlueHat.
-
2019-06-07-action1: update syntax with issue #170 resolution (Pierre-Antoine Champin) w3c/json-ld-wg#85, by @iherman.
-
2019-06-07-action3: post blog reference for feature freeze (Rob Sanderson) w3c/json-ld-wg#86, by @iherman.
-
-
9 issues closed.
-
2019-04-19-action3: check i18n questionnaire against specs (Benjamin Young) w3c/json-ld-wg#78.
-
2019-03-29-action1: facilitate decision by July 1 for TPAC (Rob Sanderson) w3c/json-ld-wg#69.
-
2019-01-25-action1: ping niklas about rdflib plans for 1.1 (Rob Sanderson) w3c/json-ld-wg#54.
-
2019-06-07-action3: post blog reference for feature freeze (Rob Sanderson) w3c/json-ld-wg#86.
-
-
10 issues received 14 new comments.
-
2019-04-19-action3: check i18n questionnaire against specs (Benjamin Young) w3c/json-ld-wg#78 (2 comments by @iherman)
-
2019-04-19-action4: check a11y questionnaire against specs (Rob Sanderson) w3c/json-ld-wg#77 (2 comments by @azaroth42, @BigBlueHat)
-
2019-06-07-action2: test if `@prefix: false` without `@id` works as expected (Pierre-Antoine Champin) w3c/json-ld-wg#87 (2 comments by @iherman, @pchampin)
-
2019-03-29-action1: facilitate decision by July 1 for TPAC (Rob Sanderson) w3c/json-ld-wg#69 (1 comment by @azaroth42)
-
2019-06-07-action1: update syntax with issue #170 resolution (Pierre-Antoine Champin) w3c/json-ld-wg#85 (1 comment by @pchampin)
-
2019-06-07-action3: post blog reference for feature freeze (Rob Sanderson) w3c/json-ld-wg#86 (1 comment by @azaroth42)
-
w3c/json-ld-syntax
-
1 issue opened.
-
Compact IRI expansion support for non-trivial prefix term definitions w3c/json-ld-syntax#191, by @iridiankin.
-
-
5 issues closed.
-
Use of `"@vocab": "_:"` in ActivityStreams 2.0 (at least) w3c/json-ld-syntax#183.
-
Compact IRIs and URI schemes (not security) w3c/json-ld-syntax#177.
-
DocumentLoader should be more visible in the specs w3c/json-ld-syntax#149.
-
Suggestion: Expected behavior for profile URIs not listed in Appendix C? w3c/json-ld-syntax#170.
-
Syntax examples missing the result of compaction w3c/json-ld-syntax#179.
-
-
1 issue reopened.
-
Unexpected @type scope behavior (term definitions persist throughout JSON tree) w3c/json-ld-syntax#174, by @azaroth42.
-
-
10 issues received 57 new comments.
-
Unexpected @type scope behavior (term definitions persist throughout JSON tree) w3c/json-ld-syntax#174 (15 comments by @azaroth42, @dlongley, @gkellogg, @iherman, @pchampin)
-
Compact IRI expansion support for non-trivial prefix term definitions w3c/json-ld-syntax#191 (14 comments by @azaroth42, @iherman, @iridiankin, @pchampin)
-
Consider context by reference with metadata w3c/json-ld-syntax#108 (8 comments by @azaroth42, @dlongley, @iherman, @pchampin, @rubensworks)
-
JSON-LD Context processing in HTML Documents w3c/json-ld-syntax#172 (7 comments by @BigBlueHat, @danbri, @gkellogg)
-
Compact IRIs and URI schemes (not security) w3c/json-ld-syntax#177 (5 comments by @dlongley, @gkellogg, @iherman, @pchampin)
-
Use of `"@vocab": "_:"` in ActivityStreams 2.0 (at least) w3c/json-ld-syntax#183 (2 comments by @iherman, @rubensworks)
-
Suggestion: Expected behavior for profile URIs not listed in Appendix C? w3c/json-ld-syntax#170 (2 comments by @iherman)
-
-
6 pull requests opened.
-
Remove index.html.orig. w3c/json-ld-syntax#197, by @davidlehn.
-
Add a Loading Documents section. w3c/json-ld-syntax#196, by @gkellogg.
-
Describe that type-scoped contexts are only in affect on the node objects in which they're used w3c/json-ld-syntax#195, by @gkellogg.
-
Add version list of lists w3c/json-ld-syntax#194, by @aljones15.
-
clarifications as suggested in #170 and w3c/json-ld-wg#85 w3c/json-ld-syntax#193, by @pchampin.
-
Add feature frozen text to README w3c/json-ld-syntax#192, by @BigBlueHat.
-
-
7 pull requests merged.
-
Remove index.html.orig. w3c/json-ld-syntax#197.
-
Add a Loading Documents section. w3c/json-ld-syntax#196.
-
Describe that type-scoped contexts are only in affect on the node objects in which they're used w3c/json-ld-syntax#195.
-
clarifications as suggested in #170 and w3c/json-ld-wg#85 w3c/json-ld-syntax#193.
-
Protected terms can be redefined, if identical w3c/json-ld-syntax#190.
-
Add feature frozen text to README w3c/json-ld-syntax#192.
-
Update example to indicate inputs and results w3c/json-ld-syntax#189.
-
-
1 pull request closed.
-
Add version list of lists w3c/json-ld-syntax#194.
-
-
7 pull requests received 20 new comments.
-
Add version list of lists w3c/json-ld-syntax#194 (4 comments by @aljones15, @gkellogg, @iherman, @pchampin)
-
clarifications as suggested in #170 and w3c/json-ld-wg#85 w3c/json-ld-syntax#193 (4 comments by @BigBlueHat, @iherman, @pchampin)
-
Describe that type-scoped contexts are only in affect on the node objects in which they're used w3c/json-ld-syntax#195 (3 comments by @dlongley, @gkellogg, @pchampin)
-
Protected terms can be redefined, if identical w3c/json-ld-syntax#190 (3 comments by @davidlehn, @gkellogg)
-
Update example to indicate inputs and results w3c/json-ld-syntax#189 (3 comments by @azaroth42, @gkellogg, @pchampin)
-
w3c/json-ld-bp
-
1 issue received 4 new comments.
-
Add example on order impact on @protected w3c/json-ld-bp#2 (4 comments by @BigBlueHat, @gkellogg, @pchampin, @rubensworks)
-
w3c/json-ld-framing
-
1 issue opened.
-
1 issue received 1 new comment.
-
Or ... can `@graph` be used in a frame document to dictate the presence of `@graph` in the resulting JSON-LD document? w3c/json-ld-framing#56 (1 comment by @gkellogg)
-
-
2 pull requests opened.
-
Update examples. w3c/json-ld-framing#55, by @gkellogg.
-
Add feature frozen text to README w3c/json-ld-framing#54, by @BigBlueHat.
-
-
2 pull requests merged.
-
Update examples. w3c/json-ld-framing#55.
-
Add feature frozen text to README w3c/json-ld-framing#54.
-
TR publications
-
3 documents published.
-
JSON-LD 1.1 published as a Working Draft. History of JSON-LD 1.1
-
JSON-LD 1.1 Framing published as a Working Draft. History of JSON-LD 1.1 Framing
-
JSON-LD 1.1 Processing Algorithms and API published as a Working Draft. History of JSON-LD 1.1 Processing Algorithms and API
-
GitHub
w3c/json-ld-syntax
-
13 issues opened.
-
Specs have references to themselves. w3c/json-ld-syntax#186, by @gkellogg.
-
Misleading introductory text in "Terminology" subsection w3c/json-ld-syntax#185, by @pchampin.
-
Inconsistencies in how @vocab is specified w3c/json-ld-syntax#184, by @pchampin.
-
Use of `"@vocab": "_:"` in ActivityStreams 2.0 (at least) w3c/json-ld-syntax#183, by @BigBlueHat.
-
Should examples use IRIs in the foaf vocabulary that do not exist? w3c/json-ld-syntax#180, by @kasei.
-
Syntax examples missing the result of compaction w3c/json-ld-syntax#179, by @kasei.
-
Example editorial / styling issues in syntax w3c/json-ld-syntax#178, by @azaroth42.
-
Compact IRIs and URI schemes (not security) w3c/json-ld-syntax#177, by @azaroth42.
-
Typo: Missing word in 1.4 definition of Literal w3c/json-ld-syntax#176, by @azaroth42.
-
Unexpected @type scope behavior (term definitions persist throughout JSON tree) w3c/json-ld-syntax#174, by @dlongley.
-
JSON-LD Context processing in HTML Documents w3c/json-ld-syntax#172, by @msporny.
-
Suggestion: Expected behavior for profile URIs not listed in Appendix C? w3c/json-ld-syntax#170, by @swickr.
-
Feedback: My Adventure In JSON-LD: Understanding @context Semantics w3c/json-ld-syntax#169, by @cjslep.
-
-
5 issues closed.
-
Example editorial / styling issues in syntax w3c/json-ld-syntax#178.
-
Typo: Missing word in 1.4 definition of Literal w3c/json-ld-syntax#176.
-
Should examples use IRIs in the foaf vocabulary that do not exist? w3c/json-ld-syntax#180.
-
Feedback: My Adventure In JSON-LD: Understanding @context Semantics w3c/json-ld-syntax#169.
-
Does HTML's `<base>` effect `@context` IRI resolution? w3c/json-ld-syntax#134.
-
-
16 issues received 54 new comments.
-
JSON-LD Context processing in HTML Documents w3c/json-ld-syntax#172 (16 comments by @azaroth42, @BigBlueHat, @dlongley, @gkellogg, @iherman, @msporny, @pchampin, @rubensworks)
-
Unexpected @type scope behavior (term definitions persist throughout JSON tree) w3c/json-ld-syntax#174 (11 comments by @Descends, @dlongley, @gkellogg, @iherman)
-
Compact IRIs and URI schemes (not security) w3c/json-ld-syntax#177 (5 comments by @azaroth42, @gkellogg, @iherman)
-
Example editorial / styling issues in syntax w3c/json-ld-syntax#178 (5 comments by @davidlehn, @gkellogg)
-
Consider context by reference with metadata w3c/json-ld-syntax#108 (2 comments by @azaroth42, @iherman)
-
Inconsistencies in how @vocab is specified w3c/json-ld-syntax#184 (2 comments by @gkellogg, @pchampin)
-
Misleading introductory text in "Terminology" subsection w3c/json-ld-syntax#185 (2 comments by @gkellogg, @pchampin)
-
Should examples use IRIs in the foaf vocabulary that do not exist? w3c/json-ld-syntax#180 (1 comment by @gkellogg)
-
Feedback: My Adventure In JSON-LD: Understanding @context Semantics w3c/json-ld-syntax#169 (1 comment by @BigBlueHat)
-
Does HTML's `<base>` effect `@context` IRI resolution? w3c/json-ld-syntax#134 (1 comment by @BigBlueHat)
-
Suggestion: Expected behavior for profile URIs not listed in Appendix C? w3c/json-ld-syntax#170 (1 comment by @gkellogg)
-
-
9 pull requests opened.
-
Protected terms can be redefined, if identical w3c/json-ld-syntax#190, by @pchampin.
-
Update example to indicate inputs and results w3c/json-ld-syntax#189, by @gkellogg.
-
Update example label styling (for contexts, etc.) and invert tabs for example 26/27 w3c/json-ld-syntax#188, by @gkellogg.
-
Be more clear about literals as value objects w3c/json-ld-syntax#187, by @gkellogg.
-
Update examples to either skip linting, or lint cleanly. w3c/json-ld-syntax#182, by @gkellogg.
-
Fix example title. w3c/json-ld-syntax#181, by @davidlehn.
-
Update ECHIDNA and travis configs for generating specs. w3c/json-ld-syntax#175, by @gkellogg.
-
Correct term assignment to proper IRI in example 42. w3c/json-ld-syntax#173, by @aljones15.
-
Fix term-selection description for 1.0 mode, not JSON-LD 1.0 spec w3c/json-ld-syntax#171, by @pchampin.
-
-
9 pull requests merged.
-
Update example label styling (for contexts, etc.) and invert tabs for example 26/27 w3c/json-ld-syntax#188.
-
Be more clear about literals as value objects w3c/json-ld-syntax#187.
-
Update examples to either skip linting, or lint cleanly. w3c/json-ld-syntax#182.
-
Fix example title. w3c/json-ld-syntax#181.
-
Update ECHIDNA and travis configs for generating specs. w3c/json-ld-syntax#175.
-
Correct term assignment to proper IRI in example 42. w3c/json-ld-syntax#173.
-
Fix term-selection description for 1.0 mode, not JSON-LD 1.0 spec w3c/json-ld-syntax#171.
-
ack script data and generated file w3c/json-ld-syntax#168.
-
Add a section on using HTML documents for contexts (and frames). w3c/json-ld-syntax#167.
-
-
6 pull requests received 19 new comments.
-
Add a section on using HTML documents for contexts (and frames). w3c/json-ld-syntax#167 (5 comments by @BigBlueHat, @gkellogg, @pchampin)
-
Protected terms can be redefined, if identical w3c/json-ld-syntax#190 (4 comments by @davidlehn, @gkellogg)
-
Correct term assignment to proper IRI in example 42. w3c/json-ld-syntax#173 (4 comments by @aljones15, @gkellogg, @iherman, @pchampin)
-
Fix term-selection description for 1.0 mode, not JSON-LD 1.0 spec w3c/json-ld-syntax#171 (3 comments by @gkellogg, @pchampin)
-
w3c/json-ld-api
-
8 issues opened.
-
Handling of @type in Expansion Algorithm w3c/json-ld-api#100, by @kasei.
-
Create Term Definition use of Context Processing algorithm is inconsistent w3c/json-ld-api#99, by @kasei.
-
Expansion algorithm 9.14 shouldn't use Otherwise w3c/json-ld-api#97, by @gkellogg.
-
Expansion concept "key's term definition" is unclear with compact IRI keys w3c/json-ld-api#94, by @iridiankin.
-
Problematic wording in expansion algorithm w3c/json-ld-api#91, by @kasei.
-
Tweak `@protected` algorithm to allow reuse of existing contexts w/o conflicts w3c/json-ld-api#90, by @dlongley.
-
Update documentLoader to return parsed document w3c/json-ld-api#85, by @gkellogg.
-
-
3 issues closed.
-
Problematic wording in expansion algorithm w3c/json-ld-api#91.
-
Create Term Definition use of Context Processing algorithm is inconsistent w3c/json-ld-api#99.
-
Expansion algorithm 9.14 shouldn't use Otherwise w3c/json-ld-api#97.
-
-
5 issues received 18 new comments.
-
More compact @prefix w3c/json-ld-api#76 (8 comments by @BigBlueHat, @davidlehn, @dlongley, @iherman, @pchampin, @rubensworks)
-
Create Term Definition use of Context Processing algorithm is inconsistent w3c/json-ld-api#99 (6 comments by @gkellogg, @kasei)
-
"Create term definition" algorithm expands schema part of an absolute IRI as if it is a compact IRI w3c/json-ld-api#96 (2 comments by @gkellogg, @lo48576)
-
Tweak `@protected` algorithm to allow reuse of existing contexts w/o conflicts w3c/json-ld-api#90 (1 comment by @iherman)
-
-
11 pull requests opened.
-
Issue 99 term context processing w3c/json-ld-api#102, by @gkellogg.
-
Improve wording in Expansion Algorithm. w3c/json-ld-api#101, by @gkellogg.
-
Update public mailing list w3c/json-ld-api#98, by @fsteeg.
-
added missing normative/informative class in intro w3c/json-ld-api#95, by @pchampin.
-
Add more type-scoped compaction tests. w3c/json-ld-api#93, by @davidlehn.
-
Add protected term redefinition tests. w3c/json-ld-api#92, by @davidlehn.
-
Update spec and add tests for limiting `@type`-scoped terms to their typed object. w3c/json-ld-api#89, by @dlongley.
-
Fix broken fromRdf API description. w3c/json-ld-api#88, by @gkellogg.
-
Rewrite LoadDocumentCallback w3c/json-ld-api#87, by @gkellogg.
-
The LoadDocumentCallback returns a broken Promise w3c/json-ld-api#86, by @gkellogg.
-
Reference definitions for processor levels to syntax document. w3c/json-ld-api#84, by @gkellogg.
-
-
11 pull requests merged.
-
Improve wording in Expansion Algorithm. w3c/json-ld-api#101.
-
Issue 99 term context processing w3c/json-ld-api#102.
-
Update public mailing list w3c/json-ld-api#98.
-
added missing normative/informative class in intro w3c/json-ld-api#95.
-
Add more type-scoped compaction tests. w3c/json-ld-api#93.
-
Rewrite LoadDocumentCallback w3c/json-ld-api#87.
-
Fix broken fromRdf API description. w3c/json-ld-api#88.
-
The LoadDocumentCallback returns a broken Promise w3c/json-ld-api#86.
-
Reference definitions for processor levels to syntax document. w3c/json-ld-api#84.
-
Issue 66 html context w3c/json-ld-api#83.
-
-
5 pull requests received 58 new comments.
-
Update spec and add tests for limiting `@type`-scoped terms to their typed object. w3c/json-ld-api#89 (33 comments by @davidlehn, @dlongley, @gkellogg)
-
w3c/json-ld-wg
-
1 issue opened.
-
Communication with OGC w3c/json-ld-wg#82, by @ajs6f.
-
-
1 issue closed.
-
1 issue received 1 new comment.
-
2019-02-08-action1: explore effect of `@nest+@container:@id` on compaction and expansion (Gregg Kellogg) w3c/json-ld-wg#52 (1 comment by @pchampin)
-
-
1 pull request opened.
-
Do not highlight example example. w3c/json-ld-wg#83, by @davidlehn.
-
-
1 pull request merged.
-
Do not highlight example example. w3c/json-ld-wg#83.
-
w3c/json-ld-framing
-
1 pull request opened.
-
added missing normative/informative class in intro w3c/json-ld-framing#53, by @pchampin.
-
-
1 pull request merged.
-
added missing normative/informative class in intro w3c/json-ld-framing#53.
-
Participants
-
1 participant joined.
-
Gregg Kellogg (W3C Invited Experts) joined.
-
GitHub
w3c/json-ld-wg
-
9 issues opened.
-
2019-04-19-action2: add privacy section recommending HTTPS (gkellog) w3c/json-ld-wg#80, by @iherman.
-
2019-04-05-action1: set up an initial repository for a common context (Ivan Herman) w3c/json-ld-wg#79, by @iherman.
-
2019-04-19-action4: check a11y questionnaire against specs (Rob Sanderson) w3c/json-ld-wg#77, by @iherman.
-
2019-04-19-action5: check with kaz about review of WoT (Rob Sanderson) w3c/json-ld-wg#76, by @iherman.
-
2019-04-19-action3: check i18n questionnaire against specs (Benjamin Young) w3c/json-ld-wg#78, by @iherman.
-
2019-04-19-action2: add privacy section recommending HTTPS (gkellog) w3c/json-ld-wg#74, by @iherman.
-
2019-04-05-action1: set up an initial repository for a common context (Ivan Herman) w3c/json-ld-wg#73, by @iherman.
-
-
7 issues closed.
-
2019-04-19-action2: add privacy section recommending HTTPS (gkellog) w3c/json-ld-wg#80.
-
2019-04-19-action2: add privacy section recommending HTTPS (gkellog) w3c/json-ld-wg#74.
-
Proposal: Create a new `json-ld-primer` repository / note w3c/json-ld-wg#17.
-
-
7 issues received 11 new comments.
-
2019-02-08-action1: explore effect of `@nest+@container:@id` on compaction and expansion (Gregg Kellogg) w3c/json-ld-wg#52 (4 comments by @gkellogg, @pchampin)
-
2019-01-25-action1: ping niklas about rdflib plans for 1.1 (Rob Sanderson) w3c/json-ld-wg#54 (2 comments by @iherman, @niklasl)
-
2019-04-19-action2: add privacy section recommending HTTPS (gkellog) w3c/json-ld-wg#80 (1 comment by @gkellogg)
-
2019-04-19-action2: add privacy section recommending HTTPS (gkellog) w3c/json-ld-wg#74 (1 comment by @gkellogg)
-
2019-04-19-action1: add internationalization section discussing lack of text direction (gkellog) w3c/json-ld-wg#75 (1 comment by @gkellogg)
-
2019-04-05-action1: set up an initial repository for a common context (Ivan Herman) w3c/json-ld-wg#73 (1 comment by @iherman)
-
w3c/json-ld-syntax
-
4 issues opened.
-
Missing @type in expanded form when an id map is used in conjunction with @type in a term definition w3c/json-ld-syntax#165, by @2bigO.
-
Cyclic definitions in section 9 w3c/json-ld-syntax#160, by @pchampin.
-
Consistent use of Dublin Core prefixes w3c/json-ld-syntax#159, by @pchampin.
-
Aliasing languages in scoped context for a language map? w3c/json-ld-syntax#158, by @azaroth42.
-
-
6 issues closed.
-
Can SRI be used in JSON-LD and for which use cases? w3c/json-ld-syntax#86.
-
Cyclic definitions in section 9 w3c/json-ld-syntax#160.
-
Aliasing languages in scoped context for a language map? w3c/json-ld-syntax#158.
-
Additional restriction to `@sealed` term clearing w3c/json-ld-syntax#136.
-
Consistent use of Dublin Core prefixes w3c/json-ld-syntax#159.
-
-
11 issues received 27 new comments.
-
Consistent use of Dublin Core prefixes w3c/json-ld-syntax#159 (8 comments by @azaroth42, @gkellogg, @iherman, @pchampin)
-
Aliasing languages in scoped context for a language map? w3c/json-ld-syntax#158 (5 comments by @azaroth42, @gkellogg, @iherman, @pchampin)
-
Missing @type in expanded form when an id map is used in conjunction with @type in a term definition w3c/json-ld-syntax#165 (2 comments by @2bigO, @azaroth42)
-
Additional restriction to `@sealed` term clearing w3c/json-ld-syntax#136 (2 comments by @dlongley, @iherman)
-
what's the use of "@container": ["@id", "@set"] w3c/json-ld-syntax#140 (1 comment by @VladimirAlexiev)
-
-
9 pull requests opened.
-
ack script data and generated file w3c/json-ld-syntax#168, by @iherman.
-
Add a section on using HTML documents for contexts (and frames). w3c/json-ld-syntax#167, by @gkellogg.
-
Disallow terms which are compact IRIs or absolute IRIs w3c/json-ld-syntax#166, by @gkellogg.
-
Update security considerations w3c/json-ld-syntax#164, by @gkellogg.
-
Add @pchampin's suggested change to the definition of _graph object_. w3c/json-ld-syntax#163, by @gkellogg.
-
Change "dc" as a prefix to "dcterms". w3c/json-ld-syntax#162, by @gkellogg.
-
Add caveat on numbers being represented as double w3c/json-ld-syntax#161, by @gkellogg.
-
a number of small editorial changes w3c/json-ld-syntax#157, by @pchampin.
-
reflected the decisions about #136 w3c/json-ld-syntax#156, by @pchampin.
-
-
8 pull requests merged.
-
Disallow terms which are compact IRIs or absolute IRIs w3c/json-ld-syntax#166.
-
Update security considerations w3c/json-ld-syntax#164.
-
Add @pchampin's suggested change to the definition of _graph object_. w3c/json-ld-syntax#163.
-
Change "dc" as a prefix to "dcterms". w3c/json-ld-syntax#162.
-
Add caveat on numbers being represented as double w3c/json-ld-syntax#161.
-
describing property-based indexing as a variant of data indexing w3c/json-ld-syntax#145.
-
reflected the decisions about #136 w3c/json-ld-syntax#156.
-
a number of small editorial changes w3c/json-ld-syntax#157.
-
-
8 pull requests received 48 new comments.
-
ack script data and generated file w3c/json-ld-syntax#168 (7 comments by @BigBlueHat, @gkellogg, @iherman)
-
describing property-based indexing as a variant of data indexing w3c/json-ld-syntax#145 (7 comments by @gkellogg, @pchampin)
-
Add caveat on numbers being represented as double w3c/json-ld-syntax#161 (5 comments by @dlongley, @gkellogg, @iherman, @rubensworks)
-
Add a section on using HTML documents for contexts (and frames). w3c/json-ld-syntax#167 (4 comments by @deniak, @gkellogg)
-
Disallow terms which are compact IRIs or absolute IRIs w3c/json-ld-syntax#166 (4 comments by @dlongley, @gkellogg, @RichardWallis)
w3c/json-ld-api
-
1 issue opened.
-
More compact @prefix w3c/json-ld-api#76, by @rubensworks.
-
-
2 issues closed.
-
Round-tripping of large numbers without decimals incorrect w3c/json-ld-api#75.
-
RDF Deserialization and @index w3c/json-ld-api#65.
-
-
1 issue reopened.
-
What if a @context URL response is HTML? w3c/json-ld-api#66, by @BigBlueHat.
-
-
3 issues received 16 new comments.
-
What if a @context URL response is HTML? w3c/json-ld-api#66 (13 comments by @BigBlueHat, @dlongley, @gkellogg, @iherman)
-
Round-tripping of large numbers without decimals incorrect w3c/json-ld-api#75 (1 comment by @gkellogg)
-
-
7 pull requests opened.
-
Issue 66 html context w3c/json-ld-api#83, by @gkellogg.
-
Add checks for terms including a colon w3c/json-ld-api#82, by @gkellogg.
-
Update security considerations w3c/json-ld-api#81, by @gkellogg.
-
Use "dcterms" in favor of "dc". w3c/json-ld-api#80, by @gkellogg.
-
Update round-tripping of numbers w3c/json-ld-api#79, by @gkellogg.
-
Protected term errors w3c/json-ld-api#78, by @gkellogg.
-
toRdf tests for @prefix w3c/json-ld-api#77, by @rubensworks.
-
-
6 pull requests merged.
-
Add checks for terms including a colon w3c/json-ld-api#82.
-
Update security considerations w3c/json-ld-api#81.
-
Use "dcterms" in favor of "dc". w3c/json-ld-api#80.
-
Protected term errors w3c/json-ld-api#78.
-
Update round-tripping of numbers w3c/json-ld-api#79.
-
compaction and expansion of indexes using a property w3c/json-ld-api#74.
-
-
1 pull request closed.
-
Add `@protected` tests and a `protectedMode` flag. w3c/json-ld-api#69.
-
-
8 pull requests received 51 new comments.
-
Issue 66 html context w3c/json-ld-api#83 (14 comments by @dlongley, @gkellogg, @iherman, @pchampin, @rubensworks)
-
compaction and expansion of indexes using a property w3c/json-ld-api#74 (7 comments by @gkellogg, @pchampin)
-
Add checks for terms including a colon w3c/json-ld-api#82 (4 comments by @davidlehn, @dlongley, @gkellogg)
-
w3c/json-ld-bp
-
1 issue opened.
-
Add note on streaming w3c/json-ld-bp#3, by @rubensworks.
-
-
4 issues received 19 new comments.
-
Define a recommended context to import w3c/json-ld-bp#9 (8 comments by @dlongley, @gkellogg, @iherman, @pchampin)
-
Streaming Profiles for JSON-LD to/from RDF w3c/json-ld-bp#4 (4 comments by @gkellogg, @iherman, @rubensworks)
-
w3c/json-ld-framing
-
2 issues closed.
-
requireAll does not require @type and should w3c/json-ld-framing#40.
-
Explore supporting `"@embed": "@first"` w3c/json-ld-framing#43.
-
-
2 issues received 4 new comments.
-
5 pull requests opened.
-
Update security considerations w3c/json-ld-framing#52, by @gkellogg.
-
Replace `@first` and `@last` with `@once. w3c/json-ld-framing#51, by @gkellogg.
-
Update frame matching and add tests for requireAll w3c/json-ld-framing#50, by @gkellogg.
-
dummy commit w3c/json-ld-framing#49, by @deniak.
-
Use "dcterms" instead of both "dc" and "dc11". w3c/json-ld-framing#48, by @gkellogg.
-
-
4 pull requests merged.
-
Update frame matching and add tests for requireAll w3c/json-ld-framing#50.
-
Update security considerations w3c/json-ld-framing#52.
-
Replace `@first` and `@last` with `@once. w3c/json-ld-framing#51.
-
Use "dcterms" instead of both "dc" and "dc11". w3c/json-ld-framing#48.
-
-
1 pull request closed.
-
dummy commit w3c/json-ld-framing#49.
-
-
2 pull requests received 8 new comments.
-
Use "dcterms" instead of both "dc" and "dc11". w3c/json-ld-framing#48 (3 comments by @gkellogg, @iherman)
w3c/json-ld-rc
-
1 issue opened.
-
Review the initial content... w3c/json-ld-rc#1, by @iherman.
-
Participants
-
1 organization joined.
-
imec joined.
-
GitHub
w3c/json-ld-syntax
-
8 issues opened.
-
IRIs are terms can be misdefined w3c/json-ld-syntax#155, by @gkellogg.
-
Does @sealed consider order? w3c/json-ld-syntax#153, by @rubensworks.
-
Using explicit @prefix declaration to create compact IRIs w3c/json-ld-syntax#151, by @rubensworks.
-
DocumentLoader should be more visible in the specs w3c/json-ld-syntax#149, by @azaroth42.
-
Add security considerations section for URI schemes w3c/json-ld-syntax#148, by @azaroth42.
-
Add security consideration about IRI concatenation w3c/json-ld-syntax#147, by @azaroth42.
-
typo (?) in section 9 intro - https://w3c.github.io/json-ld-syntax/#json-ld-grammar w3c/json-ld-syntax#146, by @rdewaele.
-
Don't use `@vocab` with `http://schema.org/` w3c/json-ld-syntax#144, by @BigBlueHat.
-
-
10 issues closed.
-
Define term without @id if term previously defined w3c/json-ld-syntax#129.
-
what's the use of "@container": ["@id", "@set"] w3c/json-ld-syntax#140.
-
Does @sealed consider order? w3c/json-ld-syntax#153.
-
Don't use `@vocab` with `http://schema.org/` w3c/json-ld-syntax#144.
-
Rename `@sealed` to `@protected` w3c/json-ld-syntax#137.
-
Support JSON values that aren’t mapped w3c/json-ld-syntax#4.
-
Using explicit @prefix declaration to create compact IRIs w3c/json-ld-syntax#151.
-
Allow partial definition / redefinition of terms w3c/json-ld-syntax#116.
-
typo (?) in section 9 intro - https://w3c.github.io/json-ld-syntax/#json-ld-grammar w3c/json-ld-syntax#146.
-
small typo in Indexed Values w3c/json-ld-syntax#139.
-
-
2 issues reopened.
-
Define term without @id if term previously defined w3c/json-ld-syntax#129, by @azaroth42.
-
Does HTML's `<base>` effect `@context` IRI resolution? w3c/json-ld-syntax#134, by @azaroth42.
-
-
15 issues received 35 new comments.
-
Support JSON values that aren’t mapped w3c/json-ld-syntax#4 (9 comments by @azaroth42, @cyberphone, @gkellogg, @iherman, @pchampin)
-
Does @sealed consider order? w3c/json-ld-syntax#153 (6 comments by @azaroth42, @dlongley, @gkellogg, @iherman, @pchampin)
-
Define term without @id if term previously defined w3c/json-ld-syntax#129 (3 comments by @azaroth42, @gkellogg, @iherman)
-
Additional restriction to `@sealed` term clearing w3c/json-ld-syntax#136 (3 comments by @azaroth42, @dlongley)
-
what's the use of "@container": ["@id", "@set"] w3c/json-ld-syntax#140 (2 comments by @azaroth42, @iherman)
-
Using explicit @prefix declaration to create compact IRIs w3c/json-ld-syntax#151 (2 comments by @gkellogg)
-
typo (?) in section 9 intro - https://w3c.github.io/json-ld-syntax/#json-ld-grammar w3c/json-ld-syntax#146 (1 comment by @pchampin)
-
Does HTML's `<base>` effect `@context` IRI resolution? w3c/json-ld-syntax#134 (1 comment by @azaroth42)
-
-
6 pull requests opened.
-
Update default vocabulary used in examples to avoid schema.org w3c/json-ld-syntax#154, by @gkellogg.
-
Better phrasing of object equality w3c/json-ld-syntax#152, by @pchampin.
-
Define JSON literal and the `rdf:JSON` datatype. w3c/json-ld-syntax#150, by @gkellogg.
-
describing property-based indexing as a variant of data indexing w3c/json-ld-syntax#145, by @pchampin.
-
Fix typo. w3c/json-ld-syntax#143, by @davidlehn.
-
Change from "sealed" to "protected". w3c/json-ld-syntax#142, by @davidlehn.
-
-
5 pull requests merged.
-
Update default vocabulary used in examples to avoid schema.org w3c/json-ld-syntax#154.
-
Change from "sealed" to "protected". w3c/json-ld-syntax#142.
-
Better phrasing of object equality w3c/json-ld-syntax#152.
-
Define JSON literal and the `rdf:JSON` datatype. w3c/json-ld-syntax#150.
-
Fix typo. w3c/json-ld-syntax#143.
-
-
5 pull requests received 32 new comments.
-
Define JSON literal and the `rdf:JSON` datatype. w3c/json-ld-syntax#150 (13 comments by @gkellogg, @iherman, @pchampin, @rubensworks)
-
describing property-based indexing as a variant of data indexing w3c/json-ld-syntax#145 (9 comments by @gkellogg, @pchampin)
-
Change from "sealed" to "protected". w3c/json-ld-syntax#142 (6 comments by @davidlehn, @gkellogg, @iherman)
-
w3c/json-ld-wg
-
43 issues opened.
-
2019-03-29-action1: facilitate decision by July 1 for TPAC (Rob Sanderson) w3c/json-ld-wg#69, by @iherman.
-
2018-10-25-action6: raise a meta issue about BIDI and langString / HTML (Rob Sanderson) w3c/json-ld-wg#65, by @iherman.
-
2018-10-25-action3: create context signature issue, related to #20 (Rob Sanderson) w3c/json-ld-wg#64, by @iherman.
-
2018-10-25-action5: reach out to the TAG re #20 (Benjamin Young) w3c/json-ld-wg#66, by @iherman.
-
2018-10-25-action4: reach out to the TAG re #20 (Rob Sanderson) w3c/json-ld-wg#62, by @iherman.
-
2019-01-18-action1: update the playground instead of scribing (David I. Lehn) w3c/json-ld-wg#59, by @iherman.
-
2019-01-18-action2: update the web page (Rob Sanderson) w3c/json-ld-wg#58, by @iherman.
-
2019-01-18-action4: review azaroth's text and add further examples (Dave Longley) w3c/json-ld-wg#57, by @iherman.
-
2019-01-25-action1: ping niklas about rdflib plans for 1.1 (Rob Sanderson) w3c/json-ld-wg#54, by @iherman.
-
2019-01-25-action2: write spec text of his mental model (Pierre-Antoine Champin) w3c/json-ld-wg#55, by @iherman.
-
2019-02-08-action3: put comment in to #31 requesting more info (Rob Sanderson) w3c/json-ld-wg#53, by @iherman.
-
2019-03-01-action1: set up a new repo for the best practices (Ivan Herman) w3c/json-ld-wg#49, by @iherman.
-
2019-03-01-action1: set up a new repo for the best practices (Ivan Herman) w3c/json-ld-wg#48, by @iherman.
-
2019-03-01-action1: set up a new repo for the best practices (Ivan Herman) w3c/json-ld-wg#47, by @iherman.
-
2019-03-01-action1: set up a new repo for the best practices (Ivan Herman) w3c/json-ld-wg#46, by @iherman.
-
2019-03-01-action1: set up a new repo for the best practices (Ivan Herman) w3c/json-ld-wg#45, by @iherman.
-
2019-03-01-action1: set up a new repo for the best practices (Ivan Herman) w3c/json-ld-wg#44, by @iherman.
-
2019-03-01-action1: set up a new repo for the best practices (Ivan Herman) w3c/json-ld-wg#43, by @iherman.
-
2019-03-01-action1: set up a new repo for the best practices (Ivan Herman) w3c/json-ld-wg#42, by @iherman.
-
2019-03-01-action1: set up a new repo for the best practices (Ivan Herman) w3c/json-ld-wg#41, by @iherman.
-
2019-03-01-action1: set up a new repo for the best practices (Ivan Herman) w3c/json-ld-wg#40, by @iherman.
-
2019-03-01-action1: set up a new repo for the best practices (Ivan Herman) w3c/json-ld-wg#39, by @iherman.
-
2019-03-01-action1: set up a new repo for the best practices (Ivan Herman) w3c/json-ld-wg#38, by @iherman.
-
2019-03-01-action1: set up a new repo for the best practices (Ivan Herman) w3c/json-ld-wg#37, by @iherman.
-
2019-03-01-action1: set up a new repo for the best practices (Ivan Herman) w3c/json-ld-wg#36, by @iherman.
-
2019-03-01-action1: set up a new repo for the best practices (Ivan Herman) w3c/json-ld-wg#35, by @iherman.
-
2019-03-01-action1: set up a new repo for the best practices (Ivan Herman) w3c/json-ld-wg#34, by @iherman.
-
2019-01-18-action1: update the playground instead of scribing (David I. Lehn) w3c/json-ld-wg#30, by @iherman.
-
2019-01-18-action4: review azaroth's text and add further examples (Dave Longley) w3c/json-ld-wg#32, by @iherman.
-
2019-01-18-action2: update the web page (Rob Sanderson) w3c/json-ld-wg#33, by @iherman.
-
39 issues closed.
-
Testing and Implementation Details w3c/json-ld-wg#19.
-
Discuss layout of the specifications w3c/json-ld-wg#20.
-
2018-10-25-action5: reach out to the TAG re #20 (Benjamin Young) w3c/json-ld-wg#66.
-
2019-01-18-action2: update the web page (Rob Sanderson) w3c/json-ld-wg#58.
-
2018-10-25-action4: reach out to the TAG re #20 (Rob Sanderson) w3c/json-ld-wg#62.
-
2019-03-01-action1: set up a new repo for the best practices (Ivan Herman) w3c/json-ld-wg#49.
-
Consider using code from json-ld.org minutes for summary w3c/json-ld-wg#24.
-
2019-03-01-action1: set up a new repo for the best practices (Ivan Herman) w3c/json-ld-wg#48.
-
2019-03-01-action1: set up a new repo for the best practices (Ivan Herman) w3c/json-ld-wg#47.
-
2019-03-01-action1: set up a new repo for the best practices (Ivan Herman) w3c/json-ld-wg#46.
-
2019-03-01-action1: set up a new repo for the best practices (Ivan Herman) w3c/json-ld-wg#45.
-
2019-03-01-action1: set up a new repo for the best practices (Ivan Herman) w3c/json-ld-wg#44.
-
2019-03-01-action1: set up a new repo for the best practices (Ivan Herman) w3c/json-ld-wg#43.
-
2019-03-01-action1: set up a new repo for the best practices (Ivan Herman) w3c/json-ld-wg#42.
-
2019-03-01-action1: set up a new repo for the best practices (Ivan Herman) w3c/json-ld-wg#39.
-
2019-03-01-action1: set up a new repo for the best practices (Ivan Herman) w3c/json-ld-wg#40.
-
2019-03-01-action1: set up a new repo for the best practices (Ivan Herman) w3c/json-ld-wg#41.
-
2019-03-01-action1: set up a new repo for the best practices (Ivan Herman) w3c/json-ld-wg#36.
-
2019-03-01-action1: set up a new repo for the best practices (Ivan Herman) w3c/json-ld-wg#37.
-
2019-03-01-action1: set up a new repo for the best practices (Ivan Herman) w3c/json-ld-wg#38.
-
2019-03-01-action1: set up a new repo for the best practices (Ivan Herman) w3c/json-ld-wg#35.
-
2019-03-01-action1: set up a new repo for the best practices (Ivan Herman) w3c/json-ld-wg#34.
-
2019-01-18-action2: update the web page (Rob Sanderson) w3c/json-ld-wg#33.
-
21 issues received 25 new comments.
-
2019-01-18-action1: update the playground instead of scribing (David I. Lehn) w3c/json-ld-wg#59 (3 comments by @azaroth42, @davidlehn, @iherman)
-
2018-10-25-action6: raise a meta issue about BIDI and langString / HTML (Rob Sanderson) w3c/json-ld-wg#65 (3 comments by @azaroth42, @iherman)
-
2019-03-29-action2: make an issue for security issue on IRI as term definition (Gregg Kellogg) w3c/json-ld-wg#70 (1 comment by @gkellogg)
-
2019-02-08-action2: explore effect of `@nest+@container:@id` on compaction and expansion (Pierre-Antoine Champin) w3c/json-ld-wg#51 (1 comment by @azaroth42)
-
2019-02-08-action1: explore effect of `@nest+@container:@id` on compaction and expansion (Gregg Kellogg) w3c/json-ld-wg#52 (1 comment by @azaroth42)
-
2019-03-22-action1: provide example in issue frame/41 of `@omitdefault` need (Dave Longley) w3c/json-ld-wg#68 (1 comment by @dlongley)
-
2018-10-25-action2: create issues for ContextList and DocumentLoader editorial changes (Rob Sanderson) w3c/json-ld-wg#67 (1 comment by @azaroth42)
-
2018-10-25-action3: create context signature issue, related to #20 (Rob Sanderson) w3c/json-ld-wg#64 (1 comment by @azaroth42)
-
2018-10-26-action2: create security consideration re javascript URIs and relative IRIs (Rob Sanderson) w3c/json-ld-wg#61 (1 comment by @azaroth42)
-
2018-10-26-action1: make a security consideration issue re relative IRI concatenation (Rob Sanderson) w3c/json-ld-wg#60 (1 comment by @azaroth42)
-
2018-10-25-action5: reach out to the TAG re #20 (Benjamin Young) w3c/json-ld-wg#66 (1 comment by @azaroth42)
-
2019-01-18-action3: document simple input and expected processing of them (Rob Sanderson) w3c/json-ld-wg#56 (1 comment by @azaroth42)
-
2019-01-25-action1: ping niklas about rdflib plans for 1.1 (Rob Sanderson) w3c/json-ld-wg#54 (1 comment by @azaroth42)
-
2018-10-25-action4: reach out to the TAG re #20 (Rob Sanderson) w3c/json-ld-wg#62 (1 comment by @azaroth42)
-
2019-02-08-action3: put comment in to #31 requesting more info (Rob Sanderson) w3c/json-ld-wg#53 (1 comment by @azaroth42)
-
2019-01-18-action4: review azaroth's text and add further examples (Dave Longley) w3c/json-ld-wg#57 (1 comment by @dlongley)
-
2019-03-01-action1: set up a new repo for the best practices (Ivan Herman) w3c/json-ld-wg#49 (1 comment by @iherman)
-
2019-01-25-action2: write spec text of his mental model (Pierre-Antoine Champin) w3c/json-ld-wg#55 (1 comment by @pchampin)
-
-
1 pull request opened.
-
Should probably be :TermDefinition rather than :ExpandedTermDefinition. w3c/json-ld-wg#29, by @pchampin.
-
-
1 pull request merged.
-
Should probably be :TermDefinition rather than :ExpandedTermDefinition. w3c/json-ld-wg#29.
-
w3c/json-ld-framing
-
3 issues opened.
-
Improve example 18 for @omitDefault w3c/json-ld-framing#46, by @gkellogg.
-
Explore supporting `"@embed": "@first"` w3c/json-ld-framing#43, by @dlongley.
-
Remove @omitDefault? w3c/json-ld-framing#41, by @gkellogg.
-
-
7 issues closed.
-
Keywords for options w3c/json-ld-framing#37.
-
Improve example 18 for @omitDefault w3c/json-ld-framing#46.
-
Remove @omitDefault? w3c/json-ld-framing#41.
-
(Editorial) visually separate the different examples? w3c/json-ld-framing#35.
-
Define media profile for frames w3c/json-ld-framing#21.
-
Frames are indistinguishable from other JSON-LD documents w3c/json-ld-framing#28.
-
(Mostly) Editorial issues Part I w3c/json-ld-framing#36.
-
-
1 issue reopened.
-
Explore supporting `"@embed": "@first"` w3c/json-ld-framing#43, by @azaroth42.
-
-
8 issues received 25 new comments.
-
Explore supporting `"@embed": "@first"` w3c/json-ld-framing#43 (8 comments by @azaroth42, @gkellogg, @iherman)
-
Improve example 18 for @omitDefault w3c/json-ld-framing#46 (3 comments by @azaroth42, @dlongley, @iherman)
-
Provide an option for all terms to get a default "@container" w3c/json-ld-framing#31 (1 comment by @azaroth42)
-
(Editorial) visually separate the different examples? w3c/json-ld-framing#35 (1 comment by @gkellogg)
-
-
4 pull requests opened.
-
Add improved example for `@omitDefault`. w3c/json-ld-framing#47, by @gkellogg.
-
Fix typos. w3c/json-ld-framing#45, by @davidlehn.
-
Issue 43 embed first w3c/json-ld-framing#44, by @gkellogg.
-
Issue 36 editorial issues w3c/json-ld-framing#42, by @gkellogg.
-
-
4 pull requests merged.
-
Add improved example for `@omitDefault`. w3c/json-ld-framing#47.
-
Issue 43 embed first w3c/json-ld-framing#44.
-
Issue 36 editorial issues w3c/json-ld-framing#42.
-
Fix typos. w3c/json-ld-framing#45.
-
-
3 pull requests received 7 new comments.
w3c/json-ld-bp
-
2 issues opened.
-
Add example on order impact on @protected w3c/json-ld-bp#2, by @rubensworks.
-
Bring in existing Best Practices w3c/json-ld-bp#1, by @BigBlueHat.
-
-
2 issues received 13 new comments.
-
Streaming Profiles for JSON-LD to/from RDF w3c/json-ld-bp#4 (7 comments by @gkellogg, @iherman, @rubensworks, @simonstey)
-
Bring in existing Best Practices w3c/json-ld-bp#1 (6 comments by @ajs6f, @BigBlueHat, @gkellogg, @iherman)
-
w3c/json-ld-api
-
1 issue opened.
-
Round-tripping of large numbers without decimals incorrect w3c/json-ld-api#75, by @gkellogg.
-
-
1 issue closed.
-
Precedence of term redefinition in scope contexts w3c/json-ld-api#61.
-
-
5 issues received 22 new comments.
-
RDF Deserialization and @index w3c/json-ld-api#65 (13 comments by @azaroth42, @davidlehn, @gkellogg, @iherman, @pchampin, @vcharpenay)
-
Round-tripping of large numbers without decimals incorrect w3c/json-ld-api#75 (2 comments by @dlongley, @pchampin)
-
Ensure that blank node identifiers for anonymous graphs are reused w3c/json-ld-api#26 (2 comments by @ericprud, @swickr)
-
-
8 pull requests opened.
-
compaction and expansion of indexes using a property w3c/json-ld-api#74, by @gkellogg.
-
Add JavaScript Object property name tests. w3c/json-ld-api#73, by @davidlehn.
-
Support JSON Literals. w3c/json-ld-api#72, by @gkellogg.
-
Fix remote-doc-manifest context. w3c/json-ld-api#71, by @davidlehn.
-
Change from "sealed" to "protected". w3c/json-ld-api#70, by @davidlehn.
-
Add `@protected` tests and a `protectedMode` flag. w3c/json-ld-api#69, by @davidlehn.
-
Change from "sealed" to "protected". w3c/json-ld-api#68, by @davidlehn.
-
Test `<subject> <rdf:first> <rdf:nil>` triple. w3c/json-ld-api#67, by @davidlehn.
-
-
5 pull requests merged.
-
Change from "sealed" to "protected". w3c/json-ld-api#70.
-
Support JSON Literals. w3c/json-ld-api#72.
-
Add JavaScript Object property name tests. w3c/json-ld-api#73.
-
Fix remote-doc-manifest context. w3c/json-ld-api#71.
-
Test `<subject> <rdf:first> <rdf:nil>` triple. w3c/json-ld-api#67.
-
-
1 pull request closed.
-
Change from "sealed" to "protected". w3c/json-ld-api#68.
-
-
5 pull requests received 23 new comments.
-
Support JSON Literals. w3c/json-ld-api#72 (12 comments by @dlongley, @gkellogg, @iherman, @pchampin)
-
Add `@protected` tests and a `protectedMode` flag. w3c/json-ld-api#69 (5 comments by @davidlehn, @gkellogg, @iherman)
-
Test `<subject> <rdf:first> <rdf:nil>` triple. w3c/json-ld-api#67 (3 comments by @davidlehn, @gkellogg)
-
GitHub
w3c/json-ld-api
-
2 issues opened.
-
What if a @context URL response is HTML? w3c/json-ld-api#66, by @BigBlueHat.
-
RDF Deserialization and @index w3c/json-ld-api#65, by @vcharpenay.
-
-
5 issues closed.
-
HTML baseURI and @context? w3c/json-ld-api#53.
-
Circular imports: Abort, Retry, Fail? w3c/json-ld-api#14.
-
Option to specify level of compaction for literals & resources w3c/json-ld-api#33.
-
Ensure that blank node identifiers for anonymous graphs are reused w3c/json-ld-api#26.
-
Relax the colliding keywords constraint for @type w3c/json-ld-api#4.
-
-
7 issues received 23 new comments.
-
Precedence of term redefinition in scope contexts w3c/json-ld-api#61 (5 comments by @davidlehn, @gkellogg, @pchampin)
-
Ensure that blank node identifiers for anonymous graphs are reused w3c/json-ld-api#26 (5 comments by @azaroth42, @ericprud, @gkellogg)
-
Option to specify level of compaction for literals & resources w3c/json-ld-api#33 (2 comments by @azaroth42, @iherman)
-
-
3 pull requests opened.
-
Add literal value tests. w3c/json-ld-api#64, by @davidlehn.
-
Add support for `@type: @none` in term definitions. w3c/json-ld-api#63, by @gkellogg.
-
Issue 14 circular imports w3c/json-ld-api#62, by @gkellogg.
-
-
4 pull requests merged.
-
Add literal value tests. w3c/json-ld-api#64.
-
Add support for `@type: @none` in term definitions. w3c/json-ld-api#63.
-
Issue 14 circular imports w3c/json-ld-api#62.
-
Add support for sealed contexts and terms. w3c/json-ld-api#60.
-
-
1 pull request closed.
-
RFC: benchmarks w3c/json-ld-api#59.
-
-
4 pull requests received 14 new comments.
-
Add support for sealed contexts and terms. w3c/json-ld-api#60 (10 comments by @gkellogg, @iherman, @pchampin)
-
Add support for `@type: @none` in term definitions. w3c/json-ld-api#63 (2 comments by @azaroth42, @gkellogg)
-
w3c/json-ld-framing
-
4 issues opened.
-
requireAll does not require @type and should w3c/json-ld-framing#40, by @azaroth42.
-
Several frames in the same frame document? w3c/json-ld-framing#38, by @iherman.
-
Keywords for options w3c/json-ld-framing#37, by @iherman.
-
(Mostly) Editorial issues Part I w3c/json-ld-framing#36, by @iherman.
-
-
2 issues closed.
-
Recursion catch fails at top level w3c/json-ld-framing#30.
-
Provide an option for all terms to get a default "@container" w3c/json-ld-framing#31.
-
-
2 issues reopened.
-
Allow class-scoped framing w3c/json-ld-framing#29, by @azaroth42.
-
Framing blank node unnamed graphs w3c/json-ld-framing#27, by @gkellogg.
-
-
10 issues received 37 new comments.
-
Framing blank node unnamed graphs w3c/json-ld-framing#27 (8 comments by @dlongley, @gkellogg, @iherman)
-
(Mostly) Editorial issues Part I w3c/json-ld-framing#36 (8 comments by @azaroth42, @dlongley, @gkellogg, @iherman)
-
Frames are indistinguishable from other JSON-LD documents w3c/json-ld-framing#28 (3 comments by @gkellogg, @iherman)
-
Several frames in the same frame document? w3c/json-ld-framing#38 (3 comments by @azaroth42, @iherman)
-
Provide an option for all terms to get a default "@container" w3c/json-ld-framing#31 (2 comments by @iherman, @michaelcpuckett)
-
-
1 pull request opened.
-
Issue 28 media type w3c/json-ld-framing#39, by @gkellogg.
-
-
1 pull request merged.
-
Issue 28 media type w3c/json-ld-framing#39.
-
w3c/json-ld-syntax
-
15 issues opened.
-
can jsonld express multiple top-level graphs? w3c/json-ld-syntax#141, by @VladimirAlexiev.
-
what's the use of "@container": ["@id", "@set"] w3c/json-ld-syntax#140, by @VladimirAlexiev.
-
small typo in Indexed Values w3c/json-ld-syntax#139, by @VladimirAlexiev.
-
json-ld 1.1: @vocab gets ignored in nested @context with @id-typed values w3c/json-ld-syntax#138, by @lukasheinrich.
-
Rename `@sealed` to `@protected` w3c/json-ld-syntax#137, by @dlongley.
-
Additional restriction to `@sealed` term clearing w3c/json-ld-syntax#136, by @dlongley.
-
Does HTML's `<base>` effect `@context` IRI resolution? w3c/json-ld-syntax#134, by @BigBlueHat.
-
Define term without @id if term previously defined w3c/json-ld-syntax#129, by @gkellogg.
-
TriG graphs in JSON-LD w3c/json-ld-syntax#128, by @iherman.
-
Bunch of editorial issues, part II w3c/json-ld-syntax#127, by @iherman.
-
Alternative to graph containers? w3c/json-ld-syntax#125, by @iherman.
-
Bunch of editorial issues, part I w3c/json-ld-syntax#124, by @iherman.
-
IRI expansions in the context... a bit messy:-( w3c/json-ld-syntax#123, by @iherman.
-
Graph container text and implementation do not match... w3c/json-ld-syntax#122, by @iherman.
-
Term definitions in context that support multiple values for @type? w3c/json-ld-syntax#121, by @tcole3.
-
-
18 issues closed.
-
can jsonld express multiple top-level graphs? w3c/json-ld-syntax#141.
-
Introduce concept of "sealed” contexts w3c/json-ld-syntax#20.
-
Node Types in @context w3c/json-ld-syntax#76.
-
json-ld 1.1: @vocab gets ignored in nested @context with @id-typed values w3c/json-ld-syntax#138.
-
Graph container text and implementation do not match... w3c/json-ld-syntax#122.
-
how to set "@version" for a list of contexts? w3c/json-ld-syntax#85.
-
Confused about version triggering w3c/json-ld-syntax#99.
-
What if a sealed context sets `@vocab`? w3c/json-ld-syntax#120.
-
Bunch of editorial issues, part II w3c/json-ld-syntax#127.
-
Bunch of editorial issues, part I w3c/json-ld-syntax#124.
-
IRI expansions in the context... a bit messy:-( w3c/json-ld-syntax#123.
-
Term definitions in context that support multiple values for @type? w3c/json-ld-syntax#121.
-
IRI-s vs. URL-s w3c/json-ld-syntax#25.
-
Feature Detection in JSON-LD Processors w3c/json-ld-syntax#33.
-
Is there a scope context mechanism for clearing context definitions? w3c/json-ld-syntax#98.
-
Add ability to restrict overriding of terms with graph containers w3c/json-ld-syntax#87.
-
Rethinking datasets and graphs? w3c/json-ld-syntax#30.
-
Alternative to graph containers? w3c/json-ld-syntax#125.
-
-
26 issues received 111 new comments.
-
Introduce concept of "sealed” contexts w3c/json-ld-syntax#20 (21 comments by @ajs6f, @azaroth42, @cwebber, @dlongley, @gkellogg, @iherman, @pchampin, @tcole3)
-
TriG graphs in JSON-LD w3c/json-ld-syntax#128 (9 comments by @dlongley, @gkellogg, @iherman, @pchampin, @VladimirAlexiev)
-
Additional restriction to `@sealed` term clearing w3c/json-ld-syntax#136 (8 comments by @dlongley, @gkellogg, @iherman, @pchampin)
-
IRI expansions in the context... a bit messy:-( w3c/json-ld-syntax#123 (7 comments by @gkellogg, @pchampin)
-
Bunch of editorial issues, part I w3c/json-ld-syntax#124 (6 comments by @gkellogg, @iherman, @pchampin)
-
Consider context by reference with metadata w3c/json-ld-syntax#108 (6 comments by @ajs6f, @iherman, @simonstey)
-
what's the use of "@container": ["@id", "@set"] w3c/json-ld-syntax#140 (5 comments by @ajs6f, @dlongley, @gkellogg, @VladimirAlexiev)
-
Allow partial definition / redefinition of terms w3c/json-ld-syntax#116 (5 comments by @dlongley, @gkellogg, @iherman, @pchampin)
-
Does HTML's `<base>` effect `@context` IRI resolution? w3c/json-ld-syntax#134 (4 comments by @BigBlueHat, @gkellogg, @iherman)
-
Add ability to restrict overriding of terms with graph containers w3c/json-ld-syntax#87 (4 comments by @BigBlueHat, @gkellogg, @iherman)
-
can jsonld express multiple top-level graphs? w3c/json-ld-syntax#141 (2 comments by @iherman, @VladimirAlexiev)
-
json-ld 1.1: @vocab gets ignored in nested @context with @id-typed values w3c/json-ld-syntax#138 (2 comments by @gkellogg, @lukasheinrich)
-
What if a sealed context sets `@vocab`? w3c/json-ld-syntax#120 (2 comments by @azaroth42, @gkellogg)
-
Term definitions in context that support multiple values for @type? w3c/json-ld-syntax#121 (2 comments by @gkellogg, @iherman)
-
Is there a scope context mechanism for clearing context definitions? w3c/json-ld-syntax#98 (1 comment by @iherman)
-
Graph container text and implementation do not match... w3c/json-ld-syntax#122 (1 comment by @gkellogg)
-
-
6 pull requests opened.
-
Add grammar pieces for framing. w3c/json-ld-syntax#135, by @gkellogg.
-
Update implicit named graph example. w3c/json-ld-syntax#133, by @gkellogg.
-
Add a bit more explanation on `@version`. w3c/json-ld-syntax#132, by @gkellogg.
-
Expand compaction section w3c/json-ld-syntax#131, by @gkellogg.
-
Editorial issues w3c/json-ld-syntax#130, by @gkellogg.
-
Clarify compact IRI term example w3c/json-ld-syntax#126, by @gkellogg.
-
-
7 pull requests merged.
-
Add grammar pieces for framing. w3c/json-ld-syntax#135.
-
Update implicit named graph example. w3c/json-ld-syntax#133.
-
Expand compaction section w3c/json-ld-syntax#131.
-
Add a bit more explanation on `@version`. w3c/json-ld-syntax#132.
-
Editorial issues w3c/json-ld-syntax#130.
-
Proposed description of sealed contexts w3c/json-ld-syntax#119.
-
Clarify compact IRI term example w3c/json-ld-syntax#126.
-
-
6 pull requests received 48 new comments.
-
Update implicit named graph example. w3c/json-ld-syntax#133 (17 comments by @dlongley, @gkellogg, @iherman, @pchampin)
-
Proposed description of sealed contexts w3c/json-ld-syntax#119 (12 comments by @gkellogg, @iherman, @pchampin)
-
w3c/json-ld-wg
-
1 pull request opened.
-
Changes on F2F minutes w3c/json-ld-wg#28, by @iherman.
-
-
1 pull request merged.
-
Changes on F2F minutes w3c/json-ld-wg#28.
-
-
1 pull request received 6 new comments.
w3c/json-ld-bp
-
1 issue received 2 new comments.
GitHub
w3c/json-ld-syntax
-
4 issues opened.
-
What if a sealed context sets `@vocab`? w3c/json-ld-syntax#120, by @pchampin.
-
Distinguishing between strings and relative URIs w3c/json-ld-syntax#117, by @markwilkinson.
-
Allow partial definition / redefinition of terms w3c/json-ld-syntax#116, by @azaroth42.
-
Enable @context to map a property differently depending on its hierarchical path w3c/json-ld-syntax#115, by @dbooth-boston.
-
-
5 issues closed.
-
Distinguishing between strings and relative URIs w3c/json-ld-syntax#117.
-
Enable @context to map a property differently depending on its hierarchical path w3c/json-ld-syntax#115.
-
Allow relative IRIs for @vocab w3c/json-ld-syntax#72.
-
HTTP parameters for specifying context or frame w3c/json-ld-syntax#8.
-
Add SPARQL to the section I w3c/json-ld-syntax#109.
-
-
1 issue reopened.
-
Introduce concept of "sealed” contexts w3c/json-ld-syntax#20, by @azaroth42.
-
-
13 issues received 81 new comments.
-
Introduce concept of "sealed” contexts w3c/json-ld-syntax#20 (33 comments by @azaroth42, @BigBlueHat, @dlongley, @gkellogg, @iherman, @pchampin)
-
HTTP parameters for specifying context or frame w3c/json-ld-syntax#8 (15 comments by @ajs6f, @azaroth42, @BigBlueHat, @gkellogg, @iherman)
-
Consider context by reference with metadata w3c/json-ld-syntax#108 (8 comments by @ajs6f, @azaroth42, @gkellogg, @iherman, @pchampin)
-
Distinguishing between strings and relative URIs w3c/json-ld-syntax#117 (4 comments by @markwilkinson, @pchampin)
-
Allow relative IRIs for @vocab w3c/json-ld-syntax#72 (4 comments by @BigBlueHat, @gkellogg, @iherman)
-
Allow partial definition / redefinition of terms w3c/json-ld-syntax#116 (3 comments by @gkellogg, @iherman)
-
Is there a scope context mechanism for clearing context definitions? w3c/json-ld-syntax#98 (2 comments by @gkellogg, @iherman)
-
Enable @context to map a property differently depending on its hierarchical path w3c/json-ld-syntax#115 (2 comments by @dbooth-boston, @gkellogg)
-
Can SRI be used in JSON-LD and for which use cases? w3c/json-ld-syntax#86 (2 comments by @BigBlueHat, @iherman)
-
-
2 pull requests opened.
-
Proposed description of sealed contexts w3c/json-ld-syntax#119, by @pchampin.
-
Update text on vocabulary mapping and `@vocab` to allow relative IRIs w3c/json-ld-syntax#114, by @gkellogg.
-
-
2 pull requests merged.
-
Update text on vocabulary mapping and `@vocab` to allow relative IRIs w3c/json-ld-syntax#114.
-
Define additional profile URIs w3c/json-ld-syntax#111.
-
-
3 pull requests received 29 new comments.
-
Define additional profile URIs w3c/json-ld-syntax#111 (14 comments by @ajs6f, @BigBlueHat, @gkellogg, @iherman)
-
Update text on vocabulary mapping and `@vocab` to allow relative IRIs w3c/json-ld-syntax#114 (4 comments by @BigBlueHat, @gkellogg, @iherman)
-
w3c/json-ld-bp
-
2 issues opened.
-
Question about good practice for @id w3c/json-ld-bp#7, by @cristianvasquez.
-
Alias @none as none as best practice? w3c/json-ld-bp#6, by @azaroth42.
-
-
1 issue received 4 new comments.
-
Question about good practice for @id w3c/json-ld-bp#7 (4 comments by @cristianvasquez, @gkellogg, @pchampin)
-
w3c/json-ld-api
-
1 issue opened.
-
Precedence of term redefinition in scope contexts w3c/json-ld-api#61, by @pchampin.
-
-
4 pull requests opened.
-
Add support for sealed contexts and terms. w3c/json-ld-api#60, by @gkellogg.
-
RFC: benchmarks w3c/json-ld-api#59, by @davidlehn.
-
Relative vocab w3c/json-ld-api#58, by @gkellogg.
-
Use test-vocabulary in this repo, rather than json-ld.org. w3c/json-ld-api#57, by @gkellogg.
-
-
2 pull requests merged.
-
Relative vocab w3c/json-ld-api#58.
-
Use test-vocabulary in this repo, rather than json-ld.org. w3c/json-ld-api#57.
-
-
1 pull request closed.
-
Http profile w3c/json-ld-api#56.
-
-
4 pull requests received 15 new comments.
w3c/json-ld-framing
-
1 issue closed.
-
Modify the fist sentence in section 1 w3c/json-ld-framing#32.
-
-
1 issue received 1 new comment.
-
2 pull requests merged.
-
Improve the introduction w3c/json-ld-framing#33.
-
Update IANA section w3c/json-ld-framing#34.
-