Are the high-level concepts clear to everyone?
The SOLID team recently released this resource to help developers to learn the concepts.
One of the core concepts is the ability to share data in a common way so that other users and applications can easily query for it and use it. The common way to define relationships between data points/nodes/resources and the resources themselves will be through RDF.
But what’s the purpose?
RDF technology is very powerful in setting standards on how to publish, classify or report information. Its strongest feature is the ability to share and publish data in an open way.
If you want to expose data so it can be easily consumed by other users, federated across different information systems, or linked by a third party system, it’s a technology without many viable alternatives actually.
Of relevance to one of the goals of SAFE is this study of the application of graph databases to molecular biology (Spoiler alert: RDF was considered more ideal for this particular application. I know, “Confirmation bias”, but I’ve really not wanted to like RDF and I found this article with that mindset.).
The first component that is required to implement RDF is URI’s to define resources and relationships:
Once we have XOR URI’s on the network. We need know how to help developers compose RDF data. What do they need to comply with RDF on SAFE? How do we design the API?
We spoke with an application developer to start the process of learning what we need to provide to make RDF compliance easy. In particular, I’d like to connect with developers from the biological fields where RDF is already in extensive use, to receive their feedback and to find out how we may serve them.
Keep your eyes and ears out.
One advantage SAFE may have is that we may be able to provide the missing incentives for RDF adoption with proper marketing around:
- Well-defined data and therefore highly shareable, searchable, and usable, can potentially earn more money for application developers.
Something along those lines. That may be the incentive that developers need to learn to think and code in Turtle or at minimum to not completely ignore RDF.
I don’t see lack of engagement. There’s been a lot of time and mental effort, not on my part, already in that regard.
What I see is a complex subject that is difficult to convey.
The Gitter chat can be highly academic at times and requires much contextual preparation to ask a useful question. Even when prepared it can be difficult to find answers to very practical questions.
That’s the point of this post then is to start to get everyone else, along with myself, up to speed so that we can engage more.
That was the partially the purpose of our PoC Patter app.
I’m wondering if we need to create our very own tutorial/educational piece on RDF and linked data over at DevHub?