Re: Proposed JSON-LD CG call

That time works for me. Looking forward to getting the band back together (plus new participants!). ;)

Thanks for suggesting and scheduling this, Gregg!

Cheers,
Benjamin
--
Co-Chair, W3C JSON-LD WG
https://bigbluehat.com/
https://linkedin.com/in/benjaminyoung
________________________________
From: Gregg Kellogg <gregg@greggkellogg.net>
Sent: Wednesday, May 25, 2022 1:40:54 PM
To: Linked JSON <public-linked-json@w3.org>
Cc: w3c/json-ld-wg <json-ld-wg@noreply.github.com>
Subject: Proposed JSON-LD CG call

There’s been some activity on JSON-LD since the release of the 1.1 recommendations and I’ve proposed a Face to Face at the upcoming W3C TPAC (physical and virtual) in Vancouver the week of September 12. I’d like to schedule a call at our previous normal time of 18:00 CEST, 17:00 BST, 12:00 EDT, 9:00 PDT on Friday June 3rd. If this does not prove to be a convenient time for such a call, we can send out a Doodle for alternative times.

General topics for discussion:

* Work on YAML-LD (https://github.com/json-ld/yaml-ld)
* State of JSON-LD-star (https://github.com/json-ld/json-ld-star) and prospects for an RDF-star Working Group.
* Open issues
  * https://github.com/json-ld/json-ld.org/issues,
  * https://github.com/w3c/json-ld-syntax/issues,
  * https://github.com/w3c/json-ld-api/issues,
  * https://github.com/w3c/json-ld-framing/issues
* Roadmap going forward.

Taken together these issues are far more than can be covered in a signal meeting, and we may want to create a regular call schedule. A F2F is generally a great way to tackle a number of outstanding issues.

The CG can issue Draft and Final reports, but is also deputized by the JSON-LD Maintenance Working Group for work that could lead to edited Recommendations using the new W3C process. This work requires a fair time commitment from sufficient participants to make the work viable. If the community is interested in taking this up, we could move forward on a number of different fronts.

Once a time is agreed, I’ll send out a detailed agenda and links for a call.

Gregg Kellogg
gregg@greggkellogg.net