owl

Ease of installation/use is the most important factor here - not performance. Small is OK as large datasets are not expected. I'd also recommend sesame , its lightweight, pretty easy to install, and provides good performance for small datasets. Query performance is far better with Sesame 1.2.x than Sesame 2.x because of the addition of context support to the 2.x series. I've tested sesame installation/deployment with tomcat, resin, and jetty, and it worked easily with all of them. I don't recommend the bindings to RDBMS components such as Postgres or MySQL, at least in the 1.x series,

It could be something as big as Jena or something smaller. Do you know anything? dajobe Most people use rdflib , but that focuses on RDF, not OWL. What looks to be the only current and active open source package: FuXi 1.0: A Python-based, bi-directional logical reasoning system for the semantic web This is a Java package but it has a Python console (via Jython): Protégé Script Console A commercial package that has python support: Python Sesame API Tutorial for AllegroGraph 4.2 Some packages that are admittedly incomplete: OWL SugarView Some older packages that appear inactive: OWL Logic Closed

When writing an ontology, there are several very commonly used types, including: DatatypeProperty ObjectProperty FunctionalProperty InverseFunctionalProperty The first three kinda look like they'd be used in a particular set of ways, but I find my idea of them being challenged by how I've seen them used in FOAF. When should each of them be used or not be used? Joshua Taylor The first two of these, DatatypeProperty and ObjectProperty, describe what kind of values a triple with the property should have. Datatype properties relate individuals to literal data (e.g., strings, numbers, datetypes,

I have a class Rates1.0 that is a sub class of the class the has a value 1.0f for the predicate ratesBy as the following: <!-- http://semanticrecommender.com/rs#Rates1.0 --> <owl:Class rdf:about="http://semanticrecommender.com/rs#Rates1.0"> <rdfs:subClassOf rdf:resource="http://semanticrecommender.com/rs#Rates"/> <rdfs:subClassOf> <owl:Restriction> <owl:onProperty rdf:resource="http://semanticrecommender.com/rs#ratesBy"/> <owl:hasValue rdf:datatype="http://www.w3.org/2001/XMLSchema#float">1.0</owl:hasValue> </owl:Restriction> </rdfs:subClassOf> </owl:Class> the predicate ratesBy is both data

I would like to define the range of a data type property as an exhaustive enumeration of strings, in a way that an individual could have as value of this property only one of the strings in the enumeration. For example, a data type property called "color", which can assume only 3 values: "Red", "Green" and "Blue". I'm using OWL 2, and Protégé 5.0. Is there an easy way of doind that using Protégé? I don't seem to be able to find an exact duplicate question, though I think that this may have been asked before. In Protege, you can use a datatype expression to represent an enumeration of literals.

It's almost a year since Unable to download Pellet plugin for Protege 4.3 suggested that it's not available for this version. Has anything changed? It should be possible to download it from their github and just drop it into Progégé's plugins folder: https://github.com/Complexible/pellet/raw/master/protege/plugin/com.clarkparsia.protege.plugin.pellet.jar 来源： https://stackoverflow.com/questions/35663220/how-to-enable-pellet-in-protege-4-3-0

I'm using Jena and Sparql to query the ontology file. I have class Tag with two subclasses : C++ and Java. class Subject with several subclasses, which stand for particular University subjects: "C++ programming","System programming", "Java programming" etc. ObjectProperty "hasTags" domain:Subject range:Tag. Each class subject has some tag like "Java", "C++" When executing query SELECT ?subject WHERE { ?subject owl:equivalentClass ?restriction . ?restriction owl:onProperty ont:hasTags . ?restriction ?restrictType ont:Java } which stands for receiving all subjects with tag "Java" I succeed. So,