JSON-LD Working Group - Activity
No matches.
TR publications
-
2 documents published.
-
YAML-LD 1.0 published twice as a Working Draft. History of YAML-LD 1.0
-
Past meetings
GitHub
w3c/json-ld-framing
-
1 issue received 1 new comment.
-
1 pull request opened.
-
algorithm treats array of nulls @json aware w3c/json-ld-framing#192, by @gobengo.
-
w3c/json-ld-api
-
3 issues opened.
-
No test covers inheritance of the default `@direction` across context layers w3c/json-ld-api#726, by @skydudie.
-
Consider supporting more that "string" values in a Language Map. w3c/json-ld-api#725, by @BigBlueHat.
-
2 issues received 2 new comments.
-
Consider supporting more that "string" values in a Language Map. w3c/json-ld-api#725 (1 comment by @daenney)
-
Is LoadDocumentCallback allowed to return a relative URL as documentUrl? w3c/json-ld-api#723 (1 comment by @anatoly-scherbakov)
-
-
3 pull requests opened.
-
remove all mentions of lexicographical(ly) w3c/json-ld-api#730, by @daenney.
-
remove all mentions of lexicographical(ly) w3c/json-ld-api#729, by @daenney.
-
Add tests for default @direction inheritance across context layers w3c/json-ld-api#727, by @skydudie.
-
-
1 pull request merged.
-
tests: add expand #t0132 (@base vs property keys) w3c/json-ld-api#686.
-
-
3 pull requests closed.
-
remove all mentions of lexicographical(ly) w3c/json-ld-api#729.
-
Add additional tests for @propagate w3c/json-ld-api#716.
-
expand: certain keywords are dropped w3c/json-ld-api#705.
-
-
5 pull requests received 9 new comments.
-
tests: add expand #t0132 (@base vs property keys) w3c/json-ld-api#686 (2 comments by @anatoly-scherbakov, @TallTed)
-
Add tests for default @direction inheritance across context layers w3c/json-ld-api#727 (1 comment by @w3cbot)
w3c/cbor-ld
-
3 issues closed.
-
round trip of JSON-LD documents that are arrays of maps w3c/cbor-ld#98.
-
Should raise an error if the CBOR-LD document is not a map w3c/cbor-ld#88.
-
Unclear step in 'decode' algorithm w3c/cbor-ld#87.
-
-
4 issues received 4 new comments.
-
What is are the "conformant registration" needs of a registration > 65,536? w3c/cbor-ld#115 (1 comment by @wes-smith)
-
2 pull requests opened.
-
add missing "closing tag" w3c/cbor-ld#128, by @pchampin.
-
Fix typo in input decoding instruction w3c/cbor-ld#127, by @TallTed.
-
-
4 pull requests received 29 new comments.
w3c/json-ld-wg
-
1 pull request opened.
-
Automatically sync common/ to other repos w3c/json-ld-wg#171, by @daenney.
-
-
1 pull request received 1 new comment.
w3c/yaml-ld
-
3 issues closed.
-
Separate YAML-LD and extended-profile publication workflows w3c/yaml-ld#246.
-
Build an implementations test report w3c/yaml-ld#227.
-
-
1 issue received 5 new comments.
-
YAML-LD Streams: blank node scope, empty elements, and alignment with RDF Messages w3c/yaml-ld#254 (5 comments by @anatoly-scherbakov, @ioggstream, @pietercolpaert)
-
-
2 pull requests opened.
-
Empty files, documents, and streams now considered non harmful w3c/yaml-ld#256, by @anatoly-scherbakov.
-
Clarify YAML-LD stream blank-node scope w3c/yaml-ld#255, by @anatoly-scherbakov.
-
-
3 pull requests merged.
-
246 separate yaml ld and extended profile publication workflows w3c/yaml-ld#247.
-
[#237]: Align Extended Profile with YAML-LD 1.0 streams w3c/yaml-ld#250.
-
Add Ruby YAML-LD implementation report w3c/yaml-ld#253.
-
-
3 pull requests received 15 new comments.
-
Empty files, documents, and streams now considered non harmful w3c/yaml-ld#256 (8 comments by @anatoly-scherbakov, @ioggstream, @TallTed)
-
Clarify YAML-LD stream blank-node scope w3c/yaml-ld#255 (6 comments by @anatoly-scherbakov, @BigBlueHat, @pietercolpaert)
-
246 separate yaml ld and extended profile publication workflows w3c/yaml-ld#247 (1 comment by @TallTed)
-
json-ld/json-ld-star
-
1 issue received 3 new comments.
w3c/json-ld-streaming
-
1 issue opened.
-
Non-propagating scoped contexts and `@nest` can trigger unpredictable buffering w3c/json-ld-streaming#69, by @daenney.
-
-
1 pull request merged.
-
Test: fixes the identifier of two tests w3c/json-ld-streaming#60.
-
-
1 pull request received 2 new comments.
w3c/json-ld-syntax
-
1 issue opened.
-
Allow null as a JSON-LD document root w3c/json-ld-syntax#501, by @anatoly-scherbakov.
-
-
2 issues received 2 new comments.
-
1 pull request opened.
-
Allow null as a JSON-LD document root w3c/json-ld-syntax#502, by @anatoly-scherbakov.
-
TR publications
-
8 documents published.
-
CBOR-LD 1.0 published 3 times as a Working Draft. History of CBOR-LD 1.0
-
YAML-LD 1.0 published 5 times as a Working Draft. History of YAML-LD 1.0
-
Past meetings
Participants
-
1 participant joined.
-
Daniele Sluijters (W3C Invited Experts) joined.
-
GitHub
w3c/cbor-ld
-
2 issues opened.
-
Parsing error type uniformity/SHOULD relaxation. w3c/cbor-ld#125, by @wes-smith.
-
not all valid JSON-LD documents can be semantically compressed with CBOR-LD w3c/cbor-ld#122, by @pchampin.
-
-
4 issues closed.
-
Update IANA contacts in spec and with IANA w3c/cbor-ld#81.
-
Discrepancy between the spec and the current registry? w3c/cbor-ld#71.
-
Add discussion of processing models and their uses. w3c/cbor-ld#47.
-
-
21 issues received 25 new comments.
-
Shouldn't the value of `@base` be compressed as a URL? w3c/cbor-ld#110 (2 comments by @pchampin, @wes-smith)
-
Outstanding questions regarding governance of the registry w3c/cbor-ld#82 (2 comments by @davidlehn, @pchampin)
-
Steps 2.6-2.7 in 5.2.6.4 Get Object Types for Decompression Algorithm look like a copy-paste error w3c/cbor-ld#107 (1 comment by @wes-smith)
-
Missing case in 5.2.6.3 Get Input Entries for Decompression Algorithm w3c/cbor-ld#105 (1 comment by @wes-smith)
-
Algorithm 5.5.1.2 Encode Context and 5.5.2.2 Encode Value are never called w3c/cbor-ld#104 (1 comment by @wes-smith)
-
why are both `typeTable` and `registryEntryId` passed to the JSON-LD to CBOR-LD encoding algorithm? w3c/cbor-ld#92 (1 comment by @wes-smith)
-
not all valid JSON-LD documents can be semantically compressed with CBOR-LD w3c/cbor-ld#122 (1 comment by @pchampin)
-
Example needed to demonstrate the difference between forms of compression w3c/cbor-ld#67 (1 comment by @wes-smith)
-
Discuss "uncompressed" CBOR-LD as a valid serialization without associated JSON-LD. w3c/cbor-ld#60 (1 comment by @wes-smith)
-
-
5 pull requests opened.
-
Fix type-scoped context algorithm signature mismatch. w3c/cbor-ld#126, by @wes-smith.
-
Fix decompression algorithm. w3c/cbor-ld#124, by @wes-smith.
-
Remove outdated reference to a varint. w3c/cbor-ld#123, by @wes-smith.
-
Add error check on CBOR byte parsing. w3c/cbor-ld#121, by @wes-smith.
-
Update IANA point of contact to be the WG. w3c/cbor-ld#120, by @wes-smith.
-
-
3 pull requests merged.
-
Add error check on CBOR byte parsing. w3c/cbor-ld#121.
-
Update IANA point of contact to be the WG. w3c/cbor-ld#120.
-
Various cleanups. w3c/cbor-ld#119.
-
-
2 pull requests closed.
-
Remove outdated reference to a varint. w3c/cbor-ld#123.
-
add json ld links w3c/cbor-ld#75.
-
-
8 pull requests received 14 new comments.
-
Add error check on CBOR byte parsing. w3c/cbor-ld#121 (5 comments by @dlongley, @pchampin, @wes-smith)
-
w3c/yaml-ld
-
2 issues opened.
-
Separate YAML-LD and extended-profile publication workflows w3c/yaml-ld#246, by @anatoly-scherbakov.
-
5 issues closed.
-
Fix localBiblio href for Extended Profile (TR URL 404s) w3c/yaml-ld#240.
-
Simplify mapping-as-key example w3c/yaml-ld#242.
-
Expand Security Considerations for YAML; cite RFC9512 for +yaml w3c/yaml-ld#235.
-
Align HTML embedding and IANA fragment identifiers with JSON-LD 1.1 w3c/yaml-ld#236.
-
Restore Basic-profile normative requirements stranded after #220 w3c/yaml-ld#230.
-
-
3 issues received 10 new comments.
-
YAML-LD Streams: blank node scope, empty elements, and alignment with RDF Messages w3c/yaml-ld#254 (8 comments by @anatoly-scherbakov, @BigBlueHat, @ioggstream, @pietercolpaert)
-
Align HTML embedding and IANA fragment identifiers with JSON-LD 1.1 w3c/yaml-ld#236 (1 comment by @anatoly-scherbakov)
-
-
8 pull requests opened.
-
Add Ruby YAML-LD implementation report w3c/yaml-ld#253, by @anatoly-scherbakov.
-
[#235]: Cite RFC9512 in Security and Interoperability Considerations w3c/yaml-ld#252, by @anatoly-scherbakov.
-
Update CODEOWNERS w3c/yaml-ld#251, by @iherman.
-
[#237]: Align Extended Profile with YAML-LD 1.0 streams w3c/yaml-ld#250, by @anatoly-scherbakov.
-
Simplify mapping-as-key example w3c/yaml-ld#248, by @anatoly-scherbakov.
-
246 separate yaml ld and extended profile publication workflows w3c/yaml-ld#247, by @anatoly-scherbakov.
-
Editorial cleanup from TallTed's post-#241 comments w3c/yaml-ld#245, by @anatoly-scherbakov.
-
-
6 pull requests merged.
-
Simplify mapping-as-key example w3c/yaml-ld#248.
-
[#235]: Cite RFC9512 in Security and Interoperability Considerations w3c/yaml-ld#252.
-
Update CODEOWNERS w3c/yaml-ld#251.
-
Editorial cleanup from TallTed's post-#241 comments w3c/yaml-ld#245.
-
Restore Basic-profile normative requirements stranded after #220 w3c/yaml-ld#241.
-
1 pull request received 5 new comments.
-
Restore Basic-profile normative requirements stranded after #220 w3c/yaml-ld#241 (5 comments by @BigBlueHat, @TallTed)
-
w3c/json-ld-api
-
5 issues opened.
-
Make `specVersion` interpretation more clear. w3c/json-ld-api#724, by @BigBlueHat.
-
Is LoadDocumentCallback allowed to return a relative URL as documentUrl? w3c/json-ld-api#723, by @mcb5637.
-
No test exercises a type-scoped context defined by an embedded context (expansion step 11.2) w3c/json-ld-api#719, by @skydudie.
-
What should happen when `@container` is the empty array w3c/json-ld-api#718, by @daenney.
-
Triage Errata and Discuss-Call for v1.2 / v1.3 / other w3c/json-ld-api#717, by @niklasl.
-
-
1 issue closed.
-
4 issues received 5 new comments.
-
If processing mode is json-ld-1.0, IRI-like terms should still be allowed to differ from their expanded forms w3c/json-ld-api#581 (2 comments by @BigBlueHat, @niklasl)
-
Term protection algorithm steps do not adequately protect `@vocab` w3c/json-ld-api#553 (1 comment by @BigBlueHat)
-
A remote context in a property-scoped context can override protected terms w3c/json-ld-api#708 (1 comment by @niklasl)
-
-
4 pull requests opened.
-
Add expand test for explicit xsd:string type coercion w3c/json-ld-api#722, by @skydudie.
-
Add tests for protected-term redefinition across IRI spellings w3c/json-ld-api#721, by @skydudie.
-
Add tests for type-scoped contexts defined by embedded contexts w3c/json-ld-api#720, by @skydudie.
-
Add additional tests for @propagate w3c/json-ld-api#716, by @daenney.
-
-
6 pull requests received 19 new comments.
-
tests: add expand #t0132 (@base vs property keys) w3c/json-ld-api#686 (7 comments by @anatoly-scherbakov, @niklasl, @TallTed)
-
Add additional tests for @propagate w3c/json-ld-api#716 (6 comments by @anatoly-scherbakov, @daenney)
-
Add processorFeature option to remote-doc #t0013. w3c/json-ld-api#687 (3 comments by @anatoly-scherbakov, @niklasl, @w3cbot)
-
Add tests for type-scoped contexts defined by embedded contexts w3c/json-ld-api#720 (1 comment by @w3cbot)
-
Add tests for protected-term redefinition across IRI spellings w3c/json-ld-api#721 (1 comment by @w3cbot)
-
w3c/json-ld-bp
-
1 issue closed.
-
Promote using an allow list of pre-downloaded contexts w3c/json-ld-bp#84.
-
-
1 issue received 2 new comments.
-
Serializing Large Collections (Hydra usage) w3c/json-ld-bp#93 (2 comments by @anatoly-scherbakov, @Ostrzyciel)
-
-
1 pull request merged.
-
Promote vetted JSON-LD contexts w3c/json-ld-bp#87.
-
-
2 pull requests received 4 new comments.
-
Serializing large collections - Pagination w3c/json-ld-bp#94 (3 comments by @canwaf, @niklasl, @pchampin)
-
w3c/json-ld-syntax
-
2 issues opened.
-
Use "Language Value Object" phrase within the specifications. w3c/json-ld-syntax#500, by @BigBlueHat.
-
Add note about `\u` entities being decoded via `JSON.parse()`. w3c/json-ld-syntax#499, by @BigBlueHat.
-
-
1 issue closed.
-
4 issues received 7 new comments.
-
Section 7.2 says escaped content remains escaped, but a major consumer applies one pass of unescaping w3c/json-ld-syntax#498 (4 comments by @BigBlueHat, @fabio-rovai, @TallTed)
-
avoid the term "remote" when talking of "context by reference" w3c/json-ld-syntax#487 (1 comment by @anatoly-scherbakov)
-
Add note about `\u` entities being decoded via `JSON.parse()`. w3c/json-ld-syntax#499 (1 comment by @fabio-rovai)
-
json-ld/json-ld-star
-
1 pull request received 1 new comment.
w3c/json-ld-framing
-
1 issue received 1 new comment.
TR publications
-
3 documents published.
-
CBOR-LD 1.0 published twice as a Working Draft. History of CBOR-LD 1.0
-
YAML-LD 1.0 published as a Working Draft. History of YAML-LD 1.0
-
Past meetings
Participants
-
1 participant left.
-
Yousouf Taghzouti (Inria) left.
-
GitHub
w3c/json-ld-syntax
-
1 issue opened.
-
Section 7.2 says escaped content remains escaped, but a major consumer applies one pass of unescaping w3c/json-ld-syntax#498, by @fabio-rovai.
-
-
1 issue received 7 new comments.
-
Section 7.2 says escaped content remains escaped, but a major consumer applies one pass of unescaping w3c/json-ld-syntax#498 (7 comments by @anatoly-scherbakov, @fabio-rovai, @pchampin)
-
w3c/json-ld-api
-
3 issues opened.
-
A remote context in a property-scoped context can override protected terms w3c/json-ld-api#708, by @daenney.
-
compaction: 12.7.1 empty array to 7.3 IRI compaction candidate w3c/json-ld-api#701, by @daenney.
-
expansion: string @value must not get @language/@direction if type mapping exists w3c/json-ld-api#700, by @daenney.
-
-
3 issues received 15 new comments.
-
A remote context in a property-scoped context can override protected terms w3c/json-ld-api#708 (10 comments by @anatoly-scherbakov, @BigBlueHat, @daenney, @niklasl, @TallTed)
-
compaction: 12.7.1 empty array to 7.3 IRI compaction candidate w3c/json-ld-api#701 (3 comments by @anatoly-scherbakov, @daenney)
-
expansion: string @value must not get @language/@direction if type mapping exists w3c/json-ld-api#700 (2 comments by @anatoly-scherbakov, @daenney)
-
-
12 pull requests opened.
-
Refresh published EARL reports w3c/json-ld-api#715, by @anatoly-scherbakov.
-
Add jsonld.js conformance validation w3c/json-ld-api#714, by @anatoly-scherbakov.
-
Add PyLD conformance validation w3c/json-ld-api#712, by @anatoly-scherbakov.
-
Add Ruby RDF JSON-LD conformance validation w3c/json-ld-api#711, by @anatoly-scherbakov.
-
Reenable example testing w3c/json-ld-api#710, by @anatoly-scherbakov.
-
Add PHP-JSON-LD implementation report w3c/json-ld-api#709, by @skydudie.
-
compaction: empty array and candidate selection w3c/json-ld-api#707, by @BigBlueHat.
-
expansion: add test for default language w3c/json-ld-api#706, by @BigBlueHat.
-
expand: certain keywords are dropped w3c/json-ld-api#705, by @daenney.
-
Skip report auto-commit for fork PRs w3c/json-ld-api#704, by @anatoly-scherbakov.
-
compaction: empty array and candidate selection w3c/json-ld-api#703, by @daenney.
-
expansion: add test for default language w3c/json-ld-api#702, by @daenney.
-
-
1 pull request merged.
-
Skip report auto-commit for fork PRs w3c/json-ld-api#704.
-
-
2 pull requests closed.
-
compaction: empty array and candidate selection w3c/json-ld-api#703.
-
expansion: add test for default language w3c/json-ld-api#702.
-
-
5 pull requests received 21 new comments.
-
expansion: add test for default language w3c/json-ld-api#702 (7 comments by @anatoly-scherbakov, @daenney, @w3cbot)
-
compaction: empty array and candidate selection w3c/json-ld-api#707 (4 comments by @BigBlueHat, @daenney, @niklasl)
-
compaction: empty array and candidate selection w3c/json-ld-api#703 (4 comments by @anatoly-scherbakov, @daenney, @w3cbot)
-
w3c/cbor-ld
-
1 issue opened.
-
suggestion: rename special type "url" to "@id" w3c/cbor-ld#118, by @pchampin.
-
-
3 issues closed.
-
cbor-ld to json-ld without semantic compression w3c/cbor-ld#97.
-
Codecs: discussion, algorithms, registry example. w3c/cbor-ld#64.
-
Ensure "processing model" is included as a registry entry option w3c/cbor-ld#29.
-
-
5 issues received 5 new comments.
-
2 pull requests opened.
-
Various cleanups. w3c/cbor-ld#119, by @davidlehn.
-
Get rid of encoders w3c/cbor-ld#117, by @pchampin.
-
-
3 pull requests merged.
-
Add processing model section and examples. w3c/cbor-ld#114.
-
clean mixed-style EOL in index.html w3c/cbor-ld#112.
-
simplify last steps of 'convert contexts for decompression' w3c/cbor-ld#103.
-
-
5 pull requests received 16 new comments.
-
Add processing model section and examples. w3c/cbor-ld#114 (11 comments by @pchampin, @TallTed, @wes-smith)
-
simplify last steps of 'convert contexts for decompression' w3c/cbor-ld#103 (2 comments by @pchampin, @wes-smith)
-
w3c/cbor-ld#116 (1 comment by @pchampin)
-
w3c/json-ld-bp
-
2 issues opened.
-
Serializing Large Collections (Hydra usage) w3c/json-ld-bp#93, by @canwaf.
-
-
1 issue received 2 new comments.
-
Serializing Large Collections (Hydra usage) w3c/json-ld-bp#93 (2 comments by @anatoly-scherbakov, @canwaf)
-
-
1 pull request opened.
-
Serializing large collections - Pagination w3c/json-ld-bp#94, by @canwaf.
-
-
2 pull requests received 22 new comments.
-
Serializing large collections - Pagination w3c/json-ld-bp#94 (14 comments by @anatoly-scherbakov, @canwaf, @TallTed)
-
Promote vetted JSON-LD contexts w3c/json-ld-bp#87 (8 comments by @anatoly-scherbakov, @simontaurus, @TallTed)
-
w3c/yaml-ld
-
1 issue opened.
-
Simplify mapping-as-key example w3c/yaml-ld#242, by @anatoly-scherbakov.
-
-
1 issue received 1 new comment.
-
1 pull request received 2 new comments.
-
Restore Basic-profile normative requirements stranded after #220 w3c/yaml-ld#241 (2 comments by @anatoly-scherbakov, @BigBlueHat)
-