emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: John Tait <johngtait@gmail.com>
To: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Thesaurus terms as org tags -- feature request
Date: Thu, 14 Jul 2011 12:54:31 +0100	[thread overview]
Message-ID: <CAPDE7Wz5DTwhdHVpwrP2kMNCVCShr7D2g0RYO9vagDydxaE7rg@mail.gmail.com> (raw)

Dear all

Some time ago I floated a "tag hierarchy" idea for org-mode. It didn't
gain much interest (through I received some very kind replies).

http://lists.gnu.org/archive/html/emacs-orgmode/2011-03/msg01393.html

There are other similar ideas here.

http://lists.gnu.org/archive/html/emacs-orgmode/2010-10/msg01171.html

http://lists.gnu.org/archive/html/emacs-orgmode/2010-10/msg00611.html

What I've discovered since then is that what we are trying to reinvent
is a thesaurus concept, including a controlled vocabulary concept.
Thesauri seem to be well understood, and are standardised by ISO 2788.

What I am looking for then is a way of managing org tags using a very
simple thesauri terms -- inside an org file.

There's software out there to manage thesauri, but I think would be
fantastic to instead build taxonomies inside org-mode and use this to
drive org exports.

The problem I'm trying to solve is that, in big publishing projects,
the number of tags can grow and might eventually need to be managed
outside org-mode. (I'm already keeping lists of my tags inside
org-mode tables.)

What I would love to do is build a simple taxonomy of tags from a
controlled vocabulary -- that I can manage entirely inside org-mode.

Then we could:
 a) have an orderly list of tags (using the thesaurus "USE" concept,
etc.) to restrict tag bloat, and in fact have a controlled list of
tags/terms.
 b) allow nesting of tags (using the thesuaris Broader Term (BT) and
Narrower Term (NT) concepts).

This would allow export of, say, :colour: to export :red: :green: and
:blue:. It would also allow publishing project to be managed by
arranging NT/BT in one place in the org file, rather than
micromanaging tags in headings. Additionally, tags could belong to
more than one taxonomy in the same publishing project.

(The dreaded DITA 1.2 spec now has something like this in the guise of
Subject Scheme maps. But I don't want to look at DITA again.)

http://docs.oasis-open.org/dita/v1.2/cs01/spec/common/subjectScheme.html

I hope you know what I am on about...thanks again for your time.

John Tait

             reply	other threads:[~2011-07-14 11:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-14 11:54 John Tait [this message]
2011-07-18 23:45 ` Thesaurus terms as org tags -- feature request Bastien
2011-07-19 15:56   ` Achim Gratz
2011-07-22  5:42   ` Christian Moe
  -- strict thread matches above, loose matches on Subject: below --
2011-07-19 20:28 John Tait

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=CAPDE7Wz5DTwhdHVpwrP2kMNCVCShr7D2g0RYO9vagDydxaE7rg@mail.gmail.com \
    --to=johngtait@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).