From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: Re: tags for functions
Date: Thu, 22 Jan 2009 08:47:01 -0600 [thread overview]
Message-ID: <86prif9z4q.fsf@lifelogs.com> (raw)
In-Reply-To: d2afcfda0901220007u76993eecm99c440be3aa4807f@mail.gmail.com
On Thu, 22 Jan 2009 03:07:23 -0500 MON KEY <monkey@sandpframing.com> wrote:
>> 2) refine the keywords into a simple taxonomy that is not too big nor too small.
>> The first question I have is, how to associate keywords with a function?
MK> Keep in mind that a taxonomic description of code's content/concepts
MK> is entirely different from a coded object class hierarchy - the
MK> distinction is subtle and all to often overlooked... esp. by
MK> programmers who *are* in fact quite adept at creating taxonomy in
MK> code.
MK> Please consider examining the following standard for a comprehensive
MK> approach to accomplishing this task with optimal consideration of TRT.
MK> ANSI/NISO Z39.19-2005
MK> Guidelines for the Construction, Format, and Management of Monolingual
MK> Controlled Vocabularies
MK> ISBN: 1-880124-65-3
MK> Available here: http://www.niso.org/standards/resources/Z39-19-2005.pdf
Well, at 180 pages of dense information this is a serious standard.
Also it defines "taxonomy" as a structural hierarchical classification,
whereas I've used it loosely to mean a tag space. I'll use "tag space"
from now on to be clear.
Since we're not classifying general knowledge but a very specific domain
(Emacs Lisp functions) I don't think the standard needs to be applied.
It makes some good points, but things like a full hierarchy are
overkill, and others like proper name conventions just don't apply.
I'll try to be consistent with its naming recommendations, at least.
It brings up "synonym rings" which may be necessary: I propose 50% of
the effort is to come from each package's predeclared Keywords header.
That's determined by the package author so it's not easy to enforce a
particular tag space over all of Emacs. With synonym rings, we can
associate synonymous keywords together.
Once the list of keywords is established, you should take a look to see
if you agree with it or have suggestions for improvements. I'll post
here.
Ted
next prev parent reply other threads:[~2009-01-22 14:47 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-22 8:07 tags for functions MON KEY
2009-01-22 14:47 ` Ted Zlatanov [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-01-23 1:46 S+*n_Pe*rm*n
2009-01-27 18:53 ` MON KEY
2009-01-22 18:15 S+*n_Pe*rm*n
2009-01-22 18:49 ` MON KEY
2009-01-22 20:38 ` Ted Zlatanov
2009-01-20 20:36 Ted Zlatanov
2009-01-20 20:44 ` Lennart Borgman
2009-01-21 22:11 ` Ted Zlatanov
2009-01-21 22:13 ` Lennart Borgman
2009-01-22 14:20 ` Ted Zlatanov
2009-01-22 19:39 ` Stefan Monnier
2009-01-22 20:09 ` Ted Zlatanov
2009-01-21 22:22 ` Glenn Morris
2009-01-22 14:54 ` Ted Zlatanov
2009-01-25 0:32 ` Juri Linkov
2009-01-26 19:50 ` Ted Zlatanov
2009-01-26 23:55 ` Juri Linkov
2009-01-27 14:31 ` Ted Zlatanov
2009-01-28 0:02 ` Juri Linkov
2009-01-28 0:36 ` Lennart Borgman
2009-01-28 17:41 ` Ted Zlatanov
2009-01-28 18:40 ` Stefan Monnier
2009-01-28 20:38 ` Ted Zlatanov
2009-01-29 1:43 ` Stefan Monnier
2009-01-29 20:03 ` Ted Zlatanov
2009-01-29 21:52 ` Stefan Monnier
2009-01-30 15:34 ` Ted Zlatanov
2009-01-30 16:06 ` Drew Adams
2009-01-30 16:52 ` Ted Zlatanov
2009-01-31 17:52 ` Juri Linkov
2009-01-31 1:55 ` Stefan Monnier
2009-01-31 2:02 ` Drew Adams
2009-01-29 20:32 ` Lennart Borgman
2009-01-30 15:29 ` Ted Zlatanov
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86prif9z4q.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=emacs-devel@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.