Hello Fedora Community,
The Candidate Recommendation of the Fedora API Specification is now available for public review.
https://fedora.info/specAs described in the 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)
* Extended Binary Resource Operations
** Fixity (HTTP headers)
** Referenced Content via message/external-body Content-Type
This announcement for public comment on the Candidate Recommendation marks the beginning of a projected two-month period within which time we are targeting the release of the full Recommendation. Minimum requirements for transitioning to releasing the 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]
Please contact the Fedora Community [3] or Fedora Specification Editors [4] with any general comments. Any comments on details of the specification, itself, should be posted as GitHub issues [5].
Regards,
Andrew Woods (on behalf of the Specification Editors and the Fedora Leadership)
[1]
https://github.com/fcrepo/fcrepo-specification/wiki/Fedora-API-Specification-Charter#fedora-api-specification-charter[2]
https://github.com/fcrepo/fcrepo-specification/wiki/Fedora-API-Specification-Charter#editorial-team-membership-and-selection[3]
fedora-c...@googlegroups.com[4]
fedora-specifi...@googlegroups.com[5]
https://github.com/fcrepo/fcrepo-specification/issues