Cost for activity

[azaroth42]

Activities do not allow for dimensions without the use of CRM-Sci's ObservableEntity.

The typical way we have to assign a price is to use a MonetaryAmount as a dimension ... meaning that we can't give a price to an activity. We avoided this for auctions by associating the prices not with the activity but with the set of objects being auctioned, which is 1:1 with the activity of auctioning the set, however that doesn't work in other cases.

Use case: We want to assign a ticket price for attending a performance.
Use case: We want to assign a ticket price for attending an exhibition.
Use case: We want to assign a cost for an agent carrying out a service.

Possible route forward: Use the Observable Entity class from CRM Sci ... however it mints a new dimension relationship, O12_has_dimension. This would be a breaking change to require everyone to swap from using P43_has_dimension.

Other options should be explored to see if there is a backwards compatible approach.

[clarisseb]

not sure this is the best solution but we gave it a try attaching a set to a theatre production : https://github.com/stage-to-data/linked-art-pa/blob/main/examples/Absalom/Set.json
This solution allows also to document the duration of the activity (the timespan is used for the dates in our case)