rdflib.js

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. EDIT: If you compare support for RDF to JSON schema, things are really not that bad.

n engine, their home speakers and Android. They'll make the experience nice enough that your aunt looking for a scone recipe won't want to leave their ecosystem, even if a more free, de-centralized alternative is available. Sure but without some way for smaller players to get access to the same data that the giants have, there's no way to compete. There's a reason Google, FB, LI, et al have spent as much energy as they have siloing their data, cutting off interop, and consolidating their services. Technical or product or user experience superiority means nothing when you don't have the data; a polished, quick search engine means nothing if it has no results to search through.