From: A A <amine.aboufirass-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: What keys / values are allowed in the `references` field in YAML metadata?
Date: Fri, 3 Mar 2023 12:48:54 +0100 [thread overview]
Message-ID: <CAMwawgOQ_1G9wkA4-monUExPuA=k1H0Yof6XTm+NKACC6SCWLw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1358 bytes --]
Is there a spec for the `references` filed in YAML metadata in Pandoc
markdown? The `references` field is supposed to be compatible with multiple
formats (BibTeX, CSL, etc.) so what different key-value pairs are allowed
in it?
The only example provided in the docs is the following:
---
references:
- type: article-journal
id: WatsonCrick1953
author:
- family: Watson
given: J. D.
- family: Crick
given: F. H. C.
issued:
date-parts:
- - 1953
- 4
- 25
title: 'Molecular structure of nucleic acids: a structure for
deoxyribose nucleic acid'
title-short: Molecular structure of nucleic acids
container-title: Nature
volume: 171
issue: 4356
page: 737-738
DOI: 10.1038/171737a0
URL: https://www.nature.com/articles/171737a0
language: en-GB
Which appears to follow a BibTeX-like format but there's no way to tell. I
mean, not all references are articles or journals right?
--
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/CAMwawgOQ_1G9wkA4-monUExPuA%3Dk1H0Yof6XTm%2BNKACC6SCWLw%40mail.gmail.com.
[-- Attachment #2: Type: text/html, Size: 1972 bytes --]
next reply other threads:[~2023-03-03 11:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-03 11:48 A A [this message]
[not found] ` <CAMwawgOQ_1G9wkA4-monUExPuA=k1H0Yof6XTm+NKACC6SCWLw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-03-03 11:53 ` AW: " denis.maier-NSENcxR/0n0
[not found] ` <9b8cbc4fabcb4930bd12742369a2f49f-NSENcxR/0n0@public.gmane.org>
2023-03-03 11:55 ` A A
[not found] ` <CAMwawgNDeWgjqB7Z-aL8hhGS-sZXx4qo_HZztECLK_-Jv3VubA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-03-03 12:05 ` A A
[not found] ` <CAMwawgMF9JGUF1PFNcmz1-0W3vabVRNXQmDpz52V2LC2WbZLOQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-03-03 12:38 ` Bastien DUMONT
2023-03-03 12:42 ` A A
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='CAMwawgOQ_1G9wkA4-monUExPuA=k1H0Yof6XTm+NKACC6SCWLw@mail.gmail.com' \
--to=amine.aboufirass-re5jqeeqqe8avxtiumwx3w@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).