JSON-LD Working Group - Activity in 2026
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
-
2 issues received 2 new comments.
-
1 pull request opened.
-
algorithm treats array of nulls @json aware w3c/json-ld-framing#192, by @gobengo.
-
w3c/yaml-ld
-
1 issue opened.
-
Retire `extractAllScripts` w3c/yaml-ld#258, by @anatoly-scherbakov.
-
-
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.
-
-
1 pull request closed.
-
Add remaining Use Case Issues. w3c/yaml-ld#37.
-
-
4 pull requests received 18 new comments.
-
Empty files, documents, and streams now considered non harmful w3c/yaml-ld#256 (9 comments by @anatoly-scherbakov, @ioggstream, @TallTed)
-
Clarify YAML-LD stream blank-node scope w3c/yaml-ld#255 (7 comments by @anatoly-scherbakov, @BigBlueHat, @pietercolpaert)
-
246 separate yaml ld and extended profile publication workflows w3c/yaml-ld#247 (1 comment by @TallTed)
-
w3c/json-ld-api
-
5 issues opened.
-
Add a reference to the recommendation in Best Practices regarding external contexts w3c/json-ld-api#735, by @niklasl.
-
Clarifications for how `@propagate` should be handled w3c/json-ld-api#734, by @daenney.
-
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)
-
-
6 pull requests opened.
-
expansion: add test for default language w3c/json-ld-api#733, by @daenney.
-
compaction: empty array and candidate selection w3c/json-ld-api#732, by @daenney.
-
expand: certain keywords are dropped w3c/json-ld-api#731, by @daenney.
-
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.
-
-
8 pull requests received 16 new comments.
-
expand: certain keywords are dropped w3c/json-ld-api#705 (3 comments by @anatoly-scherbakov, @daenney, @pchampin)
-
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/json-ld-syntax
-
2 issues opened.
-
Why not .ld.json file extension w3c/json-ld-syntax#503, by @egekorkan.
-
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.
-
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 issue received 1 new comment.
-
Non-propagating scoped contexts and `@nest` can trigger unpredictable buffering w3c/json-ld-streaming#69 (1 comment by @rubensworks)
-
-
1 pull request merged.
-
Test: fixes the identifier of two tests w3c/json-ld-streaming#60.
-
-
1 pull request received 2 new comments.
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.
json-ld/json-ld-star
-
1 issue received 3 new comments.
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)
-
TR publications
-
14 documents published.
-
YAML-LD 1.0 published 8 times as a Working Draft. History of YAML-LD 1.0
-
CBOR-LD 1.0 published 6 times as a Working Draft. History of CBOR-LD 1.0
-
Past meetings
GitHub
w3c/cbor-ld
-
16 issues opened.
-
What is are the "conformant registration" needs of a registration > 65,536? w3c/cbor-ld#115, by @BigBlueHat.
-
Idea: keep a range of registry entries for "local use"? w3c/cbor-ld#113, by @pchampin.
-
Relative context URLs in other contexts w3c/cbor-ld#111, by @pchampin.
-
Shouldn't the value of `@base` be compressed as a URL? w3c/cbor-ld#110, by @pchampin.
-
`@protected` enforcement is buggy, and possibly out-of-scope w3c/cbor-ld#109, by @pchampin.
-
Missing case in 5.2.6.3 Get Input Entries for Decompression Algorithm w3c/cbor-ld#105, by @pchampin.
-
Algorithm 5.5.1.2 Encode Context and 5.5.2.2 Encode Value are never called w3c/cbor-ld#104, by @pchampin.
-
round trip of JSON-LD documents that are arrays of maps w3c/cbor-ld#98, by @pchampin.
-
cbor-ld to json-ld without semantic compression w3c/cbor-ld#97, by @pchampin.
-
inconsistent invocation of 5.3.4 Apply Type Scoped Contexts Algorithm. w3c/cbor-ld#94, by @pchampin.
-
typos of pattern (can't put in issue title) w3c/cbor-ld#93, by @TallTed.
-
Should raise an error if the CBOR-LD document is not a map w3c/cbor-ld#88, by @pchampin.
-
Unclear step in 'decode' algorithm w3c/cbor-ld#87, by @pchampin.
-
-
1 issue closed.
-
Define registration process w3c/cbor-ld#46.
-
-
1 issue reopened.
-
inconsistent invocation of 5.3.4 Apply Type Scoped Contexts Algorithm. w3c/cbor-ld#94, by @pchampin.
-
-
4 issues received 7 new comments.
-
What is the role of parameter `output` in 5.2.3 General Conversion Algorithm? w3c/cbor-ld#91 (3 comments by @pchampin)
-
Algorithm 5.5.1.2 Encode Context and 5.5.2.2 Encode Value are never called w3c/cbor-ld#104 (2 comments by @pchampin)
-
-
14 pull requests opened.
-
Add processing model section and examples. w3c/cbor-ld#114, by @wes-smith.
-
clean mixed-style EOL in index.html w3c/cbor-ld#112, by @pchampin.
-
Signature of 5.3.5 Update Term Map Algorithm w3c/cbor-ld#108, by @pchampin.
-
typo: id→key in Get Input Entries for Decompression w3c/cbor-ld#106, by @pchampin.
-
simplify last steps of 'convert contexts for decompression' w3c/cbor-ld#103, by @pchampin.
-
fix 3 algorithms that do not need to return state w3c/cbor-ld#102, by @pchampin.
-
Add registration process. w3c/cbor-ld#101, by @wes-smith.
-
termInfo.definition is never used w3c/cbor-ld#100, by @pchampin.
-
align algorithms invocation with their signature (again) w3c/cbor-ld#96, by @pchampin.
-
align algorithms invocation with their signature w3c/cbor-ld#95, by @pchampin.
-
fix signature for Convert Document Algorithm w3c/cbor-ld#89, by @pchampin.
-
fix bug in 'CBOR-LD to JSON-LD decoding' w3c/cbor-ld#86, by @pchampin.
-
-
10 pull requests merged.
-
fix signature for Convert Document Algorithm w3c/cbor-ld#89.
-
Signature of 5.3.5 Update Term Map Algorithm w3c/cbor-ld#108.
-
typo: id→key in Get Input Entries for Decompression w3c/cbor-ld#106.
-
fix 3 algorithms that do not need to return state w3c/cbor-ld#102.
-
Add registration process. w3c/cbor-ld#101.
-
termInfo.definition is never used w3c/cbor-ld#100.
-
fix typo w3c/cbor-ld#99.
-
Add URL, Multibase, and xsd date/dateTime codecs. w3c/cbor-ld#85.
-
fix bug in 'CBOR-LD to JSON-LD decoding' w3c/cbor-ld#86.
-
fix typo w3c/cbor-ld#90.
-
-
3 pull requests closed.
-
Add registration process. w3c/cbor-ld#78.
-
align algorithms invocation with their signature (again) w3c/cbor-ld#96.
-
align algorithms invocation with their signature w3c/cbor-ld#95.
-
-
15 pull requests received 86 new comments.
-
Add URL, Multibase, and xsd date/dateTime codecs. w3c/cbor-ld#85 (28 comments by @TallTed, @w3cbot, @wes-smith)
-
Add registration process. w3c/cbor-ld#101 (9 comments by @BigBlueHat, @davidlehn, @iherman, @TallTed, @wes-smith)
-
simplify last steps of 'convert contexts for decompression' w3c/cbor-ld#103 (6 comments by @pchampin, @TallTed, @wes-smith)
-
fix signature for Convert Document Algorithm w3c/cbor-ld#89 (5 comments by @pchampin, @TallTed, @w3cbot, @wes-smith)
-
w3c/json-ld-framing
-
1 issue received 1 new comment.
w3c/yaml-ld
-
20 issues opened.
-
Fix localBiblio href for Extended Profile (TR URL 404s) w3c/yaml-ld#240, by @anatoly-scherbakov.
-
Update GitHub repo description: still says CG, not WG Rec-track WD w3c/yaml-ld#239, by @anatoly-scherbakov.
-
Align HTML embedding and IANA fragment identifiers with JSON-LD 1.1 w3c/yaml-ld#236, by @anatoly-scherbakov.
-
Expand Security Considerations for YAML; cite RFC9512 for +yaml w3c/yaml-ld#235, by @anatoly-scherbakov.
-
Rewrite Goal rationale; reduce repeated round-trip / superset claims w3c/yaml-ld#234, by @anatoly-scherbakov.
-
Nest Comments appendix B under Comments section w3c/yaml-ld#232, by @anatoly-scherbakov.
-
Add boolean mapping-key negative test w3c/yaml-ld#231, by @anatoly-scherbakov.
-
Restore Basic-profile normative requirements stranded after #220 w3c/yaml-ld#230, by @anatoly-scherbakov.
-
Context must be JSON-LD w3c/yaml-ld#228, by @anatoly-scherbakov.
-
Build an implementations test report w3c/yaml-ld#227, by @anatoly-scherbakov.
-
Track YAML-LD 1.0 to W3C Recommendation w3c/yaml-ld#226, by @anatoly-scherbakov.
-
Add example of invalid non-string mapping key to Mapping Key Types w3c/yaml-ld#223, by @anatoly-scherbakov.
-
Reference YAML processing diagram in spec structure w3c/yaml-ld#220, by @anatoly-scherbakov.
-
"YAML-LD document" seems to be used improperly w3c/yaml-ld#218, by @pchampin.
-
WHY? Please fail this project fast.... w3c/yaml-ld#216, by @daddydrac.
-
IANA registration for application/ld+yaml w3c/yaml-ld#214, by @pchampin.
-
-
8 issues closed.
-
Add example of invalid non-string mapping key to Mapping Key Types w3c/yaml-ld#223.
-
Reference YAML processing diagram in spec structure w3c/yaml-ld#220.
-
"YAML-LD document" seems to be used improperly w3c/yaml-ld#218.
-
meld JSON Schema and JSON-LD context/frame w3c/yaml-ld#54.
-
WHY? Please fail this project fast.... w3c/yaml-ld#216.
-
Use `respec-mermaid` plugin w3c/yaml-ld#210.
-
-
10 issues received 18 new comments.
-
WHY? Please fail this project fast.... w3c/yaml-ld#216 (5 comments by @anatoly-scherbakov, @daddydrac, @VladimirAlexiev)
-
Update GitHub repo description: still says CG, not WG Rec-track WD w3c/yaml-ld#239 (1 comment by @anatoly-scherbakov)
-
Restore Basic-profile normative requirements stranded after #220 w3c/yaml-ld#230 (1 comment by @TallTed)
-
Leave YAML-LD Extended profile out of bounds of the Community Report w3c/yaml-ld#88 (1 comment by @anatoly-scherbakov)
-
-
8 pull requests opened.
-
Restore Basic-profile normative requirements stranded after #220 w3c/yaml-ld#241, by @anatoly-scherbakov.
-
[#223]: Add example of invalid non-string mapping key w3c/yaml-ld#229, by @anatoly-scherbakov.
-
Vendor YAML processing diagram into our repository w3c/yaml-ld#225, by @anatoly-scherbakov.
-
[#220]: Restructure Core Requirements around YAML processing models w3c/yaml-ld#224, by @anatoly-scherbakov.
-
Note YAML-LD agent use and cite YAML vs JSON size comparison w3c/yaml-ld#222, by @anatoly-scherbakov.
-
[#218]: Fix YAML-LD document vs stream terminology w3c/yaml-ld#221, by @anatoly-scherbakov.
-
add intro explicitly refering to yaml processing steps w3c/yaml-ld#219, by @pchampin.
-
improve description of extractAllScripts for YAML streams w3c/yaml-ld#215, by @pchampin.
-
-
10 pull requests merged.
-
[#223]: Add example of invalid non-string mapping key w3c/yaml-ld#229.
-
[#220]: Restructure Core Requirements around YAML processing models w3c/yaml-ld#224.
-
Note YAML-LD agent use and cite YAML vs JSON size comparison w3c/yaml-ld#222.
-
Vendor YAML processing diagram into our repository w3c/yaml-ld#225.
-
[#218]: Fix YAML-LD document vs stream terminology w3c/yaml-ld#221.
-
Tighten Introduction section w3c/yaml-ld#213.
-
improve description of extractAllScripts for YAML streams w3c/yaml-ld#215.
-
add intro explicitly refering to yaml processing steps w3c/yaml-ld#219.
-
Make Mermaid visualizations stricter w3c/yaml-ld#212.
-
[#210]: Use respec-mermaid plugin w3c/yaml-ld#211.
-
-
6 pull requests received 22 new comments.
-
Note YAML-LD agent use and cite YAML vs JSON size comparison w3c/yaml-ld#222 (6 comments by @pchampin, @TallTed)
-
[#220]: Restructure Core Requirements around YAML processing models w3c/yaml-ld#224 (5 comments by @pchampin, @TallTed)
-
Tighten Introduction section w3c/yaml-ld#213 (5 comments by @anatoly-scherbakov, @pchampin, @w3cbot)
-
[#223]: Add example of invalid non-string mapping key w3c/yaml-ld#229 (2 comments by @anatoly-scherbakov, @TallTed)
-
w3c/json-ld-bp
-
1 pull request opened.
-
Use archived link for JSON-LD context caching article w3c/json-ld-bp#91, by @anatoly-scherbakov.
-
-
1 pull request merged.
-
Use archived link for JSON-LD context caching article w3c/json-ld-bp#91.
-
-
2 pull requests received 6 new comments.
-
Promote vetted JSON-LD contexts w3c/json-ld-bp#87 (3 comments by @anatoly-scherbakov, @BigBlueHat, @pchampin)
-
Use archived link for JSON-LD context caching article w3c/json-ld-bp#91 (3 comments by @TallTed, @w3cbot)
-
w3c/json-ld-api
-
1 issue opened.
-
Remove change tracking CSS classes related to differences from v1.0. w3c/json-ld-api#699, by @BigBlueHat.
-
-
2 issues closed.
-
RDF to Object Conversion drops type values if useNativeTypes is set to true w3c/json-ld-api#670.
-
Should we stop track changes since JSON-LD 1.0? w3c/json-ld-api#677.
-
-
3 issues received 6 new comments.
-
Remove change tracking CSS classes related to differences from v1.0. w3c/json-ld-api#699 (2 comments by @anatoly-scherbakov, @BigBlueHat)
-
Should we stop track changes since JSON-LD 1.0? w3c/json-ld-api#677 (2 comments by @BigBlueHat, @w3cbot)
-
Compaction cannot round-trip terms using `@container: @list` and `@type: @vocab` w3c/json-ld-api#558 (2 comments by @BigBlueHat, @w3cbot)
-
-
1 pull request merged.
-
Fix use native types flag with non-native values w3c/json-ld-api#671.
-
-
1 pull request closed.
-
Update titanium json-ld v2 EARL manifest w3c/json-ld-api#672.
-
-
1 pull request received 2 new comments.
-
Fix use native types flag with non-native values w3c/json-ld-api#671 (2 comments by @BigBlueHat, @w3cbot)
-
w3c/json-ld-syntax
-
1 issue opened.
-
Specify that contexts should be in JSON-LD w3c/json-ld-syntax#497, by @anatoly-scherbakov.
-
-
1 issue received 2 new comments.
-
Specify that contexts should be in JSON-LD w3c/json-ld-syntax#497 (2 comments by @BigBlueHat, @TallTed)
-
TR publications
-
10 documents published.
-
CBOR-LD 1.0 published twice as a Working Draft. History of CBOR-LD 1.0
-
YAML-LD 1.0 published 8 times as a Working Draft. History of YAML-LD 1.0
-
Past meetings
GitHub
w3c/cbor-ld
-
2 issues received 2 new comments.
-
2 pull requests opened.
-
Add URL, Multibase, and xsd date/dateTime codecs. w3c/cbor-ld#85, by @wes-smith.
-
Change all line endings to lf. w3c/cbor-ld#84, by @BigBlueHat.
-
-
3 pull requests merged.
-
Change all line endings to lf. w3c/cbor-ld#84.
-
fix broken links w3c/cbor-ld#77.
-
setup Echidna w3c/cbor-ld#83.
-
-
1 pull request closed.
-
Put line endings back to LF. w3c/cbor-ld#79.
-
-
1 pull request received 2 new comments.
w3c/yaml-ld
-
2 issues opened.
-
Use `respec-mermaid` plugin w3c/yaml-ld#210, by @anatoly-scherbakov.
-
Prefixes list is out of date w3c/yaml-ld#209, by @anatoly-scherbakov.
-
-
5 issues closed.
-
Unify YAML-LD & JSON-LD examples w3c/yaml-ld#94.
-
Anchors/aliases note breaks flow w3c/yaml-ld#197.
-
YARRRML Lessons learned w3c/yaml-ld#57.
-
Collecting JSON-LD file samples w3c/yaml-ld#10.
-
study CBOR-LD w3c/yaml-ld#16.
-
-
9 pull requests opened.
-
Tighten Introduction section w3c/yaml-ld#213, by @anatoly-scherbakov.
-
Make Mermaid visualizations stricter w3c/yaml-ld#212, by @anatoly-scherbakov.
-
[#210]: Use respec-mermaid plugin w3c/yaml-ld#211, by @anatoly-scherbakov.
-
Consolidate spec examples on intro.yamlld w3c/yaml-ld#208, by @anatoly-scherbakov.
-
Render YAML-LD examples as Mermaid graphs in the spec w3c/yaml-ld#207, by @anatoly-scherbakov.
-
[#94]: Unify spec examples under Proxima Centauri domain w3c/yaml-ld#206, by @anatoly-scherbakov.
-
Generate anchors and json-literal-expanded examples via pyld w3c/yaml-ld#205, by @anatoly-scherbakov.
-
Extract spec examples into separate files under `examples/` w3c/yaml-ld#204, by @anatoly-scherbakov.
-
-
6 pull requests merged.
-
Consolidate spec examples on intro.yamlld w3c/yaml-ld#208.
-
Render YAML-LD examples as Mermaid graphs in the spec w3c/yaml-ld#207.
-
[#94]: Unify spec examples under Proxima Centauri domain w3c/yaml-ld#206.
-
Generate anchors and json-literal-expanded examples via pyld w3c/yaml-ld#205.
-
Extract spec examples into separate files under `examples/` w3c/yaml-ld#204.
-
-
1 pull request received 1 new comment.
-
[#197]: Move YAML version requirement into a `versions` section, and move the note in Anchors & Aliases section w3c/yaml-ld#203 (1 comment by @TallTed)
-
w3c/json-ld-api
-
3 issues opened.
-
Reenable example testing. w3c/json-ld-api#698, by @BigBlueHat.
-
Cleanup some formatting of underscores. w3c/json-ld-api#697, by @BigBlueHat.
-
should we migrate CI scripts to another toolchain and/or reduce the scope of CI actions? w3c/json-ld-api#694, by @pchampin.
-
-
2 issues received 2 new comments.
-
Compaction cannot round-trip terms using `@container: @list` and `@type: @vocab` w3c/json-ld-api#558 (1 comment by @w3cbot)
-
should we migrate CI scripts to another toolchain and/or reduce the scope of CI actions? w3c/json-ld-api#694 (1 comment by @anatoly-scherbakov)
-
-
3 pull requests opened.
-
fix bug in Rakefile after removing common/ w3c/json-ld-api#693, by @pchampin.
-
use all common files by reference (to json-ld-wg) w3c/json-ld-api#692, by @pchampin.
-
finalize the removal of candidate corrections w3c/json-ld-api#691, by @pchampin.
-
-
7 pull requests merged.
-
fix bug in Rakefile after removing common/ w3c/json-ld-api#693.
-
finalize the removal of candidate corrections w3c/json-ld-api#691.
-
Improve test fromRdf#t0027. w3c/json-ld-api#669.
-
Add in memoriam text for @gkellogg. w3c/json-ld-api#675.
-
use all common files by reference (to json-ld-wg) w3c/json-ld-api#692.
-
prepare JSON-LD 1.2 API w3c/json-ld-api#690.
-
Remove `<ins>` and `<del>` markup in preparation for 1.2 w3c/json-ld-api#676.
-
-
10 pull requests received 25 new comments.
-
Fix use native types flag with non-native values w3c/json-ld-api#671 (14 comments by @niklasl, @pchampin, @TallTed, @w3cbot)
-
finalize the removal of candidate corrections w3c/json-ld-api#691 (2 comments by @pchampin, @w3cbot)
-
Remove `<ins>` and `<del>` markup in preparation for 1.2 w3c/json-ld-api#676 (1 comment by @anatoly-scherbakov)
-
w3c/json-ld-syntax
-
1 issue opened.
-
Cannot use `@reverse` combined with `"@container": "@id"` w3c/json-ld-syntax#496, by @bartkl.
-
-
5 issues closed.
-
Example 29 w3c/json-ld-syntax#476.
-
"Fred" should be "knows" w3c/json-ld-syntax#471.
-
4.1.8 Comma after “Expanding this document” w3c/json-ld-syntax#477.
-
is there a way to use `@container:@list` with custom props? w3c/json-ld-syntax#457.
-
URI in Profile triggers CORS Unsafe Request Header Byte rule w3c/json-ld-syntax#436.
-
-
5 issues received 11 new comments.
-
should JSON-LD 1.2 support RDF 1.2 basic ? w3c/json-ld-syntax#488 (4 comments by @daniel-fahey, @pchampin, @TallTed)
-
Terms defined using list containers only preserve the latest-declared list value? w3c/json-ld-syntax#492 (2 comments by @niklasl, @w3cbot)
-
is there a way to use `@container:@list` with custom props? w3c/json-ld-syntax#457 (2 comments by @BigBlueHat, @w3cbot)
-
URI in Profile triggers CORS Unsafe Request Header Byte rule w3c/json-ld-syntax#436 (2 comments by @BigBlueHat, @w3cbot)
-
-
4 pull requests merged.
-
Remove superfluous conditional in Example 29 text w3c/json-ld-syntax#483.
-
Fix Type Coercion text per issue 471 w3c/json-ld-syntax#482.
-
Editorial: remove comma in section 4.1.8 (issue #477) w3c/json-ld-syntax#481.
-
Remove the `<ins>` tag w3c/json-ld-syntax#479.
-
-
2 pull requests received 2 new comments.
json-ld/json-ld-star
-
1 issue received 2 new comments.
w3c/json-ld-bp
-
1 issue received 1 new comment.
-
Promote using an allow list of pre-downloaded contexts w3c/json-ld-bp#84 (1 comment by @anatoly-scherbakov)
-
-
2 pull requests opened.
-
Fix common.js to use document.respec.ready (ReSpec v37 CI) w3c/json-ld-bp#88, by @anatoly-scherbakov.
-
Promote vetted JSON-LD contexts w3c/json-ld-bp#87, by @anatoly-scherbakov.
-
-
2 pull requests merged.
-
sync common files w3c/json-ld-bp#86.
-
Fix common.js to use document.respec.ready (ReSpec v37 CI) w3c/json-ld-bp#88.
-
w3c/json-ld-wg
-
1 issue received 6 new comments.
-
Use common files by reference rather than by copy w3c/json-ld-wg#170 (6 comments by @anatoly-scherbakov, @pchampin)
-
-
1 pull request merged.
-
Delete package-lock.json w3c/json-ld-wg#164.
-
-
1 pull request received 1 new comment.
-
w3c/json-ld-wg#167 (1 comment by @pchampin)
-
w3c/json-ld-framing
-
1 pull request merged.
-
syncing common/terms.html with reference version w3c/json-ld-framing#189.
-
-
1 pull request received 1 new comment.
w3c/json-ld-streaming
-
1 pull request merged.
-
syncing common/terms.html with reference version w3c/json-ld-streaming#66.
-
-
1 pull request received 1 new comment.
TR publications
-
6 documents published.
-
YAML-LD 1.0 published 5 times as a Working Draft. History of YAML-LD 1.0
-
CBOR-LD 1.0 published as a Working Draft. History of CBOR-LD 1.0
-
Past meetings
Participants
-
1 participant left.
-
Ivan Herman (W3C) left.
-
GitHub
w3c/json-ld-api
-
1 issue received 1 new comment.
-
RDF to Object Conversion drops type values if useNativeTypes is set to true w3c/json-ld-api#670 (1 comment by @niklasl)
-
-
2 pull requests opened.
-
prepare JSON-LD 1.2 API w3c/json-ld-api#690, by @pchampin.
-
Add nested scoped context expansion test w3c/json-ld-api#689, by @anatoly-scherbakov.
-
-
3 pull requests received 7 new comments.
json-ld/json-ld-star
-
1 pull request opened.
-
syncing common/terms.html with reference version json-ld/json-ld-star#70, by @pchampin.
-
w3c/json-ld-streaming
-
1 pull request opened.
-
syncing common/terms.html with reference version w3c/json-ld-streaming#66, by @pchampin.
-
w3c/json-ld-framing
-
1 pull request opened.
-
syncing common/terms.html with reference version w3c/json-ld-framing#189, by @pchampin.
-
w3c/json-ld-bp
-
7 issues opened.
-
Promote long term caching of contexts w3c/json-ld-bp#85, by @anatoly-scherbakov.
-
Promote using an allow list of pre-downloaded contexts w3c/json-ld-bp#84, by @BigBlueHat.
-
Explore using Content Addressable URIs. w3c/json-ld-bp#83, by @BigBlueHat.
-
Providing a hash fragment on the context identifier/URI/URL. w3c/json-ld-bp#82, by @BigBlueHat.
-
Inline contexts w3c/json-ld-bp#81, by @BigBlueHat.
-
Explore `@sri` w3c/json-ld-bp#80, by @BigBlueHat.
-
Explore (and eventually define) Context Integrity approaches. w3c/json-ld-bp#79, by @BigBlueHat.
-
-
2 issues received 5 new comments.
-
Promote using an allow list of pre-downloaded contexts w3c/json-ld-bp#84 (4 comments by @anatoly-scherbakov, @BigBlueHat)
-
Providing a hash fragment on the context identifier/URI/URL. w3c/json-ld-bp#82 (1 comment by @niklasl)
-
-
1 pull request opened.
-
sync common files w3c/json-ld-bp#86, by @pchampin.
-
w3c/json-ld-wg
-
1 issue opened.
-
Use common files by reference rather than by copy w3c/json-ld-wg#170, by @pchampin.
-
w3c/yaml-ld
-
1 issue opened.
-
Broken links in YAML-LD 1.0 w3c/yaml-ld#201, by @dontcallmedom-bot.
-
-
2 issues closed.
-
Broken links in YAML-LD 1.0 w3c/yaml-ld#201.
-
YAML specific features are described inconsistenlty w3c/yaml-ld#194.
-
-
1 issue received 3 new comments.
-
Serializing JSON or YAML literal in YAML-LD w3c/yaml-ld#36 (3 comments by @anatoly-scherbakov, @pchampin, @VladimirAlexiev)
-
-
3 pull requests opened.
-
[#201] Fix broken documentLoader links w3c/yaml-ld#202, by @anatoly-scherbakov.
-
Fix common.js to use document.respec.ready (CI broken by respec v37) w3c/yaml-ld#200, by @anatoly-scherbakov.
-
Apply post-merge review suggestions from #196 w3c/yaml-ld#199, by @anatoly-scherbakov.
-
-
4 pull requests merged.
-
[#201] Fix broken documentLoader links w3c/yaml-ld#202.
-
[#194] Align YAML-LD feature comparison w3c/yaml-ld#198.
-
Fix common.js to use document.respec.ready (CI broken by respec v37) w3c/yaml-ld#200.
-
Apply post-merge review suggestions from #196 w3c/yaml-ld#199.
-
-
3 pull requests received 3 new comments.
-
Fix common.js to use document.respec.ready (CI broken by respec v37) w3c/yaml-ld#200 (1 comment by @niklasl)
w3c/json-ld-syntax
-
2 issues received 10 new comments.
-
should JSON-LD 1.2 support RDF 1.2 basic ? w3c/json-ld-syntax#488 (5 comments by @azaroth42, @TallTed)
-
Linking a JSON-LD context with an RDF-S/OWL schema w3c/json-ld-syntax#442 (5 comments by @DylanVanAssche, @TallTed, @trwnh)
-
w3c/cbor-ld
-
3 issues opened.
-
Outstanding questions regarding governance of the registry w3c/cbor-ld#82, by @wes-smith.
-
Update IANA contacts in spec and with IANA w3c/cbor-ld#81, by @BigBlueHat.
-
Normatively reference CBOR, CBOR tags, etc. w3c/cbor-ld#80, by @BigBlueHat.
-
-
1 issue received 2 new comments.
-
3 pull requests opened.
-
setup Echidna w3c/cbor-ld#83, by @pchampin.
-
Put line endings back to LF. w3c/cbor-ld#79, by @BigBlueHat.
-
Add registration process. w3c/cbor-ld#78, by @wes-smith.
-
-
2 pull requests received 11 new comments.
-
Add registration process. w3c/cbor-ld#78 (10 comments by @dlongley, @iherman, @pchampin, @TallTed, @wes-smith)
-
TR publications
-
4 documents published.
-
YAML-LD 1.0 published 3 times as a Working Draft. History of YAML-LD 1.0
-
CBOR-LD 1.0 published as a First Public Working Draft. History of CBOR-LD 1.0
-
Past meetings
Participants
-
1 participant joined.
-
Darius Kazemi (W3C Invited Experts) joined.
-
GitHub
w3c/json-ld-api
-
3 pull requests opened.
-
Add processorFeature option to remote-doc #t0013. w3c/json-ld-api#687, by @kphrx.
-
tests: add expand #t0132 (@base vs property keys) w3c/json-ld-api#686, by @anatoly-scherbakov.
-
Fix nullable LoadDocumentOptions callback argument w3c/json-ld-api#684, by @anatoly-scherbakov.
-
-
1 pull request merged.
-
Fix IDL definition of `LoadDocumentCallback` w3c/json-ld-api#664.
-
-
1 pull request closed.
-
Fix nullable LoadDocumentOptions callback argument w3c/json-ld-api#684.
-
-
2 pull requests received 7 new comments.
-
tests: add expand #t0132 (@base vs property keys) w3c/json-ld-api#686 (4 comments by @anatoly-scherbakov, @TallTed)
-
Fix nullable LoadDocumentOptions callback argument w3c/json-ld-api#684 (3 comments by @anatoly-scherbakov, @filip26, @pchampin)
-
w3c/yaml-ld
-
5 issues opened.
-
Anchors/aliases note breaks flow w3c/yaml-ld#197, by @anatoly-scherbakov.
-
Move anchors & aliases to Extended Profile? w3c/yaml-ld#195, by @anatoly-scherbakov.
-
YAML specific features are described inconsistenlty w3c/yaml-ld#194, by @anatoly-scherbakov.
-
Move Extended Profile into a separate NOTE document w3c/yaml-ld#191, by @anatoly-scherbakov.
-
-
4 issues closed.
-
Move anchors & aliases to Extended Profile? w3c/yaml-ld#195.
-
Move Extended Profile into a separate NOTE document w3c/yaml-ld#191.
-
Serializing JSON or YAML literal in YAML-LD w3c/yaml-ld#36.
-
Is Example 12 correct? w3c/yaml-ld#188.
-
-
3 issues received 8 new comments.
-
Move anchors & aliases to Extended Profile? w3c/yaml-ld#195 (3 comments by @iherman, @ioggstream, @pchampin)
-
Serializing JSON or YAML literal in YAML-LD w3c/yaml-ld#36 (3 comments by @anatoly-scherbakov, @pchampin, @VladimirAlexiev)
-
Create a YAML-LD namespace ontology (similar to https://www.w3.org/ns/json-ld) w3c/yaml-ld#192 (2 comments by @anatoly-scherbakov, @pchampin)
-
-
4 pull requests opened.
-
[#194] Align YAML-LD feature comparison w3c/yaml-ld#198, by @anatoly-scherbakov.
-
Clarify YAML-LD anchor and alias handling w3c/yaml-ld#196, by @anatoly-scherbakov.
-
[#191]: Move Extended Profile into a separate document w3c/yaml-ld#193, by @anatoly-scherbakov.
-
Fix stream expected outputs for name expansion w3c/yaml-ld#190, by @anatoly-scherbakov.
-
-
4 pull requests merged.
-
Clarify YAML-LD anchor and alias handling w3c/yaml-ld#196.
-
[#191]: Move Extended Profile into a separate document w3c/yaml-ld#193.
-
[#188]: Remove pseudo YAML tag syntax in C.4.1 heading w3c/yaml-ld#189.
-
-
1 pull request closed.
-
Fix stream expected outputs for name expansion w3c/yaml-ld#190.
-
-
3 pull requests received 14 new comments.
-
[#191]: Move Extended Profile into a separate document w3c/yaml-ld#193 (9 comments by @anatoly-scherbakov, @iherman)
-
Clarify YAML-LD anchor and alias handling w3c/yaml-ld#196 (4 comments by @anatoly-scherbakov, @TallTed)
-
[#36]: Add informative JSON literals section with YAML examples after Scalar Value Types w3c/yaml-ld#184 (1 comment by @pchampin)
-
w3c/cbor-ld
-
2 issues opened.
-
Discrepancy between the spec and the current registry? w3c/cbor-ld#71, by @iherman.
-
Discuss using "type maps" to annotate raw JSON. w3c/cbor-ld#68, by @wes-smith.
-
-
3 issues closed.
-
CBOR-LD Registry as RDF? w3c/cbor-ld#59.
-
Plain JSON is considered as compressed CBOR-LD w3c/cbor-ld#12.
-
12 issues received 14 new comments.
-
Ensure "processing model" is included as a registry entry option w3c/cbor-ld#29 (1 comment by @pchampin)
-
Example needed to demonstrate the difference between forms of compression w3c/cbor-ld#67 (1 comment by @pchampin)
-
Mark registry entry ID `10003` as reserved for impending CA DMV provisional registration w3c/cbor-ld#39 (1 comment by @wes-smith)
-
8 pull requests opened.
-
fix broken links w3c/cbor-ld#77, by @pchampin.
-
Prepare First Public Working Draft w3c/cbor-ld#76, by @pchampin.
-
add json ld links w3c/cbor-ld#75, by @BigBlueHat.
-
Update respecConfig since now in WG. w3c/cbor-ld#74, by @BigBlueHat.
-
docs: add selective links to JSON-LD spec(s) w3c/cbor-ld#72, by @jw408.
-
docs: update IANA Considerations with current registration links w3c/cbor-ld#70, by @jw409.
-
docs: add links to JSON-LD spec(s) w3c/cbor-ld#69, by @jw409.
-
-
3 pull requests merged.
-
Prepare First Public Working Draft w3c/cbor-ld#76.
-
Add discussion of processing model and semantic compression. w3c/cbor-ld#63.
-
-
4 pull requests closed.
-
Update respecConfig since now in WG. w3c/cbor-ld#74.
-
docs: add selective links to JSON-LD spec(s) w3c/cbor-ld#72.
-
docs: update IANA Considerations with current registration links w3c/cbor-ld#70.
-
docs: add links to JSON-LD spec(s) w3c/cbor-ld#69.
-
-
8 pull requests received 69 new comments.
-
Add discussion of processing model and semantic compression. w3c/cbor-ld#63 (32 comments by @pchampin, @TallTed, @wes-smith)
-
Apply writing and grammar fixes, remove constraints on registry dictionary format. w3c/cbor-ld#73 (15 comments by @BigBlueHat, @dlongley, @TallTed, @w3cbot, @wes-smith)
-
docs: update IANA Considerations with current registration links w3c/cbor-ld#70 (7 comments by @davidlehn, @jw409, @pchampin, @TallTed, @w3cbot)
-
docs: add selective links to JSON-LD spec(s) w3c/cbor-ld#72 (5 comments by @iherman, @jw409, @TallTed, @w3cbot, @wes-smith)
-
Prepare First Public Working Draft w3c/cbor-ld#76 (4 comments by @iherman, @pchampin, @w3cbot, @wes-smith)
-
w3c/json-ld-syntax
-
1 issue opened.
-
Terms defined using list containers only preserve the latest-declared list value? w3c/json-ld-syntax#492, by @trwnh.
-
-
1 issue received 8 new comments.
-
should JSON-LD 1.2 support RDF 1.2 basic ? w3c/json-ld-syntax#488 (8 comments by @akuckartz, @anatoly-scherbakov, @davidlehn, @iherman, @pchampin, @rubensworks)
-
TR publications
-
1 document published.
-
YAML-LD 1.0 published as a First Public Working Draft. History of YAML-LD 1.0
-
Past meetings
Participants
-
1 participant joined.
-
Jesse Wright (University of Oxford) joined.
-
-
1 organization joined.
-
University of Oxford joined.
-
GitHub
w3c/yaml-ld
-
4 issues opened.
-
Is Example 12 correct? w3c/yaml-ld#188, by @iherman.
-
Verify conformance to Manual of Style w3c/yaml-ld#187, by @anatoly-scherbakov.
-
Explain what YAML anchor is w3c/yaml-ld#183, by @anatoly-scherbakov.
-
should YAML-LD require YAML ≥ 1.2 ? w3c/yaml-ld#181, by @pchampin.
-
-
5 issues closed.
-
Explain what YAML anchor is w3c/yaml-ld#183.
-
Test: anchor names do not convey semantic information w3c/yaml-ld#103.
-
should YAML-LD require YAML ≥ 1.2 ? w3c/yaml-ld#181.
-
use regular expressions to resolve literals; URIs, CURIEs w3c/yaml-ld#83.
-
inconsistency in file extensions w3c/yaml-ld#176.
-
-
4 issues received 8 new comments.
-
should YAML-LD require YAML ≥ 1.2 ? w3c/yaml-ld#181 (4 comments by @anatoly-scherbakov, @davidlehn, @pchampin)
-
-
8 pull requests opened.
-
[#188]: Remove pseudo YAML tag syntax in C.4.1 heading w3c/yaml-ld#189, by @anatoly-scherbakov.
-
Fix a few GitHub repo links w3c/yaml-ld#186, by @anatoly-scherbakov.
-
[#181]: YAML-LD requires YAML ⩾ 1.2 w3c/yaml-ld#182, by @anatoly-scherbakov.
-
[#103]: Anchor names do not convey semantic information w3c/yaml-ld#180, by @anatoly-scherbakov.
-
Use `live-server` at `make serve` w3c/yaml-ld#179, by @anatoly-scherbakov.
-
Quote dates in tests w3c/yaml-ld#178, by @anatoly-scherbakov.
-
-
6 pull requests merged.
-
[#103]: Anchor names do not convey semantic information w3c/yaml-ld#180.
-
Fix a few GitHub repo links w3c/yaml-ld#186.
-
[#181]: YAML-LD requires YAML ⩾ 1.2 w3c/yaml-ld#182.
-
#83 YAML-LD is based on YAML Core schema (with exceptions) w3c/yaml-ld#174.
-
#176 Fix inconsistency in file extensions w3c/yaml-ld#177.
-
2 pull requests closed.
-
Use `live-server` at `make serve` w3c/yaml-ld#179.
-
Quote dates in tests w3c/yaml-ld#178.
-
-
7 pull requests received 45 new comments.
-
#83 YAML-LD is based on YAML Core schema (with exceptions) w3c/yaml-ld#174 (16 comments by @anatoly-scherbakov, @eemeli, @ioggstream)
-
[#36]: Add informative JSON literals section with YAML examples after Scalar Value Types w3c/yaml-ld#184 (9 comments by @anatoly-scherbakov, @iherman, @pchampin, @TallTed)
-
[#103]: Anchor names do not convey semantic information w3c/yaml-ld#180 (8 comments by @anatoly-scherbakov, @BigBlueHat, @iherman, @pchampin, @w3cbot)
-
[#183]: Add informative note on YAML anchors vs HTML links and URL fragments w3c/yaml-ld#185 (2 comments by @anatoly-scherbakov, @iherman)
-
w3c/cbor-ld
-
5 issues opened.
-
Example needed to demonstrate the difference between forms of compression w3c/cbor-ld#67, by @wes-smith.
-
Algorithms should use <var> instead of <code> w3c/cbor-ld#66, by @pchampin.
-
The spec lacks a "terminology" section w3c/cbor-ld#65, by @pchampin.
-
Codecs: discussion, algorithms, registry example. w3c/cbor-ld#64, by @wes-smith.
-
-
2 issues closed.
-
Update tag processing algorithms to match registration. w3c/cbor-ld#51.
-
SoTA research? w3c/cbor-ld#50.
-
-
4 issues received 4 new comments.
-
Example needed to demonstrate the difference between forms of compression w3c/cbor-ld#67 (1 comment by @TallTed)
-
Discuss "uncompressed" CBOR-LD as a valid serialization without associated JSON-LD. w3c/cbor-ld#60 (1 comment by @BigBlueHat)
-
-
3 pull requests opened.
-
Add discussion of processing model and semantic compression. w3c/cbor-ld#63, by @wes-smith.
-
Update tag processing algorithms. w3c/cbor-ld#62, by @wes-smith.
-
-
2 pull requests merged.
-
Update tag processing algorithms. w3c/cbor-ld#62.
-
3 pull requests received 41 new comments.
-
Add discussion of processing model and semantic compression. w3c/cbor-ld#63 (37 comments by @dlongley, @filip26, @iherman, @pchampin, @TallTed, @w3cbot, @wes-smith)
-
Update top-level encoding/decoding algorithms to support uncompressed use cases. w3c/cbor-ld#61 (2 comments by @w3cbot)
-
w3c/json-ld-syntax
-
4 issues opened.
-
extend language maps to support base direction w3c/json-ld-syntax#489, by @pchampin.
-
should JSON-LD 1.2 support RDF 1.2 basic ? w3c/json-ld-syntax#488, by @pchampin.
-
avoid the term "remote" when talking of "context by reference" w3c/json-ld-syntax#487, by @pchampin.
-
Included blocks + node identifier indexing w3c/json-ld-syntax#486, by @trwnh.
-
-
2 issues received 5 new comments.
-
Linking a JSON-LD context with an RDF-S/OWL schema w3c/json-ld-syntax#442 (3 comments by @pchampin, @trwnh)
-
extend language maps to support base direction w3c/json-ld-syntax#489 (2 comments by @anatoly-scherbakov, @pchampin)
-
-
1 pull request received 1 new comment.
-
w3c/json-ld-syntax#484 (1 comment by @w3cbot)
-
w3c/json-ld-bp
-
1 issue closed.
-
Update spec status and/or publish? w3c/json-ld-bp#43.
-
-
2 issues received 3 new comments.
-
2 pull requests merged.
-
Add h3 level headers for practices. w3c/json-ld-bp#74.
-
Add CODEOWNERS w/Editors, Chairs, Staff. w3c/json-ld-bp#75.
-
-
1 pull request closed.
-
Update specStatus to "unofficial". w3c/json-ld-bp#44.
-
-
1 pull request received 1 new comment.
w3c/json-ld-api
-
2 issues opened.
-
value object with `"@type": "rdf:langString"` w3c/json-ld-api#682, by @pchampin.
-
in term definition, the co-occurrence of `@language` and `@type` should be an error w3c/json-ld-api#681, by @pchampin.
-
-
2 issues received 9 new comments.
-
in term definition, the co-occurrence of `@language` and `@type` should be an error w3c/json-ld-api#681 (5 comments by @iherman, @pchampin)
-
value object with `"@type": "rdf:langString"` w3c/json-ld-api#682 (4 comments by @iherman, @pchampin)
-
Past meetings
Participants
-
1 participant joined.
-
Yousouf Taghzouti (Inria) joined.
-
-
12 participants left.
-
Ugur Acar (Depixen) left.
-
Yousouf Taghzouti (Inria) left.
-
Hu Liu (Jiangsu TPBlock Technology Co., Ltd. （江苏第三极区块链科技有限公司）) left.
-
Ricardo Iván Vieitez Parra (Apeleg Limited) left.
-
Alexandra Hitson (Tradeverifyd) left.
-
Jesse Wright (University of Oxford) left.
-
Mahmoud Alkhraishi (Mavennet Systems Inc.) left.
-
Timothée Haudebourg (Spruce Systems, Inc.) left.
-
Michael Prorock (Tradeverifyd) left.
-
Duy-Tung LUU (CANTON CONSULTING) left.
-
Jean-Yves ROSSI (CANTON CONSULTING) left.
-
Steve Blackmon (Apache Software Foundation) left.
-
-
3 organizations joined.
-
Inria joined.
-
Chinese Academy of Sciences joined.
-
Apache Software Foundation joined.
-
GitHub
w3c/yaml-ld
-
2 issues opened.
-
inconsistency in file extensions w3c/yaml-ld#176, by @pchampin.
-
Remove `/spec/` folder; match other repos. w3c/yaml-ld#171, by @BigBlueHat.
-
-
10 issues closed.
-
Should output type of `expand()` be `dict` or `str`? w3c/yaml-ld#143.
-
YAML Streams and JSON Sequences w3c/yaml-ld#63.
-
Best Practice 2 and 3 not specific to YAML-LD w3c/yaml-ld#72.
-
Remove `/spec/` folder; match other repos. w3c/yaml-ld#171.
-
investigate FHIR Shorthand (FSH) w3c/yaml-ld#98.
-
Add section: How to read this document w3c/yaml-ld#73.
-
Work Plan w3c/yaml-ld#75.
-
Iolanta: Linked Data visualization system w3c/yaml-ld#102.
-
IPR Commitments w3c/yaml-ld#163.
-
Conformance Tests w3c/yaml-ld#20.
-
-
15 issues received 28 new comments.
-
Should output type of `expand()` be `dict` or `str`? w3c/yaml-ld#143 (3 comments by @anatoly-scherbakov, @BigBlueHat, @w3cbot)
-
YAML Streams and JSON Sequences w3c/yaml-ld#63 (3 comments by @anatoly-scherbakov, @BigBlueHat, @w3cbot)
-
use regular expressions to resolve literals; URIs, CURIEs w3c/yaml-ld#83 (3 comments by @pchampin, @w3cbot)
-
Add section: How to read this document w3c/yaml-ld#73 (3 comments by @anatoly-scherbakov, @BigBlueHat)
-
Test: anchor names do not convey semantic information w3c/yaml-ld#103 (2 comments by @ioggstream, @w3cbot)
-
Downgrading from Extended Internal Representation should use value objects w3c/yaml-ld#84 (1 comment by @w3cbot)
-
-
11 pull requests opened.
-
#176 Fix inconsistency in file extensions w3c/yaml-ld#177, by @anatoly-scherbakov.
-
Fixing more broken links. w3c/yaml-ld#175, by @BigBlueHat.
-
#83 YAML-LD is based on YAML Core schema (with exceptions) w3c/yaml-ld#174, by @anatoly-scherbakov.
-
#72 Remove Best Practices section w3c/yaml-ld#173, by @anatoly-scherbakov.
-
#171 Move spec out of `spec` directory w3c/yaml-ld#172, by @anatoly-scherbakov.
-
Add CODEOWNERS w/Editors, Chairs, Staff. w3c/yaml-ld#170, by @BigBlueHat.
-
Prepare First Public Working Draft w3c/yaml-ld#169, by @pchampin.
-
#20 Reference exact test suite versions w3c/yaml-ld#168, by @anatoly-scherbakov.
-
fix links w3c/yaml-ld#167, by @BigBlueHat.
-
Specify editors, authors, and contributors w3c/yaml-ld#166, by @anatoly-scherbakov.
-
fix links in README.md to point to the w3c org w3c/yaml-ld#165, by @pchampin.
-
-
9 pull requests merged.
-
Fixing more broken links. w3c/yaml-ld#175.
-
Add CODEOWNERS w/Editors, Chairs, Staff. w3c/yaml-ld#170.
-
#72 Remove Best Practices section w3c/yaml-ld#173.
-
#171 Move spec out of `spec` directory w3c/yaml-ld#172.
-
Prepare First Public Working Draft w3c/yaml-ld#169.
-
fix links w3c/yaml-ld#167.
-
#20 Reference exact test suite versions w3c/yaml-ld#168.
-
Specify editors, authors, and contributors w3c/yaml-ld#166.
-
fix links in README.md to point to the w3c org w3c/yaml-ld#165.
-
-
6 pull requests received 11 new comments.
-
Specify editors, authors, and contributors w3c/yaml-ld#166 (3 comments by @BigBlueHat, @TallTed, @w3cbot)
w3c/cbor-ld
-
3 issues opened.
-
CBOR-LD Registry as RDF? w3c/cbor-ld#59, by @anatoly-scherbakov.
-
Update IANA CBOR Tag registration links. w3c/cbor-ld#56, by @davidlehn.
-
Add links to JSON-LD spec(s). w3c/cbor-ld#55, by @BigBlueHat.
-
-
1 issue closed.
-
Connect registry section to registry repository. w3c/cbor-ld#52.
-
-
3 issues received 3 new comments.
-
2 pull requests opened.
-
Add CODEOWNERS w/Editors, Chairs, Staff. w3c/cbor-ld#58, by @BigBlueHat.
-
fix links w3c/cbor-ld#57, by @BigBlueHat.
-
-
4 pull requests merged.
-
Add CODEOWNERS w/Editors, Chairs, Staff. w3c/cbor-ld#58.
-
fix links w3c/cbor-ld#57.
-
Remove tag registration issue, cleanup wording around CBOR tag. w3c/cbor-ld#54.
-
-
1 pull request closed.
-
Add OpenBadges v3.0.0 context URL to registry. w3c/cbor-ld#22.
-
-
4 pull requests received 8 new comments.
-
Remove inline registry table, point to external repository/document. w3c/cbor-ld#53 (4 comments by @BigBlueHat, @TallTed, @wes-smith)
-
Remove tag registration issue, cleanup wording around CBOR tag. w3c/cbor-ld#54 (1 comment by @wes-smith)
-
w3c/json-ld-api
-
1 pull request opened.
-
`LoadDocumentOptions` default value syntax is invalid w3c/json-ld-api#680, by @anatoly-scherbakov.
-
-
1 pull request closed.
-
`LoadDocumentOptions` default value syntax is invalid w3c/json-ld-api#680.
-
-
1 pull request received 1 new comment.
-
w3c/json-ld-api#679 (1 comment by @w3cbot)
-
w3c/json-ld-rc
-
1 pull request received 1 new comment.
-
w3c/json-ld-rc#54 (1 comment by @anatoly-scherbakov)
-
w3c/json-ld-syntax
-
3 issues received 4 new comments.
-
Linking a JSON-LD context with an RDF-S/OWL schema w3c/json-ld-syntax#442 (2 comments by @nichtich, @pchampin)
-
-
3 pull requests opened.
-
Remove superfluous conditional in Example 29 text w3c/json-ld-syntax#483, by @anatoly-scherbakov.
-
Fix Type Coercion text per issue 471 w3c/json-ld-syntax#482, by @anatoly-scherbakov.
-
Editorial: remove comma in section 4.1.8 (issue #477) w3c/json-ld-syntax#481, by @anatoly-scherbakov.
-
-
1 pull request received 1 new comment.
-
w3c/json-ld-syntax#485 (1 comment by @w3cbot)
-
w3c/json-ld-bp
-
2 issues received 2 new comments.
-
2 pull requests opened.
-
Add CODEOWNERS w/Editors, Chairs, Staff. w3c/json-ld-bp#75, by @BigBlueHat.
-
Add h3 level headers for practices. w3c/json-ld-bp#74, by @BigBlueHat.
-
-
3 pull requests received 3 new comments.
-
w3c/json-ld-bp#68 (1 comment by @BigBlueHat)
w3c/json-ld-framing
-
1 issue opened.
-
Setting `@graph: []` in a frame throws an unexpected error. w3c/json-ld-framing#183, by @BigBlueHat.
-
-
1 issue received 1 new comment.
w3c/json-ld-streaming
-
1 pull request opened.
-
Test: fixes the identifier of two tests w3c/json-ld-streaming#60, by @Tpt.
-
-
1 pull request received 1 new comment.
Lifecycle
Past meetings
Participants
-
1 chair appointed.
-
Victor Lu became a chair.
-
-
4 participants joined.
-
Wesley Smith (Digital Bazaar) joined.
-
Evan Prodromou (Social Web Foundation) joined.
-
Aaron Coburn (Inrupt Inc.) joined.
-
Jesse Wright (University of Oxford) joined.
-
-
9 organizations joined.
-
J. Paul Getty Trust joined.
-
imec joined.
-
OpenLink Software Inc. joined.
-
National Library of Sweden joined.
-
Social Web Foundation joined.
-
Inrupt Inc. joined.
-
Adobe joined.
-
Digital Bazaar joined.
-
University of Oxford joined.
-
-
19 organizations left.
-
University of Oxford left.
-
Depixen left.
-
Inria left.
-
Jiangsu TPBlock Technology Co., Ltd. （江苏第三极区块链科技有限公司） left.
-
National Library of Sweden left.
-
Chinese Academy of Sciences left.
-
CANTON CONSULTING left.
-
J. Paul Getty Trust left.
-
Inrupt Inc. left.
-
Google LLC left.
-
Spruce Systems, Inc. left.
-
Apache Software Foundation left.
-
Tradeverifyd left.
-
imec left.
-
Mavennet Systems Inc. left.
-
Adobe left.
-
OpenLink Software Inc. left.
-
Apeleg Limited left.
-
Digital Bazaar left.
-
GitHub
w3c/json-ld-syntax
-
1 issue opened.
-
Consistency of files under `./common` w3c/json-ld-syntax#480, by @pchampin.
-
-
8 issues received 11 new comments.
-
Expected interaction between nested properties and contexts? w3c/json-ld-syntax#469 (3 comments by @BigBlueHat, @filip26, @hcayless)
-
Consistency of files under `./common` w3c/json-ld-syntax#480 (2 comments by @anatoly-scherbakov, @pchampin)
-
Feat: add `rel="http://www.w3.org/ns/json-ld#type"` link relation. w3c/json-ld-syntax#470 (1 comment by @BigBlueHat)
-
Clarification: Example 45, expansion of interest.name w3c/json-ld-syntax#478 (1 comment by @BigBlueHat)
-
-
1 pull request opened.
-
Remove the `<ins>` tag w3c/json-ld-syntax#479, by @anatoly-scherbakov.
-
-
1 pull request received 6 new comments.
w3c/json-ld-wg
-
1 pull request received 1 new comment.
-
w3c/json-ld-wg#168 (1 comment by @anatoly-scherbakov)
-
json-ld/minutes
-
1 issue opened.
-
ToCs on the main index.html are incomplete json-ld/minutes#18, by @pchampin.
-
w3c/json-ld-api
-
1 issue opened.
-
Should we stop track changes since JSON-LD 1.0? w3c/json-ld-api#677, by @pchampin.
-
-
1 issue received 3 new comments.
-
Should we stop track changes since JSON-LD 1.0? w3c/json-ld-api#677 (3 comments by @anatoly-scherbakov, @niklasl)
-
-
1 pull request opened.
-
Remove `<ins>` and `<del>` markup in preparation for 1.2 w3c/json-ld-api#676, by @niklasl.
-
-
1 pull request received 8 new comments.
-
Remove `<ins>` and `<del>` markup in preparation for 1.2 w3c/json-ld-api#676 (8 comments by @davidlehn, @iherman, @niklasl, @pchampin)
-
w3c/cbor-ld
-
2 pull requests opened.
-
Remove tag registration issue, cleanup wording around CBOR tag. w3c/cbor-ld#54, by @wes-smith.
-
Remove inline registry table, point to external repository/document. w3c/cbor-ld#53, by @wes-smith.
-
w3c/yaml-ld
-
1 pull request merged.
-
Add In Memoriam text for @gkellogg w3c/yaml-ld#164.
-