Re: adding a new org-element?

[Eric S Fraga <e.fraga@ucl.ac.uk>]

Interesting points raised in your last email.  And also reminiscent of
the citation discussion... for better or for worse ;-)

org currently has effective support for literate programming with babel;
however, it has only rudimentary support for data: tables and properties
(and maybe tags).  More and more we are finding the desire to work with
data more generally outwith the constraints imposed by the current
support.

Links provide another interface to data but also rather rudimentary.

Maybe it is time to generalise some of these concepts while keeping
parsing straightforward.

I would be strongly in favour of some type of structure that supported
the equivalent of JSON in terms of data representation but with programming
functionality for export, interaction and display as provided by links
to some degree.

However, the easiest solution may be to extend the link syntax and
implementation, or maybe just the implementation, to address some of the
current limitations, especially in terms of display but also in terms of
linking to other objects in the org file (or even to other org files)?

At present, links have follow and export functionality.  The follow
functionality is a start towards actions on the data and is complete, in
the Turing sense, given that the full power of elisp is there.  Likewise
for export.  Two things are missing: linking and display.

Linking (confusing terminology: maybe cross-referencing) between "link
objects" could be imposed on the description which can then be processed
by the follow parameter.  Nevertheless, it probably would be desirable
to have a naming capability for individual link instances, one of the
aspects discussed in the citation thread IIRC.  What is missing entirely
in links is display functionality; this could be added as a third
argument to the link definition.

-- 
: Eric S Fraga (0xFFFCF67D), Emacs 25.0.91.1, Org release_8.3.4-626-gb62d55