Initiative Publications
This repository implements a structured, transparent publishing process for both the Health-RI Ontology and its SSSOM mapping sets, ensuring all artifacts are traceable, stable, and reusable, and supporting FAIR-aligned interoperability.
Publishing the Ontology
Before diving into specific files and artifacts, we first outline how ontology versions are tracked and the policy guiding version numbering.
Versioning Policy
Please refer to the Ontology Versioning Policy page for full details.
Published Artifacts
For each ontology release, the following artifacts are published — always in both ontologies/latest/ and ontologies/versioned/ folders.
-
OntoUML conceptual model (Visual Paradigm): Includes all OntoUML constructs and diagrams.
ontologies/latest/health-ri-ontology.vppontologies/versioned/health-ri-ontology-v<version>.vpp
-
OntoUML JSON export: Conforms to the OntoUML Schema.
ontologies/latest/health-ri-ontology.jsonontologies/versioned/health-ri-ontology-v<version>.json
-
gUFO OWL ontology (Turtle): OWL serialization that imports or reflects gUFO axioms.
ontologies/latest/health-ri-ontology.ttlontologies/versioned/health-ri-ontology-v<version>.ttl
-
SHACL validation shapes and derivation rules (Turtle): SHACL Core and SHACL Advanced Features graph that validates HRIO-aligned instance data and materializes safe, ontology-compatible triples.
ontologies/latest/health-ri-ontology.shaclontologies/versioned/health-ri-ontology-v<version>.shacl(viahttps://w3id.org/health-ri/ontology/v<version>/shacl)
-
Markdown documentation: Textual documentation of the OntoUML ontology.
ontologies/latest/documentations/documentation.mdontologies/versioned/documentations/documentation-v<version>.md
-
HTML specification: Documentation of the gUFO ontology.
ontologies/latest/documentations/specification.htmlontologies/versioned/documentations/specification-v<version>.html
Note
gUFO files may only generated for versions of the model that are syntactically valid. As a result, no .ttl or .shacl file may be provided for some versions that are still incomplete or under development.
Info
The version numbers of the .vpp/.json (OntoUML) and .ttl (OWL/gUFO) files are managed independently. The .ttl file includes a dcterms:conformsTo metadata relation to indicate which OntoUML version it corresponds to.
<https://w3id.org/health-ri/ontology#> dcterms:conformsTo <https://w3id.org/health-ri/ontouml-v0.3.0> .
Repository Structure
All current artifacts are made available in the /ontologies folder:
ontologies/
│
├── latest/
│ ├── health-ri-ontology.vpp
│ ├── health-ri-ontology.json
│ ├── health-ri-ontology.ttl
│ ├── health-ri-ontology.shacl
│ ├── documentations/
│ │ ├── documentation.md
│ │ └── specification.html
│ └── images/
│ └── *.png # Exported PNG images of all OntoUML diagrams
│
├── versioned/
│ ├── health-ri-ontology-vX.Y.Z.json
│ ├── health-ri-ontology-vX.Y.Z.vpp
│ ├── health-ri-ontology-vX.Y.Z.ttl
│ ├── health-ri-ontology-vX.Y.Z.shacl
│ └── documentations/
│ ├── documentation-vX.Y.Z.md
│ └── specification-vX.Y.Z.html
│
├── changelog-ontology.md
└── ...
What does 'latest' mean?
The latest/ folder always mirrors the contents of the highest published version. This provides stable, convenient access to the most recent files without needing to specify a version number.
Where are the images of the diagrams?
The images/ folder — containing exported PNG versions of all OntoUML diagrams — is only provided under the latest/ folder.
These images are always generated from the most recent .vpp file and are not versioned individually.
Archive and Change History
- Only the latest version of each artifact is visible directly in the
ontologies/latest/folder. - All previous versions are organized in the
ontologies/versioned/directory for transparency and reproducibility. - A changelog file (
changelog-ontology.md) summarizes all version changes and links them to their respective files and semantic impact.- The changelog follows the Keep a Changelog format.
- It is generated and maintained with the support of an AI-assisted tool to ensure consistency and clarity.
Looking for PID details?
The full description of all Persistent Identifiers (PIDs) — including format-specific URIs for each version — is documented separately. Access the complete description at: Persistent Identifiers.
Publishing SSSOM Mappings
This section describes the publication process for our SSSOM mapping sets (cross-ontology alignments), which follow a different versioning strategy than the ontology artifacts described above.
The SSSOM mapping set uses date-based versions in the format YYYY-MM-DD (at most one version per day).
Published mappings are append-only: existing rows are not deleted. To correct or supersede a row, add a new one using the replaces field to reference the previous record.
- SSSOM Mapping Set (TSV & TTL)
Curated cross-ontology alignments published as a tabular SSSOM set and as RDF/Turtle.
https://w3id.org/health-ri/semantic-interoperability/mappings— redirects to the TTL versionhttps://w3id.org/health-ri/semantic-interoperability/mappings/ttl— TTL versionhttps://w3id.org/health-ri/semantic-interoperability/mappings/tsv— TSV version
Tip
A human-readable version of the mappings can be accessed in this link.
Note
Both serializations of the SSSOM Mapping Set — TSV and TTL — are stored in the /mappings folder of this repository.
The redirect links above provide stable access to these files, while the folder itself contains the recorded versions.