incubator-stanbol-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alessandro Adamou <>
Subject Re: Identifiers of graphs within spaces
Date Thu, 22 Dec 2011 17:18:40 GMT
Dear Steve,

On 12/19/11 6:22 PM, Stephen Bayliss wrote:
> Our use-case is thus:
> 1) Create OntologyContentInputSource(stream)

Perhaps you're better off with a GraphContentInputSource(InpuStream), so 
it won't have to go through the burden of converting from OWLOntology to 
Graph just in order to store it (everything is stored as Clerezza graphs 
anyhow). Note that OWLOntology exports of scopes, spaces and ontologies 
within is possible regardless of the input source (although it is THE 
bottleneck of the current implementation, see my comment to STANBOL-433).

I'm now adding the possibility to specify the TcProvider in the 
GraphContentInputSource constructor. This should also save the burden of 
copying the triples from the in-memory SimpleGraph to the Graph stored 
in the TcManager (IF you pass the TcManager singleton as TcProvider).

>     - as our content is behind authentication, the stream is provided by an
> HTTP client
>     - the content has an identifier (URI) assigned by the external system
> (independent of the contents of the stream/ontology)
> 2) Load OntologyInputSource into the space with
> CustomOntologySpace.addOntology(...)
> 3) When updated content comes along:
>     - remove the original (from the store as well as the space)
>     - add the updated content
> As the OntologyInputSource was created from a stream, it doesn't have a
> physical IRI (I think?),


> so at (2) we don't have a "KReS identifier" for it
> - so if we want to replace the ontology in the future with an updated
> version I can't see currently an easy way of determining which ontology to
> remove from the space and then delete it prior to adding the updated
> content.

if the ontology is named (i.e. it does have  logical IRI even if not a 
physical one), you could simply call 
OntologyProvider#getKey(logicalIRI), but if you would like something 
simpler... see my next comment below.

> I can list the graph keys through the OntologyProvider; but I think what I
> need is to know (or be able to set?) the key when adding it?

Would it be enough if this key were the return value of addOntology() ?

> Also I can see that if I get the TcProvider I can do a
> .deleteTripleCollection(UriRef ref) - how would this UriRef link in with the
> above (when I look at the identifiers of the ontologies retrieved using the
> the keys from listGraphs, these are "Anonymous-xyz" and don't have an IRI).

I'll have to look into this one, fortunately I've still got some time on it.

All the best,


M.Sc. Alessandro Adamou

Alma Mater Studiorum - Università di Bologna
Department of Computer Science
Mura Anteo Zamboni 7, 40127 Bologna - Italy

Semantic Technology Laboratory (STLab)
Institute for Cognitive Science and Technology (ISTC)
National Research Council (CNR)
Via Nomentana 56, 00161 Rome - Italy

"As for the charges against me, I am unconcerned. I am beyond their timid, lying morality,
and so I am beyond caring."
(Col. Walter E. Kurtz)

View raw message