search

i-adopt / requirements

Repository used for Task 3 of the I-ADOPT workplan to define terminology requirements for given use cases
0 stars 1 forks source link

G1 - Terminology generation and management #1

Closed gwemon closed 4 years ago

gwemon commented 4 years ago

This thread aims at compiling a set of requirements shared by all use cases listed as belonging to G1 (see use_case_groups)

gwemon commented 4 years ago

Requirements for G1 will need to be in tune with FAIR semantics criteria (preliminary recommendations and best practice recommendations). See https://zenodo.org/record/3707985#.XsJ1bmhKjb0

mabablue commented 4 years ago

R1. Terminology name (e.g., CF Standard Names) R2. Globally unique, persistent and resolvable Identifier for the terminology R3. Globally unique, persistent and resolvable Identifier for the terminology metadata record R4. Globally unique, persistent and resolvable Identifier for the individual terms/classes R5. Globally unique, persistent and resolvable Identifier for the individual relationship properties R6. Provide a label for each term/concept R7. Provide a description for each term/concept R8. Terminology should be published in a semantic repository or at least publicly available R9. The terminology should provide mappings to other terminologies R10. Provide a terminology access endpoint (api) R11. Collections/branches (name, url) within the terminology that will be harvested and including their relations (e.g., skos:broader, exactMatch) R12. Available provenance information (e.g. creation and modified dates) at term-level R13. Term status (e.g., accepted)

gwemon commented 4 years ago

I am closing the group issues to declutter a little - we can reopen them if/when we need them