...
- Introduction and topic summary
- Use case discussion
- Audit service should automatically record who updated which resource when and with which action.
- Audit service should be able to include/import events that were performed external to the repository.
- Audit service should be able to purge events.
- Audit service should be RDF-based, and use PATCH semantics for updates.
- PROV-O ontology may be better suited than PREMIS.
- Audit service would ideally support map-reduce-style analytics.
- Evidence of fixity checking on a "routine basis", and with logs "stored separately or protected separately from the AIPs themselves" should be available.
- Fedora 4 REST API should support dissemination of event/audit information.
- Workplan and timelines
- Testing and validation
- Questions
...