ontology

Fuseki SPARQL INSERT produces the “Error 400: SPARQL Query: No 'query=' parameter”

谁说我不能喝 提交于 2019-11-27 08:12:58
问题 I try to insert an individual into my ontology, but get the error: Error 400: SPARQL Query: No 'query=' parameter Fuseki - version 2.4.1 (Build date: 2016-11-04T18:59:20+0000) This is my SPARQL INSERT query #1: PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> PREFIX owl: <http://www.w3.org/2002/07/owl#> PREFIX xsd: <http://www.w3.org/2001/XMLSchema#> PREFIX oo: <http://www.test.com/test-ontology.owl#> INSERT { oo:cap_123 rdf:type oo:MyTours . oo:cap_123 oo:active true . oo:cap_123 oo

path between two resources

别来无恙 提交于 2019-11-27 07:06:53
问题 Is it possible to count the number of the edges that connect two instance with a SPARQL query? I want to find a path. 回答1: You count the number of edges in a unique path using SPARQL's property paths and aggregate functions. For instance, with data like this, which contains two paths that we care about ( a to c with two edges, and d to g with three edges): @prefix : <https://stackoverflow.com/questions/19587520/sparql-path-between-two-instance/> . :a :p :b . # a to c is a path of length 2 :b

Representing if-then sentence using OWL?

我们两清 提交于 2019-11-27 05:45:55
问题 I am working with basic OWL, and it's quite easy to represent some simple sentence like "Songoku is a lecturer, he teaches Maths". E.g.: <owl:Class rdf:ID="Lecturer"></owl:Class> <owl:Class rdf:ID="Subject"></owl:Class> <owl:Property rdf:ID="teach"> <rdfs:domain rdf:resource="#Lecturer"/> <rdfs:range rdf:resource="#Subject"/> </owl:Property> <Subject rdf:ID="Maths"></Subject> <Lecturer rdf:ID="Songoku"> <teach> <Subject rdf:about="#Maths"></Subject> </teach> </Lecturer> But I faced a problem

Adding statements of knowledge to an OWL Ontology in Protege)

点点圈 提交于 2019-11-26 23:17:31
问题 In my Ontology I have three classes, Player , Team , and Competition . I also have the two object properties, employs , and competesIn . The domain of employs is Team , and the range Player , the domain of competesIn is Team or Player and the range Competition . I want the Ontology to infer that if a Player is employed by a Team and that Team competes in a Competition then the Player also competes in that Competition . Is there any way to add this information to an Ontology without putting in

Ontology property definition in Protégé-OWL / SWRL

China☆狼群 提交于 2019-11-26 23:09:21
I need to implement an OWL-ontology in Protégé, which contains a two classes: s1 and s2 , both are the instances of System class. These two classes are connected by the connection class s1_s2 , which contains property omega . This property has to take a value according to the following law: omega = 1 * s1.complete How can I implement it in Protégé, such way I could use it in SWRL-rule in the future? In general, you'd start by defining the classes and the properties that you need: At this point you could add some axioms that govern how the systems have to interact, how the properties work, etc.

How to infer isBrotherOf property between two individuals

雨燕双飞 提交于 2019-11-26 17:47:36
问题 I need to infer that one individual is the brother of other one if they have the same father. So, if I have this: Bart hasFather Homer. Lisa hasFather Homer. Because Bart and Lisa have the same father, I would like to infer: Lisa hasBrother Bart. Is there any method to do that using any property characteristics? 回答1: Use Property Chains and Rolification Antoine Zimmermann's answer is a very good start to this problem, and touches on the major point that you need to solve this sort of task:

Ontology property definition in Protégé-OWL / SWRL

喜欢而已 提交于 2019-11-26 09:13:06
问题 I need to implement an OWL-ontology in Protégé, which contains a two classes: s1 and s2 , both are the instances of System class. These two classes are connected by the connection class s1_s2 , which contains property omega . This property has to take a value according to the following law: omega = 1 * s1.complete How can I implement it in Protégé, such way I could use it in SWRL-rule in the future? 回答1: In general, you'd start by defining the classes and the properties that you need: At this