From: Jambunathan K <kjambunathan@gmail.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: Bastien <bzg@altern.org>,
Andreas Leha <andreas.leha@med.uni-goettingen.de>,
emacs-orgmode@gnu.org
Subject: Re: org-exp-bibtex missing in git?
Date: Sat, 09 Mar 2013 21:34:32 +0530 [thread overview]
Message-ID: <876210pnjj.fsf@gmail.com> (raw)
In-Reply-To: <874ngkzjt6.fsf@gmail.com> (Nicolas Goaziou's message of "Sat, 09 Mar 2013 16:15:01 +0100")
Nicolas Goaziou <n.goaziou@gmail.com> writes:
> I favor [cite:PROPERTIES] over [[cite:PROPERTIES]], because the latter
> (link syntax) implies a (optional) description part. I don't think
> a description is ever meaningful in citations.
I have been holding on to this for a while. Just typing it out as it
comes to my mind.
I favor the above syntax.
I view Citations as closer to Footnotes. The syntax should parallels
footnotes syntax.
1. PROPERTIES should be opaque to Org. It is a key or a list of keys
possibly bibtex but Org doesn't take stand on how it looks like.
2. There will be a org-BACKEND-citation-reference.
3. There will be a org-BACKEND-bibliography.
2, 3 more likely with interface with respective citation processor
(citation processor as opposed to a database) via CLI. Citation
processor could be whatever org-exp-bibtex interfaces with right now. I
also have some proof-of-concept - see zotcite - for zotero.
2, 3 will parallel footnote-reference and footnote-section callbacks in
HTML backend.
4. Footnotes can be introduced with either fn: prefix or cite: prefix.
There should be a way to put fn: and cite: in same enumeration
context. There should be a way to put fn: and cite: in different
enumeration context. The former case could be a degenerate mode
where Org can transcode what is seen in the buffer where everything
is footnotes. The latter case will result in Citations and
Bibliography being generated by the above backend transcoders.
5. Citation definitions in Org buffer will be *ignored*. (It could be
considered when the exporter works in a degenerate footnote only mode
where plain text transcoding is resorted to because there is no
suitable application available for the backend format.) Plain text
citation definitions are only to help the author have a glimpse of
what he is doing, it has only UI-value but no contents value.
6. There may be an advisory citation style - say APA, Chicago etc -
which the backends may honor or ignore.
I am not clear about:
1. How multiple keys are to be handled.
2. What prenotes or postnotes mean.
3. Chicago note style etc.
I think the community should answer and articulate 1, 2, 3 clearly.
With my proposal, there could be some minor changes in Footnotes
normalization and some minor changes in existing transcoders.
The Org syntax for citations should *at this point* in time should NOT
make any assumptions about the Citation Database or the Citation
Application. As far Org is concerned, there should be a way for Emacs
to interact with these engines and have them return Citation Refernece
and Citation Defintion contents in required backend format.
--
next prev parent reply other threads:[~2013-03-09 16:04 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-03 7:06 org-exp-bibtex missing in git? Vikas Rawal
2013-03-03 10:39 ` François Allisson
2013-03-03 17:11 ` Bastien
2013-03-03 17:19 ` Nicolas Goaziou
2013-03-03 20:00 ` Andreas Leha
2013-03-03 20:42 ` Nicolas Goaziou
2013-03-04 9:29 ` Eric S Fraga
2013-03-06 13:38 ` Andreas Leha
2013-03-06 18:25 ` Bastien
2013-03-06 18:39 ` Nicolas Goaziou
2013-03-06 21:16 ` Andreas Leha
2013-03-06 22:55 ` Bastien
2013-03-06 23:37 ` Andreas Leha
2013-03-07 8:32 ` Bastien
2013-03-07 8:44 ` Andreas Leha
2013-03-07 5:38 ` aaronecay
2013-03-07 8:54 ` Eric S Fraga
2013-03-07 10:21 ` Bastien
2013-03-07 11:04 ` Aaron Ecay
2013-03-07 11:16 ` Bastien
2013-03-07 12:03 ` Aaron Ecay
2013-03-07 13:13 ` Nicolas Goaziou
2013-03-07 15:28 ` Bastien
2013-03-07 17:39 ` Achim Gratz
2013-03-07 22:06 ` Bastien
2013-03-07 22:46 ` Achim Gratz
2013-03-07 23:37 ` Rasmus Pank Roulund
2013-03-07 23:43 ` Rasmus
2013-03-08 0:10 ` Thomas S. Dye
2013-03-08 9:27 ` Rasmus
2013-03-08 17:36 ` Thomas S. Dye
2013-03-08 19:32 ` aaronecay
2013-03-08 19:40 ` Rasmus
2013-03-08 19:29 ` aaronecay
2013-03-09 9:28 ` Bastien
2013-03-19 5:02 ` Aaron Ecay
2013-04-18 10:58 ` Bastien
2013-03-09 15:15 ` Nicolas Goaziou
2013-03-09 16:04 ` Jambunathan K [this message]
2013-03-09 16:12 ` Jambunathan K
2013-03-09 17:08 ` Thomas S. Dye
2013-03-07 10:04 ` Jambunathan K
2013-03-11 13:34 ` Andreas Leha
2013-03-04 4:40 ` Vikas Rawal
2013-03-04 13:55 ` Suvayu Ali
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=876210pnjj.fsf@gmail.com \
--to=kjambunathan@gmail.com \
--cc=andreas.leha@med.uni-goettingen.de \
--cc=bzg@altern.org \
--cc=emacs-orgmode@gnu.org \
--cc=n.goaziou@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).