...
Following the Audit Service PROV-O vs PREMIS guidelines, a typical event encoded in RDF would look like this:
| Code Block |
|---|
@prefix audit: <http://fedora.info/definitions/v4/audit#> . @prefix fedora: <http://fedora.info/definitions/v4/repository#> . @prefix foaf: <http://xmlns.com/foaf/0.1/> . @prefix premis: <http://www.loc.gov/premis/rdf/v1#> . @prefix prov: <http://www.w3.org/ns/prov#> . @prefix xsd: <http://www.w3.org/2001/XMLSchema#> . <event1> a prov:InstantaneousEvent, premis:Event, audit:InternalEvent ; premis:hasEventRelatedAgent "jquser"^^xsd:string, "Client Software v1.2.3"^^xsd:string . premis:hasEventType <http://id.loc.gov/vocabulary/preservationEvents/cre> ; premis:hasEventRelatedObject <http://localhost:8080/rest/55/59/ec/05/5559ec05-6ab1-4d61-905a-a5f3da360b23> ; premis:hasEventDateTime "2012-04-30T20:40:40"^^xsd:dateTime . |
External events (either directly added to a triplestore or created using the REST API in phase 2), should include the rdf:type audit:ExternalEvent to differentiate them from internal events.
Fixity events will also include the checksum generated:
...