Open Certiman opened 3 months ago
Note that this was currently solved in ERA5.0.0 with era:previousAuthorisation
and era:previousRegistration
, but I find this suboptimal.
Note that this was currently solved in ERA5.0.0 with
era:previousAuthorisation
andera:previousRegistration
, but I find this suboptimal.
Indeed, it will be better to reuse PROV-O for provenance... Let see also if we can reuse the https://www.w3.org/TR/prov-o/#Activity
Challenge
The ontology must cover for the following use case (using ERA example):
The link between the Vehicle to its most recent VehicleRegistration / Authorisation is updated in both cases, but the information captured in the original RegistrationCase/AuthorisationCase remains valid if unchanged.
We therefore need a link between vp:Case's, for instance using PROV-O.
This way certain properties of a vehicle are updated links to the most recent vp:Case scope-data.
Example
The query for the actual VehicleType of the Vehicle is based on the link with the registration(Case):
For an historical overview of all the types, it suffices to have: