From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp2 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms1 with LMTPS id GCMICDKZjF7AEwAAk0OIDg (envelope-from ) for ; Tue, 07 Apr 2020 15:16:02 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp2 with LMTPS id YMiBIzCZjF64ZwAAB5/wlQ (envelope-from ) for ; Tue, 07 Apr 2020 15:16:00 +0000 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 114DD94FD65 for ; Tue, 7 Apr 2020 15:15:57 +0000 (UTC) Received: from localhost ([::1]:49038 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jLpxC-0004q7-EU for larch@yhetil.org; Tue, 07 Apr 2020 11:15:54 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:37508) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jLpwn-0004oc-Ty for emacs-orgmode@gnu.org; Tue, 07 Apr 2020 11:15:31 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1jLpwm-0004Tg-4P for emacs-orgmode@gnu.org; Tue, 07 Apr 2020 11:15:29 -0400 Received: from mail-vs1-xe2e.google.com ([2607:f8b0:4864:20::e2e]:38312) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1jLpwl-0004TY-Rf for emacs-orgmode@gnu.org; Tue, 07 Apr 2020 11:15:28 -0400 Received: by mail-vs1-xe2e.google.com with SMTP id x206so2417592vsx.5 for ; Tue, 07 Apr 2020 08:15:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=ehzZGzq4o43NccvsBS+HKMqLlI0b/iKKtJSreCXBsqg=; b=tZ0Of5DeCTWEtMRBloCY4ku7dHytjdghyA/QGJOiIIyx8DiEoN/mUbqJCNjmlUI7hI olqe3YJHNO4SE1CMzIh0swQGlqqeWqj8SXrCPEFnqIV5rXpvaBhNxz+59SZJ1HwsT43K 3OuUPEuR0qWHH3a1f1k6GOJ5EEh0WuqlDJM6LNo7Vf3Prt7Z1tefpQjfURfCHz+WPE9L dE/miBzpdB/DKDl0W1J91ThpppJ+aeRYKf6V03Wi4Lly6MzJJnv4Gu60+oc0NgXJfkW4 rRofdYTjC+KuX5Y+p2Y6DAXsM5KdEbpr9nv6MQdt9aP3DPTOI4ZXiAPTGUKouTW1f15g ypnw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=ehzZGzq4o43NccvsBS+HKMqLlI0b/iKKtJSreCXBsqg=; b=imlDLZTD1Za/C2leaEb7VpYdXznoK5sqYhaqGbjdkyHn//0QVKdmgJmCIILNO15Z0e t8HlpJxXLZ5VFqau4EtUP7PzuhoDx75mKciz+wWYePon7UaMtXajS90AGUL8xqdxWnKN WiVjZvkt8Glf96/x+Nr33Xx+eDsjgQpNRo5fkk31K00mNYDhMAf7Py4iQcr8KomVoEJj Z9F6hZaumwkgTnb+KKrvrsXyu55X6YCT60/LNdYc8kVuRghemo2QuH9eMWHDf4BQi3Dp oxD9UUyv4B/xc3QSfQ9FFDvKnFsPNnPrdxFTzI62pNL00Y2Obob9+G93MUMR60mu7Q4T HSbA== X-Gm-Message-State: AGi0PuY7QpatQpBIGmS0FKDkEofhPY+u6gs2On6YNEvPJJeaBu7LmjD1 0/XpvvK/Ya35ooyEs10oQ1CalnPgH4DvSLGyp16PWDPd3FE= X-Google-Smtp-Source: APiQypLwmd/sCbrMVhKKNZolA19QRIcKjyI1hc06BrJ4X/eTMzFrpHV36nANnHWePySSxIHutiusJCWvJZyWmmlY+WY= X-Received: by 2002:a67:2247:: with SMTP id i68mr2193787vsi.19.1586272526622; Tue, 07 Apr 2020 08:15:26 -0700 (PDT) MIME-Version: 1.0 From: "Bruce D'Arcus" Date: Tue, 7 Apr 2020 11:15:15 -0400 Message-ID: Subject: wip-cite status question and feedback To: emacs-orgmode@gnu.org Content-Type: multipart/alternative; boundary="00000000000077623e05a2b4da80" X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2607:f8b0:4864:20::e2e X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: "Emacs-orgmode" ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=default; t=1586272557; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type:list-id:list-help:list-unsubscribe: list-subscribe:list-post:dkim-signature; bh=ehzZGzq4o43NccvsBS+HKMqLlI0b/iKKtJSreCXBsqg=; b=RkssDaAHZlYFqVIVFIbuT0cIUo8IX5lUW7fC5l1KpKFZeMG7+laye9fh0slxHjVYzxmgbD uz4G0EXhlZLHaI+CfsiZ8Q65GzmaSZwE5nlqYYiLcWoPZ3DHwp3xEgF7Tk1PlIxZNu8Rny vj+GP0dMLVg/hCDtVV+EBmcuVLRf1ow= ARC-Seal: i=1; s=default; d=yhetil.org; t=1586272558; a=rsa-sha256; cv=none; b=P53ksfHpuvudl/cSCKS72ga+BK/nucC/+Y538XSG3Iq/XO6kDEfMGx+aulTElIaJukV3OC 7ptzgp6p50O2z7if+dtBnmbpGy/XE9qNLsxQ28IrLp90pt7Q8jcRDZ3W6/W/epjyJHRDdz FTU5ets9U8WoEqLmCoIzwMkpbBqwxaM= ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20161025 header.b=tZ0Of5De; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (aspmx1.migadu.com: domain of emacs-orgmode-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=emacs-orgmode-bounces@gnu.org X-Scanner: scn0 X-Spam-Score: -0.71 Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20161025 header.b=tZ0Of5De; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (aspmx1.migadu.com: domain of emacs-orgmode-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=emacs-orgmode-bounces@gnu.org X-Scan-Result: default: False [-0.71 / 13.00]; GENERIC_REPUTATION(0.00)[-0.58239414405213]; R_SPF_ALLOW(-0.20)[+ip4:209.51.188.0/24:c]; FREEMAIL_FROM(0.00)[gmail.com]; TO_DN_NONE(0.00)[]; ARC_SIGNED(0.00)[i=1]; URI_COUNT_ODD(1.00)[7]; IP_REPUTATION_HAM(0.00)[asn: 22989(0.32), country: US(-0.01), ip: 209.51.188.17(-0.58)]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; MX_GOOD(-0.50)[cached: eggs.gnu.org]; MAILLIST(-0.20)[mailman]; FORGED_RECIPIENTS_MAILLIST(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:22989, ipnet:209.51.188.0/24, country:US]; TAGGED_FROM(0.00)[larch=yhetil.org]; FROM_NEQ_ENVFROM(0.00)[bdarcus@gmail.com,emacs-orgmode-bounces@gnu.org]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; RCVD_COUNT_FIVE(0.00)[6]; FROM_HAS_DN(0.00)[]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[emacs-orgmode@gnu.org]; HAS_LIST_UNSUB(-0.01)[]; RCPT_COUNT_ONE(0.00)[1]; FORGED_SENDER_MAILLIST(0.00)[] X-TUID: 6GdaWhd5auEi --00000000000077623e05a2b4da80 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi everyone; first post. >From what I can tell, there was a lot of activity here a few years back to define org citation link support, which was reflected in what seems to be a fairly developed wip-cite branch of the git repo. But that stalled somewhere, and we still have diverse tools, using diverse and incompatible methods to define citation links. I see from the archive there was an encouraging thread from April of 2018 (so, two years ago) that seemed to suggest merging to master was close, with perhaps some uncertainty around syntax being the primary hold up? My main question: how do we get this done? I'm happy to help resolve any syntax questions, if that's the primary hold up, though my coding skills in general are minimal. While I=E2=80=99m here, some feedback and thoughts below. I think the propo= sed syntax is basically sound, but maybe could be simplified. For background, I created the Citation Style Language (CSL), and the initial XSLT-based proof-of-concept formatter, which I used to format the citations and bibliography in my first book. I work in a field that has pretty diverse citation practices, and myself work at the borders of the social sciences and humanities, which influences my thinking on design priorities around citation technology. I also had a hand in the pandoc citation syntax, which is consistent with the basic design goals I had, including: 1. simple as possible plain-text format, consistent with markdown 2. prefix and suffix free text, page number locators, etc. 3. ability to radically change output style (for example, from author-date to footnote-based), without changing source. I believe the pandoc syntax achieves all of these goals. Which brings me to the org proposal. The only documentation I can find on the proposal is at the citeproc org project. https://github.com/andras-simonyi/citeproc-org#citations If the above is correct, then: 1. There are two forms of citations: short and long. 2. Short is of this syntax, and can only have a single citekey as content: [@doe2019]. 3. Anything else (multiple citations, locators, prefixes and/or suffixes) requires the long form. 4. In addition, there is a standard long form, and what the doc above calls =E2=80=9Cparenthetical=E2=80=9D form of the long form. So do I have all that right? First question: Why #4 above; a distinction between two different long forms? Moving on, assuming the above is correct, let=E2=80=99s borrow these exampl= es from the pandoc citation syntax for markdown (which it also supports in org): Blah blah [see @doe99, pp. 33-35; also @smith04, chap. 1]. Blah blah [@doe99, pp. 33-35, 38-39 and *passim*]. Blah blah [@smith04; @doe99]. So from a model perspective, a citation in pandoc is a list of one-or-more cites (or whatever we want to call them), each of which has optional: - prefix - Locators (page numbers and such) - suffix I believe this is similar to the proposed org model, with one difference: the org proposal adds prefix and suffix for the list (the citation) as a whole. So the pandoc version is a flat list, and the org version has two levels. Am I still understanding everything correctly? So ... am I correct that in none of these cases can one use the =E2=80=9Csh= ort=E2=80=9D form, and that the above would look like this converted to the proposed org syntax? Blah blah [cite:see @doe99 pp. 33-35; also @smith04 chap. 1]. Blah blah [cite:@doe99 pp. 33-35, 38-39 and *passim*]. Blah blah [cite:@smith04; @doe99]. Or the first one might treat the =E2=80=9Csee=E2=80=9D as a prefix for the = list, though I=E2=80=99m not sure what the practical benefit of that more hierarchical modelling is. While I do wonder if the syntax could be simplified, my main hope is that it actually gets merged to master and deployed, to harmonize the variety of different ways emacs tools (org-ref, ebib, pandoc, etc.) are dealing with citation links in org currently. --00000000000077623e05a2b4da80 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi everyone; first post.

