From mboxrd@z Thu Jan 1 00:00:00 1970 From: Richard Lawrence Subject: Re: Citation syntax: a revised proposal Date: Mon, 02 Mar 2015 10:50:49 -0800 Message-ID: <87twy39qt2.fsf@berkeley.edu> References: <87k2zjnc0e.fsf@berkeley.edu> <87bnkvm8la.fsf@berkeley.edu> <87zj8co3se.fsf@berkeley.edu> <87ioezooi2.fsf@berkeley.edu> <87mw4bpaiu.fsf@nicolasgoaziou.fr> <8761aznpiq.fsf@berkeley.edu> <87twyjnh0r.fsf@nicolasgoaziou.fr> <87oaopx24e.fsf@berkeley.edu> <87k2zd4f3w.fsf@nicolasgoaziou.fr> <87egpkv8g9.fsf@berkeley.edu> <877fv6xfaq.fsf@gmail.com> <87twya2ak0.fsf@berkeley.edu> <87zj81aa97.fsf@nicolasgoaziou.fr> <87ioep2r6p.fsf@berkeley.edu> <87y4ngbgm7.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:54514) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YSVRE-0002tV-3B for emacs-orgmode@gnu.org; Mon, 02 Mar 2015 13:51:33 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YSVRB-0006vL-Bv for emacs-orgmode@gnu.org; Mon, 02 Mar 2015 13:51:32 -0500 Received: from mail-pd0-f177.google.com ([209.85.192.177]:42113) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YSVRB-0006uf-6C for emacs-orgmode@gnu.org; Mon, 02 Mar 2015 13:51:29 -0500 Received: by pdbfl12 with SMTP id fl12so10474652pdb.9 for ; Mon, 02 Mar 2015 10:51:27 -0800 (PST) In-Reply-To: <87y4ngbgm7.fsf@nicolasgoaziou.fr> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Nicolas Goaziou Cc: emacs-orgmode@gnu.org Nicolas Goaziou writes: > Richard Lawrence writes: > >> That would be wonderful! Will you publish a patch or, better, a branch >> somewhere, even if it's not ready for master? > > I created a new branch: "wip-cite". It introduces support for @key > [@key] [cite:pre @key post] and [(cite):pre @key post] constructs. Great! I'll take a look. What's the next step here? Adding support for multiple references? multi-cites? `&'-keys? > As a reminder, I prefer subkeys over plists because they have a smaller > footprint in the document. Also, as already explained, having many > subkeys is not a problem with proper tooling (e.g., some completion with > descriptions). Note that this is closer to "org-ref" requirements, > probably making easier to port some features into core. > > However, opinion from advanced citation users on this ML has more weight > that mine. Instead of trying to figure out hypothetical crazy uses for > citations (e.g., using 50 different citation commands), I'd rather hear > from people with real citation requirements who are willing to use this > machinery. Yes, me too. > At this point, we probably need to implement a BIBLIOGRAPHY keyword > (files) and BIBLIOGRAPHY_BACKEND (bibtex, zotero, jabref...) and provide > basic tools to handle citations in an Org document. Could we guess the backend from the file extension on the BIBLIOGRAPHY, to keep things simple here? I don't use a citation manager, so I don't know if this is possible for anything other than Bib(La)TeX. Also, as mentioned earlier, it would be really nice to support org-bibtex as one of the reference database formats. (It's what I use, so naturally it's what I think we should bless. :) This would allow storing your reference database in-document. Some things to think about: 1) Is there ever a need to mix reference database formats in the same document (e.g., zotero and org-bibtex)? (I would think not, but my needs are simple.) 2) Is there ever a need to mix multiple reference databases in the *same* format (e.g., two different .bib files)? (I would think so, given the existence in BibLaTeX of \addbibresource.) 3) If the answer to either 1 or 2 is yes, how should we decide precedence between multiple reference databases? (Two databases might contain the same key.) Best, Richard