-
Notifications
You must be signed in to change notification settings - Fork 87
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
Semantic Web and IPFS #32
Comments
Thanks @peacekeeper, great exploration! Also, IPFS is hoping to add IPLD to their upcoming 0.4 release: ipld/go-ipld-deprecated#14 (comment) |
/cc @dukedorje @aquabu @fractastical |
See @jbenet's contributions ipfs-keychain.md and ipfs-links.md |
+1 for this |
Index/search capabilities of CRDTs being explored by IPFS. Some links: |
Also related to the https://github.com/ipfs/archives project -- eg Freebase: ipfs-inactive/archives#10 |
I tend to use RDF Dataset Normalization if storing RDF sources in filesystem, also Linked Data Signatures rely on it. The normalized g-text will always have the same checksum for particular g-snap source: https://www.w3.org/2011/rdf-wg/wiki/Graph_Terminology#Visual_Diagram |
/re Trust-Exchange-An-Architecture-for-a-Permanent-Open-Trust-Network.md
/re DecentralizedCooperationNeedsDecentralizedReputation.md
/re Distributed-Trust-Systems-and-the-Kenyesian-Beauty-Contest.md.md
/cc @jbenet
/cc @harlantwood
Several papers here mention IPFS, and a lot of us are using semantic web technologies for representing profiles, relationships, tokens, and other data.
I'd be interested in mapping out how graph models such as RDF or XDI can be stored on top of IPFS' merkle DAG. I know some early thoughts on this topic exist, e.g.:
The text was updated successfully, but these errors were encountered: