Add validation for et-al-min and et-al-use-first

[georgd]

Description

See discussion in citation-style-language/documentation#141

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• Variable addition (adds a new variable or type string)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

Checklist

• I have installed the repo pre-commit hook; if not, and I have modified any of the schema files, I have run trang and/or prettier on the files, per CONTRIBUTING
• I have performed a self-review of my own code
• I have included suggested corresponding changes to the documentation (if relevant)

[bwiernik]

Thanks!

@denismaier @bdarcus How should we handle bug fixes like this? As x.x.x.1 point releases or just update the 1.0.2 release?

[denismaier]

Good question, I've been thinking about this as well recently. (I've been pondering whether we could be more lenient when adding new terms. As this doesn't seem to affect processors they could probably added to the existing schema as well.)

Anyway, one option I was thinking about was to use a timestamp for these kind of additions, similar to emacs package versioning on melpa: e.g. https://melpa.org/#/citar

Like, if we added this today we'd still be on CSL 1.0.2, but we'd add a timestamp "20220421" or so to indicate these additions.

But, I can't really estimate how that might affect the larger ecosystem.

[bdarcus]

Seems this got stalled. Where do we stand?