Open azaroth42 opened 4 years ago
Example:
A loan could be the intent of the provenance activity, including transfer of custody, movement of the object, payments for insurance/shipping/installation or whatever. In this case, it seems like "loan" classifies the provenance activity which has parts.
A loan could also be part of another provenance activity, such as the commission of a copy of that object. Here the loan classification would be on the transfer of custody part.
General classifications go on the top event, such as purchase/sale (because the parts make up that overall activity)
Sub events can have additional classifications, which would be more specific than the top level event's classifications
Use a meta-type to classify as "type of provenance activity".
Don't require a meta-type on sub-events if they have a classification
Time spans - Put whatever knowledge about dates at whatever level you have the knowledge. Should be consistent with parts being within the master one. If you don't know the specific details, then just put on the top event. So consumer can take the top one and check the parts if there is more specific knowledge.
Further question -- are method classifications (gift, bequeathment, etc) a technique
rather than a general classification?
eg P32 has the scope note:
This property identifies the technique or method, modelled as an instance of E55 Type, that was employed in an instance of E7 Activity.
Seems like "giving" is the method by which the item's ownership was transferred...
Pushing to 1.1 as it's backwards compatible to 1.0
We should discuss where the classifications go for provenance activities -- I believe they should all go on the top level wrapper activity, and not on the parts. For example a purchase is the activity that has the acquisition and the payment as its parts, not the acquisition which would not include the payment, or vice versa.
But are there situations when a provenance activity's parts should also have further classifications?