The W3C JSON-LD Community Group

Go Back

W3C Logo


Minutes for 2023-06-28

Gregg Kellogg is scribing.
Ted Thibodeau Jr.: Without warning, my ISP has begun updating cable in my area today, so my service is intermittent at best. I'll join by zoom on my phone, but that will not support IRC

Topic: Announcements and Introductions

TPAC attendance.
Niklas Lindström: Is the deadline for registration soon? There is also a physical conference I might need to attend.
Pierre-Antoine Champin: Registration up until Sept 2.

Topic: YAML-LD

Anatoly Scherbakov: I've been working on unification of the spec, but also some more general changes.
... In the spec, I've tried to reduce the number of vocabularies we use, focusing on
... Ive rearranged some text for clarity, and added some elements comparing JSON and YAML.
... I've changed some longer sentences to lists.
... FAQ moved to different sections. Comments are mentioned as explicitly being discarded.
... YAML streams not supported, might relate to NDJSON-LD.
Niklas Lindström: +1, Same as for JSON-as-JSON-LD
Niklas Lindström: (Re. YAML as YAML-LD)
... In addition to move the section on examples, I've moved the section on aliases, and used consistent examples.
... references to YAML-LD convenience context.
Niklas Lindström: (Could be but the convenient-context repo needs to be configured to serve one branch as github-pages)
... A goal I have is to gather feedback and look for format/grammar errors.
Gregory Saumier-Finch: +Q
Gregory Saumier-Finch: When writing, should there be a "/" or not? Most examples don't use a "/".
Anatoly Scherbakov: I may have confused the context with the namespace definition
Ted Thibodeau Jr.: Pronounced "Slash" not "Back Slash"
... No problem including it, but not necessary as a context reference.
David I. Lehn: It's important that people map it correctly.
Gregory Saumier-Finch: Safe to include the "/"
Anatoly Scherbakov: Consistency is good, so we might want to stick with one convention.
David I. Lehn: Depending on the processor, if is caching contexts, it might hit in one case and not in another.
Niklas Lindström: The actual context document used comes from the response link header: link: </docs/jsonldcontext.jsonld>; rel="alternate"; type="application/ld+json"
Pierre-Antoine Champin: I think it is ok with the FIRST slash of the path, though
Ted Thibodeau Jr.: When you get a resource ending with a "/", you're technically getting a container. The default behavior is to return "index.html", or whatever is configured.
Niklas Lindström: Serves do not see whether you requested or, they GET a "/"
Niklas Lindström: (This is special for "just domain" requests, they DO differ between "/a" and "/a/")
Anatoly Scherbakov: I'd love to have more help in reviewing the quality of the text.
... After that, I'm thinking about generating some of the parts of the spec from YAML-LD itself.
Ted Thibodeau Jr.: `Serves do not see whether you requested or, they GET a "/"` That's inaccurate, but yes, we can discuss elsewhere/elsewhen
... I'm developing a tool for turning YAML-LD descriptions into tables.
Ted Thibodeau Jr.: (Subtle nuances are very important when acting on specs, which is why I'm hammering on these things in *writing* such specs.)
Niklas Lindström: TallTed -- Agree, details are crucial. I just tried CURL, it does that, but it might also be inaccurate (as many browsers are).

Topic: JSON-LD Issue Discussion

Subtopic: -> Pull Request 415 Add structured suffix (OR13) spec:substantive
Pierre-Antoine Champin: I had a look at w3c/json-ld-syntax#415, but I'm a bit uncomfortable with the duplication with the application/ld+json registration.
... Would it be possible to have the text in one place, and others point to it?
Ted Thibodeau Jr.: The registrations are handled by humans, so I don't think they need to be fully self-sufficient, but they should be easy. Replication may vary.
... I've looked at several, and there is no real consistency. We should aim for comprehension.

Subtopic: w3c/json-ld-api#559 -> Pull Request 559 Add JSON literal tests. (davidlehn)
David I. Lehn: Still needs discussion. Needs spec updates.

Subtopic: w3c/json-ld-api#566 -> Pull Request 566 Fix context processing for reverse terms (niklasl)
Niklas Lindström: I did some recent updates, so it's ready for another pass. The "changes" section may need some improvement. The others are fairly technically simple.
... It's only about three words, but they're particularly important.

Topic: JSON-LD-star


Niklas Lindström: If anyone's had time to look at json-ld/json-ld-star#45, there is some background and motivation. -> Issue 45 Keeping quoted triples sharing subject within one node object (niklasl)
Gregory Saumier-Finch: Very iterested but didn't have time to review.
Gregg Kellogg: Might need to wait for more work on RDF-star.
Pierre-Antoine Champin: I haven't either, unfortunately... :-/
Niklas Lindström: I promised to add use cases for RDF-star, so I can pick things out of this.
... Syntax does matter, as that's how people interact with the semantics. This one points to an interesting issue that I'm having a hard time separating from data access.
... It's still pretty relevant. This example also pokes at the trickiness with opacity of quoted triples without getting into it too deeply.
Pierre-Antoine Champin: I haven't been able to look at it in depth, but IIRC, you're worried about the asymmetry of subject vs object. That's not JSON-LD specific, but exists in RDF.
Niklas Lindström: It does have the same asymmetry, but I've avoided that. JSON-LD allows nesting which Turtle doesn't. I'd like to be able to do something like this in Turtle as well.
... The use cases are abstracted from real use cases, and they are related to Wikidata use cases.
Gregory Saumier-Finch: I am also working on wikidata representation with rdf star
... I've experimented with representing using RDF-star.
... Wikidata uses kind of real reification; I would expect that once RDF-star is a standard, something like this would be used with Wikidata.
... Going back to this issue, some facts in Wikidata might not be approved, but you'd still want to combine them together, so it gets into quoting pretty heavilly.
... The second JSON-LD example shows using it with a custom context and traditional reification and it becomes more readable than JSON-LD-star quoted triples.
Anatoly Scherbakov: If there is no quorum then the TPAC meeting might not happen.
Niklas Lindström: (Re: "GET /", if I read correctly, you cannot issue a fully empty HTTP GET, i.e. "/" is necessary in the protocol...?)