Date: Thu, 11 Apr 2002 14:21:23 -0400 (EDT)
From: Robin Wendler <[log in to unmask]>
Reply-To: [log in to unmask]
To: DC-Libraries Working Group <[log in to unmask]>
Subject: Re: Qualifiers for Creator, Contributor, Publisher
I've been out of the loop for a while, but...
I thought the whole point of the dumb-down rule was that the content of
the element must be semantically accurate, no matter what other bells and
whistles you might add to it locally. Are there limits to what can
be in a DCSV relative to the definition of the element? Unless the
content of each component of the DCSV conforms to the definition of the
element, it fails the dumb-down rule, to my mind. Are we only serving
recall here, or are we also serving precision?
I can and do see the tensions and constraints that the DD rule imposes,
and so understand the frustration. If the community finds that rule
impossible to live with, overturn it. But unless there are limits to
what the components of a DCSV can be, this approach seems like
pretending we're still conforming to it when we're not.
--Robin
Robin Wendler ........................ work (617) 495-3724
Office for Information Systems ....... fax (617) 495-0491
Harvard University Library ........... [log in to unmask]
Cambridge, MA, USA 02138 .............
On Thu, 11 Apr 2002, Clayphan, Robina wrote:
> This is also my understanding. Taking part of an example from the proposal,
> an application not decoding the DCSV would get the whole of the value for
> DC.Creator.author in a DC.Creator element as
> "familyName=Clayphan; givenName=Robina; affiliationLocation=The British
> Library; identifier=AAAA:xxxx".
>
> Whilst not very elegant, this does seem to meet the dumbdown requirement
> that "the remaining element value (without the qualifier) should continue to
> be generally correct and useful for discovery."
>
> Robina
>
> -----Original Message-----
> From: Ann Apps [mailto:[log in to unmask]]
> Sent: 11 April 2002 15:05
> To: [log in to unmask]
> Subject: Re: Qualifiers for Creator, Contributor, Publisher
>
>
> Diane,
>
> Sorry, I can't cite anything to back this up. I was just giving my
> understanding of DCSV. Because it is all encoded within a text
> string which is an element value, it is possible to read the value
> simply as the contents of the text string without making any
> attempt to decode it. I don't think there is any intention with
> DCSVs to make it a requirement to be able to parse them. But
> they do provide a parsable option to applications which want more
> specific detail.
>
> Ann
>
>
> Date sent: Mon, 8 Apr 2002 18:01:56 -0400
> Send reply to: DC-Libraries Working Group
> <[log in to unmask]>
> From: "Diane I. Hillmann" <[log in to unmask]>
> Subject: Re: [DC-LIBRARIES] Qualifiers for Creator,
> Contributor, Publisher
> To: [log in to unmask]
>
> > Ann:
> >
> > I'm not sure this is true. It's my understanding that there is still
> > much contention on this. Can you cite something to support your
> > belief that it is no longer an issue?
> >
> > Diane
> >
> > At 01:17 PM 4/8/2002 +0000, Ann Apps wrote:
> > >On Fri, 5 Apr 2002 Priscilla Caplan wrote:
> > >
> > > > What is the policy on dumbing-down structured values?
> > > >
> > >Priscilla,
> > >
> > >As I understand it, dumb-down is only an issue for element
> > >refinements. A DCSV is a text string which is the value of an
> > >element. If an application chooses not to decode the content of the
> > >DCSV it simply gets the whole string.
> > >
> > >I do think that this means that a DCSV string should be relatively
> > >human-readable without cryptic labels, ie so that a person could
> > >understand its content. But apart from that I don't think dumb-down
> > >is an issue of concern.
> > >
> > >Best wishes,
> > > Ann
> > >
> > >
> > >---------------------------------------------------------------------
> > >----- Mrs. Ann Apps. Senior Analyst - Research & Development, MIMAS,
> > > University of Manchester, Oxford Road, Manchester, M13 9PL, UK
> > >Tel: +44 (0) 161 275 6039 Fax: +44 (0) 0161 275 6040
> > >Email: [log in to unmask] WWW: http://epub.mimas.ac.uk/ann.html
> > >---------------------------------------------------------------------
> > >-----
> >
> > *~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*
> > Diane I. Hillmann
> > Project Manager & Metadata Specialist
> > National Science Digital Library Project at Cornell
> > Department of Computer Science Voice: 607/255-5691
> > 417 Rhodes Hall Fax: 607/255-4428
> > Ithaca, NY 14853 Email: [log in to unmask]
> > *~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*
> >
>
>
> --------------------------------------------------------------------------
> Mrs. Ann Apps. Senior Analyst - Research & Development, MIMAS,
> University of Manchester, Oxford Road, Manchester, M13 9PL, UK
> Tel: +44 (0) 161 275 6039 Fax: +44 (0) 0161 275 6040
> Email: [log in to unmask] WWW: http://epub.mimas.ac.uk/ann.html
> --------------------------------------------------------------------------
>
|