Description
An undisclosed Manufacturer has today expressed interest in hosting (through an API at its premises) linked data on some of his own Documented Evidence, which is vp:submittedFor a vehicle Authorisation Application (a vp:Request).
Concretely, it concerns EC Declarations, which close requirements as defined under instances of eralex:IC and eralex:SS (subsystem).
This would require an update of the Ontology:
- (extend range) :
vp:RequestingBody vp:delivers vp:DocumentedEvidence - (new property):
vp:RequestingBody vp:canClaim vp:Requirement(whilevp:AppropriateBody vp:certifies) - (SHACL-validation)
vp:canClaim ?orequiresvp:certifies ?oto be in the KG [BR: No unsupported EC Declarations]
The properties of DocumentedEvidence should maybe be made explicit and at least - from some or other existing Ontology:
- issueDate
- startOfValidityDate
- expirationDate
- an identifying string respecting some REGEXP (ERADIS for instance)
- a
rdfs:label, readable label. - a URI to the downloadable version of the file, WITH the file's checksum
- ...integrity metadata (see further)
This in order to allow a publication of a JSON-LD/RDF/TTL object which the Manufacturer can then publish at his premises for automated va-tools to access.
Important
The same mechanism should be applied by the AppropriateBodies (NBRail, etc) in order for the whole set of DocumentedEvidence to be a credible collection of data.
Caution
No unsigned sets of data should be trusted, which means all parties have to sign the content of the data objects, preferably using Verified Credentials. The Documented Evidence is then to be seen as a set of Claims.