- From: Pieter Colpaert <pieter.colpaert@ugent.be>
- Date: Mon, 2 Sep 2024 17:15:06 +0200
- To: "public-treecg@w3.org" <public-treecg@w3.org>
- Message-ID: <cb7b25d1-e6c7-4c9f-ac39-bd8040845e51@ugent.be>
Dear all, This Wednesday at 14:00 CET we’ll have another TREE CG meeting. The TREE CG meeting will be held on a Google Meet now. The link link is this one: https://meet.google.com/ngy-ashk-dzn The discussion points will be: 1. PR #111 started splitting of the discovery spec, but ended up being a decent rework of the spec. You can find the report here: https://github.com/TREEcg/specification/pull/111 -- While it may still evolve by Wednesday, I added the current HTML version in the attachment so you can review it more swiftly. I’m getting more and more confident this gets us right on track for a 1.0 release before the end of the year. 2. The discovery specification: how to progress there as it will take a while to get it to be a finalized report - make it a draft for now? Or get a first basic version out asap? 3. Any ideas on how to formulate the processing specific relations more clearly? 4. For the member extraction algorithm we had the idea at one point to make streaming parsing faster through a pretty-print turtle profile. I’m progressing on creating some experiments to check whether we should add it to the spec. You can find a codebase with a parser and serializer over here: https://github.com/pietercolpaert/Wurtle.js - It works uses pragma or parser directives in the comments of the turtle file (or any serialization of the N3 family). I intend to analyse the performance of this compared to other member extraction cases in the extract-cbd-shape repo. 5. Any another business: anything else we should prioritize or propose in this CG? Kind regards, Pieter -- https://pietercolpaert.be +32486747122
Attachments
- text/html attachment: spec.html
Received on Monday, 2 September 2024 15:15:14 UTC