17.3 16.1.2 Principios normativos
- A concept identifier is language-neutral and must not be derived from a display label.
- Each canonical concept must have exactly one preferred es term and one preferred en term in this release.
- A preferred term for es-MX or es-ES may differ from the neutral es term without creating a new concept.
- Aliases retrieve concepts but do not assert owl:equivalentClass or skos:exactMatch.
- A variant label is not promoted to synonym unless a curator proves identical extension and usage.
- Homonymous literals remain separate term records linked to different concepts.
- Language and region use BCP 47 tags; private-use tags require explicit governance.
- Original spelling is preserved; normalization is an index key, never the display literal.
- Case, punctuation and diacritic folding may be used for search but cannot erase meaningful distinctions.
- Regional status requires at least one attributable source and should include corpus or expert evidence.
- Machine-translated definitions remain candidates and are never published as reviewed translations.
- Deprecated terms remain resolvable and point to the preferred replacement and deprecation rationale.
- Terms for observations, phases or sensor products cannot be silently merged with movement concepts.
- Every term edit creates a revision with actor, timestamp, evidence and previous value.
- Search fallback follows locale profiles and must expose when a fallback term was shown.
- The termbase must export loss-aware projections to JSON-LD, TBX and tabular review formats.
DEBE indica requisito de release; DEBERÍA,
recomendación fuerte; PUEDE, extensión controlada.