New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding ontology for audit event types #24
Conversation
<rdf:type rdf:resource="http://www.w3.org/2004/02/skos/core#Concept"/> | ||
</owl:NamedIndividual> | ||
|
||
<owl:NamedIndividual rdf:about="http://fedora.info/definitions/v4/audit#derivativeCreation"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you expect #derivativeCreation and #indexing to be #ExternalEvents?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, that's the pattern I would normally expect -- though there may be some people using sequencers to effectively make these internal events.
I have little to contribute. I do find it somewhat bizarre that "derivativeCreation" and "indexing" are considered events for which one would audit a repository. I assume that there's some good reason for this, and we're not just conflating the auditing of a repository with the auditing of the larger system in which it is a component. |
I would echo @ajs6f. I don't have anything against these events, but they seem to be related to a different layer in a DAMS, distinct from the underlying repository itself. |
Yes, there seem to be two scopes at play:
The Audit Service is establishing a pattern for associating events to resources within the repository as well as at-large. Maybe we should separate the "external events" from this current effort... while still providing recipes for how integrators can push external events into the associated triplestore. |
I'm fine with removing indexing and derivativeGeneration from the ontology -- and saying that implementers can define their own local types for whatever events they want to track. |
The beauty of using Web ontology languages for this purpose is precisely that people can extend them however they want, with or without our input, if we do our job right. |
Resolved with: 53756a2 |
Addresses https://jira.duraspace.org/browse/FCREPO-1422