- From: Pieter Colpaert <pieter.colpaert@ugent.be>
- Date: Wed, 21 Aug 2024 15:22:43 +0200
- To: public-treecg@w3.org
- Message-ID: <44f22240-d030-476f-a67e-fe4ab9f339ca@ugent.be>
Hi all, Thanks for a fruitful meeting! The limited amount of slides can be found here: https://docs.google.com/presentation/d/1BMbjZm0c7gDMQ--v42X98U_gGTa0h4bBCu961NNpTiU/edit#slide=id.g2494e1ca6ae_0_0 Decisions: * We’ll put out new meetings in the schedule for every first Wednesday of the month at 14:00CET * We’ll welcome a PR rewriting the spec from the perspective of a client to be discussed the 4th of September (21st CG meeting). * @Konstantin: The link to the geospatial work that would start up at some point (it didn’t yet and will probably at some point be looking for people to support it), is here: https://github.com/situx/ontology-crs - it focuses on getting CRSs right. We might in time refer to that work as well when comparing geospatial properties Another something we didn’t discuss in the call but might be of interest to some is that at this moment there is a Linked Web Storage *Working *group being created at W3C. They will focus on enabling the development of web applications where data storage, entity authentication, access control, and application provider are all loosely coupled, as opposed to the web of today where these are typically all tightly coupled and changing one requires changing all, sometimes at the price of all past data. This will be achieved by standardizing a protocol between applications, on the one hand, and identity and storage servers, on the other hand. Speaking of specs that might adopt TREE for their server-based pagination, this might be a good one to also keep an eye upon. In their current charter, they also list a few community groups they want to keep an eye on, such as the Solid CG, the LDP next CG, the WebID CG, ... . TREE is not included at this moment. Kind regards, Pieter On 21/08/2024 14:04, Pieter Colpaert wrote: > Hi all, > > Apparently there’s something wrong with the Teams link. Trying to > reshare it here: > https://teams.microsoft.com/l/meetup-join/19:meeting_NDkwMWZlMzMtM2FjZi00MjZhLTlhZTMtNjAwMjU5Yjc3YWVi@thread.v2/0?context=%7B%22Tid%22:%22a72d5a72-25ee-40f0-9bd1-067cb5b770d4%22,%22Oid%22:%22074b6191-940e-49de-964e-f2919f3f8501%22%7D > > > Kind regards, > > Pieter > > On 21/08/2024 11:45, Pieter Colpaert wrote: >> Dear all, >> >> At 14:00 CET we will have our 20th TREE CG meeting. It will mainly be >> a catch-up after the summer holidays. Our next meeting will then be >> again on the 4th of September. >> >> The usual link: >> https://teams.microsoft.com/l/meetup-join/19:meeting_NDkwMWZlMzMtM2FjZi00MjZhLTlhZTMtNjAwMjU5Yjc3YWVi@thread.v2/0?context%3D%257B%2522Tid%2522:%2522a72d5a72-25ee-40f0-9bd1-067cb5b770d4%2522,%2522Oid%2522:%2522074b6191-940e-49de-964e-f2919f3f8501%2522%257D&sa=D&source=calendar&usd=2&usg=AOvVaw1Vi2FNLxrZm76Y1WVfqain >> >> Points on the agenda: >> >> * How is everyone: any updates in professional life and ambitions? >> >> * Always writing the specification from the perspective of clients >> from now on. Pieter has 90% finished version as part of the split >> discovery PR that is much clearer, but still has some open issues. It >> is up to domain specific API specifications to provide the >> documentation to API developers on how they need to implement a >> server. I envision a lot of these specifications to pop up, that can >> do not need to do anything normative: as long as they understand how >> TREE clients are going to interact with them. >> >> * Feeding our calendar with new dates >> >> * Reach-out: how will we get more people into our group? >> >> Kind regards, >> >> Pieter >> -- https://pietercolpaert.be/ +32486747122
Received on Wednesday, 21 August 2024 13:22:51 UTC