Hi Adrian
On 9/13/12 1:28 PM, Adrian Gschwend wrote:
at least in my latest trunk version there is absolutely no example on
how to pass the arguments so the CURL examples are not complete IMHO.
You are correct, there are more examples to be added. However you should
see to it that when you update and build Stanbol, the updated bundles
are actually installed. Many users posted here believing they were
updating their installations but they weren't. I'm saying this because
I'm on 1382655 and I cannot find your line
Parameters location: the physical URL of the ontology to be loaded.
even if i try an egrep -r on the whole source dir. Instead I have (for
the ontonet/ontology/{scopeid} POST)
# |file|: the physical URL of the ontology to be loaded.
# |format|: combined with|file|, the format of the submitted file. If not
supplied, all known parsers will be tried until one succeeds or all fail.
# |library|: the identifier of the ontology library whose ontologies have
to be loaded. The available libraries are shown on the /ontonet/registry
endpoint.
# |stored|: the public key of the ontology to be loaded, if already stored
in Stanbol.
# |url|: the physical URL of the ontology to be loaded.
(there is a mistake for the "file" parameter, I will correct it)
Even better, a good reasoner will infer that :Adrian and :Alessandro are
foaf:Person s
ok great, I start to see the idea and will definitely play more with
that. But I'm not really far in reasoning yet, didn't do much more than
some simple rules and SPARQL CONSTRUCTS so far.
Ok so don't worry about that right now. As soon as you decide to dig it,
just drop a line here.
Of course you could import FOAF in your ontology as well, but the
problem is that not many people think about doing that, especially in
Linked Data.
you mean make something a subproperty of a FOAF property for example if
I get you correctly? That is indeed rarely done currently.
Actually I meant something a little more brutal i.e. having an
owl:imports [foaf-url] statement in the ontology, which usually results
in computing all axioms from the imported ontology, e.g.
foaf:knows a owl:ObjectProperty ;
rdfs:domain foaf:Person ;
rdfs:range foaf:Person .
But your example also makes sense. If you add a subproperty axiom to
your schema, but then the ontology containing the data does not import
the schema, you will not be able to infer the superproperty.
Also the same question to you: If I figure out stuff I prefer to
document it somewhere so others don't have to do the same learnings
again. Is there a place where I could try doing that @ stanbol?
Otherwise I will simply start doing it for myself.
Welcome onboard! The place to do so is our issue tracker
https://issues.apache.org/jira/browse/STANBOL
Anyone who signs in can open tickets and post code patches as
attachments to tickets. Patches are also possible for the Stanbol
documentation website which can be checked out from
http://svn.apache.org/repos/asf/incubator/stanbol/site/trunk/content/stanbol/
ok is there a way to drop them right now manually? For testing this is a
bit annoying :-D
I know, it is for me too. Right now you can either build and install the
ontology store from contrib/store.
Or I think there should be some Clerezza REST bundle that you can
install too
Otherwise programmatically via Java, stuff like
tcManager.deleteTripleCollection(graphName);
Note that using these methods, the Stanbol ontology manager will still
believe that the ontologies are there. You have to wait for it to have
its own DELETE implementation.
Best,
Alessandro
--
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
"I will give you everything, just don't demand anything."
(Ettore Petrolini, 1917)
Not sent from my iSnobTechDevice
