naming-conventions.md - de-preference case

[TimGoodwill]

Update to naming-conventions.md to de-preference case, issues #23, #34, #40

Preferencing snake_case over camelCase is an odd choice, and unnecessary. Preference will largely come down to the technology stack – CamelCase for Java/JavaScript and snake_case for Python/Ruby.

In terms of common usage, the weight is with camelCase at this point in time. Several federal departments/agencies currently mandate the use of camelCase for member/field names, and camelCase has been the preference in the previous DTA API guidance, as well as current UK, WhiteHouse (US) and New Zealand API guidance. Canada specifies either camel or 'underscore' case but does not preference. CamelCase is the standard case used in JSON-API, restfulapi.net, google and Microsoft guidance and JavaScript standard convention (https://www.w3schools.com/js/js_conventions.asp).

In this edit, references to case have been reworded to remove any explicit preference of one convention over the other.
Additionally, the text has been reworded to refer to "case" explicitly, rather than 'message format', and to stress consistency.

[jordanwalsh23]

From the Victorian perspective I'm ok to proceed on this basis to de-preference the case. Whilst I do like the idea of being prescriptive, it's quite difficult to expect that all consumers will be able to adhere.

[ghost]

Agree with the update wording.

Within an API it should be consistent.

BUT to make intro easier, we need to standardise on one as the preference. Our preference is camelCase.

For QLD, with the API Graph we have consistency within the Graph using camelCase, and the more API’s to be integrated which use camelCase the less transformation that is required.