DOCSLIB.ORG

D02.02 Report on the Maintenance of DCAT-AP

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
D02.02 Report on the Maintenance of DCAT-AP D02.02 Report on the Maintenance of DCAT-AP DI/07624 - ABC IV Lot 3 SC141 V ers ion: 1 .0 0 Date: 2 3 /0 7/2019 D02.02 Report on the Maintenance of DCAT-AP Basic Document Metadata Property Value Name D02.02 Report on the Maintenance of DCAT-AP Release date 23/07/2019 Status Completed Version 1.00 Author Adina Dragan Reviewed by Fidel Santiago and Susanne Wigard Approved by Fidel Santiago and Susanne Wigard This report serves as a part of a series of status reports related to the maintenance of DCAT-AP, an Application Profile of the W3C Recommendation DCAT and its extensions, GeoDCAT-AP and Abstract StatDCAT-AP. The production of this and subsequent reports is governed by the Change and Release Management Policy for DCAT-AP. Document History Version Date Description Action 0.01 19/06/2019 Created first draft Creation 1.00 23/07/2019 Published version 1.0 Publish 23/07/2019 P age 1 D02.02 Report on the Maintenance of DCAT-AP Disclaimer: The views expressed in this report are purely those of the Author(s) and may not, in any circumstances, be interpreted as stating an official position of the European Commission. The European Commission does not guarantee the accuracy of the information included in this study, nor does it accept any responsibility for any use thereof. Reference herein to any specific products, specifications, process, or service by trade name, trademark, manufacturer, or otherwise, does not necessarily constitute or imply its endorsement, recommendation, or favouring by the European Commission. All care has been taken by the author to ensure that s/he has obtained, where necessary, permission to use any parts of manuscripts including illustrations, maps, and graphs, on which intellectual property rights already exist from the titular holder(s) of such rights or from her/his or their legal representative. 23/07/2019 P age 2 D02.02 Report on the Maintenance of DCAT-AP Table of Contents 1 INTRODUCTION AND BACKGROUND ............................................... 4 2 ISSUES UNDER CONSIDERATION ................................................... 5 2.1 OVERVIEW ................................................................................ 5 2.2 THE CATEGORISATION OF THE ISSUES ................................................... 5 2.3 ISSUES THAT INVOLVE BUG FIX CHANGES ................................................ 5 2.4 ISSUES THAT INVOLVE MINOR SEMANTIC CHANGES ...................................... 6 2.5 ISSUES THAT INVOLVE MAJOR SEMANTIC CHANGES ...................................... 7 2.6 ISSUES THAT WERE CLOSED ............................................................. 21 3 CONCLUSIONS AND NEXT STEPS .................................................. 25 ANNEX I INSTRUCTIONS FOR SUBMISSION OF CHANGE REQUESTS ...... 26 Table of Tables NO TABLE OF FIGURES ENTRIES FOUND. Table of Figures NO TABLE OF FIGURES ENTRIES FOUND. 23/07/2019 P age 3 D02.02 Report on the Maintenance of DCAT-AP 1 INTRODUCTION AND BACKGROUND This report is a status report related to the maintenance of DCAT-AP1, an Application Profile of the W3C Recommendation DCAT 2 and its siblings specifications StatDCAT- AP3 and GeoDCAT-AP 4 and is governed by the Change and Release Management Policy for DCAT-AP5. The current report includes an overview of all issues submitted on GitHub repositories as follows: section 2.1 presents the statistics about the new, open and closed issues, section 2.1 to 2.5 presents each open issue with its proposed resolution splitted up by categories like bug fixes, minor and major semantic changes and section 2.6 includes the closed issues during the reporting period. The reports closes with section 3 about conclusions and next steps of the change and release process. 1 DCAT application profile for data portals in Europe. https://joinup.ec.europa.eu/solution/dcat-application-profile-data-portals- europe/about 2 Data Catalog Vocabulary (DCAT). W3C Recommendation 16 January 2014. https://www.w3.org/TR/vocab-dcat/ 3 StatDCAT Application Profile for data portals in Europe https://joinup.ec.europa.eu/solution/statdcat-application-profile-data-portals- europe 4 GeoDCAT Application Profile for data portals in Europe https://joinup.ec.europa.eu/solution/geodcat-application-profile-data-portals- europe 5 Change and Release Management Policy for DCAT -AP. https://joinup.ec.europa.eu/node/700269 23/07/2019 P age 4 D02.02 Report on the Maintenance of DCAT-AP 2 ISSUES UNDER CONSIDERATION 2.1 Overview6 A total of 68 issues were reviewed in the period from 02 October 2018 until 20 June 2019 by being analysed and categorised in bug fixes, minor and major semantic changes. Eighteen new issues were opened during the period and twelve issues were fixed and closed under the DCAT-AP minor release version 1.2 from November 2018 and the DCAT-AP bug fix release version 1.2.1 and StatDCAT-AP bug fix release version 1.0.1 from May 2019. The remaining 56 issues remained open for discussions for the next major release planned for November 2019. The issues presented below from section 2.3 to 2.5 are still open for comments and will be discussed with the DCAT-AP Working Group, in preparation for the next major release scheduled for November 2019. 2.2 The categorisation of the issues The issues are grouped in the next sections into four categories: 1. Issues that involve bug fix changes in section 2.3 2. Issues that involve minor semantic changes in section 2.4 3. Issues that involve major semantic changes in section 2.5 4. Issues that were closed in section 2.6 2.3 Issues that involve bug fix changes ID DCAT-AP-58 Title rdf file > cleanup of the prefixes URL https://github.com/SEMICeu/DCAT-AP/issues/58 Discussion There are non-used prefixes in the RDF file and is best to clean them up. Proposed resolution Cleanup non-used prefixes in the next major release cycle from November 2019. 6 Change requests for DCAT-AP are handled through an issue tracker on GitHub (https://github.com/SEMICeu/DCAT-AP/). This repository had 28 watchers (https://github.com/SEMICeu/DCAT-AP/watchers) as of March 2019, two being members of the SEMIC team. Others include representatives from the Publications Office, and national data portals of Norway, Italy, Spain and Germany. 23/07/2019 P age 5 D02.02 Report on the Maintenance of DCAT-AP ID DCAT-AP-53 Title dcat:CatalogRecord URL https://github.com/SEMICeu/DCAT-AP/issues/53 Discussion According to DCAT-AP 1.2 PDF, adms:status MUST take one of the values :created, :updated or :deleted depending on whether this latest revision is a result of a creation, update or deletion. Instead, adms:status only defines Completed, Deprecated, UnderDevelopment and Withdrawn. Proposed resolution Correct the documentation specification with the real statuses allowed by adms:status meaning Completed, Deprecated, UnderDevelopment and Withdrawn. ID DCAT-AP-61 Title redefinition of the dcat ontology in the shacl file URL https://github.com/SEMICeu/DCAT-AP/issues/61 Discussion The dcat-ap.shapes.ttl contains the ontology description again (which is different from the official description). Proposed resolution Take out the ontology description from the SHACL representation. 2.4 Issues that involve minor semantic changes ID DCAT-AP-3 Title dcat:Catalog - dct:spatial recommended? URL https://github.com/SEMICeu/DCAT-AP/issues/3 Discussion Request to make the property recommended but not before agreeing on a more precise definition. Proposed resolution Make dct:spatial recommended for Catalog and agree on a more precise definition of the property. ID DCAT-AP-9 Title dcat:Dataset - dct:spatial recommended? URL https://github.com/SEMICeu/DCAT-AP/issues/9 Discussion None. Proposed resolution Make dct:spatial recommended for Dataset. 23/07/2019 P age 6 D02.02 Report on the Maintenance of DCAT-AP 2.5 Issues that involve major semantic changes The issues presented below are still open for comments and will be discussed in the DCAT-AP Working Group, in preparation for the next major release scheduled for November 2019. ID DCAT-AP-5 Title dcat:Catalog - remove dct:rights? URL https://github.com/SEMICeu/DCAT-AP/issues/5 Discussion None. Proposed resolution It is proposed to keep dct:rights in the model and close the issue. ID DCAT-AP-6 Title dcat:Catalog - remove dct:isPartOf? URL https://github.com/SEMICeu/DCAT-AP/issues/6 Discussion None. Proposed resolution It is proposed to keep this property in the model and close the issue. ID DCAT-AP-10 Title dcat:Dataset - remove adms:sample? URL https://github.com/SEMICeu/DCAT-AP/issues/10 Discussion Proposal to eliminate adms:Sample from Dataset as we already have dct:conformsTo. Proposed resolution It is proposed to remove adms:sample from Dataset and use dct:conformsTo that is already in the model. ID DCAT-AP-11 Title dcat:Dataset- remove adms:versionNotes? URL https://github.com/SEMICeu/DCAT-AP/issues/11 Discussion None. Proposed resolution It is proposed to keep this property in the model and close the issue. ID DCAT-AP-15 Title dcat:Dataset - remove dct:relation? URL https://github.com/SEMICeu/DCAT-AP/issues/15 Discussion None. Proposed resolution It is proposed to keep it in the model as this property is also recommended in ADMS and closing the issue. 23/07/2019 P age 7 D02.02 Report on the Maintenance of DCAT-AP ID DCAT-AP-16 Title dcat:Dataset - remove dct:source? URL https://github.com/SEMICeu/DCAT-AP/issues/16 Discussion None. Proposed resolution It is proposed to keep this property in the model and closing the issue. ID DCAT-AP-17 Title dcat:Dataset - remove dct:type? URL https://github.com/SEMICeu/DCAT-AP/issues/17 Discussion Comments received about how dct:type could be used to group related datasets into collections or that it can be used to distinguish between datasets, dataset series, geospatial datasets, documents, etc., and may use a controlled vocabulary for this.
Load more

