language en

PAD, the Platform Assertion Document data model

Revision:
0.1.0
Authors:
Bram van den Boomen
Ludo Waltman
Nees Jan van Eck
Serge Horbach
Tony Ross-Hellauer
Download serialization:
JSON-LD RDF/XML N-Triples TTL
License:
https://creativecommons.org/licenses/by/4.0/
Cite as:
Van den Boomen, Bram, Van Eck, Nees Jan, Waltman, Ludo, Ross-Hellauer, Tony, & Horbach, Serge P.J.M. (2023). The Scholarly Communication Platform Framework. Zenodo. https://doi.org/10.5281/zenodo.7860610
DOI:
https://doi.org/10.5281/zenodo.7860610
Provenance of this page
Ontology Specification Draft

Introduction

The goal of the Platform Assertion Document (PAD) data model is to add context to the information about a scholarly communication platform, for instance regarding the origin (provenance) of the information. This context is important to determine whether information can be considered reliable and up-to-date and to understand the conditions under which the information can be used. The PAD data model is inspired by the model [introduced for nanopublications](https://doi.org/10.3233/ISU-2010-0613). It uses named graphs to add provenance information. A named graph enables adding a unique identifier to a statement (i.e., to a subject-predicate-object triple). This allows statements to be made about other statements. A PAD consists of three named graphs: - The assertion graph contains statements about a scholarly communication platform. These statements may be subject to error, interpretation, and change. We therefore refer to these statements as assertions. - The provenance graph contains statements about the assertion graph. These statements may for instance provide information about the source of the assertions in the assertion graph, the date and time at which the assertions were made, and the conditions under which the information in the assertion graph can be reused. - The docinfo graph contains statements about the PAD itself. These statements are primarily used to link the named graphs that make up the PAD together. They may also provide information about the code that was used to create the PAD, the person or organization that created the PAD (which may be different from the source of the assertions in the assertion graph), etc. The PAD data model provides users of a PAD with the information needed to reason about the reliability of the information in the assertion graph, to resolve conflicting information, and to deal with updated information. Example use cases include: - Discarding information from a particular database because the information is considered unreliable. - Aggregating information about a platform, and in case of conflicting information, using the most recent information. - Correcting or updating a PAD by referring to the deprecated PAD in the provenance graph of a new PAD. - Confirming the information in a PAD by referring to the assertion and provenance graphs of that PAD. More detailed information is available in this [technical report](https://doi.org/10.5281/zenodo.7860610).

PAD, the Platform Assertion Document data model: Overview back to ToC

This ontology has the following classes and properties.

Classes

Object Properties

Named Individuals

Cross-reference for PAD, the Platform Assertion Document data model classes, object properties and data properties back to ToC

This section provides details for each class and property defined by PAD, the Platform Assertion Document data model.

Classes

Platform Assertion Documentc back to ToC or Class ToC

IRI: http://purl.org/job/pad/PAD

A Platform Assertion Document, providing machine readable, tracable way to codify information about scholarly communication platforms.
is in domain of
has Assertion op, has Doc Info op, has Provenance op, has Source PAD op
is in range of
has Source PAD op

Object Properties

has Assertionop back to ToC or Object Property ToC

IRI: http://purl.org/job/pad/hasAssertion

The property relating a Platform Assertion Document to an Assertion.

has characteristics: functional

has domain
Platform Assertion Document c
has range
Assertion c

has Doc Infoop back to ToC or Object Property ToC

IRI: http://purl.org/job/pad/hasDocInfo

The property relating a Platform Assertion Document to its DocInfo.

has characteristics: functional

has domain
Platform Assertion Document c
has range
DocInfo c

has Provenanceop back to ToC or Object Property ToC

IRI: http://purl.org/job/pad/hasProvenance

The property relating a Platform Assertion Document to the Provenance of the Assertion.

has characteristics: functional

has domain
Platform Assertion Document c
has range
Provenance c
i r i c

has Source Assertionop back to ToC or Object Property ToC

IRI: http://purl.org/job/pad/hasSourceAssertion

The property relating a Platform Assertion to a source Assertion where its data originated.

has characteristics: functional

has domain
Assertion c
has range
Assertion c

has Source PADop back to ToC or Object Property ToC

IRI: http://purl.org/job/pad/hasSourcePad

The property relating a Platform Assertion Document to a source Platform Assertion Document where its data originated.

has characteristics: functional

has domain
Platform Assertion Document c
has range
Platform Assertion Document c

Named Individuals

Assertionni back to ToC or Named Individual ToC

IRI: http://purl.org/job/pad/Assertion

belongs to
graph c
is also defined as
class

DocInfoni back to ToC or Named Individual ToC

IRI: http://purl.org/job/pad/DocInfo

belongs to
graph c
is also defined as
class

Provenanceni back to ToC or Named Individual ToC

IRI: http://purl.org/job/pad/Provenance

belongs to
graph c
is also defined as
class

Legend back to ToC

c: Classes
op: Object Properties
ni: Named Individuals

Acknowledgments back to ToC

The authors would like to thank Silvio Peroni for developing LODE, a Live OWL Documentation Environment, which is used for representing the Cross Referencing Section of this document and Daniel Garijo for developing Widoco, the program used to create the template used in this documentation.