On Thu, 25 Sep 1997, Misha Wolf wrote:
> Consider a DC-savvy search interface which allows me to enter, against
> the field Contributor, the search string:
>
> Chris Smith Illustrator
>
> A typical search engine will return all DC records where the Contributor
> field contains any of "Chris", "Smith" and "Illustrator". That leaves us
> with a few questions:
......
.......
But can we say there is a typical search engine for DC implementations? I
would imagine many of the implementations would have search
engines that allowed fielded searching.
......
......
> Hence, I stay with:
>
> <meta name="DC.contributor.name" content="Chris Smith">
> <meta name="DC.contributor.role" content="Illustrator">
> <meta name="DC.contributor.affiliation" content="United Illustrators">
>
> or:
>
> <contributor>
> <name>Chris Smith</name>
> <role>Illustrator</role>
> <affiliation>United Illustrators</affiliation>
> </contributor>
>
> The other approach proposed just doesn't scale. It was:
>
> <meta name="DC.contributor.illustrator" content="Chris Smith">
>
I can't help but feel that your preferred solutions are just shoving the
problem to the right hand side.... its a syntax solution, it doesn't solve
the real problem which is that proliferation of qualifiers works against
interoperability (however they are expressed). I think qualifiers will
only work where they are agreed between user communities, where that
community fixes on an enumerated list which can be communicated to
metadata creators, software provider and searchers. Otherwise the
qualifiers can't be used in the search process
> This would lead to things like:
>
> <meta name="DC.contributor.conductor" content="...">
> <meta name="DC.contributor.leadViolin" content="...">
> <meta name="DC.contributor.piano" content="...">
> <meta name="DC.contributor.vocals" content="...">
> <meta name="DC.contributor..." content="...">
>
> And I thought we were trying to keep down the number of sub-elements!
>
But would your solution stop people doing that?? As you say later there
would still need to be some way of imposing a finite list.
Oh, and isn't there the issue of how search engines would deal with
grouped, repeatable elements ... but I think that's another thread,
something for DC5 maybe?
Rachel
---------------------------------------------------------------------------
Rachel Heery, Research Group Co-ordinator
UKOLN (UK Office for Library and Information Networking)
University of Bath tel: +44 (0)1225 826724
Bath, BA2 7AY, UK fax: +44 (0)1225 826838
http://www.ukoln.ac.uk/
|