JSON-LD CG

Minutes for 2025-02-12

Present

Ivan Herman, Pierre-Antoine Champin, Anatoly Scherbakov, Niklas Lindström, Ted Thibodeau Jr., David I. Lehn

Regrets

Gregg Kellogg

Chair(s)

Benjamin Young

Scribe(s)

Benjamin Young, Pierre-Antoine Champin

Agenda

https://www.w3.org/events/meetings/635aef15-a607-499c-b32a-926d3cb3a580/20250212T120000/#agenda

Topics

Announcements and Introductions
JSON-LD Issue Discussion

Benjamin Young: Url: https://www.w3.org/events/meetings/635aef15-a607-499c-b32a-926d3cb3a580/20250212T120000/#agenda

Topic: Announcements and Introductions ✪

Pierre-Antoine Champin: Work on our charter has been announced to the AC [scribe assist by Benjamin Young]

Benjamin Young: ... So others can have a chance to chime in

Benjamin Young is scribing.

Pierre-Antoine Champin is scribing.

Pierre-Antoine Champin: The announcement pointed the members to the public repo (link above)

Topic: JSON-LD Issue Discussion ✪

Benjamin Young: I don't think the project has been re-sorted. Let's look at pending PRs.

Subtopic: https://github.com/w3c/json-ld-api/pull/625 -> Pull Request 625 (closes #555) Fall back to default logic in `useNativeTypes` mode for RDF numbers which are not JSON numbers (by anatoly-scherbakov) [class-3] ✪

Benjamin Young: This one was heavily approved

Anatoly Scherbakov: I've recently applied suggestions from TallTed and pchampin

Benjamin Young: The people involved in the review are all here. Any objection to merge it now?

Pierre-Antoine Champin: None from me

Benjamin Young: Hearing none, let's merge this PR

Subtopic: https://github.com/w3c/json-ld-api/pull/559 ✪

Subtopic: https://github.com/w3c/json-ld-api/pull/585 ✪

Benjamin Young: For this one (and the previous one), we don't have the commenters here. Hard to discuss them here.

Subtopic: https://github.com/w3c/json-ld-api/issues/627 ✪

Benjamin Young: We discussed this last call. I asked Jeffrey for more examples, which he provided.

... ivan, you pointed out that DID-Resolution uses INFRA instead of WebIDL.

... The main remaining issue is the amount of editorial work.

Pierre-Antoine Champin: We could maybe automate the WebIDL to INFRA conversion?

Benjamin Young: Or have an AI do that...

Subtopic: https://github.com/w3c/json-ld-api/issues/558 ✪

Benjamin Young: Niklasl, this one is yours. No activity in the past 2 years (almost exactly).

Niklas Lindström: https://github.com/niklasl/trld/commit/1190a251514e7cb7bc8d596ba6b6bf4da3632bab

Niklas Lindström: I have a proposal about what to do. I have refactored my implementation accordingly.

... (link above)

... AFAICT this fixes the issue.

Benjamin Young: Niklasl, would you be willing to write a PR for that?

Niklas Lindström: Yes, I can try

... I also need to check whether there are any side effects.

Benjamin Young: This needs to be wrapped in <ind>/<del> tags, like the other PRs we have.

Subtopic: https://github.com/w3c/json-ld-syntax/issues/436 ✪

Pierre-Antoine Champin: I discussed this with Yves Lafon, staff contact of the TAG.

... This restriction of fetch is considered as an important security feature, this is unlikely to go away.

... To mitigate this issue, should we (JSON-LD WG) set up a registry for short-names for profiles of application/ld+json ?

Niklas Lindström: I don't think that a registry would solve the problem.

... We need to distinguish data shapes from the semantics of data.

... Activity Streams went for a specific media-type, others may have to do that.

... This issue seems specific to an RDF mindset.

... E.g. I want RDF, and I only understand SKOS.

... I have not seen the same kind of issue in other contexts, where structure and semantics are the same.

Niklas Lindström: ... Does the web need "compound media type negotiation" ... ��

Pierre-Antoine Champin: Actually, video formats also suffer from the coarseness of media-types

Benjamin Young: CORS breaks a lot of things. I don't think Ruben's proposal will fly.

Niklas Lindström: (Or in the video format context, I guess "Accepts-Codex", ... And in the RDF context, maybe what I really want is "Accepts-Vocabulary" ... but try to realize that through "Accepts-Profile", for better or worse...)

... We have been discussing recently with the people working on profile-based conneg.

Pierre-Antoine Champin: Activity on the dx-connegp has been on and off for a while. We may want to provide some help.

Benjamin Young: JSON-LD mostly needs to help downstream specifications know what to choose among the media type vs. profile negotiation vs. something else

... we can and should point to the profile negotiation doc when it's available

Niklas Lindström: We at the National Libarry of Sweden, would really like to see a form of profile-based conneg. I think I could spend some time on this.

... Part of it is orthogonal to JSON-LD.

Benjamin Young: Agreed, it is not a core issue for us.

Subtopic: dlehn PRs ✪

David I. Lehn: What should I do about those, until we have a solid decision about the desired behaviour.

Benjamin Young: If you would post a comment spelling out the decision that we need to make, this would be helpful.

David I. Lehn: This mostly came out from somebody reporting a bug.

Ted Thibodeau Jr.: A possible resolution is "this is an edge case, we won't solve it now"

Subtopic: https://github.com/json-ld/cbor-ld-spec/pull/22 ✪

Benjamin Young: This PR adds a context URL in the CBOR-LD registry

... Dmitri suggested to change from the version-less URL to the versionned one.

David I. Lehn: Aren't we moving away from the registry, for CBOR-LD?

... People may continue to use the old stuff, though...

... We need to refine how it is supposed to work.

Benjamin Young: I'll ask Wes dans Dave Longley (who are most active on CBOR-LD these days) what they think of it.

... This should be a more general discussion.

Pierre-Antoine Champin: I'm uncorfortable with CBOR numbers pointing to URL with changing content.

... But we need to discuss this with Wes and Dave Longley.

The W3C JSON-LD Community Group

Go Back