search

SEMICeu / Core-Person-Vocabulary

This is the issue tracker for the maintenance of Core Person Vocabulary
15 stars 4 forks source link

Change class #10

Closed dimi-schepers closed 2 years ago

dimi-schepers commented 3 years ago

This issue can serve as the discussion forum to understand the need and use cases for the Change class and to further develop it. As taken from the Core Vocabulary specification:

Any record can only be seen as a snapshot of the data available to the publisher at a particular point in time. This is true for data related to all areas, not just people, places and businesses. The Change class is envisaged as one that captures any change in a data point. This might be a change in address, a change of name or any other update. It is likely that such a record would make it clear what data element was changed as well as when, why and by whom. This area - versioning and provenance - is a complex one that the working group hopes will be tackled by a subsequent activity as a matter of high priority.

The change relationship links a Class to a record of change in a data field associated with the Class. For example, a change of name or a person's their death. It is assumed that an inverse relationship will also be defined.

dimi-schepers commented 3 years ago

During the Core Vocs webinar dd. 2021-04-23, it was agreed that capturing changes over time are important, yet out-of-scope for the Core Vocabulary. Nevertheless, the editorial team will look into the creation of a Core Change Vocabulary, which could be useful for any registry.

GeertThijs commented 2 years ago

Change as a concept is the result of Events. Personal Events like Birth, Death, Marriage are Events relevant for Person, and Organisational Events like Foundation, Fusion etc are relevant for Organisations. Changes modeled as Events are often included in semantic models, it is History that is often left out-of-scope as it is more an implementation thing because it would easily collide with semantics. Example: on a certain moment a Person can have more than one Address, but during his lifetime he can have several Adresses as well. So it is better to keep history as much as possible out of a semantic model. Time however (eg birthdate and alike) poses no problem. And for Time there are already existing ontologies: ISO 19108 for example. Nevertheless, a Vocabulary that unambiguously defines terminology concerning History would be useful eg for implementations. Time datatypes like Moment, Interval, Period are defined in ISO 19108, but for History terminology types of time like validTime, transactionalTime etc are needed as well as terms for temporal statements like currentVersion, successiveVersions etc. See Snodgrass (2000) for more info.

EmidioStani commented 2 years ago

During the webinar of 02/12/2021 it was agreed to keep timing part outside the scope of Core Vocabularies, however new use cases can be created in: https://github.com/SEMICeu/Core-Person-Vocabulary/issues/new/choose