all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Bruce D'Arcus" <bdarcus@gmail.com>
To: Tom Gillespie <tgbugs@gmail.com>
Cc: org-mode-email <emacs-orgmode@gnu.org>,
	John Kitchin <jkitchin@andrew.cmu.edu>
Subject: Re: Expanding how the new cite syntax is used to include cross-references - thoughts?
Date: Wed, 11 Aug 2021 07:13:13 -0400	[thread overview]
Message-ID: <CAF-FPGNVjfcwyHTOu32JavzG-yWvweCF5fY5xdX+KmYgKESeAA@mail.gmail.com> (raw)
In-Reply-To: <CA+G3_PPt0Q4gfnG9SDfRDs_7AnTb1y-MATu=aGQ3=xXNxwESdw@mail.gmail.com>

Here's a recent subthread on this question:

https://lists.gnu.org/archive/html/emacs-orgmode/2021-07/msg00233.html

At the end of that discussion, my argument against using citations for
cross-references:

1. Cross-references are not citations, neither conceptually, nor in
software implementations. In LaTeX, MS Word, Libre office, InDesign,
etc, cross-references are handled differently than citations. There,
they are typed internal links. You can get a sense of how this works
in this tutorial for Word, which includes a list of cross-reference
types, and so hints at the range of things people need to internally
reference:

https://www.customguide.com/word/how-to-cross-reference-in-word

2. As John and Joost noted on that thread, because they're different,
they raise a range of implementation questions, most notably for me
what org-cite processors are supposed to do with these citations that
are not citations. As it is now, the user would just get errors and/or
unexpected output.

On Wed, Aug 11, 2021 at 1:28 AM Tom Gillespie <tgbugs@gmail.com> wrote:

...

> Actually, having written this now, I think that both solutions have
> their own use cases. Org cite is clearly about providing evidence for,
> or a scholarly reference for something, and critically it can embed
> some metadata about that reference in the document as a citation or
> perhaps as an excerpt (and extension of what org-ref does now when the
> cursor is over a reference?). Regular links do not provide any way to
> embed metadata within the document, they are purely pointers.

Right, which is what a cross-reference is.

It's just there needs to be some way to distinguish among types of
targets, I think.

> I think it would be a mistake to use up equation/eq and table/tbl or
> figure/fig prefixes for references that are internal to org, because it implicitly
> limits/collides with the #+link: keyword.

Is there a workaround for this somehow, or an alternative that gets
the same thing in the end?

Bruce


  reply	other threads:[~2021-08-11 11:14 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-11  0:58 Expanding how the new cite syntax is used to include cross-references - thoughts? John Kitchin
2021-08-11  1:19 ` Bruce D'Arcus
2021-08-11  5:28   ` Tom Gillespie
2021-08-11 11:13     ` Bruce D'Arcus [this message]
2021-08-11 11:54       ` Bruce D'Arcus
2021-08-11 13:43         ` John Kitchin
2021-08-11 14:32           ` Bruce D'Arcus
2021-08-11 14:56             ` John Kitchin
2021-08-11 15:41               ` Bruce D'Arcus
2021-08-11 16:08                 ` Timothy
2021-08-11 16:26                   ` Bruce D'Arcus
2021-08-11 14:13       ` John Kitchin
2021-08-12 15:23         ` Bruce D'Arcus
2021-08-12 17:19           ` John Kitchin
2021-08-12 18:06             ` Bruce D'Arcus
2021-08-13 15:22             ` Eric S Fraga
2021-10-10 13:30               ` Bruce D'Arcus
2021-10-12 21:16                 ` John Kitchin
2021-10-12 21:58                   ` Bruce D'Arcus
2021-10-12 23:27                     ` John Kitchin
2021-10-13  0:08                       ` Bruce D'Arcus
2021-08-11 13:23   ` John Kitchin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAF-FPGNVjfcwyHTOu32JavzG-yWvweCF5fY5xdX+KmYgKESeAA@mail.gmail.com \
    --to=bdarcus@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=jkitchin@andrew.cmu.edu \
    --cc=tgbugs@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.