...

1. If the same resource is modified in two different concurrent transactions, the first modification will succeed, but the second modification will fail with a 409 conflict with the following message: "Cannot update info:fedora/<id> because it is being updated by another transaction." This holds true for containers and binaries.
   1. In Fedora 5, both modifications would succeed, and whichever transaction committed last would be the final state of the object

GET Prefer return=minimal removed

It was determined that this option was not listed in either the Fedora or the LDP specification, so it was removed. To reproduce the previous behavior, you can use the following header:

Prefer: return=representation; include="http://www.w3.org/ns/ldp#PreferMinimalContainer"; omit="http://fedora.info/definitions/fcrepo#ServerManaged"