303 status on ResourceExistsException instead of 409?

[namedgraph]

When POST requests attempts to construct a resource that already exists, we throw ResourceExistsException which currently maps to a 409 Conflict error response.

HTTP spec seems to say that 303 See Other can be used: https://tools.ietf.org/html/rfc7231#section-4.3.3