From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp12.migadu.com ([2001:41d0:2:bcc0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms0.migadu.com with LMTPS id sG8JMZTwQGIK+QAAgWs5BA (envelope-from ) for ; Mon, 28 Mar 2022 01:17:40 +0200 Received: from aspmx1.migadu.com ([2001:41d0:2:bcc0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp12.migadu.com with LMTPS id 2A60LZTwQGKkzAAAauVa8A (envelope-from ) for ; Mon, 28 Mar 2022 01:17:40 +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 5202239DAB for ; Mon, 28 Mar 2022 01:17:40 +0200 (CEST) Received: from localhost ([::1]:49562 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nYc8g-0004c6-Ui for larch@yhetil.org; Sun, 27 Mar 2022 19:17:38 -0400 Received: from eggs.gnu.org ([209.51.188.92]:60988) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nYc81-0004by-OF for emacs-orgmode@gnu.org; Sun, 27 Mar 2022 19:16:57 -0400 Received: from [2a00:1450:4864:20::429] (port=45903 helo=mail-wr1-x429.google.com) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1nYc80-0001Ok-2P for emacs-orgmode@gnu.org; Sun, 27 Mar 2022 19:16:57 -0400 Received: by mail-wr1-x429.google.com with SMTP id w4so17926936wrg.12 for ; Sun, 27 Mar 2022 16:16:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=KUh2S8vf5wDSsP4STKZb1P4+7PI7dWOxBP/BBqsKH0A=; b=HzD87tMyo3Q8XNxzkpMIQjXtisUcqwhONn89NL0OgdA/3JZW6/yYxB/igrg5DqhPA5 Ltl7bOYMwOqYVQJcf027y8snRijUVg3oPUTaRSguJKNGnplw15CmVd9gfTJsHalgUgia apdyp0KaXsyO9ARMelNQo1GeBbQnRPlKLUoVdzOMWzTtPi/CQmAujGRTx6d1uHyDMFnd cP6IgYI9YdThDFosllvrGMj0hfBF58SHBedOs7R6uHLd8PnYFISnzrgvbqWM7YBTi1TA YARxpAl7wTPr1jGTPcBcsZfhTdM7tEwAMkvu1GQAkWZk2k6pX/xNgADvJBPrhBGxryLJ fXFg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=KUh2S8vf5wDSsP4STKZb1P4+7PI7dWOxBP/BBqsKH0A=; b=uvLbd8rAzdgM46CCCnNymY1p+SP/P6+w0L9wsrcb1/VUx5T1JDEF+YKhIxxqaQIYVt Nm/j4435lz8tI4MnUKUJJWtaAK3tMfQLmS9XnJKnclog5ckJ7mx2X6eFqlxdVECa3623 2IwEUmDkiXo+Mldcp+P4mhZo9+P+3avg7nfLdTVrA+/jOQtKlRufk//eF59wPAQOMBvN zlZBBKit2HJ67f7Uc4llMmsarzpWJ0xxqh20VX6YaHnFyltRcjDXx2PpNvjsuc/WhI6G yY95GHZj4aBFfgeuZyTlXMZt+YriW6eZukl+c5b0FO8a3Gtd1uM1xuCfHLByGb1bgBUx +JMQ== X-Gm-Message-State: AOAM531KkL6vwpENmEHXZzKKwoXxRvhhbPlPaBWTtRevx4aZAdVksW9f TixP5ldfiySUFdq49yD8BfguSseW8Hu3xSWnaPE= X-Google-Smtp-Source: ABdhPJwaP8Q9C9EIDAQD+c4AMOj2t1naRqarc2P2BcR6ls3c51JCsFWNqpL/Hx8ZXUc51gy0aN6nrmShF3/Dvbad1es= X-Received: by 2002:a5d:5046:0:b0:1ed:9eac:bade with SMTP id h6-20020a5d5046000000b001ed9eacbademr19559618wrt.697.1648423012393; Sun, 27 Mar 2022 16:16:52 -0700 (PDT) MIME-Version: 1.0 References: <87wngosqvm.fsf@nicolasgoaziou.fr> <87k0ckjs4o.fsf@nicolasgoaziou.fr> In-Reply-To: From: "Bruce D'Arcus" Date: Sun, 27 Mar 2022 19:17:16 -0400 Message-ID: Subject: Re: citations: org-cite vs org-ref 3.0 To: John Kitchin Content-Type: text/plain; charset="UTF-8" X-Host-Lookup-Failed: Reverse DNS lookup failed for 2a00:1450:4864:20::429 (failed) Received-SPF: pass client-ip=2a00:1450:4864:20::429; envelope-from=bdarcus@gmail.com; helo=mail-wr1-x429.google.com X-Spam_score_int: -6 X-Spam_score: -0.7 X-Spam_bar: / X-Spam_report: (-0.7 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, 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 , org-mode-email , Nicolas Goaziou 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=1648423060; 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:in-reply-to:in-reply-to: references:references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:dkim-signature; bh=KUh2S8vf5wDSsP4STKZb1P4+7PI7dWOxBP/BBqsKH0A=; b=GJ7P8+U6dqDgjpm9NEx2cBN/c7o7GTrkREq11bNpsNiKTlzWvtC9uvI4kUIkTGQon+VD6P tHQvXqIhuVZ8DpkbyCV2srTkA5INCgO7WKdNViNZjo5BqZutPgy5LW7UeDyWSGpAAFkyXZ 45seVxBCzgh+lygeNVu/+be6tdXO0A70tSGxEsQIwex7WKYO8xqgDv4Ih4N/9yHdpLYmvD ioFgQ8jr3rE2Yd2K+6K5IhNWhiKvA+8p+07uonG2CBbJYNJM4fxTxftX1Jv80Z2Vy5K6n0 tL0omDf5/e+QOa/LTSAyeIDAv7gqPYemiF0n47AvMJr7/pP5C8foUXjfUKekFA== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1648423060; a=rsa-sha256; cv=none; b=CAKHoFx5nw7pPk0vunxG/HBSBt+RVkgNLJVPwwXu1VRhXM8BC534EB39KO2FNECNjqff3d iqopfUNssTRroMQy5K14AhRbZ9hAfTZFx2RmiahCvRgVAPy20kBRqA4Y+Laq8q38O7Qovw 6K1GzYwIwsSei+1UXQUxZPgJO7CmbMXnIGaYcxNdGuHvWfJ/zB/Fdn3pomGQgFZJqYR5mf 7i+qPGj5ifxUrxKymX3FtDT04ZpCvoXobLCvQ9qyiKcGSrn8JXTzAvpkIRwY75DZqkMx+b qjljcwM/7aeAXsRpOhAdBYmququqBwk80M78dFot2stLsyKHkSDgy+jvR2ZZbw== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=fail ("headers rsa verify failed") header.d=gmail.com header.s=20210112 header.b=HzD87tMy; dmarc=fail reason="SPF not aligned (relaxed)" header.from=gmail.com (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.13 Authentication-Results: aspmx1.migadu.com; dkim=fail ("headers rsa verify failed") header.d=gmail.com header.s=20210112 header.b=HzD87tMy; dmarc=fail reason="SPF not aligned (relaxed)" header.from=gmail.com (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: 5202239DAB X-Spam-Score: 6.13 X-Migadu-Scanner: scn0.migadu.com X-TUID: imcIqDHow6Nn On Sun, Mar 27, 2022 at 3:41 PM John Kitchin wrote: ... > 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? You mean why shouldn't we privilege natbib, as you have in org-ref? And let me turn the question around: how would you propose to translate those natbib-derived commands to biblatex, or CSL, so it works reliably across users and documents? The mapping has to happen someplace, after all. And from a UX POV, how well would that work for users who have no previous experience with natbib or even latex? ... > 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 think what Nicolas is asking is when you have time, to itemize the pain points that made development difficult for you, so that we might figure out how to improve them (perhaps new helper functions, etc.). As another data point, one of the things I've loved about org-cite is how easy I found it to develop pretty functional processors for citar with minimal code. Total LOC for citar is just under 2000, with just under 400 specific to org. But I'm deliberately developing a small, focused, modular, package. ... > 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. The org-cite citation syntax and model, I hope you would agree, is unambiguously better than natbib or the original org-ref syntax. It's simpler than biblatex in the sense of no difference between single and multicite citations, but can easily and losslessly map to and from either. Org-ref 3.0 adds essentially a copy of that syntax and model, with a trivial difference. To me, that's the biggest problem. Aside from users having incompatible documents, it forces other developers either to dedicate additional development and maintenance time to supporting both syntaxes, or to choose one. Pandoc only supports org-cite. In the case of citar, I have also decided to only support org-cite (though I leave the function to generate citations configurable, so it's easy enough for a user to configure this themselves; but I don't include this by default because I have other processor code that relies on parsed citations). Org-roam supports all three. It sounds like the biggest hold up was with reconciling the org-ref command model with more general approach of the oc style and variants. But as a first step, you could do as you originally planned to: simply use the same names for styles. If Nicolas were to allow the mapping in natbib to be handled via the defcustom, you could even do this without having to write and maintain your own export processor. And then you could save the other part (how to map those to other export processors) for another step, if and when you or your users need it or want it. Certainly that would address the most fundamental incompatibility. I guess to be direct: what value does the v3 syntax provide you, your users, or the org ecosystem in general? Bruce