Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Do not use captital case for properties in message schema #1

Open
ts5746 opened this issue Apr 15, 2019 · 1 comment
Open

Do not use captital case for properties in message schema #1

ts5746 opened this issue Apr 15, 2019 · 1 comment

Comments

@ts5746
Copy link
Contributor

ts5746 commented Apr 15, 2019

Original internal issue suggested to follow the guidelines for REST APIs in the JSON message schema, for example: https://hackernoon.com/restful-api-designing-guidelines-the-best-practices-60e1d954e7c9

@ts5746
Copy link
Contributor Author

ts5746 commented Apr 15, 2019

In general we to comply such guidelines and conventions. However, in this case the names in the JSON message schema that are exactly as named and defined in the standard, start with a capital on purpose, namely to distinguish them from other, non-standard object names. Also, the current situation is in line with the IETF JSON specification in RFC 7159 that actually includes examples with properties using capital case.. See also this discussion: https://stackoverflow.com/questions/5543490/json-naming-convention.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant