From mboxrd@z Thu Jan 1 00:00:00 1970 From: jorge.alfaro-murillo@yale.edu (Jorge A. Alfaro-Murillo) Subject: Re: Citation syntax: a revised proposal Date: Mon, 16 Feb 2015 14:19:00 -0500 Message-ID: <87mw4d64wr.fsf@yale.edu> References: <87k2zjnc0e.fsf@berkeley.edu> <87a90e83ki.fsf@ucl.ac.uk> <874mql7r2h.fsf@yale.edu> Mime-Version: 1.0 Content-Type: text/plain; format=flowed Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:45665) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YNRGY-000830-Gb for emacs-orgmode@gnu.org; Mon, 16 Feb 2015 14:23:35 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YNRGT-0001C6-OI for emacs-orgmode@gnu.org; Mon, 16 Feb 2015 14:23:34 -0500 Received: from plane.gmane.org ([80.91.229.3]:36294) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YNRGT-0001Bz-I1 for emacs-orgmode@gnu.org; Mon, 16 Feb 2015 14:23:29 -0500 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1YNRGR-0007Xh-It for emacs-orgmode@gnu.org; Mon, 16 Feb 2015 20:23:27 +0100 Received: from nat-130-132-173-151.central.yale.edu ([130.132.173.151]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 16 Feb 2015 20:23:27 +0100 Received: from jorge.alfaro-murillo by nat-130-132-173-151.central.yale.edu with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 16 Feb 2015 20:23:27 +0100 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: emacs-orgmode@gnu.org Stefan Nobis writes: > jorge.alfaro-murillo@yale.edu (Jorge A. Alfaro-Murillo) writes: > >> From what I read in this and the previous thread, the new >> proposal tries more or less to reimplement BibTeX in org. > > No, that's wrong, not the database should be replaced. The goal > is to make citations a first class citizen in the org world (so > no fallback to LaTeX commands or links with special handlings > are needed). I see, so in the examples provided Doe99 is only the key, org would not have to know that the author name is Doe and its year is 1999, or any other information about the citation. I thought it was more or less the equivalent of implementing natbib (http://merkel.zoneo.net/Latex/natbib.php) in org, a way to decide if I wanted textual, parenthesis or numerical citations, and thus you would have to go to the process of determining what information each citation needs, for example: an article always has an author, a book always has a publisher, but a book can have an author or an editor if each chapter has a different author, that kind of thing, among many other complicated things. Sorry for the noise. But now it is not clear to me what the actual org reference points to. If it is the actual reference, I mean the article's PDF or URL, what would you do when you need to cite a physical book? Also in this case you will not be able to produce a proper bibliography when exporting since the key cannot contain all the information needed. Now if the reference points to be entry for that reference in a database, isn't there a lot of compatibility problems if one uses one type of database vs another? Again here you will not be able to produce the bibliography when exporting -- Jorge.