Skip to content

vp:Case, vp:Scope must indicate provenance #9

Open
@Certiman

Description

@Certiman

Challenge

The ontology must cover for the following use case (using ERA example):

  • An EVR-parameter for a Vehicle is updated with a new RegistrationCase.
  • The AoU for a VehicleType is extended with a new AuthorisationCase.

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

#original registration
era:veh-xyz a era:Vehicle ; era:registeredWith era:reg-xyz-0 ...
era:reg-xyz-0 a era:VehicleRegistration ; vp:submittedIn era:regcase-xyz-0-0 .... 
era:regcase-xyz-0-0 a era:RegistrationCase ; vp:concerns era:Vtype-abc ...

# registration update
era:reg-xyz-1 a era:VehicleRegistration ; vp:submittedIn era:regcase-xyz-1-0 .... 
era:regcase-xyz-1-0 a era:RegistrationCase ; vp:concerns era:Vtype-efg ...

# Update the Vehicle link at end of this Registration
era:veh-xyz a era:Vehicle ; era:registeredWith era:reg-xyz-1 ...

The query for the actual VehicleType of the Vehicle is based on the link with the registration(Case):

# Query the actual VehicleType of the Vehicle, does not require "hard-link":
?v era:registeredWith / vp:submittedIn / vp:concerns ?t ;
?t a era:VehicleType 

For an historical overview of all the types, it suffices to have:

era:regcase-xyz-1-0 prov:wasDerivedFrom era:regcase-xyz-0-0 ;

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions