Re: proposal for subjects in subject tree

"Billy Barron, VAX/Unix Systems Manager" <> Tue, 01 December 1992 00:55 UTC

Received: from by IETF.CNRI.Reston.VA.US id aa19039; 30 Nov 92 19:55 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa19035; 30 Nov 92 19:55 EST
Received: from kona.CC.McGill.CA by CNRI.Reston.VA.US id aa22277; 30 Nov 92 19:56 EST
Received: by (5.65a/IDA-1.4.2b/CC-Guru-2b) id AA00960 on Mon, 30 Nov 92 16:56:38 -0500
Received: from by with SMTP (5.65a/IDA-1.4.2b/CC-Guru-2b) id AA00952 (mail destined for /usr/lib/sendmail -odq -oi -fiafa-request iafa-out) on Mon, 30 Nov 92 16:56:30 -0500
Received: from by (PMDF #2700 ) id <>; Mon, 30 Nov 1992 15:51:17 CDT
Date: 30 Nov 1992 15:51:16 -0500 (CDT)
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: "Billy Barron, VAX/Unix Systems Manager" <>
Subject: Re: proposal for subjects in subject tree
Message-Id: <>
X-Vms-To: IN%""
X-Vms-Cc: IN%",,,,"
Mime-Version: 1.0
Content-Transfer-Encoding: 7BIT

>then in fact only the top level of the tree will be different,
>perhaps all the bottom trees will be in common.
>The tree will have two roots. Its only when you have to
>uniquely number the things that you force a single subject tree.
I see the problem as being that most of our maintainer (SEPAs) will have items
like Biology.  If one group has Unecso and another LCC, then inside Biology
will not fit one or both of those systems...  Maybe we don't care, but many
librarians will.  Also, the low levels may not be the same.  For example, one
system might have "literature, 20th century by author" and the other has
"literature, country by author".

Billy Barron, VAX/UNIX Systems Manager, University of North Texas, billy@untvax.bitnet, THENET: NTVAX::BILLY