emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Thorsten Jolitz <tjolitz@gmail.com>
To: emacs-orgmode@gnu.org
Subject: [PARSER] Why not add properties to type 'org-data'?
Date: Thu, 05 Sep 2013 17:34:12 +0200	[thread overview]
Message-ID: <87y57be0zv.fsf@gmail.com> (raw)


Hi List, 

why isn't some of the meta-data available from the communication channel
during export (especially the environmental data) stored in a property
list for the 'org-data' element type during parsing?

Of course in common use org-elements are tightly bound to a certain org
file, and that org file is used from Emacs, so all the meta-data is
there and available.

But imagine for a moment org-elements (e.g. type 'headline') are stored
somewhere else in a different (DB) format. Then those headlines/subtrees
are not tightly coupled with a file anymore, they can be used
individually, recombined to new documents etc. - each of them becomes a
individual DB object, the original containing org file is merely one of
their attributes.

In such a situation, it would of course be necessary to store
information about the 'org-data' element each of the headline elements
belonged to originally, if only to be able to reconstruct the original
org file. A simple DB link from the headline to the containing
'org-data' could do this - but currently all 'org-data' objects are
anonymous undistinguable objects with empty property lists.

Wouldn't it make sense to replace 

,----------------------------------------------
| (org-data nil (section (:begin 1 :end 52 ...)))
`----------------------------------------------

with something like

,-------------------------------------------------------------------------
| (org-data (:id-or-name file001 :input-file /my/file.org :author me :date
| 01-01-2013 :description my planning data) (section (:begin 1 :end 52
| ...)))
`-------------------------------------------------------------------------

?

-- 
cheers,
Thorsten

             reply	other threads:[~2013-09-05 15:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-05 15:34 Thorsten Jolitz [this message]
2013-09-05 19:14 ` [PARSER] Why not add properties to type 'org-data'? Nicolas Goaziou
2013-09-05 21:24   ` Thorsten Jolitz
2013-09-07  7:15     ` Nicolas Goaziou
2013-09-07  9:28       ` Thorsten Jolitz

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=87y57be0zv.fsf@gmail.com \
    --to=tjolitz@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).