From afa067361b29457bcc934b9b9a749544041da176 Mon Sep 17 00:00:00 2001 From: Gregg Kellogg Date: Wed, 7 Feb 2024 10:10:31 -0800 Subject: [PATCH] Minutes for 2024-02-07. --- 2024-02-07/index.html | 217 ++++++++++++++++++++++++++++++++++++++++++ 2024-02-07/irc.log | 127 ++++++++++++++++++++++++ index.html | 3 +- 3 files changed, 346 insertions(+), 1 deletion(-) create mode 100644 2024-02-07/index.html create mode 100644 2024-02-07/irc.log diff --git a/2024-02-07/index.html b/2024-02-07/index.html new file mode 100644 index 0000000..53e1bbc --- /dev/null +++ b/2024-02-07/index.html @@ -0,0 +1,217 @@ + + + + + + + + + + JSON-LD Community Group + + + + +
+

The W3C JSON-LD Community Group

+

Go Back

+ +
+

W3C Logo

JSON-LD CG

+

Minutes for 2024-02-07

+
+
+
Present
David I. Lehn, Gregg Kellogg, Benjamin Young, Niklas Lindström
+
Chair(s)
Gregg Kellogg
+
Scribe(s)
Gregg Kellogg
+
Agenda
https://www.w3.org/events/meetings/398465c7-3787-40df-856a-434a438d9f05/20240207T120000/
+
Topics
  1. Announcements and Introductions
  2. YAML-LD
  3. CBOR-LD
  4. JSON-LD Issue Discussion
  5. Open Discussion
Action Items
  1. pchampin to move JSON-LD in CBOR draft to json-ld org.
  2. dlehn to tag reviewers on tests to be considered for merging.
+
+

+Topic: Announcements and Introductions +

+
Gregg Kellogg is scribing.
+

+Topic: YAML-LD +

+
Anatoly Scherbakov: --Shares screen--
+
Anatoly Scherbakov: I created issue json-ld/yaml-ld#131 for script tags in HTML.
+
https://github.com/json-ld/yaml-ld/issues/131 -> Issue 131 YAML under `<script>` HTML tag unsupported in the spec (by anatoly-scherbakov) [bug]
+
... I also created json-ld/yaml-ld#132, although PR Preview is having problems.
+
https://github.com/json-ld/yaml-ld/pull/132 -> Pull Request 132 (closes #131) Embed YAML-LD into HTML `<script>` tag (by anatoly-scherbakov) [blocked-by-recharter]
+
Anatoly Scherbakov: Changes involve spec changes and some tests.
+
... We need to un-indent the code block to process a YAML stream.
+
... I have a Python implementation, that also runs JSON-LD tests, as it's a superset of JSON.
+
... This PR can't be merged due to the status of work in the WG. There is a charter issue that needs to be resolved.
+

+Subtopic: updated WG charter +

+
Benjamin Young: We haven't done any work on a charter.
+
Gregg Kellogg: Current charter only allows work on notes, not rec-track.
+
Benjamin Young: Plan is a re-charter of https://www.w3.org/2023/01/json-ld-wg-charter.html
+
Benjamin Young: Needs to be voted on by membership.
+
... I think we can continue to work on the document, but there are different patent policy considerations
+
Ted Thibodeau Jr.: We can vote that the document is a final report (which we have done).
+
... Theoretically, it should stay static. When the WG picks it up, we should stop work.
+
Benjamin Young: I think the work fell through the cracks with the WG.
+
Benjamin Young: We'll do a WG meeting in four weeks on March 6th.
+
Benjamin Young: I was trying to find out where the charter lives.
+ +
Anatoly Scherbakov: What is the WG process if re-chartered? Does the WG copy a snapshot?
+
Gregg Kellogg: Typically it is just merged over.
+
Anatoly Scherbakov: So, we can make PRs and merge later.
+

+Topic: CBOR-LD +

