- From: <niko@nextgraph.org>
- Date: Sat, 16 Nov 2024 23:13:11 +0200
- To: public-crdt4rdf@w3.org
- Message-ID: <e4de39cb-6671-4491-9c3d-b6ae9a9a9175@nextgraph.org>
Hello bergi, And welcome here! I am Niko, the author of NextGraph.org maybe you heard about it recently. I am glad you have an interest for distributed datasets and that you implemented something similar to an append-only log of changes for RDF. And the format is similar to what NextGraph is doing, as I could see. you use a set of added quads and a set of deleted quads for each change. In your repo, you write "Any conflicts of previously added/deleted quads in the same changeset are solved." I didn't have time to read your code to find out how the conflict resolution is done. Could you detail it for us ? It is an important detail if we want to understand if you solution is a CRDT. Cheers, Niko On 15/11/24 11:35 pm, bergi wrote: > Hi everyone! > > Some may know me from the RDF/JS community group and as the maintainer > of RDF-Ext and related packages. A few years ago, I created the > rdf-dataset-changelog[1] package for a PoC of a distributed dataset > using the Raft consensus algorithm[2] to store deployment information > of JS and Wasm applications for my local IoT setup. It's like a > small-scale Kubernetes cluster. With rdf-dataset-changelog, I also had > the first building block for CRDT, so I gave it a try in a very basic > PoC. While I don't have a concrete use case at the moment, I find that > topic very interesting, and I'm looking forward to working on a > specification or implementation that simplifies the usage of CRDT in > the RDF world. > > Best, > bergi > > [1] https://www.npmjs.com/package/rdf-dataset-changelog > [2] https://github.com/bergos/liferaft/ >
Attachments
- application/pgp-keys attachment: OpenPGP public key
Received on Saturday, 16 November 2024 21:14:43 UTC