This REST API will not be implemented. The page is here an historical artifact of in-progress discussions.
Request URI: /audit:{audit_id}, /path/to/some/resource/fcr:audit, /fcr:audit Methods: GET, POST, DELETE Query Parameters: FORMAT (Optional) Output format of response, possibilities TBD. Example: Response: Returns the audit entry, including the full contents of the audit entry. Example: Query Parameters: FROM (Optional) Restricts the audit entries to those that occur after this timestamp. TO (Optional) Restricts the audit entries to those that occur before this timestamp. SCOPE (Optional) Restricts the audit entries to internal or external entries. Valid values: "internal", "external". AGENT (Optional) Restricts the audit entries to those that were created by this agent. See list of agents. TYPE (Optional) Restricts the audit entries to those of this type. See list of types. FORMAT (Optional) Output format of response, possibilities TBD. Example: Response: Returns all audit entries that meet the specified criteria, including the full contents of the audit entries. Request Headers: TYPE The type of the audit entry. See list of types. Should this be optional? DESCRIPTION (Optional) A text description of the event. Example: Query Parameters: FROM (Optional) Restricts the audit entries to those that occur after this timestamp. TO (Optional) Restricts the audit entries to those that occur before this timestamp. SCOPE (Optional) Restricts the audit entries to internal or external entries. Valid values: "internal", "external". AGENT (Optional) Restricts the audit entries to those that were created by this agent. See list of agents. TYPE (Optional) Restricts the audit entries to those of this type. See list of types. FORMAT (Optional) Output format of response, possibilities TBD. Example: Response: Returns all audit entries that meet the specified criteria, including the full contents of the audit entries. Request Headers: TYPE The type of the audit entry. See list of types. Should this be optional? DESCRIPTION (Optional) A text description of the event. Example:GET Get a single audit entry
curl "http://localhost:8080/rest/audit:12345"
DELETE Delete a single audit entry
curl -X DELETE "http://localhost:8080/rest/audit:12345"
GET Get the audit history of this resource
curl "http://localhost:8080/rest/path/to/some/resource/fcr:audit"
POST Add an external audit entry on this resource
curl -X POST "http://localhost:8080/rest/path/to/some/resource/fcr:audit"
GET Get the audit history of the repository
curl "http://localhost:8080/rest/fcr:audit"
POST Add an external audit entry on the repository
curl -X POST "http://localhost:8080/rest/fcr:audit"
2 Comments
Benjamin Armintor
I'd prefer to see, as much as possible, such a service be "plain" LDP instead of new REST endpoints. As I posted to the list, this seems more or less like a textbook example of LDPC, and I think it would be great to try to minimize departure from the existing API if we could.
Andrew Woods
Are you suggesting having new audit-LDPCs that contain audit-LDPRs? or having existing repository LDPCs contain audit-LDPRs? or something else?