semantic web - Why is owl:Restriction reasoning not working in Blazegraph? -

-

with following rdf in blazegraph (taken this answer):

:eats rdf:type owl:objectproperty .  :vegetable rdf:type owl:class ;        rdfs:subclassof owl:thing .  :vegetarian rdf:type owl:class ;         owl:equivalentclass [ rdf:type owl:restriction ;                               owl:onproperty :eats ;                               owl:somevaluesfrom :vegetable                             ] .  :carrot rdf:type :vegetable ,              owl:namedindividual .  :john rdf:type owl:namedindividual , owl:thing ;       :eats :carrot .

the following sparql returning blank:

select ?who  {   ?who :vegetarian .        }

here blazegraph namespace configs (blazegraph running nanosparqlserver command line):

com.bigdata.namespace.kb.spo.com.bigdata.btree.btree.branchingfactor    1024 com.bigdata.relation.container  test-ng-2 com.bigdata.journal.abstractjournal.buffermode  diskrw com.bigdata.journal.abstractjournal.file    bigdata.jnl com.bigdata.journal.abstractjournal.initialextent   209715200 com.bigdata.rdf.store.abstracttriplestore.vocabularyclass   com.bigdata.rdf.vocab.defaultbigdatavocabulary com.bigdata.rdf.store.abstracttriplestore.textindex false com.bigdata.btree.btree.branchingfactor 128 com.bigdata.namespace.kb.lex.com.bigdata.btree.btree.branchingfactor    400 com.bigdata.rdf.store.abstracttriplestore.axiomsclass   com.bigdata.rdf.axioms.owlaxioms com.bigdata.service.abstracttransactionservice.minreleaseage    1 com.bigdata.rdf.sail.truthmaintenance   true com.bigdata.journal.abstractjournal.maximumextent   209715200 com.bigdata.rdf.sail.namespace  test-ng-2 com.bigdata.relation.class  com.bigdata.rdf.store.localtriplestore com.bigdata.rdf.store.abstracttriplestore.quads false com.bigdata.relation.namespace  test-ng-2 com.bigdata.btree.writeretentionqueue.capacity  4000 com.bigdata.rdf.store.abstracttriplestore.statementidentifiers  true

what missing?

there rdf syntax issues, underlying reason blazegraph not support owl reasoning out of box. see current support. there has been work towards , elk reasoner.

regarding rdf in example, here's update validated load in blazegraph 1.5.1. incorporates feedbackup above , adds namespaces. created properties (test.properties) file properties above , loaded blazegraph executable jar sourceforge.

java -xmx2g -dbigdata.propertyfile=test.properties -jar bigdata-bundled.jar

go workbench: http://localhost:9999/bigdata/ , paste rdf below "update" tab on workbench selecting "rdf data" format "turtle". 

@prefix : <http://stackoverflow.com/> . @prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> . @prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> . @prefix owl: <http://www.w3.org/2002/07/owl#> .  :eats rdf:type owl:objectproperty .  :vegetable rdf:type owl:class ;    rdfs:subclassof owl:thing .  :vegetarian rdf:type owl:class ;    owl:equivalentclass [ rdf:type owl:restriction ;                           owl:onproperty :eats ;                           owl:somevaluesfrom :vegetable                         ] .  :carrot rdf:type :vegetable ,          owl:namedindividual .  :carrot rdf:type owl:namedindividual , owl:thing, :carrot .  :john rdf:type owl:namedindividual , owl:thing ;           :eats :carrot .

if go query tab , run like:

select * { ?s ?p ?o }

you'll see of triples inferred owlaxiomsvocabulary.


Comments

Post a Comment

Popular posts from this blog

java - Custom OutputStreamAppender not run: LOGBACK: No context given for <MYAPPENDER> -

-
i wish write custom appender on basis of outputstreamappender . wrote following class package tests; import java.io.ioexception; import java.io.outputstream; import ch.qos.logback.core.outputstreamappender; public class myappender<e> extends outputstreamappender<e> { public myappender() { system.out.println("myappender created"); setoutputstream(new outputstream() { @override public void write(int b) throws ioexception { throw new unsupportedoperationexception(); } }); } } then wrote following runner: package tests; import org.slf4j.loggerfactory; import ch.qos.logback.classic.logger; public class runner { private static final logger log = (logger) loggerfactory.getlogger(runner.class); public static void main(string[] args) { //log.addappender(new myappender<iloggingevent>()); log.info("hello world"); } } finall...
Read more

java - UML - How would you draw a try catch in a sequence diagram? -

-
Image
is there standard way of drawing try catch sequence diagrams? i've made attempt based on this feel end result doesn't feel right. code diagram based around: public static void save () { try { filehandle filehandle = gdx.files.external(file); filehandle.writestring(boolean.tostring(constantshandler.soundenabled)+"\n", false); (int = 0; < 5; i++) { filehandle.writestring(integer.tostring(constantshandler.highscores[i])+"\n", true); } } catch (throwable e) { } } my attempt note: know still need add loop. that's ok. fragments meant show conditional control flow in sequence diagram. superstructures puts limitations on use of fragments (see pp. 467 of ss2.1.1). should use critical region try part above. , option catch . however, keep telling can take quite freedom in using uml. it's language , such changes in life time. long reader ge...
Read more

c++ - No viable overloaded operator for references a map -

-
i trying use map can make tag names reference number. when try , use it, in code error (6 in total every time reference map): src/main.cpp:25:45: error: no viable overloaded operator[] type 'std::map<std::string, std::string>' const char* idcs = node.child_value(tagmap[3]); this code: #include "pugi/pugixml.hpp" #include <iostream> #include <string> #include <map> int main() { pugi::xml_document doca, docb; std::map<std::string, pugi::xml_node> mapa, mapb; std::map<std::string, std::string> tagmap {{"1", "data"}, {"2", "entry"}, {"3", "id"}, {"4", "content"}}; if (!doca.load_file("a.xml") || !docb.load_file("b.xml")) { std::cout << "can't find input files"; return 1; } (auto& node: doca.child(tagmap[1]).children(tagmap[2])) { co...
Read more