-
Notifications
You must be signed in to change notification settings - Fork 8
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
Things in IPLD on IPFS #777
Comments
https://github.com/ipld/cid-cbor/ ? https://openengiadina.codeberg.page/rdf-cbor/ but that's not what one would want... It could be a basis, but we would want a utility which transforms IRIs into, either:
... IFF such are valid in IPLD (TBC), else string if not CID. You would want to canonicalize RDF; we may (at least initially) not need a fully "standards compliant" implementation, just what we already have in Enola (see also #1103). The "IPLD blocks" must include the IRI (as the hash is one way). We COULD postfix IRI with @multibase CID, to "version" them? And have sameAs with & without version. This would help to distinguish different Thing version itérations. Next Steps:
|
|
https://lod-cloud.net/#ipfs (broken image) and https://lod-cloud.net/ipfs-how-to.html is not what this issue is primarily about (it's just RDF in HDT on IPFS), but still worth documenting. |
It may be fun to explore storing Enola's Things on IPFS's IPLD.
This would first require being able to turn an
IImmutableThing
into the IPLD Data Model. That would enable to create predictable hashes of Things, to be generate CIDs. This will require work to turn any Datatype into one or several predictable 0/1 bits format/s (simplest could be e.g. justtoString
, and Maps as JSON with sorted keys?).That would enable e.g. IPLD DAG JSON Codec as an Enola Format.
IPFS IPLD Schemas would need to be an Enola Schema.
Related libraries of possible interest:
The text was updated successfully, but these errors were encountered: