SOLID's linked data and Blockstack


As SOLID is now pushed by a startup, I think it is good to review it again.

In particular, the linked data part is something that blockstack needs to adapt or communicate:

It is the way developers need to think about how to bring data from different users together.

Are there any blockstack apps using linked data already?


I think for any app developer, something like this is inevitable to create for someting akin to a social media where user interaction is used.

That being said, I don’t see how this needs to become a core part of Blockstack(.js). This is something implemented by the developer, not by the library, and thus should probably be regulated to a tutorial or FAQ.

As for implementing shared app data (as advertised in SOLID), this has been discussed before but without work being done so far on these “cross-app data buckets,” though I know Stealthy has been working on having cross-app reads/writes via multi-app authentication.

On a side note, it could be possible to use a SOLID Pod as a Gaia Storage backend (i.e. use blockstack sign-in for one pod folder, for all blockstack apps).


The typed links is interesting as is the structural relationship to indicate how the comment targets the image.

As @MichaelFedora points out, we’ve done some early work with Graphite and Travelstack to begin the process of sharing data between Apps. Namely a way of describing resources and how to access them. Eventually we hope to extend that for an experience that is like Jabber but with Apps (for example an improbable centralized example might be accessing your Instagram photos directly in a Google Doc ).


We’ve also created some structures and ideas to help users manage the crossing of App cryptographic boundaries for improved inter-operability.


I am heavily researching this. I am curious how I can integrate the rdflib.js with blockstack.js and gaia storage.


Actually json-ld looks more interesting and they have a javascript lib

This looks pretty cool here:

The syntax does not require many applications to change their JSON, but easily add meaning by adding context in a way that is either in-band or out-of-band. The syntax is designed to not disturb already deployed systems running on JSON, but provide a smooth migration path from JSON to JSON with added semantics. Finally, the format is intended to be fast to parse, fast to generate, stream-based and document-based processing compatible, and require a very small memory footprint in order to operate.

Maybe something like this =, the url could be your Gaia bucket url ( not valid code below just an idea )

var doc = {
  "": "", // maybe blockstack has a schema
  "": "SomeBlockstackAppDataScheme" // maybe each app can make a data schema or borrow one from


I just discovered this tool"

<script type="application/ld+json">
 	"@context": "",
 	"@type" : "DigitalDocument",
 	"url": "",
 	"name": "MyFile.pdf"