From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matt Price Subject: Re: Citation syntax: a revised proposal Date: Tue, 17 Mar 2015 21:12:06 -0400 Message-ID: References: <87k2zjnc0e.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> <87bnkbi61v.fsf@gmail.com> <87a8zlmujp.fsf@gmail.com> <87ioe8yftp.fsf@berkeley.edu> <871tkwmh87.fsf@gmail.com> <87sidb8mm7.fsf@berkeley.edu> <87lhj07ol0.fsf@berkeley.edu> <87y4mw19yj.fsf@berkeley.edu> <87twxj1tfh.fsf@berkeley.edu> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a11c3fcb0973de1051185c5bb Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:55024) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YY2Wq-0007Wa-NS for emacs-orgmode@gnu.org; Tue, 17 Mar 2015 21:12:15 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YY2Wn-0002Uj-HQ for emacs-orgmode@gnu.org; Tue, 17 Mar 2015 21:12:12 -0400 Received: from mail-la0-x232.google.com ([2a00:1450:4010:c03::232]:35005) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YY2Wn-0002UK-0l for emacs-orgmode@gnu.org; Tue, 17 Mar 2015 21:12:09 -0400 Received: by labjg1 with SMTP id jg1so23623483lab.2 for ; Tue, 17 Mar 2015 18:12:07 -0700 (PDT) In-Reply-To: <87twxj1tfh.fsf@berkeley.edu> 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: Richard Lawrence Cc: Andreas Leha , Org Mode --001a11c3fcb0973de1051185c5bb Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Tue, Mar 17, 2015 at 12:26 PM, Richard Lawrence < richard.lawrence@berkeley.edu> wrote: > Hi Andreas, > > Andreas Leha writes: > > > I have been following this thread from (quite) some distance as I am > > very interested in more general citation support from orgmode. Please > > allow some basic questions: > > > > 1. For the LaTeX user > > This change means that the LaTeX user can use org syntax for citations > > rather than bare LaTeX (or links of some sort)? > > > > And this org syntax could then (I guess is the future) be extended with > > additional link-like functionality (maybe similar to org-ref)? > > Yes, exactly. > > > 2. The non-LaTeX exports > > These are all treated the same and will contain just text, that is > > produced to mimic LaTeX's output to some extent? > > Well, that depends on what you mean by `just' text. Citations can still > contain or be wrapped in markup that is specific to the output format, > like span tags or anchor tags in HTML. > > > I think I read some question about e.g. having zotero handling the > > citations in the odt export. Are there plans for such thing? > > Maybe. As far as I know, no one has done any work on Zotero integration > yet. But Vaidheeswaran did some work to make JabRef (a different > reference database) handle citations in ODT export. > > > 3. The database > > As I understand the database currently is either bibtex or org? > > Yes. > > > But that list could in principle be extended to zotero ... ? > > Yes, in principle. Any database that can export to bibtex format is > supported to some degree, if we support that format. Whether we want to > integrate with any particular reference database more tightly than that > hasn't really been discussed, as far as I'm aware. I don't have a good > sense of what other software Org users rely on for this purpose. > Just a note about Zotero: I think for most of us, the reason to export into ODT and/or DOC is to circulate a paper either for review or collaboration. Either case will likely involve some revision to citations, which would ideally be handled through Zotero. for this to work properly, we would want to export a full Zotero citation. To do that, we would likely need to speak directly to Zotero iteself. Here is a snippet of xml from a Zotero-generated citation in an odt document: -------------- Here is a cite. 1 Lea Schick, =E2=80=9CBodies, = Embodiment and Ubiquitous Computing=E2=80=9D 21, no. 1 (March 1, 2010): 63=E2=80=9369, http://resolver.scholarsportal.info/resolve/14626268/v21i0001/63_beauc.xml. ------------------- Among other pieces of data, it contains a reference to a zotero URL which i don't think org-citeproc will know about. Can you describe what would be necessary to get text like this into an ODT, using ythe code you've been working on? THis conversation has gone a bit beyond my competence/comfort level, but I would be interested i nhelping a bit as soon as our semester is over here (just a couple of weeks left). Thanks, Matt > > And any other database X (zotero ...) would need translations X -> > > bibtex to make the LaTeX export work with it as well? > > Not necessarily. Obviously, if you want to have bibtex/biblatex do the > processing of the citations and bibliography in the document, that is > required. But there is another approach, which is the one that Pandoc > takes: directly rendering citations and bibliography into the output > .tex file. If you're not relying on bibtex/biblatex to do the > rendering, you don't need to have the database in its format. > > The org-citeproc tool I've been working on supports reading databases in > any of these formats (via pandoc-citeproc): > > Format File extension > ------------ -------------- > MODS .mods > BibLaTeX .bib > BibTeX .bibtex > RIS .ris > EndNote .enl > EndNote XML .xml > ISI .wos > MEDLINE .medline > Copac .copac > JSON citeproc .json > > --001a11c3fcb0973de1051185c5bb Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Tue, Mar 17, 2015 at 12:26 PM, Richard Lawrence &l= t;richar= d.lawrence@berkeley.edu> wrote:
Hi Andreas,

