This release is a major release (i.e. 4.45.0 instead of 4.34.1) because there are a two several REST API 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.

4.0. The theme of these updates is the removal of JCR-related properties that have heretofore been leaked from the Fedora API in the RDF returned to users. Fedora 4 is in no way dependent on JCR, and any mention of JCR found in RESTful responses will be removed. No client code should require updating for this release unless it contains dependencies on JCR-namespaced properties.

See tickets in "Application Programming Interface" below.