emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: John Tait <johngtait@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Tag hierarchy idea redux -- thesaurus -- Feature request
Date: Wed, 13 Jul 2011 19:01:20 +0100	[thread overview]
Message-ID: <CAPDE7Wx=+r9uvgFxPrL8s6fO28Z3dkPJax8NigAsAn6p5NqWHA@mail.gmail.com> (raw)

Dear all

Some time ago I floated a "tag hierarchy" idea for org-mode. It didn't
gain much interest.

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

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

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

The problem I've 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.

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 "USE" concept, etc.) to
restrict tag bloat.
  b) allow nesting of tags (using the BT and NT concepts). This would
allow export of, say, :colour: to export :red: :green: and :blue:. It
would also allow the BT tags to be managed 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. Please don't make me 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-13 18:01 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CAPDE7Wx=+r9uvgFxPrL8s6fO28Z3dkPJax8NigAsAn6p5NqWHA@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).