Bug #472
closedEvent and actor: wrong domain E5 for P14
Description
Done
- don't allow changes of class
- E5 to E7
- P22/23 are only selectable if class of event is E8
- only allow actor activity p11 for event destruction
- update schema
Solved with solution 2
- wrong domain E6 for P14 (performed at a destruction)
tricky thing... Actually it should be possible to link an actor with a destruction (as performer) but it isnt... Working on this
on the other hand one can link an actor with the production E12 as it is a subclass of E11 which is a subclass of E7 (activity)
problem is that production should have the same status as destruction but destruction is not a subclass of activity
Suggestion 1 (dirty): We ignore this and allow E6 with p14
Suggestion 2 (clean): We link actors to E6 with p11
Question: the cidoc wiki says that if the destruction is performed by actors and done on purpose then it is an E6 and E7 at the same time
How is this meant? How can we implement this?
Solved because of immutable class
- what should happen if an E8 (Acquisition) event with P22/23 relations is updated to another class, e.g. E6? The system only checks creating of links so there would be no error and the P22/23 relations would still be existing.
also tricky... some suggestions:
1. alert if this happens and ask if the P22 etc. links should be deleted
2. lock the class of a E8 event once there is a P22 or similar link
Description
wrong domain E5 for P14
solution: we do not use E5 but E7 (Activity). It goes with P14
Also: wrong domain E5 for P22 ...
solution: we allow P22 only with E8 (same with E23) and P22/23 are only selectable if class of event is E8
Happens when trying to add an actor to an event (E5) and defining his activity as e.g. performed.
I'm not sure about that but domain for P14 is E8 which is a grandchild of E5 and I assume one can't link the grandparent.
as E8 is a subclass of E7 it should be possible to link a person via P14 to an E8 event, for example as the "Master of Ceremony" that confirms the Aquisition
If this is not possible we could fix it with only allowing legitimate activity for the event class.