adding schema for general glossaries / term collections ??

[lzehl]

Not sure how this colliding with our controlledTerms module.

Suggestion is to offer schemas for defining systems specific glossaries / term collections.

In schema.org the glossary/collection is called DefinedTermSet that is then linked respectively from DefinedTerm.

If we stick to those names we probably want to go with the following properties (for now):

DefinedTermSet (or Glossary)

• provider (or publisher): linked_types - Organization
• license: linked_types - License (1, required) [applies to all terms associated to the term set]
• accessibility: ??
• copyright: ??
• repository: ?? (should point to where the terms are maintained)
• publication: ?? (url to online accessible glossary)

DefinedTerm (or GlossaryTerm)

• isPartof: linked_types - DefinedTermSet
• name
• synonym
• definition (or only description?)
• description
• publication: ?? (url to online accessible term or just aiming to make atid resolvable?)

@olinux @apdavison (@openMetadataInitiative/openminds-developers) please provide your feedback as soon as possible, because this needs to be set up for EBRAINS as soon as possible.

[Raphael-Gazzotti]

Sounds good! However, I wonder if incorporating properties from standards like SKOS or WordNet could enhance the representation of hierarchical knowledge (e.g., subject, broader, narrower) and allow us to define richer relationships between terms, such as antonym, hyponym, meronym, and others.