...

1. Requirements:
   1. Check fixity of binary resource(s) by comparing computed value with stored value
   2. Check fixity of binary resource(s) given a specific set of Fedora object rdf:types
   3. Persist results of fixity check
      1. In log file?
      2. In database?
      3. In Fedora?
2. Scheduled fixity service:
   1. Probably not part of the core
   2. Run as a separate service (see: Riprap)
   3. Potentially implemented as a circular queue of Fedora resources, ordered by "last fixity check" date property on Fedora resource
3. Retain "fedora:hasFixityService" triple or header
4. At the OCFL-level, interest in providing fixity over an OCFL storage hierarchy

Query service

1. Should also consider this "Query Service Specification"
2. Proposal: Query service / endpoint should support the following queries:
   1. List all resources
   2. List resources by mimetype
   3. List resources by parent
   4. List resources by mimetype, parent, and modified date (<>=)
   5. List resources where modified  <> x date
3. Open questions around scope of resources to be searchable
   1. Fedora resources?
   2. Resources defined in RDF documents within the repository?
   3. Hash URIs?
4. Open questions around properties to support
   1. Server-managed triples?
   2. All properties?
5. Triplestore not necessarily required

...