Skip to content

Repository files navigation

OntoUML/UFO Catalog

OntoUML/UFO Catalog logo

The OntoUML/UFO Catalog is a curated collection of conceptual models for research and reuse. These models describe concepts and relationships in domains such as trust, services, or software; they are not collections of observations about individual objects. OntoUML is a conceptual modeling language based on the Unified Foundational Ontology (UFO), a foundation for describing categories and relationships in models.

Also known as the FAIR Model Catalog for Ontology-Driven Conceptual Modeling Research, the catalog supports empirical research into why, where, and how modeling approaches are used. It brings together models from different domains, purposes, and levels of modeling experience as structured, machine-processable material. Curation and automated checks do not guarantee every model's semantic quality or suitability for a particular use.

I want to… Start here
View or download a model Using models — choose PNG, VPP, JSON, Turtle, or a complete source snapshot
Reuse or cite the collection Citation guidance and existing license statements
Submit a model or report a problem Contribution and support guide
Understand the formats and validation limits Technical overview
Run repository maintenance tools Script index and setup

Important

Current source of catalog data: This GitHub repository is the catalog's actively maintained and regularly updated storage, distribution, and contribution layer. The separately operated FAIR Data Point (FDP) has not been updated since its initial release, is currently outdated, and has no planned update or synchronization work at this time. Use this repository and its releases for current catalog content. See the documentation index for the full reader paths.

Note

Community dashboard: The existing catalog dashboard is a community-contributed companion project that provides another view of the catalog. It is independently operated, is not an official component of the OntoUML/UFO Catalog, and may lag behind the maintained GitHub repository. It remains linked here in recognition of that contribution.

Table of Contents

Catalog’s Content

Data Organization

Each direct folder under models/ contains a model and its available representations. Folder names commonly combine an author, year, or model name; read metadata.yaml for the actual description and sources.

