- From: Niko - NextGraph <niko@nextgraph.org>
- Date: Mon, 9 Dec 2024 02:02:29 +0200
- To: public-crdt4rdf@w3.org
- Message-ID: <2e3a0616-c3e4-4fc3-b95e-0e226638d0c2@nextgraph.org>
Hello everyone, Apart from the very important and generic topic on how to make CRDTs for RDF, I am sharing with you my thoughts and proposal on how CRDT could be added to the Solid specs. On the generic topic of conflict resolution mechanism for RDF, maybe Hala Skaf-Molli could give us an overview of the available options? I have implemented SU-set in NextGraph, which is an Observed remove set (insert wins over delete). But maybe there are other ways of conflict resolution mechanism for RDF ? In the meanwhile, I share with you the Use-Case issue I created for the W3C Linked Web Storage WG, where I am talking about bringing another level of abstraction for the APIs in the Solid specs. I believe that there is a fundamental difference between the approach used in NextGraph and the one we have seen so far in other attempts at bringing CRDT to Solid, and I try to explain this in the Github issue. Let's discuss here what you think about this proposal, i you want :) https://github.com/w3c/lws-ucs/issues/24 Wishing you all a good end of the year! Cheers, Niko
Attachments
- application/pgp-keys attachment: OpenPGP public key
Received on Monday, 9 December 2024 00:02:53 UTC