Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

multiple sources of truth and cross validation #7

Closed
elf-pavlik opened this issue Aug 23, 2015 · 6 comments
Closed

multiple sources of truth and cross validation #7

elf-pavlik opened this issue Aug 23, 2015 · 6 comments

Comments

@elf-pavlik
Copy link
Member

Following up on: valueflows/exchange#2
How holodex relationships get stored, where each Agent publishes to its autonomous data space? https://github.com/holodex/enspiral-data/blob/master/relationships.csv

In such case, for each relation between two Agents, we will always have at least two web resources which describe this relation, each from one of the agents perspective. Similar to my comment w3c/activitystreams#180 (comment)

In hackers4peace/plp-docs#12 (comment) I see you use symetric property to link both.

Once again, http://opencreds.org/ seem to me very promising here...

@ahdinosaur
Copy link
Member

great design requirement to bring up.

the approach i have in mind for this is to architect the system where each Agent has their own autonomous data space, where related objects are linked together via URLs.

i'd rather the data provenance, signing, verification, encryption, and decryption be a data layer below the app layer, instead of having to handle that here; for this i'm keen to use ssb.

@elf-pavlik
Copy link
Member Author

Do you hang out with @dominictarr there in far south? 😄

When it comes to signaures, Linked Data Signatures seem very attractive to me. Since one signs the meaning of he message and not particular serializaion. So for example if you use JSON-LD, all the formating including white spaces etc. doesn't matter, before signing it goes through graph normalization currently worked on as part of W3C hosted http://opencreds.org/ (see videos after scrolling down)

If we settle at least on common data model, than one can do messagin on top of HTTP, XMPP, PSYC etc. I still find it important that no matter how systems exchange messages, the actual payload can stay the same!

@dominictarr
Copy link

heeey. btw back in NZ. will be down your ways in sept!

@elf-pavlik
Copy link
Member Author

@dominictarr @ahdinosaur how in Secure Scuttlebutt you manage such cases? I guess you just sign everything and verify things by checking signatures. Can we take case of membership in a secret group with a group wall (message board), chat room and calendar?

Can you point me to information on how you manage such membership in secret groups and access control levels (eg. member, admin, moderator etc.)? I need to check new features of github organizations and teams but we could see how to replicate exact that in distributed scenario, including secret organizations and secret teams.

Currently I start implementing Web Access Control also used in SoLiD draft, which BTW should get more push thanks to http://crosscloud.org/jobs/

ping @jnny @fractastical

@dominictarr
Copy link

@elf-pavlik hey yes in ssb every post is signed. it naturally works well with subjective data. for example, my name for you overwrites your name for yourself. But to get that i must explicitly name you.

We do not have groups implemented yet, though we are thinking about how to do it. I'm fairly sure it will work as a data structure on top of the ssb feeds, but we have just had many smaller bridges to cross to get to this one.

@almereyda
Copy link
Member

We have moved the ValueFlows organization from GitHub to https://lab.allmende.io/valueflows.

This issue has been closed here, and all further discussion on this issue can be done at

https://lab.allmende.io/valueflows/agent/-/issues/7.

If you have not done so, you are very welcome to register at https://lab.allmende.io and join the ValueFlows organization there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants