From Andrew Woods, Fedora Tech Lead, on behalf of the Specification Editors and the Fedora Leadership

After much discussion and iteration, the initial public working draft of the Fedora API Specification is now available for broader public review.

As described in the specification charter [1], this specification is designed to:

  1. Define the characteristics and expectations of how clients interact with Fedora implementations

  2. Define such interactions such that an implementation’s conformance is testable

  3. Enable interoperability by striving to minimize the need for modifications to client applications in order to work with different implementations of the Fedora API specification

The core HTTP and notification services defined in this specification are listed below, along with the associated standards from which they are derived:

  • Resource Management (Linked Data Platform)

  • Resource Versioning (Memento)

  • Resource Authorization (Web Access Controls)

  • Notifications (Activity Streams)

  • Binary Resource Fixity (HTTP headers)

This announcement for public comment on the initial working draft marks the beginning of a projected four-month period within which time we are targeting the graduation of the specification to “candidate recommendation”. Minimum requirements for transitioning to a candidate recommendation include:

  • Specification compliance test suite

  • Two or more implementations of the specification

  • No unresolved, outstanding critical issues, as defined by the specification editors [2]

This initial working draft specification is broadly in line with the current community implementation of Fedora 4.7.x, although there are a number of differences. Certain features have been made optional in the draft specification, and Batch Atomic Operations have been split off into a separate specification. We seek community feedback on the balance between features that are optional or required to comply with the specification.

Please contact the Fedora Community [3] or Fedora Specification Editors [4] with any general comments or if you would like to participate in implementation and/or test suite sprints. Any comments on details of the specification, itself, should be posted as GitHub issues [5].







Leave a Reply

Your email address will not be published. Required fields are marked *