Issue 572: R34 has validity period
In the 51st CIDOC CRM & 44th FRBRoo SIG meeting, SIG members decided to start a new issue where to discuss what the appropriate model for R34 has validity period is.
Inthe 54th CIDOC CRM & 47th FRBR/LRMoo SIG meeting, Pat Riva made the proposal to deprecate R34 has validity period (also F34 Controlled Vocabulary, its domain class).
Discussion points:
R34 is too narrow, cannot be extended to other things besides a controlled vocabulary at this time. A broader conceptualization would allow to capture all the different things that come with validity periods (laws, rights, plans, observations, volatile digital objects, etc.).
Classification schemes are good examples of things that have a validity period (relates to versions etc.). The validity period does not have to be “the present”, but the validity period of the version in question.
The construct has a state-like quality to it, which seems to be clashing with the CRM-event centric approach.
Decision:
- Deprecate F34 (use E32 Authority Document) and R34 (whose domain is F34) in LRMoo
- Keep the issue open, but separate from LRMoo (i.e., link it to CRMbase & CRMdig instead). Produce a more general property for validity periods in general.
- Could also be reconsidered in the scope of CRMdig & PARTHENOS harmonization (HW for GB and group working on issue 547) –define the validity period of authority documents seen as volatile resources (undergoing continual updates)
Rome, September 2022