On Mon, Jun 20, 2022 at 10:13 AM David Lukeš <dafydd.lu...@gmail.com> wrote: ...
> > it's likely we'll change the date property to prefer an > > EDTF string > > Will that be stored in the `raw` or `literal` field? In that case, the > current implementation should work with (not too wild) EDTF strings. > If not, code will have to be added to extract the value from the > appropriate field. I need to emphasize a major caveat: this is subject to change, discussion, etc., and would take time regardless to see in the wild. So you shouldn't do anything with this information ATM; I just mention it because it may be relevant in the future. And of course, we welcome feedback. But currently, the draft schema for the next major release allows this as an option (this is an EDTF date range): "issued": "2020-07/2020-08", E.g. a (preferred) EDTF string, OR the current date object. In general, I should add, there are some competing priorities here. The CSL JSON was first created for the citeproc-js project, whose initial and primary consumer is Zotero, which embeds that data in word processing documents. In that case, machines are the only consumers. But it's since become more widely used, including in pandoc, and now in org. So the planned move to EDTF is in part to balance those priorities. But as I say, we still need feedback from the different constituencies. Bruce