From what I can tell, there = was a lot of activity here a few years back to define org citation link sup= port, which was reflected in what seems to be a fairly developed wip-cite b= ranch of the git repo.

But that stalled somewhere, and we still = have diverse tools, using diverse and incompatible methods to define citati= on links.=C2=A0


I see from the archive there was an encouraging thread from April= of 2018 (so, two years ago) that seemed to suggest merging to master= was close, with perhaps some uncertainty around syntax being the primary h= old up?


My main question: how do we get this done?


I'm happy to help resolve any syntax questions, if that's the prim= ary hold up, though my coding skills in general are minimal.


=

= While= I=E2=80=99m here, some feedback and thoughts below. I think the proposed s= yntax is basically sound, but maybe could be simplified.


For backg= round, I created the Citation Style Language (CSL), and the initial XSLT-ba= sed proof-of-concept formatter, which I used to format the citations and bi= bliography in my first book.


I work in a field that has pretty div= erse citation practices, and myself work at the borders of the social scien= ces and humanities, which influences my thinking on design priorities aroun= d citation technology.


I also had a hand in the pandoc citation sy= ntax, which is consistent with the basic design goals I had, including:


  1. simple as possible plain-text format, consistent with = markdown

  2. prefix and su= ffix free text, page number locators, etc.

  3. ability to radically change output style (for example,= from author-date to footnote-based), without changing source.


