From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Graph not hierarchical?
Date: Tue, 18 Feb 2014 13:00:22 -0500 [thread overview]
Message-ID: <87bny4nvwp.fsf@alphaville.bos.redhat.com> (raw)
In-Reply-To: ir4k3cs2vbb.fsf@lycastus.phy.bnl.gov
Brett Viren <bv@bnl.gov> writes:
> Lawrence Bottorff <borgauf@gmail.com> writes:
>
>> being able to organize and
>> extract based on your stuff being stored graph-aware would be nice,
>> IMHO.
>
> I'm by no means an expert on this but I know org-element-parse-buffer
> returns a data structure which is a directed-graph.
>
> http://orgmode.org/worg/org-api/org-element-api.html
>
> Note, each node has a :parent reference which makes the data structure
> circular. Traversing it must take this feature into account.
>
I thought Lawrence was looking for a way to *impose* a graph structure
on his data (stored in an org file, augmented with whatever is necessary
to implement his graph(s)). org-element-parse-buffer returns a graph
(actually, it's probably closer to a tree) which reflects the *internal*
structure of the org document.
In some ways, the analogy here is between a Unix file (internal structure:
sequence of bytes, operations: open/close/read/write/seek/etc) on one
hand, and a structured file: e.g. compiling a program
into some intermediate language and storing the result into a file.
The file itself doesn't know anything about the structure of its
contents: the contents are just a sequence of bytes. But there are
tools (compilers, loaders, assemblers, debuggers, etc.) that
"understand" the superimposed structure.
Similarly here, we have an ordinary org file, but it contains additional
stuff that allow other tools to do special things (e.g. cross-link
sections of the document into a directed graph). Org itself provides
certain mechanisms that *could* be used for that (properties, links)
but would not itself "understand" the additional structure. You'd need
other tools (probably built on top of org-element-*) to do that.
The challenge here is that you can impose structure in a very specific
manner, so that both the structure and the tools are only useful in a
very specific setting. Or you try to come with generic structure and
generic tools that can accommodate a variety of applications. The
balance between these two extremes (surgical scalpel vs kitchen sink) is
very much a matter of need, taste and experience.
That's my understanding - I hope I have not misrepresented the situation
too much.
--
Nick
next prev parent reply other threads:[~2014-02-18 18:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-15 2:58 Graph not hierarchical? Lawrence Bottorff
2014-02-15 10:44 ` Eric S Fraga
2014-02-15 15:34 ` Lawrence Bottorff
2014-02-15 21:05 ` Eric S Fraga
2014-02-18 17:18 ` Brett Viren
2014-02-18 18:00 ` Nick Dokos [this message]
2014-02-18 18:33 ` Samuel Wales
2014-02-18 18:36 ` Samuel Wales
2014-02-18 18:46 ` Samuel Wales
2014-02-20 3:11 ` Lawrence Bottorff
2014-03-01 7:26 ` Bastien
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bny4nvwp.fsf@alphaville.bos.redhat.com \
--to=ndokos@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).