emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
* Tag hierarchy idea redux -- thesaurus -- Feature request
@ 2011-07-13 18:01 John Tait
  0 siblings, 0 replies; only message in thread
From: John Tait @ 2011-07-13 18:01 UTC (permalink / raw)
  To: emacs-orgmode

Dear all

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


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..!)


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

John Tait

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2011-07-13 18:01 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-07-13 18:01 Tag hierarchy idea redux -- thesaurus -- Feature request John Tait

Code repositories for project(s) associated with this public inbox


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).