Agenda for 2024-10-09 CG meeting #688
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
TallTed
suggested changes
Oct 9, 2024
|
|
||
| * eP: Niko who is developing NextGraph will give 15-20min presentation | ||
| * Niko: presenting slides and demo | ||
| * ...: Peer to Peer semantic we collaboration |
There was a problem hiding this comment.
Suggested change
| * ...: Peer to Peer semantic we collaboration | |
| * ...: Peer to Peer semantic web collaboration |
Comment on lines
+61
to
+63
| * ...: Local-first CRDT of RDF - you can edit offline and data gets synchronized once you get online and without conflicts. I developed CRDTs for RDF, there are already formats for JSON. I added compatibility with automerge and yjs. This way one can mix all kinds of data. | ||
| * ...: end-to-end encrypted | ||
| * ...: decentralized - 2 tier. Not peer-to-peer we have servers which act as brokers. It is based on pub/sub where replicas subscribe. All the changes are propageted. Brokers are constantly exchanging updates in anticipation for the devices that subscribe to them. Local replica offers SPARQL locally to the applictions. |
There was a problem hiding this comment.
Suggested change
| * ...: Local-first CRDT of RDF - you can edit offline and data gets synchronized once you get online and without conflicts. I developed CRDTs for RDF, there are already formats for JSON. I added compatibility with automerge and yjs. This way one can mix all kinds of data. | |
| * ...: end-to-end encrypted | |
| * ...: decentralized - 2 tier. Not peer-to-peer we have servers which act as brokers. It is based on pub/sub where replicas subscribe. All the changes are propageted. Brokers are constantly exchanging updates in anticipation for the devices that subscribe to them. Local replica offers SPARQL locally to the applictions. | |
| * ...: Local-first CRDT of RDF — you can edit offline and data gets synchronized once you get online and without conflicts. I developed CRDTs for RDF, there are already formats for JSON. I added compatibility with automerge and yjs. This way one can mix all kinds of data. | |
| * ...: end-to-end encrypted | |
| * ...: decentralized — 2 tier. Not peer-to-peer; we have servers which act as brokers. It is based on pub/sub where replicas subscribe. All the changes are propageted. Brokers are constantly exchanging updates in anticipation of the devices that subscribe to them. Local replica offers SPARQL locally to the applications. |
| * ...: end-to-end encrypted | ||
| * ...: decentralized - 2 tier. Not peer-to-peer we have servers which act as brokers. It is based on pub/sub where replicas subscribe. All the changes are propageted. Brokers are constantly exchanging updates in anticipation for the devices that subscribe to them. Local replica offers SPARQL locally to the applictions. | ||
| * ...: also binary data | ||
| * ...: we have an app mobile, desktopand web - alpha |
There was a problem hiding this comment.
Suggested change
| * ...: we have an app mobile, desktopand web - alpha | |
| * ...: we have an app mobile, desktop and web — alpha |
Comment on lines
+68
to
+69
| * ...: we are collaborating with ActivityPods, already mentioned today, yesterday we annonced the collabortion. On Monday activitypods released v2.0 - it combines ActivityPub with Solid. | ||
| * ...: ActivityPods also uses SPARQL, solid documents are named graphs. Next Graph is doing the same which fits well. They will also adopt DIDs for documents and agents, as NextGraph. A special DID method will be registered. |
There was a problem hiding this comment.
Suggested change
| * ...: we are collaborating with ActivityPods, already mentioned today, yesterday we annonced the collabortion. On Monday activitypods released v2.0 - it combines ActivityPub with Solid. | |
| * ...: ActivityPods also uses SPARQL, solid documents are named graphs. Next Graph is doing the same which fits well. They will also adopt DIDs for documents and agents, as NextGraph. A special DID method will be registered. | |
| * ...: we are collaborating with ActivityPods, already mentioned today, yesterday we announced the collaboration. On Monday, activitypods released v2.0. It combines ActivityPub with Solid. | |
| * ...: ActivityPods also uses SPARQL; Solid documents are named graphs. NextGraph is doing the same which fits well. They will also adopt DIDs for documents and agents, as NextGraph. A special DID method will be registered. |
| * ...: let's do another update, now in the other app we see the whole history of the document, creation, signature, adding first triple, then adding another triple. I will add another one on the left and we can see another commit on the right. | ||
| * ...: Now I will disable connection in the web app, I can still edit the document. And in the other ap I will make a different update. No sync yet since the webapp is offline. Now we go backonline and we see on the right a fork. As soon as I make another commit we can see the automatic merge. So it has the automerge without conflicts, it also work on data deletion. | ||
| * Rui: what does the `o` mean in the DID identifier? | ||
| * Niko: We are registering the `did:ng` method, the rest is specific to the next graph and `o` means a document. You can find it in the DID section of NextGraph docs |
There was a problem hiding this comment.
Suggested change
| * Niko: We are registering the `did:ng` method, the rest is specific to the next graph and `o` means a document. You can find it in the DID section of NextGraph docs | |
| * Niko: We are registering the `did:ng` method; the rest is specific to NextGraph, and `o` means a document. You can find it in the DID section of NextGraph docs. |
Comment on lines
+100
to
+102
| * Niko: yes key rotation is very important, it is already integrated into protocol and the design. The public key is never going to change, but it is not used for signing. There is a chain, this can be revoked and updated. | ||
| * Hadrian: a discussion for another time | ||
| * Niko: please feel invited to nextgraph forum |
There was a problem hiding this comment.
Suggested change
| * Niko: yes key rotation is very important, it is already integrated into protocol and the design. The public key is never going to change, but it is not used for signing. There is a chain, this can be revoked and updated. | |
| * Hadrian: a discussion for another time | |
| * Niko: please feel invited to nextgraph forum | |
| * Niko: yes, key rotation is very important. It is already integrated into the protocol and the design. The public key is never going to change, but it is not used for signing. There is a chain; this can be revoked and updated. | |
| * Hadrian: A discussion for another time. | |
| * Niko: Please feel invited to NextGraph forum. |
Comment on lines
+122
to
+124
| * eP: Solid calendar app and integrated schedule polling can be a **use case**. With conflicts detector and templates for starting a poll and responding. | ||
| * Hadrian: I have a conflict as well. One proposal was to have two times for different timezones. | ||
| * eP: Propose to remove the one that's in the calendar and we can do online polls and then we make sure that the experts in the field can be present. Better than one fixed slot. For instance we can run polls for 2 weeks ahead and reach out to the expert. |
There was a problem hiding this comment.
Suggested change
| * eP: Solid calendar app and integrated schedule polling can be a **use case**. With conflicts detector and templates for starting a poll and responding. | |
| * Hadrian: I have a conflict as well. One proposal was to have two times for different timezones. | |
| * eP: Propose to remove the one that's in the calendar and we can do online polls and then we make sure that the experts in the field can be present. Better than one fixed slot. For instance we can run polls for 2 weeks ahead and reach out to the expert. | |
| * eP: Solid calendar app and integrated schedule polling can be a **use case**. With conflict detector, and templates for starting and responding to a poll. | |
| * Hadrian: I have a conflict as well. One proposal was to have two times, for different timezones. | |
| * eP: Propose to remove the one that's in the calendar. We can do online polls and make sure that the experts in the field can be present. Better than one fixed slot. For instance, we can run polls 2 weeks ahead, and reach out to the experts. |
Comment on lines
+125
to
+127
| * Tim: A year or two ago, we had SolidOS meeting and decided to have them all in the same constant GMT timezone. We should keep it fixet to the GMT. | ||
| * Rahul: I see this coordination problem, especially when you want to get the timezones. I would still suggest to find antohter fixed slot, and keep it reserved for STM. Having it there would make things easier. | ||
| * Tim: You could cooridnate with different priority on different weeks. |
There was a problem hiding this comment.
Suggested change
| * Tim: A year or two ago, we had SolidOS meeting and decided to have them all in the same constant GMT timezone. We should keep it fixet to the GMT. | |
| * Rahul: I see this coordination problem, especially when you want to get the timezones. I would still suggest to find antohter fixed slot, and keep it reserved for STM. Having it there would make things easier. | |
| * Tim: You could cooridnate with different priority on different weeks. | |
| * Tim: A year or two ago, we had SolidOS meetings, and decided to have them all in the same constant GMT timezone. We should keep it fixed to GMT. | |
| * Rahul: I see this coordination problem, especially when you want to get the timezones. I would still suggest to find another fixed slot, and keep it reserved for STM. Having it there would make things easier. | |
| * Tim: You could coordinate with different priority on different weeks. |
Comment on lines
+128
to
+131
| * eP: We had this slot and didn't really use it. It clearly doesn't work. For me it conflicts. Suggest we start with online slots. After a few months we can decide if to use the same slot. If all experts are using the same slot then we can continue that way. | ||
| * Hadrian: we have proposal for a poll and for fixed slots | ||
| * eP: I don't think the two proposals are mutually exclusive. Especially if we want to reach out to experts with are not Solid CG regulars. | ||
| * Hadrain: I'm propose reducing STM meeting to one hour, have multiple slots in the week which would be empty. Everyone can become champion of the meeting and can reserve slot and ensure experts are present. |
There was a problem hiding this comment.
Suggested change
| * eP: We had this slot and didn't really use it. It clearly doesn't work. For me it conflicts. Suggest we start with online slots. After a few months we can decide if to use the same slot. If all experts are using the same slot then we can continue that way. | |
| * Hadrian: we have proposal for a poll and for fixed slots | |
| * eP: I don't think the two proposals are mutually exclusive. Especially if we want to reach out to experts with are not Solid CG regulars. | |
| * Hadrain: I'm propose reducing STM meeting to one hour, have multiple slots in the week which would be empty. Everyone can become champion of the meeting and can reserve slot and ensure experts are present. | |
| * eP: We had this slot and didn't really use it. It clearly doesn't work. For me, it conflicts. Suggest we start with online slots. After a few months, we can decide whether to use the same slot. If all experts are using the same slot, we can continue that way. | |
| * Hadrian: We have proposal for a poll and for fixed slots. | |
| * eP: I don't think the two proposals are mutually exclusive. Especially if we want to reach out to experts who are not Solid CG regulars. | |
| * Hadrain: I'm propose reducing STM meetings to one hour, and having multiple slots in the week which would be empty to start. Anyone can become a champion of a meeting, reserve a slot, and ensure experts are present. |
| * https://www.discourse.org/ (forum) | ||
| * https://about.gitlab.com/ (project management) | ||
| * https://huly.app (project management) | ||
| * https://openfoodnetwork.org/software-platform/ (supply chains - food) |
There was a problem hiding this comment.
Suggested change
| * https://openfoodnetwork.org/software-platform/ (supply chains - food) | |
| * https://openfoodnetwork.org/software-platform/ (supply chains — food) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.