[ ] Requires that the terminology includes semantic relations between concepts
[ ] Requires mappings between terminologies
[ ] Requires that the provenance and status metadata of mappings between concepts be accessible.
[ ] Requires coarse-grained terminologies for observable properties
[ ] Requires fine-grained terminologies for observable properties
[ ] Requires a long-term commitment to the terminology content governance
[ ] Requires a community-endorsed terminology
[ ] Requires the terminology to be discoverable (not just technically but also e.g. listed in relevant community portals or discoverable via search engines)
[ ] Requires that the terminology supports multilingual terms
[ ] Requires common minimum metadata describing the terminology
[ ] Requires definitions of the individual terms within a terminology
[ ] Requires that any underlying model used by the terminology be described and accessible
[ ] Requires the provenance properties of individual terms to be documented in a standardized way
[ ] Requires examples of usage of the terminology to be available and documented
[ ] Requires the terminology to be accessible programmatically
[ ] Requires deprecated term status and deprecation policy
[ ] Requires tools supporting annotation using the terminologies
[ ] Requires tools validating the applied terms against terminologies
[ ] Requires tools for mapping
[ ] Requires a mean to manage alternative notations
Data mining and AI
Discovering patterns in large data sets
Corresponding user stories
Requirements identified in the spreadsheet (and open for discussion)
last updated: 2020-09-21