public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
* Any reason to keep bibliography in YAML?
@ 2021-06-18 19:35 Joseph Reagle
       [not found] ` <d6d1c254-27f7-32ca-e19a-2ce96fe05197-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
  0 siblings, 1 reply; 4+ messages in thread
From: Joseph Reagle @ 2021-06-18 19:35 UTC (permalink / raw)
  To: pandoc-discuss


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"
   }

...


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Any reason to keep bibliography in YAML?
       [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>
  0 siblings, 1 reply; 4+ messages in thread
From: John MacFarlane @ 2021-06-20  4:45 UTC (permalink / raw)
  To: Joseph Reagle, pandoc-discuss


There is one potentially important difference, regarding
formatting.

CSL JSON accepts some limited formatting using HTML tags.

YAML, however, accepts the full range of Markdown formatting;
so, for example, you can include tex math (which you can't
do in the JSON format at present).

Joseph Reagle <joseph.2011-T1oY19WcHSwdnm+yROfE0A@public.gmane.org> writes:

> 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"
>    }
>
> ...
>
> -- 
> You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/d6d1c254-27f7-32ca-e19a-2ce96fe05197%40reagle.org.


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Any reason to keep bibliography in YAML?
       [not found]     ` <m2k0mpf8jf.fsf-d8241O7hbXoP5tpWdHSM3tPlBySK3R6THiGdP5j34PU@public.gmane.org>
@ 2021-06-21 12:22       ` Joseph Reagle
  2021-06-21 15:22       ` Joseph Reagle
  1 sibling, 0 replies; 4+ messages in thread
From: Joseph Reagle @ 2021-06-21 12:22 UTC (permalink / raw)
  To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw


Thanks John, I went to play with formatting and realized I had made a mistake thinking my embedded JSON was working.

Can we embed csljson as part of the documents YAML metadata? The following doesn't work.

https://reagle.org/joseph/2016/min-eg/cite-json-embed.md

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

---
"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"
   }
]
...


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Any reason to keep bibliography in YAML?
       [not found]     ` <m2k0mpf8jf.fsf-d8241O7hbXoP5tpWdHSM3tPlBySK3R6THiGdP5j34PU@public.gmane.org>
  2021-06-21 12:22       ` Joseph Reagle
@ 2021-06-21 15:22       ` Joseph Reagle
  1 sibling, 0 replies; 4+ messages in thread
From: Joseph Reagle @ 2021-06-21 15:22 UTC (permalink / raw)
  To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw

On the formatting front, I don't have any tex math in my title, but I do have some italics.

The [json csl spec][1] says: "Note that tags must be JSON-encoded in the input object", which led me to believe that I'd have to move from:

	  "title-short": "Rewriting *The Rules*",

to

	  "title-short": "Rewriting &lt;i&gt;The Rules&lt;i&gt;"

but that doesn't work, and this does:

	  "title-short": "Rewriting <i>The Rules</i>"


[1]: https://citeproc-js.readthedocs.io/en/latest/csl-json/markup.html#html-like-formatting-tags

On 21-06-20 00:45, John MacFarlane wrote:
> There is one potentially important difference, regarding
> formatting.
> 
> CSL JSON accepts some limited formatting using HTML tags.
> 
> YAML, however, accepts the full range of Markdown formatting;
> so, for example, you can include tex math (which you can't
> do in the JSON format at present).


^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2021-06-21 15:22 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-06-18 19:35 Any reason to keep bibliography in YAML? Joseph Reagle
     [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

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).