public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Joseph Reagle <joseph.2011-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Any reason to keep bibliography in YAML?
Date: Fri, 18 Jun 2021 15:35:46 -0400	[thread overview]
Message-ID: <d6d1c254-27f7-32ca-e19a-2ce96fe05197@reagle.org> (raw)


My biblio tool can now create JSON-CSL output -- in addition to bibtex, biblatex, YAML-CSL, and Wikipedia citation template.

The JSON functionality is rather redundant with YAML, which I'm inclined to delete.
pandoc is so much faster with JSON, and if JSON is YAML, I can't see much reason to keep YAML.
I can even embed JSON-CSL in markdown files, just like YAML-CSL, as seen in example below.

Before I gut the YAML functionality and tweak my build system for the CSL, is there any reason to keep it?


====================

[1]: https://reagle.org/joseph/2016/04/min-eg/cite-json-embed.md

...
# References

---
references:

   { "id": "BurkeKraut2008mum",
     "type": "chapter",
     "author": [
         {
       "family": "Burke",
       "given": "Moira"
         },
         {
       "family": "Kraut",
       "given": "Robert"
         }
       ],
     "container-title": "Proceedings of the ACM 2008 Conference on Computer Supported Cooperative Work",
     "custom2": "wikip-secondary.mm",
     "issued":
       {
       "date-parts": [ [
         2008,
         11,
         8
       ] ] },
     "keyword": "structure",
     "page": "37-46",
     "publisher": "ACM",
     "title-short": "Mopping up",
     "title": "Mopping up: modeling Wikipedia promotion decisions",
     "URL": "http://portal.acm.org/citation.cfm?id=1460571",
     "accessed":
       {
       "date-parts": [ [
         2009,
         5,
         27
       ] ] },
     "event-place": "San Diego"
   }

...


             reply	other threads:[~2021-06-18 19:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-18 19:35 Joseph Reagle [this message]
     [not found] ` <d6d1c254-27f7-32ca-e19a-2ce96fe05197-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
2021-06-20  4:45   ` John MacFarlane
     [not found]     ` <m2k0mpf8jf.fsf-d8241O7hbXoP5tpWdHSM3tPlBySK3R6THiGdP5j34PU@public.gmane.org>
2021-06-21 12:22       ` Joseph Reagle
2021-06-21 15:22       ` Joseph Reagle

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d6d1c254-27f7-32ca-e19a-2ce96fe05197@reagle.org \
    --to=joseph.2011-t1oy19wchswdnm+yrofe0a@public.gmane.org \
    --cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
    /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.
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 NNTP newsgroup(s).