35
results
-
opmv - Open Provenance Model Vocabulary http://purl.org/net/opmv/ns# OPMV, the Open Provenance Model Vocabulary, provides terms to enable practitioners of data publishing to publish their data responsibly. @en -
prvt - Provenance Vocabulary types http://purl.org/net/provenance/types# Extends the Provenance Vocabulary by defining subclasses of the types of provenance elements introduced in the core ontology. @en -
voag - Vocabulary Of Attribution and Governance http://voag.linkedmodel.org/schema/voag VOAG is intended to specify licensing, attribution, provenance and governance of an ontology. @en -
irw - The Identity of Resources on the Web ontology http://www.ontologydesignpatterns.org/ont/web/irw.owl This ontology is an evolution of IRE ontology. It describes identification of resources on the Web, through the definition of relationships between resources and their representations on the Web. The requirement is to describe what can be identified by URIs and how this is handled e.g. in form of HTTP requests and reponds. @en -
airo - AI Risk Ontology https://w3id.org/airo AIRO represents AI risk concepts and relations based on the AI Act draft and ISO 31000 standard series. @en -
pmlp - PML2 provenance ontology http://inference-web.org/2.0/pml-provenance.owl The provenance part of PML2 ontology. It is a fundamental component of PML2 ontology. @en -
daq - Dataset Quality Vocabulary http://purl.org/eis/vocab/daq# Quality metrics can be (in principle) calculated on various forms of data (such as datasets, graphs, set of triples etc...). This vocabulary allow the owner/user of such RDF data to calculate metrics on multiple (and different) resources. @en -
dqc - The Data Quality Constraints Library http://semwebquality.org/ontologies/dq-constraints This RDF document contains a library of data quality constraints represented as SPARQL query templates based on the SPARQL Inferencing Framework (SPIN). The data quality constraint templates are especially useful for the identification of data quality problems during data entry and for periodic quality checks during data usage. @en -
dqv - Data Quality Vocabulary http://www.w3.org/ns/dqv The Data Quality Vocabulary (DQV) is seen as an extension to DCAT to cover the quality of the data, how frequently is it updated, whether it accepts user corrections, persistence commitments etc. When used by publishers, this vocabulary will foster trust in the data amongst developers. @en -
cert - The Cert Ontology http://www.w3.org/ns/auth/cert# Ontology for Certificates and crypto stuff. @en -
sh - W3C Shapes Constraint Language (SHACL) Vocabulary http://www.w3.org/ns/shacl# This vocabulary defines terms used in SHACL, the W3C Shapes Constraint Language. @en -
sw-quality - SQuAP Ontology https://w3id.org/squap/ Quality, architecture, and process are considered the keystones of software engineering. ISO defines them in three separate standards. However, their interaction has been poorly studied, so far. The SQuAP model (Software Quality, Architecture, Process) describes twenty-eight main factors that impact on software quality in banking systems, and each factor is described as a relation among some characteristics from the three ISO standards. Hence, SQuAP makes such relations emerge rigorously, although informally. SQaAP-Ont is an OWL ontology that formalises those relations in order to represent and reason via Linked Data about software engineering in a three-dimensional model consisting of quality, architecture, and process characteristics. @en -
dq - OWL representation of ISO 19115 (Geographic Information - Metadata - Data quality package) http://def.seegrid.csiro.au/isotc211/iso19115/2003/dataquality An OWL representation of parts of the Geographic Metadata model described in ISO 19115:2003 with Corrigendum 2006 - DQ Package @en -
opmo - Open Provenance Model http://openprovenance.org/model/opmo The Open Provenance Model is a model of provenance that is designed to meet the following requirements: (1) To allow provenance information to be exchanged between systems, by means of a compatibility layer based on a shared provenance model. (2) To allow developers to build and share tools that operate on such a provenance model. (3) To define provenance in a precise, technology-agnostic manner. (4) To support a digital representation of provenance for any 'thing', whether produced by computer systems or not. (5) To allow multiple levels of description to coexist. (6) To define a core set of rules that identify the valid inferences that can be made on provenance representation. @en -
acrt - Agent Certification Ontology http://privatealpha.com/ontology/certification/1# This document specifies a vocabulary for asserting the existence of official endorsements or certifications of agents, such as people and organizations. @en