18F/api-standards

Remove recommendation to use a file extension to indicate format

konklone opened this issue · 3 comments

I suggest we remove all use of the file extension (.json) to indicate the format of an API endpoint. This was fashionable for some time in the late 2000's -- especially for APIs that support multiple output formats -- but mime types in HTTP headers handle this far better. Plus, they communicate more information, like UTF-8 encoding.

Didn't commit db3a2cb already do this?

Good catch!