From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp10.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms0.migadu.com with LMTPS id IDqoKty9QGI6ZwEAgWs5BA (envelope-from ) for ; Sun, 27 Mar 2022 21:41:16 +0200 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp10.migadu.com with LMTPS id yMIQI9y9QGIFHwAAG6o9tA (envelope-from ) for ; Sun, 27 Mar 2022 21:41:16 +0200 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 AAD302849D for ; Sun, 27 Mar 2022 21:41:15 +0200 (CEST) Received: from localhost ([::1]:48428 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nYYlG-0002qC-Dd for larch@yhetil.org; Sun, 27 Mar 2022 15:41:14 -0400 Received: from eggs.gnu.org ([209.51.188.92]:59726) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nYYk5-0002nI-07 for emacs-orgmode@gnu.org; Sun, 27 Mar 2022 15:40:01 -0400 Received: from [2607:f8b0:4864:20::834] (port=39861 helo=mail-qt1-x834.google.com) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1nYYk2-0004jT-AO for emacs-orgmode@gnu.org; Sun, 27 Mar 2022 15:40:00 -0400 Received: by mail-qt1-x834.google.com with SMTP id bp39so10738788qtb.6 for ; Sun, 27 Mar 2022 12:39:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=sender:references:user-agent:from:to:cc:subject:date:in-reply-to :message-id:mime-version:content-transfer-encoding; bh=B2+4PItATuigXNSinxaCGn0hVr7xd7lt5htvNsS7cts=; b=U5Bg3ygL6JuD26j4o0lzI/vOMRxBXBds+Qqjzkt9WCch5TSXtKA5P2kYqVTae02+iF 31FIS7vj8v62LNQqUA34XjJloRHzUTchUQ3MHRQjXhXAA/nArrsRvErE3nc6aVASpsJc znZM8x/D5/H8GgOcElXKqt5NbWmJhzPwng+rN91Yw6OsF3sEm7RX0ertt4cjlWCuj1z5 8fa4nel+fNwOSpL0rl1I3e/UKxNbZqQ89UbaFPO4oedK8mQxOJ1eYI3KqXR7m1TPQnbC Zqcd40ZbmzUF57Yg9Jm5rUTNuwjLDsIE3rYIonvZu7KAn0zXUPQTBkn8UX2FKQycKzH4 7ZLQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:sender:references:user-agent:from:to:cc:subject :date:in-reply-to:message-id:mime-version:content-transfer-encoding; bh=B2+4PItATuigXNSinxaCGn0hVr7xd7lt5htvNsS7cts=; b=RkVqEUMgWPaIgFUTqNDlE1HbelSowmIUAeqJBnFcehJPxUgHNvGGRo2pCQedCexFej gCjMC6urRUnXhjYRIaS135uKvE5e8jHiLA7C3LM7BlVKf2wTseI2IciAVMFAZYF1HpTJ eUNP1G/49W1x1OP+x67RhuezczErtHKHpxIBZ7Co9z9dRJfS5pJ9+Wa0XVtXIAdhsOoT oCom25S/DjLyGdeJ4wPhmS9FomrBP6girs1SBYvujhRizWnQOH2ttqzk/LegvJZ7b8by gHEIEP5rK/QYrSqB0sBR/QBs0s9ps0jL7uH+WHLRheT4SKizeINf1kh1boZjrHFYxczt +oVw== X-Gm-Message-State: AOAM533egn2MrZDCRR1gFt6xwVMYkIJ2SmQYH2sXqgOhlCR9lDIUEk0R kZ6JYOCo11EggxWHB+AWztXDP/vHk+E= X-Google-Smtp-Source: ABdhPJyVclD7CCSBi/LaZmlaW+mm0eGXwdB6qoTn1SS9FOhSHBkUUgKfhUjACiHv0O+Vn4x1m3/UNg== X-Received: by 2002:a05:622a:38a:b0:2e2:2fdf:246e with SMTP id j10-20020a05622a038a00b002e22fdf246emr19005703qtx.482.1648409996787; Sun, 27 Mar 2022 12:39:56 -0700 (PDT) Received: from Johns-iMac.local ([2601:547:901:82e0:4464:b3ca:1e89:d3da]) by smtp.gmail.com with ESMTPSA id n10-20020a05622a040a00b002e315b9f08asm9232427qtx.35.2022.03.27.12.39.55 (version=TLS1_2 cipher=ECDHE-ECDSA-CHACHA20-POLY1305 bits=256/256); Sun, 27 Mar 2022 12:39:56 -0700 (PDT) References: <87wngosqvm.fsf@nicolasgoaziou.fr> <87k0ckjs4o.fsf@nicolasgoaziou.fr> User-agent: mu4e 1.6.10; emacs 28.0.90 From: John Kitchin To: Nicolas Goaziou Subject: Re: citations: org-cite vs org-ref 3.0 Date: Sun, 27 Mar 2022 13:00:40 -0400 In-reply-to: <87k0ckjs4o.fsf@nicolasgoaziou.fr> Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Host-Lookup-Failed: Reverse DNS lookup failed for 2607:f8b0:4864:20::834 (failed) Received-SPF: pass client-ip=2607:f8b0:4864:20::834; envelope-from=johnrkitchin@gmail.com; helo=mail-qt1-x834.google.com X-Spam_score_int: 0 X-Spam_score: -0.1 X-Spam_bar: / X-Spam_report: (-0.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, PDS_HP_HELO_NORDNS=0.659, RCVD_IN_DNSWL_NONE=-0.0001, RDNS_NONE=0.793, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Vikas Rawal , emacs-orgmode@gnu.org Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: "Emacs-orgmode" X-Migadu-Flow: FLOW_IN X-Migadu-To: larch@yhetil.org X-Migadu-Country: US ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1648410076; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:list-id:list-help: list-unsubscribe:list-subscribe:list-post:dkim-signature; bh=B2+4PItATuigXNSinxaCGn0hVr7xd7lt5htvNsS7cts=; b=Ucb348ljWfyKgSABp+gdxS0joLvzaQhKiu2PfgN2ZBrIz3s6oR0Jc4SqrgQHqCwKtL02CD 9wVqfeoL5jmUNR7V93mI/JPSfm9IsJIoL+LKLuERzbAPnXbfKS+HrYdwgRnQp1sthHLoCL M2hrbM+br8ZaYTDUyS6NW7+qrruNJE5WsqqpSgHBOJGeSvcuBAg0xRXNJ0HbXGiatPrrdv wUNMZH6oBgDEpJZM/W8er1C7y/QKlsrluOfnx/U80hQgHW/o1XuKab5fE9i0IeZqI9q6XP 2MkvIBwEUPSjpx/2SYU9nJi4NGrLZDksHj0Z1eAeuvv+iQ2d+eNCEoFyQ3xfpQ== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1648410076; a=rsa-sha256; cv=none; b=teHS5yQ+oRfINDza+Y7B1z5k9HYNcBaGe7RXlLaJu/EYgFiiv/U15NT5J8EFVSAW3GSHrW 7OvK9AFW40KL8Bib0ot/rYYpKBKNCao1lfRCjywjv0lJm0xjFPBfbWAw+fQaFW8+qQvRZO dehaiXBQqS9T3k+cv7DmY7p76ad0XepSUJmMb2U2SJg3AcnHcppzoBop3VvE8NZSVtCIsa bosFGdwq8vdsS02ZEPeQI7sgU69SKINwUG2UIxEinCttccb4L8UjPUJUlr7vzQW6Y7LDhC Z73XTHiqALSPBuIg/PuQxS1lK1sr5uKpIarHXHEPsPK1q/7E7D8NltVU1XDcVQ== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=fail ("headers rsa verify failed") header.d=gmail.com header.s=20210112 header.b=U5Bg3ygL; dmarc=fail reason="SPF not aligned (relaxed)" header.from=andrew.cmu.edu (policy=none); spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org" X-Migadu-Spam-Score: 6.14 Authentication-Results: aspmx1.migadu.com; dkim=fail ("headers rsa verify failed") header.d=gmail.com header.s=20210112 header.b=U5Bg3ygL; dmarc=fail reason="SPF not aligned (relaxed)" header.from=andrew.cmu.edu (policy=none); spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org" X-Migadu-Queue-Id: AAD302849D X-Spam-Score: 6.14 X-Migadu-Scanner: scn1.migadu.com X-TUID: Ktg00G/HfISK Nicolas Goaziou writes: > Hello, > > John Kitchin writes: > >> I do not think it is productive for the community to say or consider it >> is a sad situation. Many good things have emerged from these >> discussions, even if it is not yet consensus on a solution. It is a >> complex problem, with many years of effort by many people on each side. >> That is an indication of how ambitious this project is and that there >> may be more than one solution that is needed. > > [...] > >> There are more than 8 years of legacy org-ref documents. I have written >> 40+ scientific papers with it, and countless technical documents with >> more than 8000 cite links among them. org-ref has exceeded 190K >> downloads from MELPA, so I feel obligated to maintain org-ref for >> myself, and those users. org-ref may be heavyweight in bundling a lot of >> capability together that could be separated into individual packages, >> but it is also convenient for people who need it, and a GitHUB issue or >> pull request away from new features. I remain committed to supporting >> this, and I do it in a way I can manage, hence the monolithic package >> design. > > I think there's a misunderstanding here. Org Cite was never meant as > a replacement for Org Ref. It was designed from the beginning as > a framework other libraries could rely on and extend in their own way. > Org Ref could have been one of them. > > It looks like a social problem to me. I remember well asking for > feedback when implementing the various prototypes, i.e., ways to make > Org Cite more useful to other libraries. I don't think I got much of it, > barring the cross-references topic, which is not solved. Maybe I was not > explicit enough about what I was expecting. For example, this is=E2=80=94= please > correct me if I'm wrong=E2=80=94the first time I read about the "BibLaTeX= is not > fully implemented in Org Cite" and "Org Cite is adding an extra > abstraction layer on top of BibLaTeX commands" issues, which are both > trivial to solve, either on the Org Cite or the Org Ref side. But then > again, it is perfectly fine if Org Cite doesn't provide that, as some > libraries can extend it if needed. I don't think it is the first time I have mentioned biblatex is not fully implemented, but I am not sure. I have mentioned things like \citenum somewhere, but it is not the main point. I know it is not that difficult to add support for LaTeX export in org-cite, e.g. [cite/num:]. I don't think it is all that easy to add additional backend support though, for something like [cite/num:] in HTML or other backends. No doubt, it is not impossible, if someone would just do it, and that might include extending citeproc too, or developing some pre-processing function to get a citation number, or something else. Whether cite/num or any other command exists is not the main point. What is the point is what mechanisms exist to support the addition, and the exports to various backends. Regarding that org-cite adds an abstraction layer, how else could one interpret this (from https://blog.tecosaur.com/tmio/2021-07-31-citations.html#cite-syntax) other than abstraction: [cite/na/b:@key] or [cite/noauthor/bare:@key] to mean \citeyear{key}? Why wouldn't it be \citetitle? or \citeurl, or \citedate? or even, \citenum? I get it, you can define [cite/noauthor/year:] or even [cite/year:] or [cite/y:] and even [cite/citeyear:] to get the command in there, and something for each of those other ones. Maybe even the documented convention will change to some other potentially mnemonic form.=20 I also get they are not all that common perhaps, except for a few people who use them, and maybe should be responsible for supporting it themselves, either by defcustom or their own library. This is just trading a proliferation of links for a proliferation of styles IMO, and it feels a lot like the XKCD standards issue https://xkcd.com/927/. As others have argued, it is just a bit of knowledge, maybe a UI can compensate to help you insert what you want, then know what it means later. It is my opinion that this will be a technical debt though. I am content to agree to disagree on this point. It might be a social problem, and I do not think it is trivial to solve. It is not just about having a syntax that works. I wrote and shared a whole set of processors for org-cite that did or tried to do all those things above. It was fine to use, but it was very difficult code to write for me. I don't personally want to support it in part because it was so difficult to write. I don't even want to support it for my own use at this time. This should not stop anyone who wants to do that themselves though. Maybe there is a cleaner approach I missed, or others may be better programmers, and/or have more time to figure this out. At this time, I do not have time to make for it. > On the other hand, there have been much activity on GitHub repositories, > i.e., out of this mailing list. It seems to me Org Ref project has been > trying to work around possible blockers in Org Cite project the whole > time without the latter knowing about them, and having an opportunity to > lift them. There is nothing nefarious happening here. That work happened in public, and with some interactions with people on the org-list including Bruce.=20 Some motivation for org-cite stemmed from at least perceived limitations in org-ref, especially related to pre/post notes and CSL support. I think it is totally reasonable to learn if those were real limitations or not.=20 >> Both projects have benefited from this discussion a lot. org has >> org-cite now, and org-ref now handles pre/post notes like org-cite does, >> it supports CSL much better, and is even a little more modular, lighter >> weight, and more easily integrated with other completion backends than >> ivy or helm. That should broadly be viewed as a win-win situation. > > But it is not. There are now two, more or less official, citations > syntax. Interoperability is the big loss. Features do not count; it is > perfectly fine to have different packages targeting different needs, as > long as they share the same syntax. > > Hopefully, at some point, we'll be able to build a list of blockers that > prevent Org Ref being built on top of Org Cite, and proceed. You can use the org-cite syntax with org-ref. If all one wants is a citation syntax for their org-files, and an occasional standard (cite/citet/citep) LaTeX export export, org-cite will probably meet their needs. As a few have reported, it works for them. If you have very large bibtex files, you may find that the basic processors don't have good performance yet, and you may need to configure org to use a performant set of processors for activation and insertion. Yes, this is being worked on in org, and you will need to use the latest version of org to benefit from it. If you have very specific needs in biblatex, you may find not every command has a corresponding org-cite implementation. You may have to add this to your own setup, or use a specific set of processors that provide it. You can do that, and still use it with org-ref. Maybe one day I will have time to try integrating org-cite with org-ref again. I have been stretched too thin by work for the past two years, and in the forseeable future to spend much time on org-cite. This is a me issue, not an org-cite issue. > > Regards, --=20 Professor John Kitchin Doherty Hall A207F Department of Chemical Engineering Carnegie Mellon University Pittsburgh, PA 15213 412-268-7803 @johnkitchin http://kitchingroup.cheme.cmu.edu Pronouns: he/him/his