As I was thinking about this, thought I’d post it …
We have recently added EDTF to represent dates on the input schema.
Open questions are which features we support, and the status of the date-parts JSON representation. If it stays long-term, we might want to reconcile them as much as possible now.
If not, this could help with documenting regardless.
|Feature||EDTF||CSL JSON 1.0||Notes|
|Seasons||2019-21||“season” property||The JSON could also support this on the month part.|
|“circa” property||Which do we support, and how do we interpret in CSL? Biblatex treats ~ as circa.|
|Ranges (including open)||2018-21/2018-22
|supported, with two
||Specify 0 for open-end?|
|Decades and centuries||12XX (13th century)
195X (1950s decade)
|not supported||I’m not clear if we really need this, but could be addressed by allowing X on the year part.|