Encode concept relationships from diagrams

[ronaldtse]

From the diagrams given in geolexica/isotc204.geolexica.org#10, we need to link the concepts accordingly.

There are "common relationships" and "arbitrary relationships".

• Common relationships are the ones provided here: https://github.com/glossarist/concept-model/blob/master/models/concepts/RelatedConceptType.lutaml
• Arbitrary relationships are ones made up by the author as needed to express relations

Example 1

In Figure A.1.

In this image, we can see that "immaterial entity" is a specialization to "entity".

This means that:

• in the "entity" page we should display the "immaterial entity" as a specialization of it (or a "narrower concept")
• in the "immaterial entity" page display "entity" as a generalization of it (or a "broader concept")

This relies on us encoding the concept relationships (specialization of, generalization of) in the Glossarist concept YAML files.

Example 2

In Figure A.4

"functional viewpoint" is marked with a relationship called "governs" that points from "functional viewpoint" to "functional view". We then have to establish a relationship between the glossarist concepts.

Example 3

In Figure A.11

Between "interface dialogue" and "message":

• "interface dialogue" is a generalization of "message"
• "interface dialogue" has a 1...* (1 to many) relationship with "message"
• "interface dialogue" an arbitrary relationship "uses" that points from "interface dialogue" to "message"

Summary

We need to have a way to describe concept relationships in the Glossarist YAML files and the Glossarist gem.

All relationships (defined, arbitrary) should be encoded in some file e.g. relations.yaml at the root of the dataset.

In a concept dataset, we need to have a set of allowed relationships, and should not allow undefined relationships.

We should have a way to validate the concepts dataset.

[ronaldtse]

We should also have a way to draw these diagrams from the encoded relationships. For example, we can use the LutaML syntax to define views and relationships. We need to think about it.