Release date: 21 January, 2016
We are proud to announce the release of Fedora 4.5.0.
The Fedora 4.4.0 release furthers several major objectives:
This release is a major release (i.e. 4.4.0 instead of 4.3.1) because there are a two updates that are not strictly speaking backwards compatible with 4.3.0:
Although not a backwards incompatible update in the 4.4.0 release, it should be noted that the Import and Export services [6] have been deprecated due to their reliance on a JCR serialization versus an RDF-centric approach. These services will be supplanted by externalized machinery that transacts in RDF. |
One of the technical priorities [9] of Fedora is to define a well-specified application programming interface (API) against which client applications can be written and future server-side implementations can be created. This Fedora API should be clear and detailed enough such that a cooresponding technology compatibility kit [10] (TCK) would be able to indicate if the any Fedora implementation fullfills or diverges from the specification. With this in mind, several issues where addressed in this release that clean up Fedora's RESTful interaction and tease out the non-core aspects of the Fedora ontology [11].
Fedora is a Linked Data Platform (LDP) server implementation. This release fixes a few bugs that relate to the interactions that an LDP client should expect.
A primary focus of the ongoing Fedora effort is to facilitate the upgrade/migration of Fedora3 repositories to Fedora4. To this end, a couple of improvements have been incorporated into the "migration-utils [12]" upgration utility.
|
One of the exciting capabilities that Fedora enables is the creation of distributed, asynchronous, message-driven services that are external to the core repository but are triggered by repository events. This release further improves the deployment and runtime configurability of the Fedora-related Apache Camel-based [13] features.
A significant community success that is found in this release is an initial implementation of an Web Access Control [14] authorization module. This authorization module enables the establishment of access policies modeled as linked data. This feature was initiated, planned, designed, and implemented by a group of community stakeholders.
Numerous refactorings, bugfixes, and clean-up tasks were addressed in this release:
[1] https://wiki.duraspace.org/display/FF/Downloads [2] http://docs.fcrepo.org [3] http://www.w3.org/TR/ldp/ [4] http://www.w3.org/wiki/WebAccessControl [5] https://wiki.duraspace.org/display/FEDORA44/RESTful+HTTP+API+-+Fixity [6] https://wiki.duraspace.org/display/FEDORA44/RESTful+HTTP+API+-+Export+and+Import [7] http://www.duraspace.org/registry/fedora [8] http://www.duraspace.org/register-repository [9] https://wiki.duraspace.org/display/FF/2015+-+2016+Technical+Priorities [10] https://en.wikipedia.org/wiki/Technology_Compatibility_Kit [11] http://fedora.info/definitions/v4/2015/07/24/repository [12] https://github.com/fcrepo4-exts/migration-utils [13] http://camel.apache.org/ [14] http://www.w3.org/wiki/WebAccessControl |