rdflib.js VS solid

Another possibly useful resource is https://docs.inrupt.com/developer-tools/javascript/client-libraries/, detailing the various JS tools Inrupt provides. Was thinking this could be useful to share, along with https://github.com/linkeddata/rdflib.js/, which is a powerful tool for working with Linked Data in JavaScript.

There's also rdflib.js (https://github.com/linkeddata/rdflib.js/) if you want another approach to handling linked data.

> Talking about RDF is absolutely meaningless without talking about Serialisation (and that includes ...URGH.. XML serialisation), XML Schema data-types, localisations, skolemisation, and the ongoing blank-node war.

Don't implement XML serialization. The simplest and most widely used serialization is n-quads (https://www.w3.org/TR/n-quads/). 10 pages, again with exaples, toc, and lots of non-normative content.

You don't need to handle every data type, and you can't even if you wanted to because data types are also not a fixed set. And whatever you need to know about skolemisation, localization, and blank-nodes is in the standards AFAIK.

> C'mon, rdflib is a joke. It has a ridiculous 200 issues / 1 commit a month ratio, buggy as hell, and is for all intents and purposes abandonware.

It works, not all functionality works perfectly but like I said I have used it and it worked just fine.

> rdflib.js is in memory only, so nothing you could use in production for anything beyond simple stuff. Also there's essentially ZERO documentation.

For processing RDF in browser it works pretty well, not sure what you expect but to me RDF support does not imply it should be a fully fledged tripple-store with disk backing. Also not really zero documentation: https://github.com/linkeddata/rdflib.js/#documentation

> > What are the alternatives?

> SIMPLICITY!

> But the great thing about it is that there could be dozens of equally simple systems and standards, and we could actually see which approaches are best, from usage.

Okay, so you roll your own that fits your use case. Not much use to me and it is not a standard. Lets talk again when you standardize it. Otherwise do you mind giving an alternative that I can actually take off the shelf to at least the extent that I can with RDF?

I am not going to roll my own standard, and if all the RDF data sets instead used their own standards instead of RDF it won't really improve anything.

This doesn't support the various consumer cloud storage APIs, but you've just reminded me of a project I ran into years ago that seems to still be around: https://remotestorage.io/

There's also Solid which attempts to do something similar: https://solidproject.org/

It is surprising to me this is not talked about more. I see little to none online news, podcasts, YouTube videos or anything else where this is discussed. I only found out about it because of research I did on Tim Berners-Lee in preparation for a Career Day talk at my kids middle school. Otherwise I would have probably not known about it still today. And even after I found out and started watching YouTube videos on the topic, YouTube won't even suggest any related videos about it even after already watching multiple videos on the subject (Web 3.0, Solid Project, Decentralized Web...etc).. is Big Tech trying to keep the web from evolving into what Sir Tim Berners-Lee is proposing?

It's only an unreasonable amount of work if you assume that the user is managing a separate storage backend for each library. If you take the Tim Berners-Lee approach (re: https://solidproject.org/) then each user is only managing one storage backend: the one that stores their data. The marginal cost of hooking in one more library low.

We just have to get a little more fed up with all of these services and then the initial cost of setting it up in the first place will be worth it. Any day now...

Solid is a web native protocol to enable interoperable, read-write, collaborative, and decentralized web, truer to web's original vision.

Manas project(https://github.com/manomayam/manas/tree/main) aims to create a modular framework and ecosystem to create correct, robust storage servers adhering to Solid protocol in rust.

[Solid](https://solidproject.org/) is a web native protocol to enable interoperable, read-write, collaborative, and decentralized web, truer to web's original vision.

    Solid adds to existing Web standards to realise a space where individuals can maintain their autonomy, control their data and privacy, and choose applications and services to fulfil their needs.

You're describing Solid, not the Semantic Web. Granted, Solid uses Semantic technologies to achieve it. https://solidproject.org/

Tim Berners-Lee's Solid project is working on that. Put data in "pods" that are stored on pod servers, which are federated. You can self-host.

It could be a federated layer of identity & personal content decoupled from social platforms.

https://solidproject.org/

Check out https://solidproject.org (If you want a short intro I recently gave a ~30min talk about it: https://noeldemartin.com/fosdem)