Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Selecting CRM classes #5

Open
jpadfield opened this issue Feb 18, 2020 · 1 comment
Open

Selecting CRM classes #5

jpadfield opened this issue Feb 18, 2020 · 1 comment

Comments

@jpadfield
Copy link
Owner

jpadfield commented Feb 18, 2020

ngo:002-0432-0000 crm:P14.carried out by ng:0QCD-0001-0000-0000 ePID@@aPID
ng:0QCD-0001-0000-0000 crm:P2.has type crm:E21.Person

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
Copy link
Owner Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant