teachcode VS rdflib.js

teachcode

We haven't tracked posts mentioning teachcode yet.
Tracking mentions began in Dec 2020.

rdflib.js

• Local First Tuple Database
  2 projects | news.ycombinator.com | 14 Aug 2022
• Useful resources for Solid
  7 projects | /r/SOLID | 29 Sep 2021

  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.

• Recording of Solid World February 2021
  1 project | /r/SOLID | 9 Feb 2021

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

• A Review of the Semantic Web Field
  3 projects | news.ycombinator.com | 26 Jan 2021

  > 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.