Andreas Leha <andr= eas.leha@med.uni-goettingen.de> writes:

> I have been following this thread from (quite) some distance as I am > very interested in more general citation support from orgmode.=C2=A0 P= lease
> allow some basic questions:
>
> 1. For the LaTeX user
> This change means that the LaTeX user can use org syntax for citations=
> rather than bare LaTeX (or links of some sort)?
>
> And this org syntax could then (I guess is the future) be extended wit= h
> additional link-like functionality (maybe similar to org-ref)?

Yes, exactly.

> 2. The non-LaTeX exports
> These are all treated the same and will contain just text, that is
> produced to mimic LaTeX's output to some extent?

Well, that depends on what you mean by `just' text.=C2=A0 Citati= ons can still
contain or be wrapped in markup that is specific to the output format,
like span tags or anchor tags in HTML.

> I think I read some question about e.g. having zotero handling the
> citations in the odt export.=C2=A0 Are there plans for such thing?

Maybe.=C2=A0 As far as I know, no one has done any work on Zotero in= tegration
yet.=C2=A0 But Vaidheeswaran did some work to make JabRef (a different
reference database) handle citations in ODT export.

> 3. The database
> As I understand the database currently is either bibtex or org?

Yes.

> But that list could in principle be extended to zotero ... ?

Yes, in principle.=C2=A0 Any database that can export to bibtex form= at is
supported to some degree, if we support that format.=C2=A0 Whether we want = to
integrate with any particular reference database more tightly than that
hasn't really been discussed, as far as I'm aware.=C2=A0 I don'= t have a good
sense of what other software Org users rely on for this purpose.

Just a note about Zotero:=C2=A0 I think for most = of us, the reason to export into ODT and/or DOC is to circulate a paper eit= her for review or collaboration.=C2=A0 Either case will likely involve some= revision to citations, which would ideally be handled through Zotero.=C2= =A0 for this to work properly, we would want to export a full Zotero citati= on.=C2=A0 To do that, we would likely need to speak directly to Zotero ites= elf.=C2=A0 Here is a snippet of xml from a Zotero-generated citation in an = odt document:
--------------
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 <text:= p text:style-name=3D"P1">Here is a cite.
=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0 <text:note text:id=3D"ftn0" text:note-class=3D&qu= ot;footnote">
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 <tex= t:note-citation>1
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 </tex= t:note-citation>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 <text:= note-body>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 <= ;text:p text:style-name=3D"Footnote">
=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 <text:reference-mark-start= text:name=3D"ZOTERO_ITEM CSL_CITATION {&quot;citationID&quot;= :&quot;ECYx4ePh&quot;,&quot;properties&quot;:{&quot;for= mattedCitation&quot;:&quot;{\\rtf Lea Schick, \\uc0\\u8220{}Bodies,= Embodiment and Ubiquitous Computing\\uc0\\u8221{} 21, no. 1 (March 1, 2010= ): 63\\uc0\\u8211{}69, http://resolver.scholarsporta= l.info/resolve/14626268/v21i0001/63_beauc.xml.}&quot;,&quot;pla= inCitation&quot;:&quot;Lea Schick, =E2=80=9CBodies, Embodiment and = Ubiquitous Computing=E2=80=9D 21, no. 1 (March 1, 2010): 63=E2=80=9369, http://resolver.scholarsportal.info/resolve/14626268/v2= 1i0001/63_beauc.xml.&quot;},&quot;citationItems&quot;:[{&am= p;quot;id&quot;:5262,&quot;uris&quot;:[&quot;http://zotero.org/users/2= 0/items/AJGK5FDE&quot;],&quot;uri&quot;:[&quot;http://zotero.org/= users/20/items/AJGK5FDE&quot;],&quot;itemData&quot;:{&q= uot;id&quot;:5262,&quot;type&quot;:&quot;article-journal&am= p;quot;,&quot;title&quot;:&quot;Bodies, embodiment and ubiquito= us computing&quot;,&quot;page&quot;:&quot;63-69&quot;,&= amp;quot;volume&quot;:&quot;21&quot;,&quot;issue&quot;:= &quot;1&quot;,&quot;URL&quot;:&quot;https://gith= ub.com/citation-style-language/schema/raw/master/csl-citation.json&quot= ;} RNDXQmSceXdkV"/>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0 <text:span text:style-name=3D"T1"&= gt;Lea Schick, =E2=80=9CBodies, Embodiment and Ubiquitous Computing=E2=80= =9D 21, no. 1 (March 1, 2010): 63=E2=80=9369, http://resolver.s= cholarsportal.info/resolve/14626268/v21i0001/63_beauc.xml.
=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 </text:span>= ;
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 <= ;text:reference-mark-end text:name=3D"ZOTERO_ITEM CSL_CITATION {&q= uot;citationID&quot;:&quot;ECYx4ePh&quot;,&quot;properties&= amp;quot;:{&quot;formattedCitation&quot;:&quot;{\\rtf Lea Schic= k, \\uc0\\u8220{}Bodies, Embodiment and Ubiquitous Computing\\uc0\\u8221{} = 21, no. 1 (March 1, 2010): 63\\uc0\\u8211{}69, http:= //resolver.scholarsportal.info/resolve/14626268/v21i0001/63_beauc.xml.}&= ;quot;,&quot;plainCitation&quot;:&quot;Lea Schick, =E2=80= =9CBodies, Embodiment and Ubiquitous Computing=E2=80=9D 21, no. 1 (March 1,= 2010): 63=E2=80=9369, http://resolver.scholarsporta= l.info/resolve/14626268/v21i0001/63_beauc.xml.&quot;},&quot;cit= ationItems&quot;:[{&quot;id&quot;:5262,&quot;uris&quot;= :[&quot;http://zotero.org/users/20/items/AJGK5FDE&quot;],&quot;uri&= ;quot;:[&quot;http://zotero.org/users/20/items/AJGK5FDE&quot;],&quot;i= temData&quot;:{&quot;id&quot;:5262,&quot;type&quot;:&am= p;quot;article-journal&quot;,&quot;title&quot;:&quot;Bodies= , embodiment and ubiquitous computing&quot;,&quot;page&quot;:&a= mp;quot;63-69&quot;,&quot;volume&quot;:&quot;21&quot;,&= amp;quot;issue&quot;:&quot;1&quot;,&quot;URL&quot;:&= ;quot;http://resolver.scholarsportal.info/resolve/1462= 6268/v21i0001/63_beauc.xml&quot;,&quot;ISSN&quot;:&quot= ;14626268&quot;,&quot;author&quot;:[{&quot;family&quot;= :&quot;Schick&quot;,&quot;given&quot;:&quot;Lea&quo= t;}],&quot;issued&quot;:{&quot;date-parts&quot;:[[&quot= ;2010&quot;,3,1]]}}}],&quot;schema&quot;:&quot;https://github.com/citation-style-language/schema/raw/master/c= sl-citation.json&quot;} RNDXQmSceXdkV"/>
=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 </text:p>
=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0 </text:note-body>
=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0 </text:note>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 </text= :p>
-------------------

Among other pieces of data,= it contains a reference to a zotero URL which i don't think org-citepr= oc will know about.=C2=A0 Can you describe what would be necessary to get t= ext like this into an ODT, using ythe code you've been working on?=C2= =A0 THis conversation has gone a bit beyond my competence/comfort level, bu= t I would be interested i nhelping a bit as soon as our semester is over he= re (just a couple of weeks left).=C2=A0

Thanks,
Matt



> And any other database X (zotero ...) would need translations X -><= br> > bibtex to make the LaTeX export work with it as well?

Not necessarily.=C2=A0 Obviously, if you want to have bibtex/biblate= x do the
processing of the citations and bibliography in the document, that is
required.=C2=A0 But there is another approach, which is the one that Pandoc=
takes: directly rendering citations and bibliography into the output
.tex file.=C2=A0 If you're not relying on bibtex/biblatex to do the
rendering, you don't need to have the database in its format.

The org-citeproc tool I've been working on supports reading databases i= n
any of these formats (via pandoc-citeproc):

Format=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 File extension
------------=C2=A0 =C2=A0 =C2=A0 --------------
MODS=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 .mods
BibLaTeX=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 .bib
BibTeX=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 .bibtex
RIS=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0.ris
EndNote=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0.enl
EndNote XML=C2=A0 =C2=A0 =C2=A0 =C2=A0.xml
ISI=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0.wos
MEDLINE=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0.medline
Copac=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0.copac
JSON citeproc=C2=A0 =C2=A0 =C2=A0.json


--001a11c3fcb0973de1051185c5bb--