– DRAFT –
JSON-LD WG

Announcements and Introductions

bigbluehat: Gregg Kellogg passed away this weekend.

<ivan> https://www.w3.org/TR/epub-33/#ack

ivan: The least we can do is to put a similar paragraph honoring Gregg.

bigbluehat: The number of things Gregg contributed to is probably beyond the reach of AI...

ivan: It's practical to put it in JSON-LD 1.2 but we may get an acknowledgement to put it in JSON-LD 1.1

<niklasl> +100

bigbluehat: I'd like to get something public now if possible.

ivan: Me and pchampin can probably get OK for that

bigbluehat: I can draft probably a PR

TallTed: I would be in favour of putting it in both 1.1 and 1.2

All in agreement.

Recharger Next Steps

Victor Lu: JSON-LD is very important in a lot of things so I very much appreciate honoring Gregg for this.

bigbluehat: We all voted in agreement over email.

<ivan> latest version: https://w3c.github.io/json-ld-charter-2025/

ivan: One thing still to do - for bigbluehat to approve the latest version

bigbluehat: I approve

pchampin: As next step I will request horizontal review

<pchampin> w3c/strategy#494

<gb> Issue 494 [wg/json-ld] JSON-LD Working Group Charter (by plehegar) [Advance Notice Sent] [charter]

pchampin: Now the horizontal review gets the requests for this. It may take some weeks, and then we can go to AC review.
… should it take too much time, we might still be able to go forward

ivan: I presume there will be comments from the horizontal review and/or AC. We till handle them as issues (in the w3c repo).
… please keep an eye on these as they come in.

bigbluehat: Thank you for getting that ready. We'll watch it closely.

<Zakim> TallTed, you wanted to ask practicality question about minutes generation for this WG/CG

TallTed: Gregg has preferred tools for generating logs/minutes. Is anyone acquainted with them (or other shared tools)?

bigbluehat: I will look at the code in the repo (probably code that Manu wrote, and I worked on).

pchampin: I did use those tools a few weeks ago. It went pretty smoothly, except for a timeout of a github action.
… More people looked on that.
… I'm in favour of keeping them running. The trickiest part is the size of the repo.

bigbluehat: Moving to a static site hit upon that as well. The gh repo is very large.
… That timeout will probably increase, we may have to address that.

bigbluehat: Do we have people able to pick up from Gregg?

niklasl: I'd like to try
… in my current position is probably more on the JSON-LD Star aspect of this work
… and that's a bit tricky with separate repos, etc.
… but I'm not yet sure we're in dire need of an editor
… so, we may be fine

ivan: we have to be careful here

ivan: We have to be careful here.
… the reorganization of the charter means we're talking about v1.2
… which are all the technical changes on 1.1
… but not the new things from RDF 1.2
… we are planning to have a JSON-LD 1.3 to incubate during the WG
… We're talking about JSON-LD 1.2, with the editorial, errata, and so on. We will have a separate 1.3 which will be optional to start on.
… and toward the end move to a v1.3 publication toward the end of the group
… So at this point, 1.2 is not that.

bigbluehat: I don't recall how many things are pending. We may need to analyze that in upcoming calls.

niklasl: there is one thing that I am almost ready to make a PR of
… and it's not Star/RDF-1.2 related
… it's already approved, but likely still need some changes
… so my contributions are not 100% RDF-1.2 related

bigbluehat: We need to discuss co-chair and editor workloads

pchampin: A possibly crazy idea - we are struggling with the version numbers. Maybe adding nicknames as well (bear with me).
… What about calling the first one Gregg.
… Debian had names from Toy Story. What about using Kellogg mascots?

<TallTed> `1.1.5`? `1.1bis`? and make eventual 1.2 sync with RDF 1.2?

pchampin: Mostly internal nicknames..

<TallTed> We could do worse than informally using Kellogg's mascots

I like it too.

ivan: We may consider something not associated too much with the name.

<pchampin> https://en.wikipedia.org/wiki/List_of_integer_sequences

bigbluehat: We can look for good names in that list and choose next meeting.

ivan: We should be careful about considering joint CG/WG meetings; especially for IPR reasons

bigbluehat: I am currently the only chair for both groups. We should discuss how to proceed with the CG as well.
… The VC group has also done a good job of promoting JSON-LD.

Open Discussion

bigbluehat: bye all