REST API: DELETE /composition have response codes 409 Conflict though 412 Precondition Failed seems more appropriate

Quick question: when the previous version of the object (e.g. COMPOSITION) is not the last, we have a 409 Conflict in the spec, though that doesn’t seems to be conflict but a precondition for the operation for deleting an object.

Does someone remember why we choose 409 Conflict over 412 Precondition Failed response code?

Thanks!

UPDATE: just verified that in REST 1.0.3 the PUT /composition does have 412, though it doesn’t seem to have a check that the uid_based_id if the prefix of the If-Match value, which IMHO would be a 400.