The application behind the API may be implemented using object attribute naming conventions and other considerations which may be in conflict with conventions of JSON API. Specific example can be found in #361, so I am not repeating it here.

If no solution to the general problem described in #361 can be attained for one reason or another, I would like to propose to at least change the name of the mandatory API resource attribute id to something else. The best candidate I can think of is identifier. It does not seem to compromise on anything: one word, no artificial prefixes, the meaning is exactly what is expected. I believe that 2 vs 10 characters is not a crucial argument for a format designed primarily for machines.

Less suitable options I can think of are key and handle.