From: Karl Voit <devnull@Karl-Voit.at>
To: emacs-orgmode@gnu.org
Subject: Standard property proposal (was: org-jira.el... and Org conventions (Bastien, Carsten and all))
Date: Wed, 4 Jan 2012 00:34:54 +0100 [thread overview]
Message-ID: <2012-01-04T00-22-49@devnull.Karl-Voit.at> (raw)
In-Reply-To: 80ipkt6wfe.fsf@somewhere.org
Hi!
* Sebastien Vauban <wxhgmqzgwmuf@spammotel.com> wrote:
>
> But this triggers, for me, another "concern" which is the very wide variety of
> ways to define the same thing.
[...]
Totally agree to that.
> So, my point is: wouldn't it be better if we proposed standard properties in
> Org (in the manual), and implemented mappings in the Org "integration"
> packages (org-jira, org-taskjuggler, org-redmine and the like)?
>
> So, say for example that, from now on, it's more standard in Org to use
> "Assignee" (or anything else) for representing who's assigned a task, and have
> every package map the property "Assignee" to whatever keyword used in external
> tools for representing that concept?
I'd say that this issue is a HUGE one for the future of Org-mode. It
is ubiquitous to users all over. I myself had troubles adopting
org-contacts[1][2] because of only one single email property defined.
When I started developing software that *massively* converts user
data into Org-mode format[3], I felt this strange itch, whether my
property definitions are well chosen or not ...
I *love* the fact that Org-mode is so lightweight and so heavy the
same time - just as the user wants it.
But using conventions also has some drawbacks. Whenever someone
wants to define a certain format with properties for example, she
has to define her own way. If there is an Org-mode extension using
similar data, users woun't notice until some data show up on this
list and another Org-mode user is adding a hint.
So a free-to-use recommendation list of standard properties would be
*very* fine.
Part of my research work is in the field of information architecture
for personal information management. If I can be of any help in some
kind of discussion and definition process, I'd be glad.
[1] http://article.gmane.org/gmane.emacs.orgmode/47478
[2] http://article.gmane.org/gmane.emacs.orgmode/45347
[3] https://github.com/novoid/Memacs
--
Karl Voit
next prev parent reply other threads:[~2012-01-03 23:35 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-02 12:08 org-jira.el Bao Haojun
2012-01-03 8:07 ` org-jira.el... and Org conventions (Bastien, Carsten and all) Sebastien Vauban
2012-01-03 15:53 ` Bao Haojun
2012-01-03 16:25 ` Sebastien Vauban
2012-01-03 16:28 ` Allen S. Rout
2012-01-04 16:47 ` Bastien
2012-01-04 17:13 ` Nick Dokos
2012-01-03 23:34 ` Karl Voit [this message]
2012-01-04 16:50 ` Standard property proposal Bastien
2012-01-03 13:49 ` org-jira.el Marc Spitzer
2012-01-04 16:52 ` org-jira.el Bastien
2012-01-04 17:53 ` org-jira.el Nick Dokos
2012-01-05 10:00 ` org-jira.el Bastien
2012-01-05 14:42 ` org-jira.el Bao Haojun
2012-01-05 17:08 ` org-jira.el Jonathan Arkell
2012-01-06 0:32 ` org-jira.el Bao Haojun
2012-01-06 15:24 ` org-jira.el Bao Haojun
2012-01-04 18:36 ` org-jira.el Richard Riley
2012-01-04 19:49 ` org-jira.el Mehul Sanghvi
2012-01-05 10:01 ` org-jira.el Bastien
2012-01-05 15:42 ` org-jira.el OSiUX
2012-01-06 0:28 ` org-jira.el Bao Haojun
2012-01-06 15:54 ` org-jira.el Bao Haojun
2012-01-09 20:26 ` org-jira.el OSiUX
2012-01-10 2:40 ` org-jira.el Bao Haojun
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=2012-01-04T00-22-49@devnull.Karl-Voit.at \
--to=devnull@karl-voit.at \
--cc=emacs-orgmode@gnu.org \
--cc=news1142@Karl-Voit.at \
/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).