Stephan Druskat

There should be a place to document rationales for deprecating fields.

Thanks, @jspaaks, done now ([first comment](https://github.com/citation-file-format/citation-file-format/issues/453#issue-1871111692) and #456)

[JSON Schema has a `deprecated` keyword](https://json-schema.org/draft/2019-09/json-schema-validation#rfc.section.9.3) that we could consider using.

- We agree that the JSON Schema keyword is a good way to signal deprecation in future versions. - We still need to define and document the full process for...

Issue may be removed from the milestone if it turns out to be blocking the release and we don't have enough resources to resolve.

1. Yes, we should hardwire the identifier to maintain machine-readability. We chose to communicate to machine users the schema they will have to use to validate a file. 2. For...

> There's not an easy solution to this. Agree. > If we suggest that tooling ignores the `cff-version` error then one could have a CFF file with `1.3.0`-only features in...

Thanks @TJHeeringa for suggesting this tooling! I'm assuming that one major use case for this would be to populate the project's CFF file's `references` section? Were you thinking of differentiating...

Thanks @TJHeeringa. I'll have a look at your project. Please consider adding it to the [tools table](https://github.com/citation-file-format/citation-file-format#tools-to-work-with-citationcff-files-wrench) in the README if you like. (The table will be replaced with something...

Examples: - Changed the regular expression for PMC ID to allow 8 digits in addition to the preexisting 7. Issue https://github.com/citation-file-format/citation-file-format/issues/443; PR https://github.com/citation-file-format/citation-file-format/pull/469 should be **changed** - *Allow references with...