From: "Bruce D'Arcus" <bdarcus@gmail.com>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: "David Lukeš" <dafydd.lukes@gmail.com>,
org-mode-email <emacs-orgmode@gnu.org>
Subject: Re: oc-basic: CSL-JSON year as number vs. string (nativecomp?)
Date: Mon, 20 Jun 2022 09:11:50 -0400 [thread overview]
Message-ID: <CAF-FPGOf7Lnk5nAsTss7vphK5s88Dze5T2uxQ3qsVc5JUpfCfg@mail.gmail.com> (raw)
In-Reply-To: <8735fz4k0i.fsf@localhost>
On Mon, Jun 20, 2022 at 8:04 AM Ihor Radchenko <yantar92@gmail.com> wrote:
>
> "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.
I had not. But the schema doesn't have a lot of rules.
Aside from dates, the other structured object definition is for
(author etc) names.
oc-basic ignores the properties beyond "family" and "given" names,
most of which probably don't matter for this purpose, except maybe
"literal" (for organizational authors).
Bruce
next prev parent reply other threads:[~2022-06-20 13:13 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 [this message]
2022-06-20 14:13 ` David Lukeš
2022-06-20 14:24 ` Bruce D'Arcus
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
Reply instructions:
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAF-FPGOf7Lnk5nAsTss7vphK5s88Dze5T2uxQ3qsVc5JUpfCfg@mail.gmail.com \
--to=bdarcus@gmail.com \
--cc=dafydd.lukes@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).