Logic and Inference: Rules
Total Page:16
File Type:pdf, Size:1020Kb
Load more
Recommended publications
-
Basic Querying with SPARQL
Basic Querying with SPARQL Andrew Weidner Metadata Services Coordinator SPARQL SPARQL SPARQL SPARQL SPARQL Protocol SPARQL SPARQL Protocol And SPARQL SPARQL Protocol And RDF SPARQL SPARQL Protocol And RDF Query SPARQL SPARQL Protocol And RDF Query Language SPARQL SPARQL Protocol And RDF Query Language SPARQL Query SPARQL Query Update SPARQL Query Update - Insert triples SPARQL Query Update - Insert triples - Delete triples SPARQL Query Update - Insert triples - Delete triples - Create graphs SPARQL Query Update - Insert triples - Delete triples - Create graphs - Drop graphs Query RDF Triples Query RDF Triples Triple Store Query RDF Triples Triple Store Data Dump Query RDF Triples Triple Store Data Dump Subject – Predicate – Object Query Subject – Predicate – Object ?s ?p ?o Query Dog HasName Cocoa Subject – Predicate – Object ?s ?p ?o Query Cocoa HasPhoto ------- Subject – Predicate – Object ?s ?p ?o Query HasURL http://bit.ly/1GYVyIX Subject – Predicate – Object ?s ?p ?o Query ?s ?p ?o Query SELECT ?s ?p ?o Query SELECT * ?s ?p ?o Query SELECT * WHERE ?s ?p ?o Query SELECT * WHERE { ?s ?p ?o } Query select * WhErE { ?spiderman ?plays ?oboe } http://deathbattle.wikia.com/wiki/Spider-Man http://www.mmimports.com/wp-content/uploads/2014/04/used-oboe.jpg Query SELECT * WHERE { ?s ?p ?o } Query SELECT * WHERE { ?s ?p ?o } Query SELECT * WHERE { ?s ?p ?o } Query SELECT * WHERE { ?s ?p ?o } LIMIT 10 SELECT * WHERE { ?s ?p ?o } LIMIT 10 http://dbpedia.org/snorql SELECT * WHERE { ?s ?p ?o } LIMIT 10 http://dbpedia.org/snorql SELECT * WHERE { ?s -
Mapping Spatiotemporal Data to RDF: a SPARQL Endpoint for Brussels
International Journal of Geo-Information Article Mapping Spatiotemporal Data to RDF: A SPARQL Endpoint for Brussels Alejandro Vaisman 1, * and Kevin Chentout 2 1 Instituto Tecnológico de Buenos Aires, Buenos Aires 1424, Argentina 2 Sopra Banking Software, Avenue de Tevuren 226, B-1150 Brussels, Belgium * Correspondence: [email protected]; Tel.: +54-11-3457-4864 Received: 20 June 2019; Accepted: 7 August 2019; Published: 10 August 2019 Abstract: This paper describes how a platform for publishing and querying linked open data for the Brussels Capital region in Belgium is built. Data are provided as relational tables or XML documents and are mapped into the RDF data model using R2RML, a standard language that allows defining customized mappings from relational databases to RDF datasets. In this work, data are spatiotemporal in nature; therefore, R2RML must be adapted to allow producing spatiotemporal Linked Open Data.Data generated in this way are used to populate a SPARQL endpoint, where queries are submitted and the result can be displayed on a map. This endpoint is implemented using Strabon, a spatiotemporal RDF triple store built by extending the RDF store Sesame. The first part of the paper describes how R2RML is adapted to allow producing spatial RDF data and to support XML data sources. These techniques are then used to map data about cultural events and public transport in Brussels into RDF. Spatial data are stored in the form of stRDF triples, the format required by Strabon. In addition, the endpoint is enriched with external data obtained from the Linked Open Data Cloud, from sites like DBpedia, Geonames, and LinkedGeoData, to provide context for analysis. -
Validating RDF Data Using Shapes
83 Validating RDF data using Shapes a Jose Emilio Labra Gayo a University of Oviedo, Spain Abstract RDF forms the keystone of the Semantic Web as it enables a simple and powerful knowledge representation graph based data model that can also facilitate integration between heterogeneous sources of information. RDF based applications are usually accompanied with SPARQL stores which enable to efficiently manage and query RDF data. In spite of its well known benefits, the adoption of RDF in practice by web programmers is still lacking and SPARQL stores are usually deployed without proper documentation and quality assurance. However, the producers of RDF data usually know the implicit schema of the data they are generating, but they don't do it traditionally. In the last years, two technologies have been developed to describe and validate RDF content using the term shape: Shape Expressions (ShEx) and Shapes Constraint Language (SHACL). We will present a motivation for their appearance and compare them, as well as some applications and tools that have been developed. Keywords RDF, ShEx, SHACL, Validating, Data quality, Semantic web 1. Introduction In the tutorial we will present an overview of both RDF is a flexible knowledge and describe some challenges and future work [4] representation language based of graphs which has been successfully adopted in semantic web 2. Acknowledgements applications. In this tutorial we will describe two languages that have recently been proposed for This work has been partially funded by the RDF validation: Shape Expressions (ShEx) and Spanish Ministry of Economy, Industry and Shapes Constraint Language (SHACL).ShEx was Competitiveness, project: TIN2017-88877-R proposed as a concise and intuitive language for describing RDF data in 2014 [1]. -
Computational Integrity for Outsourced Execution of SPARQL Queries
Computational integrity for outsourced execution of SPARQL queries Serge Morel Student number: 01407289 Supervisors: Prof. dr. ir. Ruben Verborgh, Dr. ir. Miel Vander Sande Counsellors: Ir. Ruben Taelman, Joachim Van Herwegen Master's dissertation submitted in order to obtain the academic degree of Master of Science in Computer Science Engineering Academic year 2018-2019 Computational integrity for outsourced execution of SPARQL queries Serge Morel Student number: 01407289 Supervisors: Prof. dr. ir. Ruben Verborgh, Dr. ir. Miel Vander Sande Counsellors: Ir. Ruben Taelman, Joachim Van Herwegen Master's dissertation submitted in order to obtain the academic degree of Master of Science in Computer Science Engineering Academic year 2018-2019 iii c Ghent University The author(s) gives (give) permission to make this master dissertation available for consultation and to copy parts of this master dissertation for personal use. In the case of any other use, the copyright terms have to be respected, in particular with regard to the obligation to state expressly the source when quoting results from this master dissertation. August 16, 2019 Acknowledgements The topic of this thesis concerns a rather novel and academic concept. Its research area has incredibly talented people working on a very promising technology. Understanding the core principles behind proof systems proved to be quite difficult, but I am strongly convinced that it is a thing of the future. Just like the often highly-praised artificial intelligence technology, I feel that verifiable computation will become very useful in the future. I would like to thank Joachim Van Herwegen and Ruben Taelman for steering me in the right direction and reviewing my work quickly and intensively. -
Using Rule-Based Reasoning for RDF Validation
Using Rule-Based Reasoning for RDF Validation Dörthe Arndt, Ben De Meester, Anastasia Dimou, Ruben Verborgh, and Erik Mannens Ghent University - imec - IDLab Sint-Pietersnieuwstraat 41, B-9000 Ghent, Belgium [email protected] Abstract. The success of the Semantic Web highly depends on its in- gredients. If we want to fully realize the vision of a machine-readable Web, it is crucial that Linked Data are actually useful for machines con- suming them. On this background it is not surprising that (Linked) Data validation is an ongoing research topic in the community. However, most approaches so far either do not consider reasoning, and thereby miss the chance of detecting implicit constraint violations, or they base them- selves on a combination of dierent formalisms, eg Description Logics combined with SPARQL. In this paper, we propose using Rule-Based Web Logics for RDF validation focusing on the concepts needed to sup- port the most common validation constraints, such as Scoped Negation As Failure (SNAF), and the predicates dened in the Rule Interchange Format (RIF). We prove the feasibility of the approach by providing an implementation in Notation3 Logic. As such, we show that rule logic can cover both validation and reasoning if it is expressive enough. Keywords: N3, RDF Validation, Rule-Based Reasoning 1 Introduction The amount of publicly available Linked Open Data (LOD) sets is constantly growing1, however, the diversity of the data employed in applications is mostly very limited: only a handful of RDF data is used frequently [27]. One of the reasons for this is that the datasets' quality and consistency varies signicantly, ranging from expensively curated to relatively low quality data [33], and thus need to be validated carefully before use. -
Towards Unifying Rules and Policies for Semantic Web Services
Towards Unifying Rules and Policies for Semantic Web Services Nima Kaviani 1, Dragan Gaševi ć1, Marek Hatala 1, David Clement 2, Gerd Wagner 3 1Simon Fraser University Surrey, Canada 2Visiphor Corporation, Canada 3Brandenburg University of Technology at Cottbus, Germany {nkaviani, dgasevic, mhatala}@sfu.ca, [email protected], [email protected] Abstract However, the current proposed standards for describing Semantic Web services (i.e. OWL-S [14], Simplifying the discovery of web services on one hand WSDL-S [1], Web Service Modeling Ontology [7], and protecting them from misuse on the other hand has and Semantic Web Service Language – SWSL [2]) initiated several lines of research in the area of policy- demonstrate that it is important to use a rule language aware semantic web services. However, the diversity of in addition to ontologies. This allows run-time approaches, ontologies and languages chosen for discovery, composition, and orchestration of Semantic defining Semantic Web services and policies has made Web services by defining preconditions or post- the research area cluttered. It is now ambiguous how conditions for all Web service messages exchanged different registries and agents with different policy [13]. For example, OWL-S recommends using OWL languages and Semantic Web service ontologies would ontologies together with different types of rule share their information. In this paper we try to solve languages (SWRL, KIF, or DRS), WSMO uses F- the problem of exchanging information between the Logic, while WSDL-S is fully agnostic about the use of registries by defining an interchange framework to a vocabulary (e.g., UML, ODM, OWL) or rule transform business rules and concepts from one language (e.g., OCL, SWRL, RuleML). -
Introduction Vocabulary an Excerpt of a Dbpedia Dataset
D2K Master Information Integration Université Paris Saclay Practical session (2): SPARQL Sources: http://liris.cnrs.fr/~pchampin/2015/udos/tuto/#id1 https://www.w3.org/TR/2013/REC-sparql11-query-20130321/ Introduction For this practical session, we will use the DBPedia SPARQL access point, and to access it, we will use the Yasgui online client. By default, Yasgui (http://yasgui.org/) is configured to query DBPedia (http://wiki.dbpedia.org/), which is appropriate for our tutorial, but keep in mind that: - Yasgui is not linked to DBpedia, it can be used with any SPARQL access point; - DBPedia is not related to Yasgui, it can be queried with any SPARQL compliant client (in fact any HTTP client that is not very configurable). Vocabulary An excerpt of a dbpedia dataset The vocabulary of DBPedia is very large, but in this tutorial we will only need the IRIs below. foaf:name Propriété Nom d’une personne (entre autre) dbo:birthDate Propriété Date de naissance d’une personne dbo:birthPlace Propriété Lieu de naissance d’une personne dbo:deathDate Propriété Date de décès d’une personne dbo:deathPlace Propriété Lieu de décès d’une personne dbo:country Propriété Pays auquel un lieu appartient dbo:mayor Propriété Maire d’une ville dbr:Digne-les-Bains Instance La ville de Digne les bains dbr:France Instance La France -1- /!\ Warning: IRIs are case-sensitive. Exercises 1. Display the IRIs of all Dignois of origin (people born in Digne-les-Bains) Graph Pattern Answer: PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> PREFIX owl: <http://www.w3.org/2002/07/owl#> PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#> PREFIX foaf: <http://xmlns.com/foaf/0.1/> PREFIX skos: <http://www.w3.org/2004/02/skos/core#> PREFIX dc: <http://purl.org/dc/elements/1.1/> PREFIX dbo: <http://dbpedia.org/ontology/> PREFIX dbr: <http://dbpedia.org/resource/> PREFIX db: <http://dbpedia.org/> SELECT * WHERE { ?p dbo:birthPlace dbr:Digne-les-Bains . -
INPUT CONTRIBUTION Group Name:* MAS WG Title:* Semantic Web Best Practices
Semantic Web best practices INPUT CONTRIBUTION Group Name:* MAS WG Title:* Semantic Web best practices. Semantic Web Guidelines for domain knowledge interoperability to build the Semantic Web of Things Source:* Eurecom, Amelie Gyrard, Christian Bonnet Contact: Amelie Gyrard, [email protected], Christian Bonnet, [email protected] Date:* 2014-04-07 Abstract:* This contribution proposes to describe the semantic web best practices, semantic web tools, and existing domain ontologies for uses cases (smart home and health). Agenda Item:* Tbd Work item(s): MAS Document(s) Study of Existing Abstraction & Semantic Capability Enablement Impacted* Technologies for consideration by oneM2M. Intended purpose of Decision document:* Discussion Information Other <specify> Decision requested or This is an informative paper proposed by the French Eurecom institute as a recommendation:* guideline to MAS contributors on Semantic web best practices, as it was suggested during MAS#9.3 call. Amélie Gyrard is a new member in oneM2M (via ETSI PT1). oneM2M IPR STATEMENT Participation in, or attendance at, any activity of oneM2M, constitutes acceptance of and agreement to be bound by all provisions of IPR policy of the admitting Partner Type 1 and permission that all communications and statements, oral or written, or other information disclosed or presented, and any translation or derivative thereof, may without compensation, and to the extent such participant or attendee may legally and freely grant such copyright rights, be distributed, published, and posted on oneM2M’s web site, in whole or in part, on a non- exclusive basis by oneM2M or oneM2M Partners Type 1 or their licensees or assignees, or as oneM2M SC directs. -
Using Rule-Based Reasoning for RDF Validation
View metadata, citation and similar papers at core.ac.uk brought to you by CORE provided by Ghent University Academic Bibliography Using Rule-Based Reasoning for RDF Validation Dörthe Arndt, Ben De Meester, Anastasia Dimou, Ruben Verborgh, and Erik Mannens Ghent University - imec - IDLab Sint-Pietersnieuwstraat 41, B-9000 Ghent, Belgium [email protected] Abstract. The success of the Semantic Web highly depends on its in- gredients. If we want to fully realize the vision of a machine-readable Web, it is crucial that Linked Data are actually useful for machines con- suming them. On this background it is not surprising that (Linked) Data validation is an ongoing research topic in the community. However, most approaches so far either do not consider reasoning, and thereby miss the chance of detecting implicit constraint violations, or they base them- selves on a combination of dierent formalisms, eg Description Logics combined with SPARQL. In this paper, we propose using Rule-Based Web Logics for RDF validation focusing on the concepts needed to sup- port the most common validation constraints, such as Scoped Negation As Failure (SNAF), and the predicates dened in the Rule Interchange Format (RIF). We prove the feasibility of the approach by providing an implementation in Notation3 Logic. As such, we show that rule logic can cover both validation and reasoning if it is expressive enough. Keywords: N3, RDF Validation, Rule-Based Reasoning 1 Introduction The amount of publicly available Linked Open Data (LOD) sets is constantly growing1, however, the diversity of the data employed in applications is mostly very limited: only a handful of RDF data is used frequently [27]. -
Rule Interchange Format: the Framework
Rule Interchange Format: The Framework Michael Kifer State University of New York at Stony Brook 1 Outline What is Rule Interchange Format (RIF)? RIF Framework Basic Logic Dialect (BLD) 2 What is RIF? A collection of dialects Rule system 1 (rigorously defined rule languages) semantics preserving Intended to facilitate rule mapping sharing and exchange RIF dialect X Dialect consistency Sharing of RIF machinery: semantics preserving XML syntax mapping Presentation syntax Semantics Rule system 2 3 Why Rule Exchange ? (and not The One True Rule Language ) Many different paradigms for rule languages Pure first-order Logic programming/deductive databases Production rules Reactive rules Many different features, syntaxes Different commercial interests Many egos, different preferences, ... 4 Why RIF Dialects ? (and not just one dialect ) Again: many paradigms for rule languages First-order rules Logic programming/deductive databases Reactive rules Production rules Many different semantics Classical first-order Stable-model semantics for negation Well-founded semantics for negation ... ... ... A carefully chosen set of interrelated dialects can serve the purpose of sharing and exchanging rules over the Web 5 Current State of RIF Dialects Need your feedback! Advanced LP . Advanced LP dialect 1 dialect N RIF-PRD (Production Rules Dialect) Basic LP dialect RIF-BLD (Basic Logic Dialect) - ready to go - under development - future plans RIF-Core 6 Why Is RIF Important? Best chance yet to bring rule languages into mainstream Can make -
Supporting SPARQL Update Queries in RDF-XML Integration *
Supporting SPARQL Update Queries in RDF-XML Integration * Nikos Bikakis1 † Chrisa Tsinaraki2 Ioannis Stavrakantonakis3 4 Stavros Christodoulakis 1 NTU Athens & R.C. ATHENA, Greece 2 EU Joint Research Center, Italy 3 STI, University of Innsbruck, Austria 4 Technical University of Crete, Greece Abstract. The Web of Data encourages organizations and companies to publish their data according to the Linked Data practices and offer SPARQL endpoints. On the other hand, the dominant standard for information exchange is XML. The SPARQL2XQuery Framework focuses on the automatic translation of SPARQL queries in XQuery expressions in order to access XML data across the Web. In this paper, we outline our ongoing work on supporting update queries in the RDF–XML integration scenario. Keywords: SPARQL2XQuery, SPARQL to XQuery, XML Schema to OWL, SPARQL update, XQuery Update, SPARQL 1.1. 1 Introduction The SPARQL2XQuery Framework, that we have previously developed [6], aims to bridge the heterogeneity issues that arise in the consumption of XML-based sources within Semantic Web. In our working scenario, mappings between RDF/S–OWL and XML sources are automatically derived or manually specified. Using these mappings, the SPARQL queries are translated on the fly into XQuery expressions, which access the XML data. Therefore, the current version of SPARQL2XQuery provides read-only access to XML data. In this paper, we outline our ongoing work on extending the SPARQL2XQuery Framework towards supporting SPARQL update queries. Both SPARQL and XQuery have recently standardized their update operation seman- tics in the SPARQL 1.1 and XQuery Update Facility, respectively. We have studied the correspondences between the update operations of these query languages, and we de- scribe the extension of our mapping model and the SPARQL-to-XQuery translation algorithm towards supporting SPARQL update queries. -
XBRL and the Semantic
How can we exploit XBRL and Semantic Web technologies to realize the opportunities? Track 3: Case Studies in XBRL Solutions 19th XBRL International Conference, Paris, 23rd June 2009 Dave Raggett <[email protected]> W3C Fellow – Financial data & Semantic Web Member – XBRL INT Technical Standards Board With some slides from Diane Mueller, JustSystems 1 Outline XBRL: adding semantics to business reports World Wide Adoption of XBRL Users and use cases for XBRL Realizing the potential Feeding the Semantic Web ◦ XBRL, XLink, RDF, Turtle, SPARQL, OWL ◦ Web APIs, Smart Searches, Web Scale Queries ◦ Findings June 2009 2 So What is XBRL? eXtensible Business Reporting Language ◦ a freely available electronic language for financial reporting. ◦ based on XML, XML Schema and XLink ◦ based on accepted financial reporting standards and practices to transport financial reports across all software, platforms and technologies Business reporting includes, but is not limited to: ◦ financial statements, ◦ financial and non-financial information ◦ general ledger transactions ◦ regulatory filings such as annual and quarterly financial statements. “XBRL allows software vendors, programmers and end users who adopt it as a specification to enhance the creation, exchange, and comparison of business reporting information” from xbrl.org June 2009 3 Not just a number XBRL binds each reported fact to a concept in a reporting taxonomy e.g. US GAAP, IFRS ◦ Each concept can be bound to a description and its definition in the accounting literature Hierarchy of Terse label, EN Currency, amount Reporting period concepts Impairment of goodwill: $M21 3 months to 2009-04-30 Description Impairment of goodwill: Loss recognized during the period that results from the write-down of goodwill after comparing the implied fair value of reporting unit goodwill with the carrying amount of that goodwill.