W3C home > Mailing lists > Public > semantic-web@w3.org > March 2016

Re: rdflib.js 0.5.0 - renames Symbol to NamedNode

From: Niklas Petersen <petersen@cs.uni-bonn.de>
Date: Fri, 18 Mar 2016 14:22:01 +0100
Cc: semantic-web@w3.org
To: Dmitri Zagidulin <dzagidulin@gmail.com>
Message-ID: <56EC00F9.5090007@cs.uni-bonn.de>
Hey,

thanks for sharing. I am considering to use it.

Two questions:

(1) It says: "SPARQL queries (not full SPARQL)"
Could you tell me to what extend the library supports SPARQL (1.1?) and 
if a full compliance has a high priority?

(2) Are there any plans to support JSON transformations?


Best regards,
Niklas


On 03/03/2016 09:30 PM, Dmitri Zagidulin wrote:
> rdflib.js 0.5.0 - renames Symbol to NamedNode
> Hi all,
>
> A quick heads-up to any users ofhttps://github.com/linkeddata/rdflib.js/
> out there.
>
> We've been doing some refactoring and spring cleaning of it lately.
> Version 0.5.0 introduces a couple of changes:
>
> - Renames $rdf.Symbol to $rdf.NamedNode. (The motivation for the renaming
> came about because Symbol is a reserved type in ES6). So, if you've been
> using rdf.Symbol directly, be sure to rename
> it in your code to NamedNode (when upgrading to 0.5.0 and above).
>
> - Also got rid of the jQuery usage internally (it uses its own
> XmlHttpRequest logic, however, so you
> should not see any difference).
>
> Dmitri Zagidulin

-- 
Niklas Petersen
Database Engineer
Enterprise Information Systems @ Fraunhofer IAIS / University of Bonn
+49 2241 14 3458
http://eis.iai.uni-bonn.de/
petersen@cs.uni-bonn.de
Received on Friday, 18 March 2016 13:22:39 UTC

This archive was generated by hypermail 2.3.1 : Friday, 18 March 2016 13:22:47 UTC