On Wed, 10 Nov 2004 07:42:56 -0800, Walter Underwood <[EMAIL PROTECTED]> wrote:
>
>
>
> --On Tuesday, November 9, 2004 9:42 PM -0800 Tim Bray <[EMAIL PROTECTED]>
> wrote:
> > On Nov 9, 2004, at 9:10 PM, Walter Underwood wrote:
> >
> >> So, a decent solution ought to have (some of these optional):
> >>
> >> an ID for the taxonomy
> >> an ID for the category within that
> >> a name for the category ("Safety")
> >> a display string for the category ("Maritime > Safety")
> >
> > I wonder why you need both a name and an ID; if you conflate those two,
> > you have more or less PaceCategoryRevised. -Tim
>
> The simple category names are not unique because of common subheadings.
> "Safety" is the name of both "Maritime > Safety" and "Highways > Safety".
> So you need some other node ID to distinguish them.
Ok, but it does seem to be leading towards a big jump from a simple
string in dc:subject.
> This is a real example from the National Transportation Library
> at the US Dept. of Transportation. We added full a topic path
> display option because the simple names were insufficient.
Couldn't the topic path be used as the label instead of the name where needed?
> In library jargon, "classification" gives a unique hierarchial location
> for each document, because it is used for shelf position, while
> "subject headings" allow discovery under multiple categories.
> A subject heading might have multiple parents, while classification
> cannot.
Couldn't such a situation be dealt with using multiple elements where
needed, being explicit, something like:
<category scheme="http://library.com/classification";
term="Maritime/Safety" label ="Maritime > Safety" />
<category scheme="http://library.com/headings"; term="Safety" label ="Safety" />
Cheers,
Danny.
--
http://dannyayers.com