+
David I. Lehn: I haven't done any work on the spec.
+ +
Gregg Kellogg: We probably need to publish a final report.
+ +
Niklas Lindström: The https://github.com/json-ld/charter repo is inactive, and this is the current charter (mentions YAML and CBOR)? https://www.w3.org/2023/01/json-ld-wg-charter.html
+
Gregg Kellogg: Maybe could be published as a draft report
+
Benjamin Young: How many links do we want to publish?
+
... Do we want to issue both as notes?
+
Gregg Kellogg: I'd say list both as draft reports.
+
Benjamin Young: Maybe should move PA's version to the json-ld org, so it's not confusing.
+
ACTION: pchampin to move JSON-LD in CBOR draft to json-ld org.
+
Sorry, I don't know what repository to use.
+
Benjamin Young: Repo to pchampin's spec https://github.com/w3c/json-ld-cbor/
+ +
Benjamin Young: Question is do they need to be finalized for the WG to take them up?
+
Benjamin Young: Implementation https://github.com/digitalbazaar/cborld
+
Gregg Kellogg: It would be good to have issues added to CBOR-LD to indicate needed changes to match implementations.
+
Benjamin Young: It takes some time to make those updates, and time is short. I referenced a link to the implementation.
+
Gregg Kellogg: I'd like to see something with a bit more of a summary for how implementation diverges from spec.
+
David I. Lehn: For the current stuff, before we tag it, I want to double-check to make sure URLs are up to date.
+
... Not sure if people are familiar with how the spec works.
+
Gregg Kellogg: Editorial changes, including editors notes, should be fine. normative changes may need more agreement.
+

+Topic: JSON-LD Issue Discussion +

+ +
David I. Lehn: Do we need a process for merging tests.
+
For example w3c/json-ld-api#591
+
https://github.com/w3c/json-ld-api/pull/591 -> Pull Request 591 Add test for `@context` redefinition. (by davidlehn) [test:missing-coverage]
+
David I. Lehn: Looked into this, and it looked like an error.
+
... It was a bug in JSON-LD where it was too generous.
+
... I think our implementation would have ultimately failed.
+
Niklas Lindström: https://w3c.github.io/json-ld-api/#algorithm-0 (step 4 and 5)
+
David I. Lehn: When we don't have tests it can be hard to tell.
+
Gregg Kellogg: I think its an issue that we don't specifically linked from normative statements to tests.
+
Niklas Lindström: +1 For test coverage for each normative statement
+
Niklas Lindström: And +1 for predictable naming of those ...
+
Gregg Kellogg: Not too difficult, but time consuming.
+
David I. Lehn: On the same topic, if all implementations did coverage reports, that would be useful.
+
Gregg Kellogg: I would say that test changes that have developer approval can be merged, as long as they don't require a normative change to the spec.
+
ACTION: dlehn to tag reviewers on tests to be considered for merging.
+
Sorry, I don't know what repository to use.
+
Gregg Kellogg: Also work should go forward on the charter where people can contribute.
+

+Topic: Open Discussion +

+
Gregg Kellogg: Meet again on February 21.
+
+ + \ No newline at end of file diff --git a/2024-02-07/irc.log b/2024-02-07/irc.log new file mode 100644 index 0000000..e4dae05 --- /dev/null +++ b/2024-02-07/irc.log @@ -0,0 +1,127 @@ +17:00:51 RRSAgent has joined #json-ld +17:00:55 logging to https://www.w3.org/2024/02/07-json-ld-irc +17:00:55 RRSAgent, make logs Public +17:00:56 please title this meeting ("meeting: ..."), gkellogg +17:00:59 meeting: JSON-LD CG +17:01:02 present+ +17:01:22 agenda: https://www.w3.org/events/meetings/398465c7-3787-40df-856a-434a438d9f05/20240207T120000/ +17:01:23 clear agenda +17:01:23 agenda+ Announcements and Introductions +17:01:23 agenda+ YAML-LD +17:01:23 agenda+ CBOR-LD +17:01:23 agenda+ JSON-LD Issue Discussion +17:01:25 agenda+ Open Discussion +17:01:28 agenda+ Next call +17:01:35 zakim, next agendum +17:01:35 agendum 1 -- Announcements and Introductions -- taken up [from agendabot] +17:02:01 bigbluehat has joined #json-ld +17:02:08 chair: gkellogg +17:02:11 scribe+ +17:02:16 present+ +17:02:40 present+ +17:02:41 zakim, close item 1 +17:02:41 agendum 1, Announcements and Introductions, closed +17:02:43 I see 5 items remaining on the agenda; the next one is +17:02:43 2. YAML-LD [from agendabot] +17:02:45 zakim, next item +17:02:45 agendum 2 -- YAML-LD -- taken up [from agendabot] +17:02:54 q+ +17:03:01 ack anatoly-scherbakov +17:03:18 anatoly-scherbakov: --shares screen-- +17:03:33 niklasl has joined #json-ld +17:03:38 present+ +17:04:14 anatoly-scherbakov: I created issue json-ld/yaml-ld#131 for script tags in HTML. +17:04:15 https://github.com/json-ld/yaml-ld/issues/131 -> Issue 131 YAML under `