...
Fedora is moving towards a tightly defined, standards-based, set of RESTful services that are supplemented with a pattern of integrating message-driven, asynchronous services for non-core capabilities. The 4.3.0 release includes several updates that move the software in that direction.
- Aligning with LDP [3] by
- Returning a 400 response when illegal triples are not persisted
- Advertising constraints in responses when an update request fails due to a repository constraint
- Showing inbound references for indirectly contained resources
- Tightening the core repository services by
- Forbidding the update of resources that are not the target of the request
- Removing the leakage of the underlying UUID to repository clients
- Allowing "mimeType" and "filename" properties to be mutable
- Moving towards full OSGi [4] deployability for runtime configuration and feature activation
- Ensuring modules are property packaged as OSGi bundles
- Ensuring modules are importing and exporting correct dependencies and services
- Creating a Fedora features.xml for dependable deployment into Apache Karaf [5]
- Enhancing external services with the Apache Camel [6] integration framework by
- Adding a "reindex" endpoint
- Adding a "fixity" invocation service
- Adding support to the REST API for the JSON-LD "Accept" header "profile" parameter
...
A primary focus of the ongoing Fedora effort is to facilitate the upgrade/migration of Fedora3 repositories to Fedora4. To those ends, a number of improvements have been incorporated into the "migration-utils [7]" upgration utility.
- Packaging the utility as a standalone executable application
- Using opaque identifiers for migrated resources
- Adding support for user-provided RDF namespace mappings
- Providing specific mappings of Fedora3 to Fedora4 properties
- Improving support for migrating resources with non-existent datastreams
...
After the completion of the Audit Service [8] sprints this spring, there remained two items to be completed:
...
- Cleaning the Fedora ontology [9] by removing the obsolete "fedora:Blanknode" class
- Creating a JSON-LD @context file for the Portland Common Data Model [10] ontology
| Expand | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||
|
...
The Fedora Java Client library [11] was updated for this release by
...
| Expand | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||
|
References
| No Format |
|---|
[1] https://wiki.duraspace.org/display/FF/Downloads [2] http://docs.fcrepo.org [3] http://www.w3.org/TR/ldp/ [4] http://www.osgi.org/Technology/WhatIsOSGi [5] http://karaf.apache.org [6] http://camel.apache.org [7] https://github.com/fcrepo4-labs/migration-utils [8] https://wiki.duraspace.org/display/FEDORA43/Setup+Audit+Service [9] https://github.com/fcrepo4/ontology [10] https://github.com/duraspace/pcdm [11] https://github.com/fcrepo4-labs/fcrepo4-client |