Re: report of the October meeting

Hi Melvin,

> I've been using rdflib.js for the last 2 years, and im very happy with it, in terms of functionality and performance.

Just as a test case, I've briefly set up a performance test:
https://github.com/RubenVerborgh/JavaScript-Turtle-Parser-Performance
This repository contains the performance test I already use for the N3.js parser,
plus an adapted version for rdflib.js.
(I have not translated the specification test, but can do so on request.)

Here are the results for my machine (please verify on your own):
– N3.js parses 999,999 DBpedia triples in 4,091ms, or 244,438 triples per second with 65MB RAM.
– rdflib.js parses 999,999 DBpedia triples in 37,481ms, or 26,680 triples per second with 323MB RAM.

So N3.js parses roughly a quarter of a million triples per second; rdflib.js only a tenth of that.

This is not a quality judgement in any way.
On the contrary, it reinforces my prior belief: we should work together.
I don't have the time nor ambition to work on a complete RDF/JS library,
but I do have the expertise to build high-performance parsers and other components.
Others will also have expertise in specific domains and will want to share that.

So this is why I strongly believe we need a shared spec,
which will allow us to write libraries that are compatible with each other
instead of the competition we see now, which hurts the ecosystem.
RDF/JS developers, let's unite, and let the Representation Task Force
be a starting point to combat the current fragmentation.

Best,

Ruben

Received on Thursday, 5 November 2015 09:52:54 UTC