Skip to main content
QUICK REVIEW

[Paper Review] Constraints to Validate RDF Data Quality on Common Vocabularies in the Social, Behavioral, and Economic Sciences

Thomas Hartmann, Benjamin Zapilko|arXiv (Cornell University)|Apr 17, 2015
Semantic Web and Ontologies5 references3 citations
TL;DR

This paper proposes a comprehensive set of 81 RDF constraints to validate data quality in common vocabularies used in the social, behavioral, and economic (SBE) sciences, including DDI-RDF, RDF Data Cube, SKOS, XKOS, and PHDD. The constraints are classified by severity (INFO to ERROR) and derived from domain expert input and real-world data, enabling robust validation of metadata and data quality in Linked Data applications.

ABSTRACT

To ensure high quality of and trust in both metadata and data, their representation in RDF must satisfy certain criteria - specified in terms of RDF constraints. From 2012 to 2015 together with other Linked Data community members and experts from the social, behavioral, and economic sciences (SBE), we developed diverse vocabularies to represent SBE metadata and rectangular data in RDF. The DDI-RDF Discovery Vocabulary (DDI-RDF) is designed to support the dissemination, management, and reuse of unit-record data, i.e., data about individuals, households, and businesses, collected in form of responses to studies and archived for research purposes. The RDF Data Cube Vocabulary (QB) is a W3C recommendation for expressing data cubes, i.e. multi-dimensional aggregate data and its metadata. Physical Data Description (PHDD) is a vocabulary to model data in rectangular format, i.e., tabular data. The data could either be represented in records with character-separated values (CSV) or fixed length. The Simple Knowledge Organization System (SKOS) is a vocabulary to build knowledge organization systems such as thesauri, classification schemes, and taxonomies. XKOS is a SKOS extension to describe formal statistical classifications. In this paper, we describe RDF constraints to validate metadata on unit-record data (DDI-RDF), aggregated data (QB), thesauri (SKOS), and statistical classifications (XKOS) and to validate tabular data (PHDD) - all of them represented in RDF. We classified these constraints according to the severity of occurring constraint violations. This technical report is updated continuously as modifying, adding, and deleting constraints remains ongoing work.

Motivation & Objective

  • To identify and formalize critical constraints for ensuring high-quality RDF-structured metadata and data in the social, behavioral, and economic (SBE) sciences.
  • To address the lack of standardized validation mechanisms for SBE vocabularies used in Linked Data applications.
  • To classify constraint violations by severity (INFO to ERROR) to guide data practitioners in prioritizing data quality issues.
  • To support the development of constraint languages by grounding requirements in actual SBE data use cases and expert input.
  • To contribute to the W3C SHACL and RDF validation ecosystem by curating a publicly available, collaboratively maintained database of validation requirements.

Proposed method

  • The authors collected constraints from well-established SBE vocabularies, including DDI-RDF, RDF Data Cube (QB), PHDD, SKOS, and XKOS, based on real data and expert input.
  • Constraints were categorized into 12 quality issue types, such as labeling, documentation, vocabulary usage, and URI scheme compliance.
  • Each constraint was formally specified and mapped to a severity level (INFO, WARNING, ERROR) based on expert evaluation of impact on data quality and usability.
  • The validation rules were implemented using SPARQL and SPIN, leveraging SPARQL’s native support for constraint checking and inference.
  • The work builds on the DCMI RDF Application Profiles Task Group’s public database of validation requirements, enriching it with SBE-specific constraints.
  • The entire framework is continuously updated and publicly available at http://purl.org/net/rdf-validation, enabling community contributions.

Experimental results

Research questions

  • RQ1What types of RDF constraints are essential for ensuring data quality in SBE-domain vocabularies such as DDI-RDF, QB, SKOS, and PHDD?
  • RQ2How can constraint violations in SBE RDF data be systematically classified by severity to guide data quality improvement?
  • RQ3What are the most critical validation requirements for metadata and data in the SBE domain, as identified by domain experts and real-world data analysis?
  • RQ4How do existing constraint languages like SPIN, SHACL, and OWL 2 compare in expressing SBE-specific validation rules?
  • RQ5What role do linked data best practices—such as HTTP URI usage and proper labeling—play in maintaining data quality across SBE vocabularies?

Key findings

  • The study identified and formalized 81 distinct constraint types essential for validating RDF data quality in SBE vocabularies, covering metadata, labeling, documentation, and structural integrity.
  • Constraints were classified into severity levels, with 11 constraints marked as ERROR (e.g., HTTP URI scheme violations, undefined SKOS resources), indicating critical data quality issues.
  • The most frequent constraint violations involved missing or malformed labels (e.g., empty labels, unprintable characters), highlighting the need for improved data documentation practices.
  • A significant number of constraints (e.g., SKOS-C-LABELING-AND-DOCUMENTATION-01 to SKOS-C-LABELING-AND-DOCUMENTATION-06) target labeling and documentation quality, underscoring the importance of human-readable metadata.
  • The study confirmed that HTTP URI scheme violations (e.g., using URNs or DOIs instead of HTTP URIs) are a widespread issue, classified as ERROR-level constraints.
  • The work provides a publicly accessible, continuously updated database of validation requirements, forming a foundation for future constraint language development and tooling in the SBE domain.

Better researchstarts right now

From reading papers to final review, dramatically reduce your research time.

No credit card · Free plan available

This review was created by AI and reviewed by human editors.