Author-maintained inputs Generated and committed outputs
ontology.vpp and its ontology.json export ontology.ttl, generated from JSON using the pinned converter and metadata language
metadata.yaml Model-level metadata.ttl, retaining existing catalog-managed identifiers/values and aggregating distribution links
original-diagrams/*.png and/or new-diagrams/*.png Per-image metadata-png-o-*.ttl / metadata-png-n-*.ttl sidecars
Model source files and metadata metadata-vpp.ttl, metadata-json.ttl, and metadata-turtle.ttl, describing the corresponding file distributions
Optional references.bib No generated bibliography; validated when supplied
Root catalog.yaml, together with generated model metadata Root catalog.ttl, containing catalog metadata, membership, and derived contributors

The native project is created or reconstructed in Visual Paradigm. The OntoUML Plugin for Visual Paradigm provides a JSON export route; repository automation does not perform VPP-to-JSON export. Contributors keep these representations consistent. Original diagrams retain the authors' representations, including images from publications; new-diagrams/ contains Visual Paradigm recreations.

Generated metadata can preserve existing RDF identities, curated fields, and dates; regenerating it is not simply converting YAML from scratch. The technical input/output map explains dependencies and the difference between a model, a distribution, and its metadata.

The shapes/ directory stores SHACL constraints for resource, dataset, catalog, semantic-artefact, and distribution metadata. Current repository workflows do not run a SHACL validation engine; see what validation establishes.

Catalog Releases

Repository releases use date tags in YYYYMMDD form. Each attached ontouml-models-YYYYMMDD.ttl asset aggregates eligible model and metadata RDF; it is not an archive of native projects, JSON, images, or bibliographies. Use the release's Source code (zip) or Source code (tar.gz) for the complete tracked snapshot. See download instructions and a pinned example, GitHub Releases, and the release operator guide.

Data Schemas

The OntoUML Schema specifies a JSON representation; the OntoUML Vocabulary supplies RDF terms. Both relate to the implementation-independent OntoUML Metamodel, but this repository's JSON-to-RDF conversion is not guaranteed lossless. Read the conversion limits and independent version information before choosing a representation.

OntoUML Metamodel

The OntoUML Metamodel describes model elements independently of a particular serialization. It focuses on UML class-diagram features relevant to OntoUML, simplifying their representation for software manipulation and exchange.

OntoUML Schema

The OntoUML Schema specifies the JSON representation used for model exchange and programmatic processing. Repository automation parses JSON and checks selected conversion rules; it does not run a full JSON Schema validation engine or demonstrate every external modeling service's behavior.

Models in Linked Data

RDF represents model content as a graph; Turtle is the text syntax used for the stored RDF files. Loading a model or release into an RDF library or graph store enables analyses such as pattern detection and statistical queries. SPARQL is a query language for RDF and requires a query-capable tool; downloading Turtle alone does not provide a query interface. See the format chooser.

Metadata

Metadata overview showing a catalog, model datasets, their file distributions, and descriptive links. The technical overview explains the relationships and known constraint differences.

Note

This image is a conceptual overview, not the current normative validation specification. A text explanation and constraint comparison documents differences from the stored shapes and the separate YAML authoring rules.

Catalog metadata reuses classes and properties from the following RDF/OWL vocabularies:

As we could not satisfy the metadata needs of our stakeholders using the existing vocabularies alone, we complemented them with one of our own authorship, the OntoUML/UFO Catalog Metadata Vocabulary.

The OntoUML/UFO Catalog Metadata Vocabulary was created to satisfy the metadata needs of the OntoUML/UFO Catalog, complementing the catalog's schema with properties to improve the findability and reusability of the catalog and its models. The vocabulary's content can be accessed through the following links:

The OntoUML/UFO Catalog Metadata Vocabulary's elements are identified below by the prefix ocmv.

FAIR Data Point: The Data Discovery Service

The OntoUML FAIR Data Point is the catalog's separately operated discovery service, based on the FAIR Data Point approach to exposing rich metadata.

Important

The FDP has not been updated since its initial release and does not represent the current catalog state. No FDP update or synchronization work is currently planned. The GitHub repository remains actively maintained and is the authoritative source for current files, metadata, history, contributions, and releases. See the responsibility boundary.

Catalog's Persistent URLs

Persistent entry points are listed below. A stable URL is not necessarily an immutable snapshot; record a release tag and commit for reproducible use.

Resource Persistent entry point
FDP catalog page (currently outdated) Catalog discovery
GitHub repository Repository
OntoUML vocabulary OntoUML
Latest catalog release Latest release
Specific catalog release https://w3id.org/ontouml-models/release/<release_tag> — substitute a date tag; for example, 20230602
Catalog Vocabulary Turtle Catalog metadata vocabulary
Metadata shapes Catalog, Dataset, Distribution, Resource, SemanticArtefact

How to Contribute

Your contribution is fundamental to the catalog's success. We highly encourage authors to submit their models and tools to this catalog. With that, you will be supporting research in (ontology-driven) conceptual modeling, ontology engineering, software design, and several others.

We greatly appreciate your contribution to this project!

Start with the contribution and support guide for routes, required inputs, metadata guidance, and the review checklist.

Contribute by Submitting an Ontology

The easiest way to contribute to this catalog is to simply send us the following:

  1. your ontology model project;
  2. the model's metadata information; and
  3. the model's associated bibliography (when available).

If you wish to contribute to this initiative by submitting your ontology, use the catalog's contribution form.

Note

Anonymous ontologies are allowed in the catalog. If you do not want your name to be displayed in your ontology's metadata, inform us and we will keep the model's authorship anonymous. In that case, you must be the owner of the ontology's legal rights.

If you wish to contribute by submitting someone else's ontology, consult the "Not Started" or "Started" sheets in the List of UFO and OntoUML Ontology Models. The Started sheet may identify an existing working branch; confirm the current entry and branch with an administrator before duplicating work.

For providing high-quality data, submissions are required to comply with the defined rules to be accepted as part of the catalog. If you have any questions about submitting new models or reusing those available in this catalog, please create an issue.

For a repository submission, prepare one model folder directly under models/ containing:

  • metadata.yaml, the manually maintained source for the model's descriptive metadata;
  • ontology.vpp, the native model project;
  • ontology.json, the model's JSON export and the source of truth for its RDF graph;
  • at least one valid PNG diagram directly inside original-diagrams/ or new-diagrams/;
  • optionally, references.bib.

Keep the JSON export consistent with the native project; VPP-to-JSON export is not automated by the catalog. Do not add a manually generated ontology.ttl or edit generated Turtle to change the model: update ontology.json instead.

Important

Automatic submission processing requires a branch in the same repository as the PR's target. Fork-based PR writeback is not supported. Contributors without branch access can use the contribution form above or contact a catalog administrator.

For a normal same-repository PR, automation validates the sources, generates ontology.ttl, synchronizes distribution and model metadata, updates root catalog.ttl, and commits changes back to the PR branch. This can include normalized metadata.yaml, with comments or formatting changed, as well as generated files. A synchronized rerun creates no additional commit. A curator reviews the resulting PR before merging it; automated checks do not establish semantic quality or rights clearance. See the submission workflow guide for the exact processing order, warnings, failure behavior, and local validation commands.

Other Ways to Contribute

If you wish to contribute to this initiative by creating and reporting an application for the catalog, please inform us through the catalog's contribution form or create an issue.

If you find any problems in the repository or have ideas for its improvement, please let us know through the catalog's contribution form or by creating an issue.

Relevant Associated Works

The list of works that use the data provided by the OntoUML/UFO Catalog to test algorithms and perform other tasks grows over time. Instead of keeping a manual list in this document, we recommend you access its Google Scholar and ResearchGate citation lists for updated information.

Catalog administration

The OntoUML/UFO Catalog is maintained by the Semantics, Cybersecurity & Services (SCS) Group of the University of Twente, in The Netherlands. Its principal administrators are:

Feel free to get in contact with the administrators using the links provided. For questions, contributions, or to report any problem, you can open an issue at this repository.

How to Cite this Catalog

Please cite the OntoUML/UFO Catalog as:

  • Prince Sales, T., Barcelos, P. P. F., Fonseca, C. M., Souza, I. V., Romanenko, E., Bernabé, C. H., Bonino da Silva Santos, L. O., Fumagalli, M., Kritz, J., Almeida, J. P. A., & Guizzardi, G. (2023). A FAIR catalog of ontology-driven conceptual models. Data & Knowledge Engineering, 147, 102210. https://doi.org/10.1016/j.datak.2023.102210. Permanent URL: https://w3id.org/ontouml-models/.

For creating citations using different formats, refer to the webpage of the paper's publisher for getting the paper's complete information.

For obtaining the paper's complete BibTeX record, use the citation export options available on the same webpage.

This paper reflects the state of the catalog as of June 2022.

Machine-readable citation metadata is available in CITATION.cff. Also record the snapshot and cite individual model sources when reporting your research.

Acknowledgements

We would like to thank all the contributors to the OntoUML/UFO Catalog, as well as all the modelers who shared their work and allowed us to include it here.

License disclaimer

Caution

Existing rights statements may have incomplete or inconsistent coverage, including differences between model YAML and retained RDF metadata. Consult the statements below, LICENSE, and the relevant model metadata and original sources; seek clarification from the catalog administrators where necessary. This caution does not resolve those differences or determine which statement controls.

The OntoUML/UFO Catalog is licensed under the Creative Commons Attribution-ShareAlike 4.0 International Public License.

Although the OntoUML/UFO Catalog is an open project with a permissive license, special attention must be given to the following licensing clauses:

  • The OntoUML/UFO Catalog is a noncommercial work created strictly for academic research purposes.
  • This license only applies to the catalog structure itself, not to the models included in the repository.
  • Information about licensing of individual ontologies included in the catalog can be found on their related metadata.yaml file.
  • The models included in the repository were obtained directly from the authors or academic sources using open or valid licensed access.
  • This license by no means overwrites the license of the models included in the repository, which maintain their original license.
  • All catalog ontologies that are without explicit licensing information on their associated metadata.yaml file must be interpreted as being private and having a restrictive license.
  • License holders sending their models to the OntoUML/UFO Catalog expressly agree that the sent content is going to be hosted and made available for other users in the terms of this license.
  • Whoever uses the OntoUML/UFO Catalog expressly understands and agrees with its licensing information.

Ontologies are going to be immediately removed from the catalog in case of a request by the original license holders. For content removal, please create an issue or report it through the catalog's contribution form.

About

A curated, versioned collection of OntoUML and UFO conceptual models for research and reuse, with native files, JSON, RDF/Turtle, diagrams, and metadata.

Topics

Resources

Stars

82 stars

Watchers

10 watching

Forks

Releases

Contributors

Languages