– DRAFT –
RDF & SPARQL WG meeting

Approval of last week’s minutes: 1

<ktk> PROPOSAL: Approve last week's minutes

<AndyS> +1

<niklasl> +1

<ktk> +1

<Dominik_T> +1

<tl> +1

<olaf> +1

<TallTed> +1

<pchampin> +1

<lisp> +1

RESOLUTION: Approve last week's minutes

Review of open actions, available at 2

ktk: Nothing new on open actions

Identifying issues to solve before CR 3

ktk: Regarding recognized members of the WG, I have a final query to share.
… me, Ora and Pierre-Antoine went through the generated sparql query results for recognized members, with nickname cleanups, and asked where to draw the line.
… Our proposal is to draw the line at 30 attendances, with one exception for Jerven, who joined late but took over the RDF/XML editor role.
… Does anyone miss oneself or any other in this list?
… I will map this to our user names and that will count as the list of active members of the working group.
… If no objections, that will be the final list for approval.
… But please contact the chairs if something is missing.

TallTed: I'm a bit concerned that this is focused only on teleconferences; not e.g. mailing list and/or github work.

ktk: Agreed. We did take other activities into account when deciding on drawing the line at 30.
… The scoring shouldn't be interpreted as anything, it was to get an initial set of suggested names.

TallTed: That'll do.

AndyS: I added the issue on RDF/XML, specifically the tests we have. It needs some sorting out; e.g. how it deals with the new rdf:version, which seems different for different features.
… There is really no way to evolve RDF/XML, the two extension features we've got doesn't really give leeway.
… E.g. adding rdf:* attributes comes with problems.

ktk: Do we expect to break something?

AndyS: There are corner-cases. We don't suspect them to have practically occurred in the wild.
… It would mean people tramping in on the rdf: namespace, etc.

ktk: Should this be documented in the new version?

AndyS: We need to add a line or two.
… I know Jerven thinks about this too.
… The issue w3c/rdf-xml#86 is for these details.

<gb> Issue 86 Evolving 1.2 triple term features : rdf:parseType, rdf:annotation (by afs) [ms:CR]

ktk: Those who actively use RDF/XML are welcome to chime in on this issue.

AndyS: We don't have a clean break, like in Turtle etc., where adding new things is a syntax error in older versions.

AndyS: One contributior to Jena uses RDF/XML, for the CIM

ktk: Are we on track with the test files tracking issue?

pchampin: We have tacking issues for the semantics tests and one other. Some line items are thus redundant.

ktk: We have captured this information and can close without waiting.

Any Other Business (AOB), time permitting

ktk: What's the status of Sophia?

pchampin: Parsers pass all the tests on Turtle, TriG [and more]
… Reuses tpt:s implementation (oxigraph)

<ktk> pchampin/sophia-cli

pchampin: My implementation has simple, RDF and RDFS entailments (without extra datatypes), they all pass.

ktk: the rust-based cli is useful for large sets of small files, etc.

I've got niklasl/oxrq based on oxigraph; use it like awk for our core vocab files, etc.

I hope this one may prove useful, did it over the last couple of evenings: a TriG pretty-printer niklasl/gnarly (pyoxigraph-based)