Hi Reto, one way to do it is: 1. Create a Scope within Ontonet using the foaf ontology, for ex:
curl -v -L -X PUT http://dev.iks-project.eu:8081/ontonet/ontology/People?coreont=http://xmlns.com/foaf/spec/index.rdf (HTTP/1.1 201 Created) 2. when you call the reasoner, refer to the scope, ex: curl " http://dev.iks-project.eu:8081/reasoners/rdfs/classify?scope=People&url=http://dig.csail.mit.edu/2008/webdav/timbl/foaf.rdf<http://dev.iks-project.eu:8081/reasoners/rdfs/classify?scope=User&url=http://dig.csail.mit.edu/2008/webdav/timbl/foaf.rdf>" -H "Accept: text/turtle" The idea is that you keep all the t-box(es) in ontonet and refer to it from the reasoners when sending the a-box. Try and let me know if this is what you are looking for. Bests, Enrico On 26 May 2013 12:46, Sebastian Hellmann <[email protected]> wrote: > Well your choices are limited: > > 1. Either the data contains the axioms already (mix like in OWL test cases) > 2. Data contains "owl:imports" > 3. You add the links to the ontologies via the http parameters (there is no > reason, why this shouldn't work as an array except "not implemented yet") > 4. Download the most common ontologies (FOAF, etc. ) and use them per > default within the component or provide a mechanism to download and cache > them on demand, e.g. by: > "curl http://xmlns.com/foaf/0.1/knows"; > > Other than that I wouldn't know how your reasoning component would get the > necessary knowledge to draw conclusions. > (Note that I am a complete Stanbol newbie, but this is how all other > frameworks I know work) > > -- Sebastian > > > Am 26.05.2013 13:32, schrieb Reto Bachmann-Gmür: >> >> Hi Sebastian >> >> Thanks for your mail. The parameter array proposal seemed promising but >> unfortunately it doesn't work. The second url-parameter is simply ignored. >> >> My example shouldn't be about inference in general but on how stanbol >> components can be used to do something useful with cms data or with data out >> there on the web. So crafted example documents unrealistically mixing >> instance data with t-box ontology or w3c test cases are not an option. >> >> A couple of curl commands showing something that goes into the direction >> of the example describen in "Knowledge within content" on >> https://stanbol.apache.org/docs/trunk/components/ontologymanager/ would be >> fine as well. >> >> Cheers, >> Reto >> >> >> On Sun, May 26, 2013 at 11:35 AM, Sebastian Hellmann >> <[email protected] >> <mailto:[email protected]>> wrote: >> >> Hi Reto, >> you can use the OWL test cases: >> http://www.w3.org/TR/owl-test/ >> (I am not sure, whether RDFS has the same... ) >> They have nice minimal examples: >> http://www.w3.org/2002/03owlt/TransitiveProperty/ >> >> e.g http://www.w3.org/2002/03owlt/TransitiveProperty/premises001.rdf >> concludes: >> http://www.w3.org/2002/03owlt/TransitiveProperty/conclusions001.rdf >> >> Actually for your webservice you should be able to add the schema >> as well, maybe via a parameter array: >> >> http://localhost:8080/reasoners/rdfs/classify?url=http://dig.csail.mit.edu/2008/webdav/timbl/foaf.rdf&uri=http://xmlns.com/foaf/spec/index.rdf >> >> >> Normal, the data doesn't have an owl:imports statement, so you can >> not assume that this is given. >> All the best, >> Sebastian >> >> Am 26.05.2013 11:10, schrieb Reto Bachmann-Gmür: >> >> Hello, >> >> I'm trying to create a simple demo for OntologyManager and/or >> Reasoner. >> >> I thought that it might be nice to show how by rdfs entailment >> on the >> rdfs:range of the foaf:knows properties we could add missing >> rdf:type >> statements to http://dig.csail.mit.edu/2008/webdav/timbl/foaf.rdf >> >> Just getting >> >> http://localhost:8080/reasoners/rdfs/classify?url=http://dig.csail.mit.edu/2008/webdav/timbl/foaf.rdfdoesn't >> >> < http://localhost:8080/reasoners/rdfs/classify?url=http://dig.csail.mit.edu/2008/webdav/timbl/foaf.rdfdoesn%27t > >> >> >> >> add these statements. Probably because it doesn't know about the >> rdfs:range of foaf:knows. >> >> Is there an easy way to do this? >> >> I would also be open to other's suggestion on how to show >> ontologynetwork >> and/or reasoner features with a couple of curl invocations or >> lines of js >> code. Unfortunately for now the only thing I've found our >> Adrian Gschwend's >> IKS Evaluation which basically shows how to use the >> ontologynetwork as a >> cache/proxy for ontology. This seems to be quite little with >> respect to >> what these components should be able to do. >> >> Cheers, >> Reto >> >> >> >> -- Dipl. Inf. Sebastian Hellmann >> Department of Computer Science, University of Leipzig >> Events: NLP & DBpedia 2013 (http://nlp-dbpedia2013.blogs.aksw.org, >> >> Deadline: *July 8th*) >> Venha para a Alemanha como PhD: >> http://bis.informatik.uni-leipzig.de/csf >> Projects: http://nlp2rdf.org , http://linguistics.okfn.org , >> http://dbpedia.org/Wiktionary , http://dbpedia.org >> Homepage: http://bis.informatik.uni-leipzig.de/SebastianHellmann >> Research Group: http://aksw.org >> >> > > > -- > Dipl. Inf. Sebastian Hellmann > Department of Computer Science, University of Leipzig > Events: NLP & DBpedia 2013 (http://nlp-dbpedia2013.blogs.aksw.org, Deadline: > *July 8th*) > Venha para a Alemanha como PhD: http://bis.informatik.uni-leipzig.de/csf > > Projects: http://nlp2rdf.org , http://linguistics.okfn.org , > http://dbpedia.org/Wiktionary , http://dbpedia.org > Homepage: http://bis.informatik.uni-leipzig.de/SebastianHellmann > Research Group: http://aksw.org -- Enrico Daga -- http://www.enridaga.net skype: enri-pan
