[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gzz] Wrapper mini-API to RDF
From: |
Alatalo Toni |
Subject: |
Re: [Gzz] Wrapper mini-API to RDF |
Date: |
Tue, 18 Mar 2003 23:39:20 +0200 (EET) |
On Tue, 18 Mar 2003, Benja Fallenstein wrote:
> I think that would be exactly backwards: First make your experience with
> the APIs out there, then decide whether you need your own... :-)
i read this so that what follows must not necessarily be made, but:
> If I had to design an RDF API today, I'd offer three kinds of access:
> Object-oriented style, triples lookup style, and fast access.
this sure sounds interesting.
> Object-oriented style: using methods on nodes--
> node.get(rdf.type) --> Node
...
> node.all(rdf.type, -1) --> List of Nodes
> node.set(rdf.type, node2);
> node.add(rdf.type, node2);
something like that we definitely need, and, i'd assume, have already in
use? i don't know the Jena API.
> Here, we're trying to get the idea across that you're accessing *a
> property of a node*, representing the node as an object.
y
> Triples lookup style: using methods on the graph--
hm
> graph.add(node, prop, node2);
ok
> Fast access style: for views, using a special kind of iterator to avoid
isn't there the thing about using impartial/incomplete data? (also due to
delays in a networked implementation?)
> iter.lookup(subj, prop, obj);
.. as the lookup time varies?
or is this stuff handled on a different level?
i haven't read the dtn related stuff mentioned.
> Maybe once the views get to slow, and we identify Jena's interface as
> the bottleneck?
sounds sensible,
OTOH you do know that i don't really know about views nor optimatizations
-- just trying to follow the developments a bit.
> - Benja
~Toni