ontology

KO | EN

gitlite — search

#python #java #python3 #arduino #golang #machine-learning #rust #html #flask #javascript #seismology #nodejs

★ 11 Open GitHub ↗

The Health IT Ontology.

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# HITO—The Health IT Ontology

[![build](https://github.com/hitontology/ontology/actions/workflows/build.yml/badge.svg)](https://github.com/hitontology/ontology/actions/workflows/build.yml)
[![SHACL status](https://github.com/hitontology/ontology/actions/workflows/shacl.yml/badge.svg)](https://github.com/hitontology/ontology/actions/workflows/shacl.yml)
[![License: CC0](https://img.shields.io/badge/license-CC0-blue)](https://raw.githubusercontent.com/hitontology/ontology/master/LICENSE)
[![DOI](https://zenodo.org/badge/207314773.svg)](https://zenodo.org/badge/latestdoi/207314773)

The source of truth for HITO, excluding software products and related attributes, whose source is the database initially filled by <https://github.com/hitontology/database>, and catalogues, which are created in spreadsheets and transformed using <https://github.com/hitontology/csv2rdf>.

To create a combined file, execute the `build` script, which creates `/dist/hito.ttl` and `/dist/hito.nt`.
This file can then be uploaded to the HITO SPARQL endpoint:

1. Login to <https://hitontology.eu/conductor/>
2. Delete graph http://hitontology.eu/ontology at Linked Data -> Graphs -> Graphs
3. Upload the file at Linked Data -> Quad Store Upload to the graph <http://hitontology.eu>

Warning: This will not include updated software products from the database.

## Documentation
[Download WIDOCO](https://github.com/dgarijo/Widoco/releases) and make it available as `widoco`, then run `./scripts/doc` under Linux to generate the ontology documentation and open `/tmp/doc/index-en.html`.
Automatically built and published to <https://hitontology.github.io/ontology/>.
Adapt the `doc` script accordingly on other operating systems.

## List of files

The relevant DBpedia and SWO resources are put under version control in the dist folder to keep the referential integrity of the database.
You do not need to regenerate them but if you do, using `/scripts/dbpedia` and /scripts/sparql

## Import software products from the database
See <https://github.com/hitontology/database>.

## Import catalogues
See <https://github.com/hitontology/csv2rdf>.

## Validation
While syntactic validation can be done using `rapper -c`, syntactically correct data may still violate the HITO ontology or the HITO diagram including cardinalities.

### Quality Check
The [HITO Quality Check Tool](https://hitontology.eu/qualitycheck/) contains custom error and warning categories based on SPARQL queries.

### SHACL
SHACL shapes including cardinalities for closed-world validation are included in `shacl.ttl`.
Validate using `scripts/shacl`.
Requires [pySHACL](https://github.com/RDFLib/pySHACL) to be installed and available as `pyshacl`, for example via `pip install pyshacl`.

## Build

The `build` Linux shell script combines the ontology and all instances into a single file `./dist/hito.ttl`.
It requires the [Redland Raptor RDF syntax parsing and serializing utility (Rapper)](https://librdf.org/).

## Docker

Executes the `build` script and deploys it into the `/ontology/dist` volume.
Used in the [docker compose setup](https://github.com/hitontology/docker).

## License

HITO is dedicated to the public domain using Creative Commons Zero v1.0 Universal, see [LICENSE](LICENSE).

However, a small amount of SNOMED CT terms are used with special permission from SNOMED in <http://hitontology.eu/ontology/Snomed>.
Another exception is <https://hitontology.eu/ontology/WhoDhi1-0>, which references the WHO Classification of Digital Health Interventions v1.0, which is licensed under the [Creative Commons Attribution-NonCommercial-ShareAlike 3.0 IGO Licence (CCBY-NC-SA 3.0 IGO)](https://creativecommons.org/licenses/by-nc-sa/3.0/igo/).

Licensee agrees and acknowledges that HITO may not own all right, title, and interest, in and to the Materials and that the Materials may contain and/or reference intellectual property owned by third parties (“Third Party IP”).
Acceptance of these License Terms does not grant Licensee any rights with respect to Third Party IP.
Licensee alone is responsible for identifying and obtaining any necessary licenses or authorizations to utilize Third Party IP in connection with the Materials or otherwise.
Any actions, claims or suits brought by a third party resulting from a breach of any Third Party IP right by the Licensee remains the Licensee’s liability.

ontology

Explore Similar Repositories

Was this content helpful?

Recent Feedback

Download README