From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: MON KEY Newsgroups: gmane.emacs.devel Subject: Re: tags for functions Date: Thu, 22 Jan 2009 13:49:26 -0500 Message-ID: References: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1232650181 18152 80.91.229.12 (22 Jan 2009 18:49:41 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 22 Jan 2009 18:49:41 +0000 (UTC) Cc: emacs-devel@gnu.org To: tzz@lifelogs.com Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jan 22 19:50:53 2009 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1LQ4dh-0000Bf-MR for ged-emacs-devel@m.gmane.org; Thu, 22 Jan 2009 19:50:53 +0100 Original-Received: from localhost ([127.0.0.1]:37534 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LQ4cQ-0004rj-6o for ged-emacs-devel@m.gmane.org; Thu, 22 Jan 2009 13:49:34 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LQ4cM-0004rC-Fx for emacs-devel@gnu.org; Thu, 22 Jan 2009 13:49:30 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LQ4cK-0004qn-UY for emacs-devel@gnu.org; Thu, 22 Jan 2009 13:49:30 -0500 Original-Received: from [199.232.76.173] (port=48000 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LQ4cK-0004qi-OT for emacs-devel@gnu.org; Thu, 22 Jan 2009 13:49:28 -0500 Original-Received: from rn-out-0910.google.com ([64.233.170.185]:35182) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LQ4cK-0001Z2-Bp for emacs-devel@gnu.org; Thu, 22 Jan 2009 13:49:28 -0500 Original-Received: by rn-out-0910.google.com with SMTP id k50so824700rnd.7 for ; Thu, 22 Jan 2009 10:49:27 -0800 (PST) Original-Received: by 10.64.88.2 with SMTP id l2mr772745qbb.131.1232650166538; Thu, 22 Jan 2009 10:49:26 -0800 (PST) In-Reply-To: X-Google-Sender-Auth: 025a6785c9dd0a19 X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:108107 Archived-At: Forgot to mention that the initial formulation of a controlled vocabulary may well be already done for you. If you consider that the emacs/elisp info manuals are *already* formatted in a structured manner not unlike the Z39.19 you might recognize that many of the `keywords' and relationships you need are already in the .texi source. I suggest you start with the the .texi source and extract the relevant terms as a proposed hierarchy for your controlled vocabulary. This can then be extended by with `freely assignable 'sub-tags' attached to the core controlled headwords. BT: Yanking::Replacing Yanks <= post :: is the authors `freely assigned' sub-tag NT: Earlier Kills::Regexp on Kill Ring <= post :: is the authors `freely assigned' sub-tag RT: Mark Ring::Conditional Yanks <= post :: is the authors `freely assigned' sub-tag Such a structure might afford integration/reflection with make-info at build time and present a more consistent interface at a higher level.