JSON-LD Working Group - Activity in 2022
No matches.
Lifecycle
-
1 charter extension.
-
Charter extended until 31 January 2023.
-
Participants
-
1 participant joined.
-
Jesse Wright (University of Oxford) joined.
-
-
1 organization joined.
-
Inrupt Inc. joined.
-
GitHub
w3c/json-ld-framing
-
1 issue opened.
-
Possible bug with `@json` being treated as invalid `type` in frame w3c/json-ld-framing#142, by @dlongley.
-
-
1 issue closed.
-
Ex. 41 Playground doesn't contain `@omitGraph: false` + playground does not apply `@omitGraph` w3c/json-ld-framing#116.
-
-
1 issue received 7 new comments.
-
Possible bug with `@json` being treated as invalid `type` in frame w3c/json-ld-framing#142 (7 comments by @davidlehn, @gkellogg, @pasquale95)
-
-
1 pull request opened.
-
Added tests for `@json` field testcase in framing w3c/json-ld-framing#144, by @pasquale95.
-
-
2 pull requests merged.
-
Added tests for `@json` field testcase in framing w3c/json-ld-framing#144.
-
Fix omitgraph example w3c/json-ld-framing#139.
-
-
1 pull request received 5 new comments.
-
Added tests for `@json` field testcase in framing w3c/json-ld-framing#144 (5 comments by @gkellogg, @w3cbot)
-
w3c/json-ld-api
-
1 issue opened.
-
blind spot in RDF to object conversion w3c/json-ld-api#555, by @pchampin.
-
-
2 issues received 4 new comments.
-
Is the possibility of having `@id: null` in an expanded document intended? w3c/json-ld-api#480 (1 comment by @timothee-haudebourg)
-
1 pull request received 1 new comment.
-
w3c/json-ld-api#554 (1 comment by @w3cbot)
-
w3c/json-ld-syntax
-
1 issue closed.
-
Define rdf:type for nested objects w3c/json-ld-syntax#403.
-
-
1 issue received 2 new comments.
GitHub
w3c/json-ld-syntax
-
4 issues opened.
-
RDF* in CBOR? w3c/json-ld-syntax#451, by @ChristopherA.
-
Define rdf:type for nested objects w3c/json-ld-syntax#403, by @weissjoh.
-
IKMF w3c/json-ld-syntax#401, by @DirectorIKMF.
-
-
2 issues received 8 new comments.
-
Define rdf:type for nested objects w3c/json-ld-syntax#403 (7 comments by @AtesComp, @gkellogg, @simonstey, @TallTed, @weissjoh)
-
w3c/json-ld-api
-
2 issues opened.
-
Term protection algorithm steps do not adequately protect `@vocab` w3c/json-ld-api#553, by @dlongley.
-
Change "Lexicographical Order" (and related) to "Unicode code point order". w3c/json-ld-api#552, by @gkellogg.
-
-
2 issues received 5 new comments.
-
Compaction of IRIs with "@list" @container for sets of @list w3c/json-ld-api#547 (3 comments by @gkellogg, @tchoutri)
-
Term protection algorithm steps do not adequately protect `@vocab` w3c/json-ld-api#553 (2 comments by @dlongley, @gkellogg)
-
w3c/cbor-ld
-
2 issues opened.
-
Document codec value gap w3c/cbor-ld#16, by @davidlehn.
-
Add Open Badges v3 context w3c/cbor-ld#15, by @davidlehn.
-
-
1 issue received 1 new comment.
w3c/json-ld-framing
-
1 issue opened.
-
Change "Lexicographical Order" (and related) to "Unicode code point order". w3c/json-ld-framing#141, by @gkellogg.
-
-
1 issue received 2 new comments.
-
how to use the `frame` and `framed` profiles? w3c/json-ld-framing#133 (2 comments by @lisp, @VladimirAlexiev)
-
w3c/yaml-ld
-
1 issue received 2 new comments.
-
use regular expressions to resolve literals; URIs, CURIEs w3c/yaml-ld#83 (2 comments by @OR13, @VladimirAlexiev)
-
Past meetings
-
1 meeting.
Participants
-
1 participant joined.
-
Kirill Noskov (Koodos Labs) joined.
-
-
1 organization joined.
-
Koodos Labs joined.
-
GitHub
w3c/json-ld-framing
-
3 issues closed.
-
Should tests for `@embed`: `@last` be restricted to JSON-LD 1.0? w3c/json-ld-framing#110.
-
validation errors/warnings w3c/json-ld-framing#124.
-
Use a property several time when framing w3c/json-ld-framing#122.
-
-
1 issue reopened.
-
IANA profile should be `frame` not `framed` w3c/json-ld-framing#132, by @gkellogg.
-
-
4 issues received 5 new comments.
-
Ex. 41 Playground doesn't contain `@omitGraph: false` + playground does not apply `@omitGraph` w3c/json-ld-framing#116 (1 comment by @gkellogg)
-
Should tests for `@embed`: `@last` be restricted to JSON-LD 1.0? w3c/json-ld-framing#110 (1 comment by @gkellogg)
-
3 pull requests opened.
-
Fix omitgraph example w3c/json-ld-framing#139, by @gkellogg.
-
Add note on running tests that `processingMode` set to `json-ld-1.0` … w3c/json-ld-framing#138, by @gkellogg.
-
Comment out normative update w3c/json-ld-framing#137, by @gkellogg.
-
-
2 pull requests merged.
-
Comment out normative update w3c/json-ld-framing#137.
-
Add note on running tests that `processingMode` set to `json-ld-1.0` … w3c/json-ld-framing#138.
-
-
2 pull requests received 2 new comments.
-
w3c/json-ld-framing#140 (1 comment by @w3cbot)
-
w3c/json-ld-syntax
-
1 issue received 1 new comment.
-
1 pull request received 1 new comment.
-
w3c/json-ld-syntax#400 (1 comment by @w3cbot)
-
w3c/json-ld-api
-
2 issues opened.
-
Blank node as predicate tests w3c/json-ld-api#550, by @gkellogg.
-
missing instructions in Node Map generation w3c/json-ld-api#549, by @pchampin.
-
-
7 issues received 14 new comments.
-
Rules for dropping free-floating values in Expansion Algorithm w3c/json-ld-api#496 (4 comments by @gkellogg, @pchampin)
-
missing instructions in Node Map generation w3c/json-ld-api#549 (2 comments by @gkellogg, @pchampin)
-
integer JSON value should be expanded to an IRI in presence of a base IRI w3c/json-ld-api#509 (1 comment by @gkellogg)
-
Which context should be used to get the term definition in compaction algorithm step 6? w3c/json-ld-api#502 (1 comment by @gkellogg)
-
-
1 pull request received 1 new comment.
-
w3c/json-ld-api#551 (1 comment by @w3cbot)
-
w3c/yaml-ld
-
4 issues received 12 new comments.
-
Downgrading from Extended Internal Representation should use value objects w3c/yaml-ld#84 (2 comments by @gkellogg)
-
1 pull request opened.
-
WIP: More tests w3c/yaml-ld#87, by @gkellogg.
-
-
1 pull request merged.
-
WIP: More tests w3c/yaml-ld#87.
-
-
1 pull request received 4 new comments.
json-ld/json-ld-star
-
1 issue received 3 new comments.
-
new container type leveraging RDF-star to encode order json-ld/json-ld-star#35 (3 comments by @gkellogg, @niklasl, @pchampin)
-
Lifecycle
-
1 charter extension.
-
Charter extended until 30 November 2022.
-
Past meetings
Participants
-
1 participant joined.
-
Mahmoud Alkhraishi (Mavennet Systems Inc.) joined.
-
-
1 participant left.
-
Timothy Cole (University of Illinois) left.
-
-
4 organizations joined.
-
Trinsic joined.
-
Trinsic joined.
-
National Institute of Standards and Technology (NIST) joined.
-
Mavennet Systems Inc. joined.
-
-
1 organization left.
-
Trinsic left.
-
GitHub
w3c/yaml-ld
-
3 issues opened.
-
get rid of "@" in a yaml spec w3c/yaml-ld#85, by @micheldumontier.
-
Downgrading from Extended Internal Representation should use value objects w3c/yaml-ld#84, by @gkellogg.
-
use regular expressions to resolve literals; URIs, CURIEs w3c/yaml-ld#83, by @VladimirAlexiev.
-
-
4 issues closed.
-
get rid of "@" in a yaml spec w3c/yaml-ld#85.
-
YAML presentation ("cosmetic") controls w3c/yaml-ld#42.
-
Choose prefix character to replace @ w3c/yaml-ld#55.
-
Replace $-keywords with @-keywords w3c/yaml-ld#11.
-
-
14 issues received 53 new comments.
-
use regular expressions to resolve literals; URIs, CURIEs w3c/yaml-ld#83 (9 comments by @anatoly-scherbakov, @gkellogg, @ioggstream, @OR13, @VladimirAlexiev)
-
YAML-LD datatypes (and tags for datatypes) w3c/yaml-ld#17 (8 comments by @gkellogg, @TallTed, @VladimirAlexiev)
-
Serializing JSON or YAML literal in YAML-LD w3c/yaml-ld#36 (5 comments by @gkellogg, @TallTed, @VladimirAlexiev)
-
meld JSON Schema and JSON-LD context/frame w3c/yaml-ld#54 (4 comments by @gkellogg, @ioggstream, @nissimsan, @VladimirAlexiev)
-
Add section: How to read this document w3c/yaml-ld#73 (4 comments by @anatoly-scherbakov, @gkellogg)
-
Downgrading from Extended Internal Representation should use value objects w3c/yaml-ld#84 (1 comment by @pchampin)
-
-
1 pull request opened.
-
Test suite w3c/yaml-ld#86, by @gkellogg.
-
-
2 pull requests merged.
-
Test suite w3c/yaml-ld#86.
-
Spec progress w3c/yaml-ld#78.
-
-
3 pull requests received 26 new comments.
json-ld/json-ld-star
-
2 issues opened.
-
rename "embedded node" json-ld/json-ld-star#36, by @pchampin.
-
new container type leveraging RDF-star to encode order json-ld/json-ld-star#35, by @pchampin.
-
-
1 issue received 3 new comments.
-
new container type leveraging RDF-star to encode order json-ld/json-ld-star#35 (3 comments by @gkellogg, @pchampin)
-
w3c/cbor-ld
-
1 pull request opened.
-
Add registration for Multikey and Data Integrity. w3c/cbor-ld#14, by @gannan08.
-
-
1 pull request merged.
-
Add registration for Multikey and Data Integrity. w3c/cbor-ld#14.
-
-
1 pull request received 2 new comments.
-
Add registration for Multikey and Data Integrity. w3c/cbor-ld#14 (2 comments by @davidlehn, @dlongley)
-
w3c/json-ld-api
-
1 issue received 1 new comment.
-
`@set` in the data does not override `@list` in the context w3c/json-ld-api#548 (1 comment by @gkellogg)
-
Past meetings
GitHub
w3c/yaml-ld
-
6 issues opened.
-
YAML-LD IRI tags w3c/yaml-ld#79, by @gkellogg.
-
Add section: How to read this document w3c/yaml-ld#73, by @juusoautiosalo.
-
Best Practice 2 and 3 not specific to YAML-LD w3c/yaml-ld#72, by @ioggstream.
-
YAML streams pre-dates 1.2 w3c/yaml-ld#68, by @ioggstream.
-
Terminology not normative? w3c/yaml-ld#67, by @ioggstream.
-
-
5 issues closed.
-
YAML streams pre-dates 1.2 w3c/yaml-ld#68.
-
Terminology not normative? w3c/yaml-ld#67.
-
add section outlining conversion to Internal Representation w3c/yaml-ld#62.
-
editorial: add hrefs to Conformance w3c/yaml-ld#47.
-
editorial: replace data-cite with xref w3c/yaml-ld#40.
-
-
12 issues received 54 new comments.
-
YAML Streams and JSON Sequences w3c/yaml-ld#63 (13 comments by @anatoly-scherbakov, @gkellogg, @ioggstream)
-
Replace $-keywords with @-keywords w3c/yaml-ld#11 (9 comments by @anatoly-scherbakov, @gkellogg, @ioggstream, @TallTed)
-
Best Practice 2 and 3 not specific to YAML-LD w3c/yaml-ld#72 (7 comments by @anatoly-scherbakov, @gkellogg, @ioggstream)
-
YAML-LD datatypes (and tags for datatypes) w3c/yaml-ld#17 (7 comments by @gkellogg, @rob-metalinkage, @TallTed)
-
Serializing JSON or YAML literal in YAML-LD w3c/yaml-ld#36 (6 comments by @gkellogg, @ioggstream, @TallTed)
-
-
9 pull requests opened.
-
#81 The YAML-LD Primer w3c/yaml-ld#82, by @anatoly-scherbakov.
-
#73 How to read this document w3c/yaml-ld#80, by @anatoly-scherbakov.
-
Spec progress w3c/yaml-ld#78, by @gkellogg.
-
Definition of yaml-ld namespace documents w3c/yaml-ld#77, by @gkellogg.
-
Run continuous integration on spec w3c/yaml-ld#76, by @gkellogg.
-
Json profile w3c/yaml-ld#74, by @gkellogg.
-
Replace "named anchor" with "node anchor" w3c/yaml-ld#71, by @gkellogg.
-
JSON-LD compatible profile w3c/yaml-ld#70, by @rob-metalinkage.
-
Fix #68. Cleanup notes. w3c/yaml-ld#69, by @ioggstream.
-
-
6 pull requests merged.
-
#73 How to read this document w3c/yaml-ld#80.
-
Run continuous integration on spec w3c/yaml-ld#76.
-
Json profile w3c/yaml-ld#74.
-
Fix #68. Cleanup notes. w3c/yaml-ld#69.
-
Replace "named anchor" with "node anchor" w3c/yaml-ld#71.
-
Description of converting YAML to the internal representation. w3c/yaml-ld#65.
-
-
1 pull request closed.
-
JSON-LD compatible profile w3c/yaml-ld#70.
-
-
9 pull requests received 169 new comments.
-
Definition of yaml-ld namespace documents w3c/yaml-ld#77 (39 comments by @BigBlueHat, @gkellogg, @ioggstream, @pchampin, @TallTed)
-
Description of converting YAML to the internal representation. w3c/yaml-ld#65 (16 comments by @gkellogg, @TallTed)
-
#73 How to read this document w3c/yaml-ld#80 (14 comments by @anatoly-scherbakov, @gkellogg, @TallTed)
w3c/json-ld-framing
-
3 issues opened.
-
Fix invalid WebIDL w3c/json-ld-framing#136, by @gkellogg.
-
how to use the `frame` and `framed` profiles? w3c/json-ld-framing#133, by @VladimirAlexiev.
-
IANA profile should be `frame` not `framed` w3c/json-ld-framing#132, by @VladimirAlexiev.
-
-
1 issue closed.
-
Fix invalid WebIDL w3c/json-ld-framing#136.
-
-
3 issues received 12 new comments.
-
how to use the `frame` and `framed` profiles? w3c/json-ld-framing#133 (9 comments by @gkellogg, @iherman, @rob-metalinkage, @RubenVerborgh, @VladimirAlexiev)
-
-
2 pull requests opened.
-
Fix invalid Web IDL w3c/json-ld-framing#135, by @tidoust.
-
-
2 pull requests merged.
-
Fix invalid Web IDL w3c/json-ld-framing#135.
-
Fix iana w3c/json-ld-framing#134.
-
-
2 pull requests received 4 new comments.
w3c/json-ld-bp
-
1 issue opened.
-
Update spec status and/or publish? w3c/json-ld-bp#43, by @gkellogg.
-
-
1 issue received 5 new comments.
-
1 pull request opened.
-
Update specStatus to "unofficial". w3c/json-ld-bp#44, by @gkellogg.
-
-
1 pull request received 1 new comment.
w3c/json-ld-api
-
3 issues opened.
-
`@set` in the data does not override `@list` in the context w3c/json-ld-api#548, by @pchampin.
-
Compaction of IRIs with "@list" @container for sets of @list w3c/json-ld-api#547, by @progval.
-
toRdf/0118-out.nq nquad blank node as predicate is not allowed w3c/json-ld-api#546, by @mvanassche.
-
-
2 issues received 3 new comments.
-
toRdf/0118-out.nq nquad blank node as predicate is not allowed w3c/json-ld-api#546 (2 comments by @gkellogg, @pchampin)
-
Compaction of IRIs with "@list" @container for sets of @list w3c/json-ld-api#547 (1 comment by @gkellogg)
-
w3c/json-ld-syntax
-
1 issue received 3 new comments.
-
Consider context by reference with metadata w3c/json-ld-syntax#108 (3 comments by @danbri, @gkellogg, @TallTed)
-
Past meetings
GitHub
w3c/yaml-ld
-
17 issues opened.
-
YAML Streams and JSON Sequences w3c/yaml-ld#63, by @ioggstream.
-
add section outlining conversion to Internal Representation w3c/yaml-ld#62, by @ghurlbot.
-
Links to sections of YAML spec do not work w3c/yaml-ld#61, by @anatoly-scherbakov.
-
YARRRML Lessons learned w3c/yaml-ld#57, by @bjdmeest.
-
Choose prefix character to replace @ w3c/yaml-ld#55, by @anatoly-scherbakov.
-
meld JSON Schema and JSON-LD context/frame w3c/yaml-ld#54, by @VladimirAlexiev.
-
sigil: change prefix char in context w3c/yaml-ld#51, by @VladimirAlexiev.
-
editorial: add hrefs to Conformance w3c/yaml-ld#47, by @ioggstream.
-
Multiple documents in YAML w3c/yaml-ld#46, by @VladimirAlexiev.
-
YAML-LD-star w3c/yaml-ld#45, by @VladimirAlexiev.
-
YAML-LD context and frame w3c/yaml-ld#44, by @VladimirAlexiev.
-
YAML-LD canonicalization (c14n) w3c/yaml-ld#43, by @VladimirAlexiev.
-
YAML presentation ("cosmetic") controls w3c/yaml-ld#42, by @VladimirAlexiev.
-
editorial: replace data-cite with xref w3c/yaml-ld#40, by @ioggstream.
-
Conformance section w3c/yaml-ld#38, by @ioggstream.
-
Serializing JSON or YAML literal in YAML-LD w3c/yaml-ld#36, by @gkellogg.
-
Defining various interoperability profiles w3c/yaml-ld#35, by @ioggstream.
-
-
11 issues closed.
-
Links to sections of YAML spec do not work w3c/yaml-ld#61.
-
I would like to contribute w3c/yaml-ld#1.
-
Pospone discussion on "$" and "@" w3c/yaml-ld#9.
-
Conformance section w3c/yaml-ld#38.
-
Multiple documents in YAML w3c/yaml-ld#46.
-
char encoding: UTF-8 only? w3c/yaml-ld#15.
-
Round-trip safe json-ld -> yaml-ld -> json-ld w3c/yaml-ld#8.
-
File signature w3c/yaml-ld#7.
-
YAML versions w3c/yaml-ld#21.
-
Upcoming teleconference w3c/yaml-ld#18.
-
Security, interoperability and IANA considerations w3c/yaml-ld#29.
-
-
28 issues received 113 new comments.
-
Serializing JSON or YAML literal in YAML-LD w3c/yaml-ld#36 (14 comments by @gkellogg, @ioggstream, @pchampin, @VladimirAlexiev)
-
YAML-LD canonicalization (c14n) w3c/yaml-ld#43 (9 comments by @gkellogg, @ioggstream, @OR13, @VladimirAlexiev)
-
YAML Streams and JSON Sequences w3c/yaml-ld#63 (8 comments by @anatoly-scherbakov, @gkellogg, @ioggstream, @TallTed)
-
YAML-LD context and frame w3c/yaml-ld#44 (7 comments by @anatoly-scherbakov, @gkellogg, @TallTed, @VladimirAlexiev)
-
Multiple documents in YAML w3c/yaml-ld#46 (7 comments by @anatoly-scherbakov, @gkellogg, @ioggstream, @VladimirAlexiev)
-
Replace $-keywords with @-keywords w3c/yaml-ld#11 (6 comments by @anatoly-scherbakov, @BigBlueHat, @ioggstream, @juusoautiosalo)
-
add section outlining conversion to Internal Representation w3c/yaml-ld#62 (5 comments by @gkellogg, @ioggstream)
-
sigil: change prefix char in context w3c/yaml-ld#51 (5 comments by @anatoly-scherbakov, @ioggstream, @OR13, @VladimirAlexiev)
-
YAML presentation ("cosmetic") controls w3c/yaml-ld#42 (5 comments by @gkellogg, @ioggstream, @OR13, @VladimirAlexiev)
-
meld JSON Schema and JSON-LD context/frame w3c/yaml-ld#54 (4 comments by @anatoly-scherbakov, @ioggstream, @OR13)
-
Defining various interoperability profiles w3c/yaml-ld#35 (4 comments by @gkellogg, @ioggstream, @rob-metalinkage)
-
Round-trip safe json-ld -> yaml-ld -> json-ld w3c/yaml-ld#8 (3 comments by @gkellogg, @VladimirAlexiev)
-
-
15 pull requests opened.
-
move note about Streams to better location w3c/yaml-ld#66, by @TallTed.
-
Description of converting YAML to the internal representation. w3c/yaml-ld#65, by @gkellogg.
-
Update YAML reference to 1.2.2, addressing references to "YAML stream". w3c/yaml-ld#64, by @gkellogg.
-
Missing suggestion from @TallTed w3c/yaml-ld#60, by @gkellogg.
-
Update imported term definitions and repair some document structure. w3c/yaml-ld#59, by @gkellogg.
-
Propose YAML-LD document definition w3c/yaml-ld#58, by @anatoly-scherbakov.
-
Fix example: no escaping, only quote w3c/yaml-ld#56, by @ioggstream.
-
Update examples w3c/yaml-ld#53, by @gkellogg.
-
Fix reference to YAML media type. w3c/yaml-ld#52, by @gkellogg.
-
Implement Best Practices section w3c/yaml-ld#50, by @anatoly-scherbakov.
-
YAML files are streams w3c/yaml-ld#49, by @ioggstream.
-
Fix: #7. Same as YAML. w3c/yaml-ld#48, by @ioggstream.
-
Fix: #21. No specific YAML version. w3c/yaml-ld#41, by @ioggstream.
-
Fix: #38. Stubs Conformance. w3c/yaml-ld#39, by @ioggstream.
-
Add remaining Use Case Issues. w3c/yaml-ld#37, by @gkellogg.
-
-
14 pull requests merged.
-
move note about Streams to better location w3c/yaml-ld#66.
-
Propose YAML-LD document definition w3c/yaml-ld#58.
-
Missing suggestion from @TallTed w3c/yaml-ld#60.
-
Fix example: no escaping, only quote w3c/yaml-ld#56.
-
Update examples w3c/yaml-ld#53.
-
Implement Best Practices section w3c/yaml-ld#50.
-
Fix: #38. Stubs Conformance. w3c/yaml-ld#39.
-
Fix reference to YAML media type. w3c/yaml-ld#52.
-
Fix: #21. No specific YAML version. w3c/yaml-ld#41.
-
Preliminary rules for discussion w3c/yaml-ld#34.
-
YAML files are streams w3c/yaml-ld#49.
-
Fix: #7. Same as YAML. w3c/yaml-ld#48.
-
-
12 pull requests received 175 new comments.
-
Preliminary rules for discussion w3c/yaml-ld#34 (66 comments by @gkellogg, @ioggstream, @pchampin, @TallTed)
-
Propose YAML-LD document definition w3c/yaml-ld#58 (28 comments by @anatoly-scherbakov, @gkellogg, @TallTed)
-
Description of converting YAML to the internal representation. w3c/yaml-ld#65 (26 comments by @anatoly-scherbakov, @gkellogg, @ioggstream, @TallTed)
-
Implement Best Practices section w3c/yaml-ld#50 (15 comments by @anatoly-scherbakov, @gkellogg, @OR13, @TallTed, @VladimirAlexiev)
-
Update YAML reference to 1.2.2, addressing references to "YAML stream". w3c/yaml-ld#64 (3 comments by @gkellogg, @TallTed)
-
Update imported term definitions and repair some document structure. w3c/yaml-ld#59 (1 comment by @anatoly-scherbakov)
-
w3c/cbor-ld
-
1 issue opened.
-
Plain JSON is considered as compressed CBOR-LD w3c/cbor-ld#12, by @filip26.
-
-
1 pull request opened.
-
Fix CBOR-LD tags; should be 1280 (0x0500) and 1281 (0x0501). w3c/cbor-ld#13, by @dlongley.
-
-
1 pull request merged.
-
Fix CBOR-LD tags; should be 1280 (0x0500) and 1281 (0x0501). w3c/cbor-ld#13.
-
-
1 pull request received 3 new comments.
-
Fix CBOR-LD tags; should be 1280 (0x0500) and 1281 (0x0501). w3c/cbor-ld#13 (3 comments by @dlongley, @dmitrizagidulin)
-
json-ld/minutes
-
1 pull request opened.
-
Bring back internal scribe tool json-ld/minutes#11, by @gkellogg.
-
-
1 pull request merged.
-
Bring back internal scribe tool json-ld/minutes#11.
-
-
1 pull request received 4 new comments.
json-ld/json-ld-star
-
1 issue opened.
-
are multiple triples forbidden in `@id`? json-ld/json-ld-star#34, by @VladimirAlexiev.
-
-
2 issues received 3 new comments.
-
allow `"@type": "@triple"` or something similar? json-ld/json-ld-star#28 (2 comments by @gkellogg, @VladimirAlexiev)
-
Past meetings
-
1 meeting.
Participants
-
1 participant joined.
-
Timothée Haudebourg (Spruce Systems, Inc.) joined.
-
-
1 organization joined.
-
Spruce Systems, Inc. joined.
-
GitHub
w3c/yaml-ld
-
6 issues opened.
-
Fragment identifier w3c/yaml-ld#31, by @ioggstream.
-
Security, interoperability and IANA considerations w3c/yaml-ld#29, by @ioggstream.
-
File extension w3c/yaml-ld#25, by @juusoautiosalo.
-
YAML versions w3c/yaml-ld#21, by @VladimirAlexiev.
-
Conformance Tests w3c/yaml-ld#20, by @VladimirAlexiev.
-
Polyglot Modeling w3c/yaml-ld#19, by @VladimirAlexiev.
-
-
5 issues closed.
-
File extension w3c/yaml-ld#25.
-
YAML LD media type and profiles w3c/yaml-ld#14.
-
Compatibility with existing libraries w3c/yaml-ld#5.
-
YAML-LD UCRs w3c/yaml-ld#2.
-
Work on YAML-LD w3c/yaml-ld#3.
-
-
2 issues reopened.
-
Use tags to distinguish "plain" YAML-LD from "idiomatic" YAML-LD w3c/yaml-ld#6, by @gkellogg.
-
YAML-LD datatypes (and tags for datatypes) w3c/yaml-ld#17, by @gkellogg.
-
-
16 issues received 45 new comments.
-
char encoding: UTF-8 only? w3c/yaml-ld#15 (9 comments by @ericprud, @gkellogg, @ioggstream, @pchampin, @TallTed, @VladimirAlexiev)
-
YAML LD media type and profiles w3c/yaml-ld#14 (5 comments by @anatoly-scherbakov, @gkellogg, @ioggstream, @VladimirAlexiev)
-
YAML-LD datatypes (and tags for datatypes) w3c/yaml-ld#17 (5 comments by @anatoly-scherbakov, @gkellogg, @ioggstream, @pchampin, @VladimirAlexiev)
-
Define anchor usage in yaml-ld w3c/yaml-ld#13 (5 comments by @anatoly-scherbakov, @gkellogg, @ioggstream, @VladimirAlexiev)
-
Security, interoperability and IANA considerations w3c/yaml-ld#29 (2 comments by @gkellogg, @ioggstream)
-
-
10 pull requests opened.
-
Preliminary rules for discussion w3c/yaml-ld#34, by @ioggstream.
-
Reference YAML for media type encoding w3c/yaml-ld#33, by @ioggstream.
-
Cleanup IANA w3c/yaml-ld#32, by @gkellogg.
-
Stub for security, interoperability and fragment identifier considera… w3c/yaml-ld#30, by @ioggstream.
-
Stub introduction / abstract w3c/yaml-ld#28, by @ioggstream.
-
Adds a preliminary IANA section with placeholders. w3c/yaml-ld#27, by @gkellogg.
-
UCR boilerplate w3c/yaml-ld#26, by @gkellogg.
-
remove errant period w3c/yaml-ld#24, by @TallTed.
-
README rewording suggested by @TallTed. w3c/yaml-ld#23, by @gkellogg.
-
Move spec under /spec, and add /UCR/index.html. w3c/yaml-ld#22, by @gkellogg.
-
-
8 pull requests merged.
-
Cleanup IANA w3c/yaml-ld#32.
-
Adds a preliminary IANA section with placeholders. w3c/yaml-ld#27.
-
Stub introduction / abstract w3c/yaml-ld#28.
-
UCR boilerplate w3c/yaml-ld#26.
-
remove errant period w3c/yaml-ld#24.
-
README rewording suggested by @TallTed. w3c/yaml-ld#23.
-
Move spec under /spec, and add /UCR/index.html. w3c/yaml-ld#22.
-
-
1 pull request closed.
-
Reference YAML for media type encoding w3c/yaml-ld#33.
-
-
6 pull requests received 55 new comments.
-
Adds a preliminary IANA section with placeholders. w3c/yaml-ld#27 (23 comments by @gkellogg, @ioggstream, @VladimirAlexiev)
-
Stub for security, interoperability and fragment identifier considera… w3c/yaml-ld#30 (17 comments by @gkellogg, @ioggstream, @TallTed)
-
w3c/json-ld-syntax
-
4 issues opened.
-
Incorrect `foaf` context examples w3c/json-ld-syntax#399, by @Jym77.
-
Examples 119 and 120 don't seem right w3c/json-ld-syntax#398, by @VladimirAlexiev.
-
clarify that `@none @id` are blank nodes, swap Examples 104 and 105 w3c/json-ld-syntax#397, by @VladimirAlexiev.
-
minor typo for `@none` language w3c/json-ld-syntax#396, by @VladimirAlexiev.
-
-
1 issue closed.
-
Incorrect `foaf` context examples w3c/json-ld-syntax#399.
-
-
5 issues received 10 new comments.
-
Specify a node type when interpreting JSON as JSON-LD (was: use of "@type" in "@context") w3c/json-ld-syntax#386 (3 comments by @ioggstream, @rob-metalinkage)
-
clarify that `@none @id` are blank nodes, swap Examples 104 and 105 w3c/json-ld-syntax#397 (2 comments by @VladimirAlexiev)
-
Make it easier to keep semantics of object-oriented models w3c/json-ld-syntax#376 (2 comments by @about-code, @pchampin)
-
Elaborate on handling of JSON builtin types `integer` and `double` w3c/json-ld-syntax#387 (1 comment by @gkellogg)
-
-
1 pull request opened.
-
address #387 w3c/json-ld-syntax#395, by @pchampin.
-
-
1 pull request received 2 new comments.
json-ld/minutes
-
3 pull requests opened.
-
Restore util files. json-ld/minutes#10, by @davidlehn.
-
Add nicknames.json CORS. json-ld/minutes#9, by @davidlehn.
-
-
3 pull requests merged.
-
Restore util files. json-ld/minutes#10.
-
Add nicknames.json CORS. json-ld/minutes#9.
-
-
1 pull request closed.
-
Upgrade moment.js to address vulnerability json-ld/minutes#1.
-
-
1 pull request received 1 new comment.
w3c/json-ld-rc
-
1 issue opened.
-
Context architecture - patterns and antipatterns, or convenience packages? w3c/json-ld-rc#24, by @rob-metalinkage.
-
w3c/json-ld-api
-
1 issue opened.
-
compacting native types with a type specification in context w3c/json-ld-api#545, by @ethieblin.
-
-
1 issue received 4 new comments.
-
compacting native types with a type specification in context w3c/json-ld-api#545 (4 comments by @ethieblin, @gkellogg, @pchampin)
-
w3c/json-ld-wg
-
1 pull request opened.
-
Make landing page information current. w3c/json-ld-wg#157, by @gkellogg.
-
-
1 pull request merged.
-
Make landing page information current. w3c/json-ld-wg#157.
-
Participants
-
1 Team contact appointed.
-
Philippe Le Hegaret became a Team contact.
-
-
1 Team contact stepped down.
-
Philippe Le Hegaret stepped down as a Team contact.
-
-
1 participant joined.
-
Philippe Le Hegaret (W3C) joined.
-
-
1 participant left.
-
Philippe Le Hegaret (W3C) left.
-
GitHub
w3c/yaml-ld
-
17 issues opened.
-
Upcoming teleconference w3c/yaml-ld#18, by @gkellogg.
-
YAML-LD datatypes (and tags for datatypes) w3c/yaml-ld#17, by @VladimirAlexiev.
-
study CBOR-LD w3c/yaml-ld#16, by @VladimirAlexiev.
-
char encoding: UTF-8 only? w3c/yaml-ld#15, by @VladimirAlexiev.
-
YAML LD media type and profiles w3c/yaml-ld#14, by @VladimirAlexiev.
-
Define anchor usage in yaml-ld w3c/yaml-ld#13, by @ioggstream.
-
Convert JSON-LD to YAML-LD using standard YAML libraries w3c/yaml-ld#12, by @pchampin.
-
Replace $-keywords with @-keywords w3c/yaml-ld#11, by @anatoly-scherbakov.
-
Collecting JSON-LD file samples w3c/yaml-ld#10, by @ioggstream.
-
Pospone discussion on "$" and "@" w3c/yaml-ld#9, by @ioggstream.
-
Round-trip safe json-ld -> yaml-ld -> json-ld w3c/yaml-ld#8, by @ioggstream.
-
File signature w3c/yaml-ld#7, by @nichtich.
-
Use tags to distinguish "plain" YAML-LD from "idiomatic" YAML-LD w3c/yaml-ld#6, by @pchampin.
-
Compatibility with existing libraries w3c/yaml-ld#5, by @ericprud.
-
I would like to contribute w3c/yaml-ld#1, by @ioggstream.
-
YAML-LD UCRs w3c/yaml-ld#2, by @VladimirAlexiev.
-
Work on YAML-LD w3c/yaml-ld#3, by @gkellogg.
-
-
15 issues received 91 new comments.
-
Work on YAML-LD w3c/yaml-ld#3 (28 comments by @anatoly-scherbakov, @cmungall, @gkellogg, @nichtich, @OR13, @pchampin, @tetron, @VladimirAlexiev)
-
YAML-LD UCRs w3c/yaml-ld#2 (11 comments by @ericprud, @gkellogg, @ioggstream, @OR13, @VladimirAlexiev)
-
File signature w3c/yaml-ld#7 (10 comments by @anatoly-scherbakov, @gkellogg, @ioggstream, @nichtich, @pchampin, @VladimirAlexiev)
-
Use tags to distinguish "plain" YAML-LD from "idiomatic" YAML-LD w3c/yaml-ld#6 (7 comments by @anatoly-scherbakov, @ioggstream, @pchampin)
-
Pospone discussion on "$" and "@" w3c/yaml-ld#9 (6 comments by @anatoly-scherbakov, @ioggstream, @VladimirAlexiev)
-
YAML LD media type and profiles w3c/yaml-ld#14 (4 comments by @anatoly-scherbakov, @gkellogg, @ioggstream)
-
char encoding: UTF-8 only? w3c/yaml-ld#15 (4 comments by @anatoly-scherbakov, @gkellogg, @ioggstream, @pchampin)
-
Round-trip safe json-ld -> yaml-ld -> json-ld w3c/yaml-ld#8 (4 comments by @anatoly-scherbakov, @gkellogg, @ioggstream, @nichtich)
-
YAML-LD datatypes (and tags for datatypes) w3c/yaml-ld#17 (3 comments by @anatoly-scherbakov, @ioggstream, @pchampin)
-
Define anchor usage in yaml-ld w3c/yaml-ld#13 (3 comments by @ioggstream, @pchampin, @VladimirAlexiev)
-
Replace $-keywords with @-keywords w3c/yaml-ld#11 (3 comments by @anatoly-scherbakov, @gkellogg, @pchampin)
-
-
1 pull request opened.
-
Update issue templates w3c/yaml-ld#4, by @gkellogg.
-
-
1 pull request merged.
-
Update issue templates w3c/yaml-ld#4.
-
-
1 pull request received 2 new comments.
w3c/json-ld-syntax
-
1 issue opened.
-
Using @context on children of a mapped vocabulary w3c/json-ld-syntax#392, by @PonteIneptique.
-
-
2 issues closed.
-
YAML-LD? w3c/json-ld-syntax#389.
-
Using @context on children of a mapped vocabulary w3c/json-ld-syntax#392.
-
-
3 issues received 14 new comments.
-
YAML-LD? w3c/json-ld-syntax#389 (9 comments by @anatoly-scherbakov, @gkellogg, @tetron, @VladimirAlexiev)
-
Using @context on children of a mapped vocabulary w3c/json-ld-syntax#392 (2 comments by @pchampin, @PonteIneptique)
-
-
3 pull requests received 3 new comments.
-
w3c/json-ld-syntax#394 (1 comment by @w3cbot)
-
w3c/json-ld-syntax#393 (1 comment by @w3cbot)
-
w3c/json-ld-syntax#391 (1 comment by @w3cbot)
-
w3c/json-ld-api
-
2 pull requests received 2 new comments.
-
w3c/json-ld-api#544 (1 comment by @w3cbot)
-
w3c/json-ld-api#543 (1 comment by @w3cbot)
-
w3c/json-ld-framing
-
3 pull requests received 3 new comments.
-
w3c/json-ld-framing#131 (1 comment by @w3cbot)
-
w3c/json-ld-framing#130 (1 comment by @w3cbot)
-
w3c/json-ld-framing#129 (1 comment by @w3cbot)
-
GitHub
w3c/cbor-ld
-
1 issue opened.
-
Is this a W3C CCG Work item? w3c/cbor-ld#11, by @OR13.
-
w3c/json-ld-api
-
1 pull request received 1 new comment.
-
w3c/json-ld-api#541 (1 comment by @w3cbot)
-
w3c/json-ld-syntax
-
1 issue opened.
-
YAML-LD? w3c/json-ld-syntax#389, by @VladimirAlexiev.
-
-
1 pull request received 1 new comment.
-
w3c/json-ld-syntax#390 (1 comment by @w3cbot)
-
w3c/json-ld-rc
-
1 issue received 1 new comment.
Participants
-
1 participant joined.
-
Pierre-Antoine Champin (W3C) joined.
-
-
1 participant left.
-
Pierre-Antoine Champin (ERCIM) left.
-
GitHub
w3c/json-ld-api
-
3 pull requests opened.
-
Normalize indents. w3c/json-ld-api#540, by @davidlehn.
-
Update link for tests download. w3c/json-ld-api#539, by @gkellogg.
-
Fix link to test suite on github w3c/json-ld-api#538, by @Khady.
-
-
2 pull requests merged.
-
Normalize indents. w3c/json-ld-api#540.
-
Update link for tests download. w3c/json-ld-api#539.
-
-
1 pull request closed.
-
Fix link to test suite on github w3c/json-ld-api#538.
-
-
2 pull requests received 7 new comments.
w3c/json-ld-syntax
-
1 issue received 4 new comments.
-
Make it easier to keep semantics of object-oriented models w3c/json-ld-syntax#376 (4 comments by @about-code, @pchampin)
-
w3c/json-ld-streaming
-
1 issue opened.
-
Serialization to different profiles w3c/json-ld-streaming#29, by @rubensworks.
-
w3c/json-ld-bp
-
1 pull request merged.
-
Update spec status w3c/json-ld-bp#39.
-
GitHub
w3c/json-ld-syntax
-
1 issue opened.
-
Elaborate on handling of JSON builtin types `integer` and `double` w3c/json-ld-syntax#387, by @VladimirAlexiev.
-
-
5 issues received 23 new comments.
-
Elaborate on handling of JSON builtin types `integer` and `double` w3c/json-ld-syntax#387 (10 comments by @dlongley, @msporny, @pchampin, @VladimirAlexiev)
-
Specify a node type when interpreting JSON as JSON-LD (was: use of "@type" in "@context") w3c/json-ld-syntax#386 (7 comments by @ioggstream, @msporny, @pchampin)
-
Make it easier to keep semantics of object-oriented models w3c/json-ld-syntax#376 (3 comments by @about-code, @pchampin)
-
Type Coercion / Node Conversion: @coerce keyword or similar w3c/json-ld-syntax#335 (2 comments by @msporny, @VladimirAlexiev)
-
-
1 pull request received 1 new comment.
-
w3c/json-ld-syntax#388 (1 comment by @w3cbot)
-
w3c/json-ld-bp
-
1 pull request opened.
-
Update spec status w3c/json-ld-bp#39, by @gkellogg.
-
-
2 pull requests received 2 new comments.
-
w3c/json-ld-bp#38 (1 comment by @gkellogg)
w3c/json-ld-api
-
1 pull request received 1 new comment.
-
w3c/json-ld-api#537 (1 comment by @w3cbot)
-
w3c/json-ld-framing
-
1 pull request received 1 new comment.
-
w3c/json-ld-framing#127 (1 comment by @w3cbot)
-
Participants
-
3 participants left.
-
Nat Holloway (USAA) left.
-
Thomas Schwarz (USAA) left.
-
Joel Hartshorn (USAA) left.
-
-
1 organization left.
-
USAA left.
-
GitHub
w3c/json-ld-syntax
-
2 issues opened.
-
Specify a node type when interpreting JSON as JSON-LD (was: use of "@type" in "@context") w3c/json-ld-syntax#386, by @ioggstream.
-
Register application/ld+yaml media type w3c/json-ld-syntax#385, by @ioggstream.
-
-
3 issues received 8 new comments.
-
Specify a node type when interpreting JSON as JSON-LD (was: use of "@type" in "@context") w3c/json-ld-syntax#386 (4 comments by @gkellogg, @ioggstream, @pchampin)
-
Type Coercion / Node Conversion: @coerce keyword or similar w3c/json-ld-syntax#335 (2 comments by @ioggstream)
-
would it be possible to reserve @view for JSON-LD v.next w3c/json-ld-syntax#384 (2 comments by @melvincarvalho, @Peeja)
-
w3c/cbor-ld
-
1 pull request opened.
-
Add `status-list` context. w3c/cbor-ld#10, by @JSAssassin.
-
-
1 pull request merged.
-
Add `status-list` context. w3c/cbor-ld#10.
-
w3c/json-ld-api
-
1 issue opened.
-
Graph-aliased keywords don't work as containers in JSON-LD 1.1 w3c/json-ld-api#536, by @niklasl.
-
-
1 issue received 1 new comment.
-
Graph-aliased keywords don't work as containers in JSON-LD 1.1 w3c/json-ld-api#536 (1 comment by @gkellogg)
-
json-ld/json-ld-star
-
1 issue received 2 new comments.