Recommended publications
  • V a Lida T in G R D F Da
    Series ISSN: 2160-4711 LABRA GAYO • ET AL GAYO LABRA Series Editors: Ying Ding, Indiana University Paul Groth, Elsevier Labs Validating RDF Data Jose Emilio Labra Gayo, University of Oviedo Eric Prud’hommeaux, W3C/MIT and Micelio Iovka Boneva, University of Lille Dimitris Kontokostas, University of Leipzig VALIDATING RDF DATA This book describes two technologies for RDF validation: Shape Expressions (ShEx) and Shapes Constraint Language (SHACL), the rationales for their designs, a comparison of the two, and some example applications. RDF and Linked Data have broad applicability across many fields, from aircraft manufacturing to zoology. Requirements for detecting bad data differ across communities, fields, and tasks, but nearly all involve some form of data validation. This book introduces data validation and describes its practical use in day-to-day data exchange. The Semantic Web offers a bold, new take on how to organize, distribute, index, and share data. Using Web addresses (URIs) as identifiers for data elements enables the construction of distributed databases on a global scale. Like the Web, the Semantic Web is heralded as an information revolution, and also like the Web, it is encumbered by data quality issues. The quality of Semantic Web data is compromised by the lack of resources for data curation, for maintenance, and for developing globally applicable data models. At the enterprise scale, these problems have conventional solutions. Master data management provides an enterprise-wide vocabulary, while constraint languages capture and enforce data structures. Filling a need long recognized by Semantic Web users, shapes languages provide models and vocabularies for expressing such structural constraints.
    [Show full text]
  • Deciding SHACL Shape Containment Through Description Logics Reasoning
    Deciding SHACL Shape Containment through Description Logics Reasoning Martin Leinberger1, Philipp Seifer2, Tjitze Rienstra1, Ralf Lämmel2, and Steffen Staab3;4 1 Inst. for Web Science and Technologies, University of Koblenz-Landau, Germany 2 The Software Languages Team, University of Koblenz-Landau, Germany 3 Institute for Parallel and Distributed Systems, University of Stuttgart, Germany 4 Web and Internet Science Research Group, University of Southampton, England Abstract. The Shapes Constraint Language (SHACL) allows for for- malizing constraints over RDF data graphs. A shape groups a set of constraints that may be fulfilled by nodes in the RDF graph. We investi- gate the problem of containment between SHACL shapes. One shape is contained in a second shape if every graph node meeting the constraints of the first shape also meets the constraints of the second. Todecide shape containment, we map SHACL shape graphs into description logic axioms such that shape containment can be answered by description logic reasoning. We identify several, increasingly tight syntactic restrictions of SHACL for which this approach becomes sound and complete. 1 Introduction RDF has been designed as a flexible, semi-structured data format. To ensure data quality and to allow for restricting its large flexibility in specific domains, the W3C has standardized the Shapes Constraint Language (SHACL)5. A set of SHACL shapes are represented in a shape graph. A shape graph represents constraints that only a subset of all possible RDF data graphs conform to. A SHACL processor may validate whether a given RDF data graph conforms to a given SHACL shape graph. A shape graph and a data graph that act as a running example are pre- sented in Fig.
    [Show full text]
  • 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.
    [Show full text]
  • Bibliography of Erik Wilde
    dretbiblio dretbiblio Erik Wilde's Bibliography References [1] AFIPS Fall Joint Computer Conference, San Francisco, California, December 1968. [2] Seventeenth IEEE Conference on Computer Communication Networks, Washington, D.C., 1978. [3] ACM SIGACT-SIGMOD Symposium on Principles of Database Systems, Los Angeles, Cal- ifornia, March 1982. ACM Press. [4] First Conference on Computer-Supported Cooperative Work, 1986. [5] 1987 ACM Conference on Hypertext, Chapel Hill, North Carolina, November 1987. ACM Press. [6] 18th IEEE International Symposium on Fault-Tolerant Computing, Tokyo, Japan, 1988. IEEE Computer Society Press. [7] Conference on Computer-Supported Cooperative Work, Portland, Oregon, 1988. ACM Press. [8] Conference on Office Information Systems, Palo Alto, California, March 1988. [9] 1989 ACM Conference on Hypertext, Pittsburgh, Pennsylvania, November 1989. ACM Press. [10] UNIX | The Legend Evolves. Summer 1990 UKUUG Conference, Buntingford, UK, 1990. UKUUG. [11] Fourth ACM Symposium on User Interface Software and Technology, Hilton Head, South Carolina, November 1991. [12] GLOBECOM'91 Conference, Phoenix, Arizona, 1991. IEEE Computer Society Press. [13] IEEE INFOCOM '91 Conference on Computer Communications, Bal Harbour, Florida, 1991. IEEE Computer Society Press. [14] IEEE International Conference on Communications, Denver, Colorado, June 1991. [15] International Workshop on CSCW, Berlin, Germany, April 1991. [16] Third ACM Conference on Hypertext, San Antonio, Texas, December 1991. ACM Press. [17] 11th Symposium on Reliable Distributed Systems, Houston, Texas, 1992. IEEE Computer Society Press. [18] 3rd Joint European Networking Conference, Innsbruck, Austria, May 1992. [19] Fourth ACM Conference on Hypertext, Milano, Italy, November 1992. ACM Press. [20] GLOBECOM'92 Conference, Orlando, Florida, December 1992. IEEE Computer Society Press. http://github.com/dret/biblio (August 29, 2018) 1 dretbiblio [21] IEEE INFOCOM '92 Conference on Computer Communications, Florence, Italy, 1992.
    [Show full text]
  • SHACL Satisfiability and Containment
    SHACL Satisfiability and Containment Paolo Pareti1 , George Konstantinidis1 , Fabio Mogavero2 , and Timothy J. Norman1 1 University of Southampton, Southampton, United Kingdom {pp1v17,g.konstantinidis,t.j.norman}@soton.ac.uk 2 Università degli Studi di Napoli Federico II, Napoli, Italy [email protected] Abstract. The Shapes Constraint Language (SHACL) is a recent W3C recom- mendation language for validating RDF data. Specifically, SHACL documents are collections of constraints that enforce particular shapes on an RDF graph. Previous work on the topic has provided theoretical and practical results for the validation problem, but did not consider the standard decision problems of satisfiability and containment, which are crucial for verifying the feasibility of the constraints and important for design and optimization purposes. In this paper, we undertake a thorough study of different features of non-recursive SHACL by providing a translation to a new first-order language, called SCL, that precisely captures the semantics of SHACL w.r.t. satisfiability and containment. We study the interaction of SHACL features in this logic and provide the detailed map of decidability and complexity results of the aforementioned decision problems for different SHACL sublanguages. Notably, we prove that both problems are undecidable for the full language, but we present decidable combinations of interesting features. 1 Introduction The Shapes Constraint Language (SHACL) has been recently introduced as a W3C recommendation language for the validation of RDF graphs, and it has already been adopted by mainstream tools and triplestores. A SHACL document is a collection of shapes which define particular constraints and specify which nodes in a graph should be validated against these constraints.
    [Show full text]
  • 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].
    [Show full text]
  • Finding Non-Compliances with Declarative Process Constraints Through Semantic Technologies
    Finding Non-compliances with Declarative Process Constraints through Semantic Technologies Claudio Di Ciccio2, Fajar J. Ekaputra1, Alessio Cecconi2, Andreas Ekelhart1, Elmar Kiesling1 1 TU Wien, Favoritenstrasse 9-11, 1040 Vienna, Austria, [email protected] 2 WU Vienna, Welthandelsplatz 1, 1020 Vienna, Austria fclaudio.di.ciccio,[email protected] Abstract. Business process compliance checking enables organisations to assess whether their processes fulfil a given set of constraints, such as regulations, laws, or guidelines. Whilst many process analysts still rely on ad-hoc, often handcrafted per- case checks, a variety of constraint languages and approaches have been developed in recent years to provide automated compliance checking. A salient example is DE- CLARE, a well-established declarative process specification language based on tem- poral logics. DECLARE specifies the behaviour of processes through temporal rules that constrain the execution of tasks. So far, however, automated compliance check- ing approaches typically report compliance only at the aggregate level, using binary evaluations of constraints on execution traces. Consequently, their results lack gran- ular information on violations and their context, which hampers auditability of pro- cess data for analytic and forensic purposes. To address this challenge, we propose a novel approach that leverages semantic technologies for compliance checking. Our approach proceeds in two stages. First, we translate DECLARE templates into state- ments in SHACL, a graph-based constraint language. Then, we evaluate the resulting constraints on the graph-based, semantic representation of process execution logs. We demonstrate the feasibility of our approach by testing its implementation on real- world event logs. Finally, we discuss its implications and future research directions.
    [Show full text]
  • Integrating Semantic Web Technologies and ASP for Product Configuration
    Integrating Semantic Web Technologies and ASP for Product Configuration Stefan Bischof1 and Gottfried Schenner1 and Simon Steyskal1 and Richard Taupe1,2 Abstract. Currently there is no single dominating technol- own proprietary specification language. Also in the product ogy for building product configurator systems. While research configuration community there is currently no standard way often focuses on a single technology/paradigm, building an to specify product configuration problems although the topic industrial-scale product configurator system will almost al- of ontologies and product configuration is over 20 years old ways require the combination of various technologies for dif- (cf. [21]) and pre-dates the Semantic Web. ferent aspects of the system (knowledge representation, rea- In Section2 we describe the technologies used for this pa- soning, solving, user interface, etc.) This paper demonstrates per. In Section3 we show how to define a product configurator how to build such a hybrid system and how to integrate var- knowledge base with RDF and SHACL, that allows checking ious technologies and leverage their respective strengths. of constraints and interactive solving. Due to the increasing popularity of the industrial knowledge For solving product configuration problems, RDF and graph we utilize Semantic Web technologies (RDF, OWL and SHACL are combined with Answer Set Programming in Sec- the Shapes Constraint Language (SHACL)) for knowledge tion4. In Section5 we illustrate how reasoning with OWL representation and integrate it with Answer Set Programming can help to integrate the product configuration solutions into (ASP), a well-established solving paradigm for product con- the knowledge graph and facilitate reuse of ontologies. figuration.
    [Show full text]
  • Linked Data Schemata: Fixing Unsound Foundations
    Linked data schemata: fixing unsound foundations Editor(s): Amrapali Zaveri, Stanford University, USA; Dimitris Kontokostas, Universität Leipzig, Germany; Sebastian Hellmann, Universität Leipzig, Germany; Jürgen Umbrich, Wirtschaftsuniversität Wien, Austria Solicited review(s): Mathieu d’Aquin, The Open University, UK; Peter F. Patel-Schneider, Nuance Communications, USA; John McCrae, Insight Centre for Data Analytics, Ireland; One anonymous reviewer Kevin Chekov Feeney, Gavin Mendel Gleason, and Rob Brennan Knowledge and Data Engineering Group & ADAPT Centre, School of Computer Science & Statistics, Trinity College Dublin, Ireland Corresponding author’s e-mail: [email protected] Abstract. This paper describes our tools and method for an evaluation of the practical and logical implications of combining common linked data vocabularies into a single local logical model for the purpose of reasoning or performing quality evalua- tions. These vocabularies need to be unified to form a combined model because they reference or reuse terms from other linked data vocabularies and thus the definitions of those terms must be imported. We found that strong interdependencies between vocabularies are common and that a significant number of logical and practical problems make this model unification inconsistent. In addition to identifying problems, this paper suggests a set of recommendations for linked data ontology design best practice. Finally we make some suggestions for improving OWL’s support for distributed authoring and ontology reuse. Keywords: Linked Data, Reasoning, Data Quality 1. Introduction In order to validate any dataset which uses the adms:Asset term we must combine the adms ontolo- One of the central tenets of the linked data move- gy and the dcat ontology in order to ensure that ment is the reuse of terms from existing well-known dcat:Dataset is a valid class.
    [Show full text]
  • Trav-SHACL: Efficiently Validating Networks of SHACL Constraints
    Trav-SHACL: Efficiently Validating Networks of SHACL Constraints M´onicaFiguera1,2, Philipp D. Rohde1,3, and Maria-Esther Vidal1,3 1L3S Research Center, Leibniz University of Hannover, Germany 2University of Bonn, Germany 3TIB Leibniz Information Centre for Science and Technology, Hannover, Germany [email protected], fphilipp.rohde,[email protected] Abstract Knowledge graphs have emerged as expressive data structures for Web data. Knowledge graph potential and the demand for ecosystems to facili- tate their creation, curation, and understanding, is testified in diverse domains, e.g., biomedicine. The Shapes Constraint Language (SHACL) is the W3C rec- ommendation language for integrity constraints over RDF knowledge graphs. Enabling quality assements of knowledge graphs, SHACL is rapidly gaining attention in real-world scenarios. SHACL models integrity constraints as a net- work of shapes, where a shape contains the constraints to be fullfiled by the same entities. The validation of a SHACL shape schema can face the issue of tractability during validation. To facilitate full adoption, efficient computational methods are required. We present Trav-SHACL, a SHACL engine capable of planning the traversal and execution of a shape schema in a way that invalid entities are detected early and needless validations are minimized. Trav-SHACL reorders the shapes in a shape schema for efficient validation and rewrites target and constraint queries for the fast detection of invalid entities. Trav-SHACL is empirically evaluated on 27 testbeds executed against knowledge graphs of up to 34M triples. Our experimental results suggest that Trav-SHACL exhibits high performance gradually and reduces validation time by a factor of up to arXiv:2101.07136v1 [cs.DB] 18 Jan 2021 28.93 compared to the state of the art.
    [Show full text]
  • OSLC Core Version 3.0. Part 8: Constraints Project Specification 01 17 September 2020
    Standards Track Work Product OSLC Core Version 3.0. Part 8: Constraints Project Specification 01 17 September 2020 This stage: https://docs.oasis-open-projects.org/oslc-op/core/v3.0/ps01/core-shapes.html (Authoritative) https://docs.oasis-open-projects.org/oslc-op/core/v3.0/ps01/core-shapes.pdf Previous stage: N/A Latest stage: https://docs.oasis-open-projects.org/oslc-op/core/v3.0/core-shapes.html (Authoritative) https://docs.oasis-open-projects.org/oslc-op/core/v3.0/core-shapes.pdf Latest version: https://open-services.net/spec/core/latest Latest editor's draft: https://open-services.net/spec/core/latest-draft Open Project: OASIS Open Services for Lifecycle Collaboration (OSLC) OP Project Chairs: Jim Amsden ([email protected]), IBM Andrii Berezovskyi ([email protected]), KTH Editor: Jim Amsden ([email protected]), IBM Additional components: This specification is one component of a Work Product that also includes: OSLC Core Version 3.0. Part 1: Overview. oslc-core.html OSLC Core Version 3.0. Part 2: Discovery. discovery.html OSLC Core Version 3.0. Part 3: Resource Preview. resource-preview.html OSLC Core Version 3.0. Part 4: Delegated Dialogs. dialogs.html OSLC Core Version 3.0. Part 5: Attachments. attachments.html OSLC Core Version 3.0. Part 6: Resource Shape. resource-shape.html OSLC Core Version 3.0. Part 7: Vocabulary. core-vocab.html core-shapes Copyright © OASIS Open 2020. All Rights Reserved. 17 September 2020 - Page 1 of 19 Standards Track Work Product OSLC Core Version 3.0. Part 8: Constraints (this document).
    [Show full text]
  • Healing the Fragmentation to Realise the Full Potential of The
    HealingHealing thethe fragmentationfragmentation toto realiserealise thethe fullfull potentialpotential of thethe IoTIoT Dr.Dr. DaveDave Raggett,Raggett, W3C/ERCIMW3C/ERCIM email:email: [email protected]@w3.org 2525 JuneJune 20202020 ThisThis talktalk isis supportedsupported byby thethe CreateCreate--IoTIoT CoordinationCoordination andand SupportSupport ActionAction withwith fundingfunding fromfrom thethe EuropeanEuropean CommissionCommission Investments in IoT are at risk! Eric Siow, Director, Open Web Platform Standards and Ecosystem Strategies at Intel: • IoT is a little over 10 years old • Hype has been much greater than present reality • IoT is “biting off more that it can chew” • Trying to address too many markets • Involves too many and mostly uncoordinated SDOs and SIGs 2/14 Key IoT Challenges Facing Smart Cities • Lack of coalescence around a set of complementary standards • Hinders scalability, interoperability and evolution • Need to simplify: prioritise and define requirements • Regional regulatory differences adding to the confusion • Diverse requirements impede scalability of the market • Need regulatory agencies to participate and help with standardisation requirements • Lack of interoperability wastes up to 40% of IoT value1 • Cities and technology partners may waste up to $321 billion by 20252 1. https://www.mckinsey.com/business-functions/digital-mckinsey/our-insights/the-internet-of-things-the-value-of-digitizing-the-physical-world 2. https://machinaresearch.com/news/smart-cities-could-waste-usd341-billion-by-2025-on-non-standardized-iot-deployments/
    [Show full text]