Support time validity in DV_IDENTIFIER
Raise
Analysis
Raise
Analysis
Description
Activity
Show:
Erik Sundvall September 30, 2019 at 3:15 PM
Added pull request with guidance note in specification, see
Bjørn Næss September 30, 2019 at 2:30 PM
According to the specification:
DV_IDENTIFIER is used to represent any identifier of a real thing, issued by some authority or agency.
The real thing should keep the data for validity. If you need more attributes on the entity "at hand" you might create an archetype modeling the "thing". I.e. CLUSTER, ADMIN_ENTRY
Won't Do
Details
Details
Reporter
Sebastian IancuComponents
Priority
MinorReason For Rejection
Was discussed SEC meeting 30 Sep 2019 Valencia:
- we decided the field cannot be reliably set, and should continue using CLUSTER archetypes (see I McNicoll).
Created April 18, 2018 at 1:56 PM
Updated February 14, 2024 at 1:32 PM
Resolved September 30, 2019 at 2:26 PM
For DV_IDENTIFIER sometimes we need to specify the date interval (or only a start date or an end date) when the information is considered active (valid). Currently this is done in the archetype level by using CLUSTER and ELEMENTs, but it would be easier just to have this information on the type itself. These attributes should be optional and if not filled-in they should be assumed active (perhaps by assuming them as min-date, max-date).
0..1 DV_IDENTIFIER.validity = DV_INTERVAL<DV_DATE>
NOT DONE: use CLUSTER archetypes to add in meta-data to do with data integration.