I'd be in favor of of maybe not doing because we'll have to keep updating the citation.cff file AND the "how to cite" with every new BEP paper.
Would rather have a single place for that information.

or we could have the citation.file be the place where we store that info and use a macro to update the src/introduction.md

or we could have the citation.file be the place where we store that info and use a macro to update the src/introduction.md

I would be in favor of this solution, as it'd make the "how to cite" part machine readable and standardized.

or we could have the citation.file be the place where we store that info and use a macro to update the src/introduction.md

I would be in favor of this solution, as it'd make the "how to cite" part machine readable and standardized.

ok so time to add some more macros...

Hum... Wondering if we should not put those references in a bib file and rely on mkdocs plugins.

• See Add DOI links and references section for cited papers? #403 (comment)

Both seem to have their benefits and drawbacks.

• CITATION.cff
  • + it's part of the standardized file and may even populate zenodo metadata for the PDF spec release
  • - it'd need a custom macro to put it into the spec text
• bib file
  • + can rely on mkdocs plugins, no macro needed (??)
  • - need to add an additional file to the repo, and citation metadata is split over files

other + for bib file:

• allows standardization of ALL references in the spec (not many so far but makes it easy to scale up)