search

glossarist / glossarist-ruby

Concept modeller in Ruby
BSD 2-Clause "Simplified" License
1 stars 1 forks source link

Enum strictness #4

Closed skalee closed 2 years ago

skalee commented 3 years ago

https://github.com/glossarist/concept-model defines many enums. For example, designation's normative status can be either preferred, admitted, or deprecated.

Zrzut ekranu 2021-05-07 o 20 37 09

Is it possible that some glossaries will require custom values for these enums? For example, normative status in glossary X limited to preferred and deprecated, whereas normative status in glossary Y extended to e.g. preferred, admitted, discouraged (instead of deprecated), obsoleted, under_review?

I'm asking because I'm going to validate data, and I wonder if allowed values can be hardcoded in glossarist gem, or maybe they should be configurable per glossary? This may have some impact on technology stack.

cc @ronaldtse @opoudjis

ronaldtse commented 3 years ago

@skalee initially we will be using an identical schema for administrative data (incl. NormativeStatus) because the users are ISO and IEC. Other organizations may be supported in the future that utilize different statuses.

ronaldtse commented 2 years ago

To add to this, yes the list of accepted statuses can differ per glossary. If they can be read through a config that would be great.