[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: oc-basic: CSL-JSON year as number vs. string (nativecomp?)
From: |
Ihor Radchenko |
Subject: |
Re: oc-basic: CSL-JSON year as number vs. string (nativecomp?) |
Date: |
Mon, 20 Jun 2022 20:06:05 +0800 |
"Bruce D'Arcus" <bdarcus@gmail.com> writes:
> 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.
Have you ever checked if oc-basic parser complies with the schema?
It is clear that is not for year field, but I am wondering about other
fields.
Best,
Ihor
- 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, 2022/06/19
- Re: oc-basic: CSL-JSON year as number vs. string (nativecomp?),
Ihor Radchenko <=
- 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