jpadfield / cidoc-crm.examples

Example diagrams showing how the CIDOC CRM (http://www.cidoc-crm.org/) can be used to model information for Heritage Science.
https://jpadfield.github.io/cidoc-crm.examples/
4 stars 1 forks source link

Selecting CRM classes #5

Open jpadfield opened 4 years ago

jpadfield commented 4 years ago

https://github.com/jpadfield/cidoc-crm.examples/blob/91a5c277088dc9cd912c2e3df587bf1dcc831a9f/models/production/production-triples.csv#L37-L38

For this example we have a production event carried out by a person. But it is possible that a production event could have been carried out by a E21 Person or an E74 Group, so should one always use the parent class E39 Actor?

From comments originally made by @natuk

jpadfield commented 4 years ago

In this particular use case the CRM class should be defined during the definition of the person or group not during the definition of the event.

Therefore a given events could be carried out by an Actor, Person or a Group, depending on the PID chosen.

Therefore from a modelling point of view there should be no restriction beyond the event being carried out by some sort of Actor.

So any software being written to make use of this data would need to be searching for classes including Actors and their children.