Ron Daniel wrote:
> In trying to
> create examples of its use for the RDF working group, I've just noticed
> that trying to define the role of a contributor is a bit awkward.
> The "scheme" qualifer could be used to say
> <contributor scheme="illustrator">Chris Smith</creator>
> except that it should really be used for things like "AACR2" which
> defines a whole bunch of potential types of contributors. We used to
> have the "role" qualifier to handle exactly this problem, but that
> got thrown out a long time ago.
>
> Recommendations?
Dave Beckett replied:
> I think the reasoning for throwing out the role is that it was a
> refinement of contributor i.e. a sub-structure so it would be
>
> Element: contributor.illustrator
> Value: Chris Smith
>
> and any further qualifiers (Scheme, Language) as appropriate.
>
> If the sub-element structure ('minimalist') wanted to look at it, it
> would be still clear that Chris Smith was a contributor.
When I suggested, at DC4, that "role" is inappropriate as a distinct
qualifier, I argued that "role" is simply an instance of "type". Hence:
<meta name="DC.contributor.name" content="Chris Smith">
<meta name="DC.contributor.role" content="Illustrator">
<meta name="DC.contributor.affiliation" content="United Illustrators">
and:
<contributor>
<name>Chris Smith</name>
<role>Illustrator</role>
<affiliation>United Illustrators</affiliation>
</contributor>
--------------------------------------------------------------------------
Misha Wolf Email: [log in to unmask] 85 Fleet Street
Standards Manager Voice: +44 171 542 6722 London EC4P 4AJ
Reuters Limited Fax : +44 171 542 8314 UK
--------------------------------------------------------------------------
Fifth DC Metadata Workshop, 6-8 Oct 1997, linnea.helsinki.fi/meta/DC5.html
------------------------------------------------------------------------
Any views expressed in this message are those of the individual sender,
except where the sender specifically states them to be the views of
Reuters Ltd.
