[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: oc-basic: CSL-JSON year as number vs. string (nativecomp?)
From: |
Bruce D'Arcus |
Subject: |
Re: oc-basic: CSL-JSON year as number vs. string (nativecomp?) |
Date: |
Sun, 19 Jun 2022 09:39:45 -0400 |
On Sat, Jun 18, 2022 at 11:31 PM David Lukeš <dafydd.lukes@gmail.com> wrote:
>
> > I suspect that multiple json formats may be available in the wild. Some
> > parsed as a list of strings and some parsed as a list of numbers.
>
> > The JSON schema allows either:
>
> Ah, thanks for looking this up!
I created CSL, and have helped develop the data schema.
BTW, just to look forward, it's likely we'll change the date property
to prefer an EDTF string; same as biblatex does now.
Bruce
- oc-basic: CSL-JSON year as number vs. string (nativecomp?), David Lukeš, 2022/06/18
- Re: oc-basic: CSL-JSON year as number vs. string (nativecomp?), Ihor Radchenko, 2022/06/18
- Re: oc-basic: CSL-JSON year as number vs. string (nativecomp?), Bruce D'Arcus, 2022/06/18
- Re: oc-basic: CSL-JSON year as number vs. string (nativecomp?), David Lukeš, 2022/06/18
- Re: oc-basic: CSL-JSON year as number vs. string (nativecomp?),
Bruce D'Arcus <=
- Re: oc-basic: CSL-JSON year as number vs. string (nativecomp?), Ihor Radchenko, 2022/06/20
- Re: oc-basic: CSL-JSON year as number vs. string (nativecomp?), Bruce D'Arcus, 2022/06/20
- Re: oc-basic: CSL-JSON year as number vs. string (nativecomp?), David Lukeš, 2022/06/20
- Re: oc-basic: CSL-JSON year as number vs. string (nativecomp?), Bruce D'Arcus, 2022/06/20
- Re: oc-basic: CSL-JSON year as number vs. string (nativecomp?), Ihor Radchenko, 2022/06/20
- Re: oc-basic: CSL-JSON year as number vs. string (nativecomp?), David Lukeš, 2022/06/21
- Re: oc-basic: CSL-JSON year as number vs. string (nativecomp?), Ihor Radchenko, 2022/06/20