...
Developers
- ...
Issue Reporters
- A. Soroka
- Unknown User (acoburn)
- Andrew Woods
- Bethany Seeger
- Unknown User (daniel-dgi)
- David Wilcox
- Esmé Cowles
- Jared Whiklo
- Justin Coyne
- Longshou Situ
- Michael Durbin
- Mohamed Mohideen Abdul Rasheed
- Monika Mevenkamp
- Nick Ruest
- Osman Din
- Peter Eichman
- Ralf Claussnitzer
- Rob Sanderson
- Steven Anderson...
Summary
The Fedora 4.5.0 release furthers several major objectives:
...
One of the technical priorities [95] 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 corresponding technology compatibility kit [106] (TCK) would be able to indicate if any Fedora implementation fulfills or diverges from the specification. With this in mind, several issues were addressed in this release that clean up Fedora's RESTful interaction and tease out the non-core aspects of the Fedora ontology [117].
| Expand | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||
|
...
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 [128]" upgration utility, the most notable of which is enabling the utility to optionally be configured with authorization credentials.
...
- Human-readable serialization to disk: A new component has been added to the suite of Apache Camel recipes that can be employed to react to updates in the Fedora repository by writing the resource RDF (and optionally the binaries) to a specified location on disk. This feature is now available in the Fedora Vagrant box.
- Backup strategies: By default, the database that Fedora currently is configured to use is LevelDB LevelDB [9]. This release includes documentation and recommendations for performing backup and restore of internal data Fedora uses in maintaining state.
...
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 includes an update to the Fedora-related Apache Camel-based [1310] toolbox introducing the ability to configure the LDP 'Prefer' header that is used when requesting RDF to be indexed in an external triplestore.
...
Following the initial implementation of the Web Access Control [1411] authorization module, this release furthers that effort with several fixes and improvements. Enhancements include:
WebACLs can now apply to binary resources
An HTTP header, 'On-Behalf-Of', can optionally be configured to offer delegated authorization (documentation [12])
- A WebACL can be placed on the server acting as the final backstop for authorization decisions for resources that have no other effective WebACL (documentation [13])
- WebACLs can now include references to 'agentClass' Fedora resources as defined in the Web Access Control specification [14]
- An HTTP 'Link' header is included in responses to protected resources pointing to the effective WebACL
Additional documentation of Fedora's implementation of Web Access Controls is available on the wiki [15].
| Expand | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||
|
...