Inconsistency between publishing geography and policy

[d-koppenhagen]

Currently there is an inconsistent behaviour between the geography and policy author APIs when publishing a policy/geography:

• PUT for geography/geographies/{ID}/publish
• POST for policy/policies/{ID}/publish

This behaviour should be unified.

[jschirrmacher]

Best would be, in my opinion, to have a route POST policy/policies/{ID}/versions (same for geographies, as you might have expected).

My reasons:

• We create a new version of the resource identified by the ID in the path.
• The versions of a resource are resources themselves.
• Resources in REST paths are normally specified as plural.
• The POST method is intended to create new resources.

However, to keep the change small, I would at least expect both services to use POST with .../publish. This might not quite be resource oriented (rather invoking a command, which is not REST, but RPC), but at least it is symmetric.

[avatarneil]

Cc. @janedotx