Versions Compared

Old Version 11

changes.mady.by.user David Wilcox

Saved on

compared with

New Version Current

changes.mady.by.user Andrew Woods

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The Fedora 4.4.0 release furthers several major objectives:

  • Tighten the definition of the RESTful application programming interface (API)
  • Further align this API to community standards, including the Linked Data Platform [3] (LDP) and Web Access Control [4] (WebAC)
  • Improve tooling for legacy Fedora repositories to Fedora4
  • Improve tooling for external services live in the ecosystem around the repository
  • Fix bugs

Excerpt
Note

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:

  • HTTP GET requests on descriptions of NonRDF resources (i.e. binaries) now return RDF triples that all have the NonRDF resource as the subject, whereas previously the returned RDF contained a mix of subjects in the response: some subjects were the NonRDF resource, some subjects were the NonRDF description resource
  • When requesting the fixity service [5] be performed on a binary resource, the "status" of the fixity result has been changed in this release from: "fedora:status" to "premis:hasEventOutcome"

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.

Expand
titleRelated JIRA ticket...

Jira
serverDuraSpace JIRA
serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
keyFCREPO-1640

Jira
serverDuraSpace JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
keyFCREPO-1746

Jira
serverDuraSpace JIRA
serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
keyFCREPO-1666

...

DuraSpace maintains a registry [7] of installations that is populated on a voluntary basis. The 4.4.0 release raises the visibility of that registry, and hopefully the likelihood that repository managers will self-register [8] in it, by adding a link on the Fedora installation spashsplash-page requesting exactly that.

...

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 corresponding technology compatibility kit [10] (TCK) would be able to indicate if the any Fedora implementation fullfills fulfills or diverges from the specification. With this in mind, several issues where were addressed in this release that clean up Fedora's RESTful interaction and tease out the non-core aspects of the Fedora ontology [11].

...