Better JSON standardization

Hello,

Just digging into the schema and it seems like there isn’t much standardization when it comes to property naming conventions and even some property values in the JSON schema.

To give some examples:

Naming conventions There seems like there is a good mixture of camelCase and kebab-case in properties

shortTitle vs collection-editor (okay, perhaps this only occurs once)

Property value conventions The following properties accept both type string and type number

id
issue
number
number-of-volumes
volume

The following properties only accept type string

call-number
chapter-number
citation-number
collection-number
number-of-pages
page
page-first
version

Just a friendly drop in the suggestion box for a better standardization on the next schema update 👍

[rmzelle]

Yeah, good call.

For shortTitle, this is a duplicate of https://github.com/citation-style-language/schema/issues/113.

Regarding the property value conventions, the latter properties should probably be relaxed to accept both “string” and “number”.

[njbart]

Would that affect a decision on whether to adopt EDTF: Not at all.

It’s only the handling of months in edtf.js I find worrying, and my question to the js experts listening here is, would it make sense to try and get this fixed in edtf.js now, before starting any work on citeproc-js and possibly others.