semantic-web

OWL Property Restrictions vs. SHACL

北慕城南 提交于 2019-12-04 06:49:47
Given a choice between OWL Property Restrictions and SHACL , is there any reason to choose the OWL approach any more? Particularly with respect to cardinality constraints, I'm wondering whether SHACL is considered to supercede OWL. The syntax appears similar, to my casual inspection. I am probably missing the purpose of OWL cardinality constraints. As part of an ontology, they should facilitate inferencing (a separate concern from validation). But how do cardinality constraints facilitate inferencing? The differences between OWL and SHACL are presented in the table below. | OWL | SHACL | |----

Measuring distances among classes in RDF/OWL graphs

被刻印的时光 ゝ 提交于 2019-12-04 06:47:05
Maybe someone could give me a hint. Is it possible to measure the distance between 2 concepts/classes that belong to the same ontology? For example, let's suppose I have an ontology with the Astronomy class and the Telescope class. There is a link between both, but it is not a direct link. Astronomy has a parent class called Science, and Telescope has a parent class called Optical Instrument which belongs to its parent called Instrumentation, that is related to a class called Empirical Science that finally belongs to a class called Science. So there is an indirect link between Telescope and

RESTful Web Service usage of custom link relations - 'rel'

狂风中的少年 提交于 2019-12-04 06:17:01
I'm working on a RESTful service and have been focusing on Discoverability, Link relations - 'rel' and microformats. I'm not clear about the values of 'rel' in the context of REST - am I allowed to make use of any custom value, to provide richer semantics or should I only use the default values (which are very constraining)? I am aware that microformats have indeed extended the values of 'rel', but I am not using any kind of microformat yet. Any help is appreciated. Thanks. Link Relations (rel) are one of the two ways that you can convey semantics to a client. The other way is media types. The

Sparql query with Blank node can be complex

痞子三分冷 提交于 2019-12-04 06:10:58
I read this blog article, Problems of the RDF model: Blank Nodes , and there's mentioned that using blank nodes can complicate the handling of data. Can you give me an example why using blank nodes is difficult to perform a SPARQL query? I do not understand the complexity of blank nodes. Can you explain me the meaning and semantics of an existential variable? I do not understand clearly this explanation given in the RDF Semantics Recommendation, 1.5. Blank Nodes as Existential Variables . Joshua Taylor Existential Variables In the (first-order) predicate calculus, there is existential

create RDF from XML

独自空忆成欢 提交于 2019-12-04 05:39:41
问题 I have this xml file, how can I create RDF triple from it using xpath and ModelFactory in java? <xml> <person> <name>Joe</name> <website url="www.example1.com">contact1</website > <vote>20</vote> </person> <person> <name>Anna</name> <website url="www.example2.com">contact2</website> <vote>80</vote> </person> </xml> Thanks for help Thanks for replay, I would like to obtain following RDF <rdf:Description rdf:about="http://www.example.com/xml"> <j.0:hasCritic>Joe</j.0:hasCritic> <rdf:Description

how group graph pattern work in SPARQL

生来就可爱ヽ(ⅴ<●) 提交于 2019-12-04 05:04:36
问题 First of all, i don't know if this really called group graph pattern or not. Anyway, Look at this query please select ?x ?y where { {?x rdf:type rs:Recommendable} union {?xd rs:doesntexist ?y} } there is no rs:doesntexist but with union i got the results only from the first sub graph which is {?x rdf:type rs:Recommendable} but if i remove the union, so the query will be: select ?x ?y where { {?x rdf:type rs:Recommendable} {?xd rs:doesntexist ?y} } I get empty results, may I ask you please who

Using the 'GRAPH' keyword in SPARQL to fetch remote graphs

不羁的心 提交于 2019-12-04 04:18:10
I'm looking to use SPARQL for a relatively basic task: Given a FOAF graph, I'd like to parse the elements I find in there, get their tags (if they exist) and then, use those as new graphs from which to find information about those people. So for instance, you could imagine a simple use case where I want to run a SPARQL query to list all of my favorite foods (as per my FOAF file), and also the favorite foods of all my friends. Here is what this looks like at the moment. Note that for testing purposes, at the moment all I'm trying to do with the query below is fetch the name of the friend,

What are the pros and cons of RDB2RDF tools? [closed]

北战南征 提交于 2019-12-04 02:56:09
问题 Closed . This question needs to be more focused. It is not currently accepting answers. Want to improve this question? Update the question so it focuses on one problem only by editing this post. Closed last year . I need to know the difference between RDB2RDF tools. Could anybody tell me what are the pros and cons of RDB2RDF tools? Especially for the following ones: Virtuoso, Ultrawrap, Ontop, Morph, Xsparql, D2RQ,.... 回答1: There are two W3C-standardized ways to convert relational data to RDF

Why some rdf files does not contain <rdf:Description rdf:about=…>?

…衆ロ難τιáo~ 提交于 2019-12-04 02:05:40
问题 I'm using Jena to write a rdf file that describes online posts. According to the sioc ontology/namespace that I'm using there is, for instance, the following: Class: sioc:Post Property: sioc:has_creator How can I, in Jena, include the sioc:Post in the file as <sioc:Post rdf:about="http://example.com/vb/1035092"> instead of <rdf:Description rdf:about="http://example.com/vb/1035092"> and what is the best practice? 回答1: Both of the answers so far make good points: You should not pay much

sparql: randomly select one connection for each node

三世轮回 提交于 2019-12-04 01:54:46
问题 I have the following data: <node:1><urn:connectTo><node:2> <node:1><urn:connectTo><node:3> <node:1><urn:connectTo><node:4> <node:2><urn:connectTo><node:10> <node:2><urn:connectTo><node:11> <node:2><urn:connectTo><node:12> <node:3><urn:connectTo><node:21> <node:3><urn:connectTo><node:13> <node:3><urn:connectTo><node:41> <node:3><urn:connectTo><node:100> <node:4><urn:connectTo><node:119> <node:4><urn:connectTo><node:120> As you can see, every node has multiple connections. I want to select one