I have been monitoring the discussion and have a couple of comments.
I would like to see 'audience' elevated to an element rather than try to
qualify 'audience' in DC.Description or DC.Subject. DC.Description being
free text allows the opportunity to drop in terminology which describes the
object using natural language. By creating an element for 'audience' then
qualifying the element with the user levels, target audience, etc. would
provide more precise searching. Further I see audience as a way of limiting
the search strategy via the element to focus on specific targeted resources
and hence improve precision. I do not see DC.Description
(qualified)offering the same amount of precision.
I believe we should concentrate on describing the resource. However, it is
helpful to our clients to provide information about the audience, especially
in education, when the resource has been designed to suit a level of
student, target group, learning context, etc. This does not preclude others
from using the resource but at least they know for whom it was developed and
that is added information.
I do have education blinkers on hence the above. However, I would have
thought other disciplines would have need for 'audience'. Jon it would be
interesting to know how much out there is 'audience-neutral'. As you have
said Stuart, time will tell.
Is DCMI out on this debate and we do have to qualify 'audience' within the
15 Dublin Core set of elements?
It was great to put faces to names last Thursday in Adelaide, but wow! the
heat, even for a Queenslander.
Regards
Myrl
Myrl Allison
Senior Librarian and Web Services Metadata Project Officer
Education Queensland Library
Phone 07 32370602(Tuesday) Phone 07 32370512
email: [log in to unmask]
http://www.qed.qld.gov.au
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
|