From: "Bruce D'Arcus" <firstname.lastname@example.org>
To: "David Lukeš" <email@example.com>
Cc: Ihor Radchenko <firstname.lastname@example.org>,
Subject: Re: oc-basic: CSL-JSON year as number vs. string (nativecomp?)
Date: Mon, 20 Jun 2022 10:24:20 -0400 [thread overview]
Message-ID: <CAF-FPGMP58i+vg95Oay+230LQE0eSp5s4zWakKotjPNs1EUUemail@example.com> (raw)
On Mon, Jun 20, 2022 at 10:13 AM David Lukeš <firstname.lastname@example.org> 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):
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
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
But as I say, we still need feedback from the different constituencies.
next prev parent reply other threads:[~2022-06-20 14:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-18 6:34 oc-basic: CSL-JSON year as number vs. string (nativecomp?) David Lukeš
2022-06-19 1:44 ` Ihor Radchenko
2022-06-19 1:55 ` Bruce D'Arcus
2022-06-19 3:31 ` David Lukeš
2022-06-19 13:39 ` Bruce D'Arcus
2022-06-20 12:06 ` Ihor Radchenko
2022-06-20 13:11 ` Bruce D'Arcus
2022-06-20 14:13 ` David Lukeš
2022-06-20 14:24 ` Bruce D'Arcus [this message]
2022-06-21 3:28 ` Ihor Radchenko
2022-06-21 12:02 ` David Lukeš
2022-07-31 4:05 ` Ihor Radchenko
2022-06-20 12:04 ` Ihor Radchenko
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).