W3C home > Mailing lists > Public > www-rdf-interest@w3.org > July 2003

Re: (trying to) Understand RDF and N3

From: Libby Miller <Libby.Miller@bristol.ac.uk>
Date: Tue, 22 Jul 2003 16:57:00 +0100 (BST)
To: Miguel Branco <miguel.branco@cern.ch>
cc: www-rdf-interest@w3.org
Message-ID: <Pine.GSO.4.44.0307221648340.20601-100000@mail.ilrt.bris.ac.uk>

hi Miguel,


> I have this project I'm working on where it would be very useful to have
> a "standard"/consistent way of expressing and querying information. I
> was thinking of using RDF to publish all info but it seems that there's
> no consistent way of querying it... So I was thinking of using N3

As an aside, we have been looking at querying RDF using Ntriples,
treating blank nodes as variables. This work is in very early stages -
and is really only designed for the implementation testing framework we
are developing, not as a proposal for a query langauge. But I thought
it might be worth mentioning in this context, as the fact that we can
map various query languages (or subsets of them) to what looks to be a
fairly simple model (an RDF graph with holes) indicates that syntactic
differences may not always be relevant. More information is here:


various example QLs

survey of various RDF QLs

> instead (because this allows us to filter information besides being also
> extremely simple to add new facts)  -  kind of like using N3 on top of
> HTTP...  I could add N3 facts to an existing list of facts with a HTTP
> PUT, do a N3 filter with a POST (passing the filter in the body), get
> the whole N3 from a given network node with a GET, delete with a DELETE...

As Leo pointed out, Joseki sounds a lot like what you want.


Received on Tuesday, 22 July 2003 11:58:53 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:07:46 UTC