...
CRUD / LDP
Versioning
Fixity
Transmission Fixity
- Summary: No change.
- Modeshape impl: Add a Digest header to content uploads. The server compares the digest to the uploaded content's digest, and if they do not match, it will discard the content and return a 409 Conflict error status.
- Spec: Same
Persistence Fixity
- Summary: The exact mechanism has changed, but the basic approach is similar.
- Modeshape impl: Add "/fcr:fixity" to the end of a binary URL (advertised in the binary description with a triple with the predicate fedora:hasFixityService). The response RDF will contain one or more triples with the predicate premis:hasEventOutcome, and the object "SUCCESS" on success, and "BAD_CHECKSUM" and/or "BAD_SIZE" on failure.
- Spec: A HEAD or GET request to a binary with the Want-Digest header triggers a fixity check. The response will include a Digest header with the computed checksum. The client will need to compare the digest to the stored value.