I believe the pandoc syntax achieves all of these goals.

<= br>

Wh= ich brings me to the org proposal.=C2=A0


The only documentation I = can find on the proposal is at the citeproc org project.


https://github.com/andras-simonyi/citepr= oc-org#citations


If the above is correct, then:


=
  1. There are two forms of citations: short and long.

  2. =
  3. Short is of this syntax, and can only= have a single citekey as content: [@doe2019].

  4. Anything else (multiple citations, locators, prefi= xes and/or suffixes) requires the long form.

  5. In addition, there is a standard long form, and what= the doc above calls =E2=80=9Cparenthetical=E2=80=9D form of the long form.=


So do I have all that right?


First question:= =C2=A0


Why #4 above; a distinction between two different long form= s?


Moving on, assuming the above is correct, let=E2=80=99s borrow = these examples from the pandoc citation synta= x for markdown (which it also supports in org):


Blah blah [see @doe99, pp. 33-35; also @smith04, chap. 1].<= /p>

Blah blah [@doe99, pp. 33-35, 38-39 and *passim*].


Blah blah [@smith04; @doe99].

So from a = model perspective, a citation in pandoc is a list of one-or-more cites (or = whatever we want to call them), each of which has optional:

  • prefix=C2=A0

  • Locators = (page numbers and such)

  • s= uffix


I believe this is similar to the proposed org mode= l, with one difference: the org proposal adds prefix and suffix for the lis= t (the citation) as a whole.=C2=A0


So the pandoc version is a flat= list, and the org version has two levels.


Am I still understandin= g everything correctly?


So ... am I correct that in none of these = cases can one use the =E2=80=9Cshort=E2=80=9D form, and that the above woul= d look like this converted to the proposed org syntax?


Blah blah [cite:see @doe99 pp. 33-35; also @smith04 chap. 1].


Blah blah [cite:@doe99 pp. 33-35, 38-39 and *passi= m*].


Blah blah [cite:@smith04; @doe99].

While I do wonder if the syntax could = be simplified, my main hope is that it actually gets merged to master and d= eployed, to harmonize the variety of different ways emacs tools (org-ref, e= bib, pandoc, etc.) are dealing with citation links in org currently.=


--00000000000077623e05a2b4da80--