JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for DC-GENERAL Archives


DC-GENERAL Archives

DC-GENERAL Archives


DC-GENERAL@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

DC-GENERAL Home

DC-GENERAL Home

DC-GENERAL  November 2008

DC-GENERAL November 2008

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: [Public Comment] DCAP Guidelines

From:

"Diane I. Hillmann" <[log in to unmask]>

Reply-To:

Diane I. Hillmann

Date:

Tue, 11 Nov 2008 10:54:33 -0500

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (68 lines)

Owen:

Some comments below ...

Stephens, Owen wrote:
> Isn't this the point of the section on Selecting or Defining Metadata
> Terms though - reuse what you can, invent only what you must? The
> aspects of FOAF that are usable should be used, as it introduces the
> potential for more flexibility - the fact that FOAF isn't rich enough
> for all aspects of Library authority files just means that librarian's
> will have to look elsewhere or define new elements where existing FOAF
> elements aren't enough.
>
>
I have no argument with this, except that there's this swirl of other
activity happening that I fervently hope will enrich our choices in this
regard, and I'd really like to see that acknowledged.  It's not that
FOAF isn't rich enough--for what it is, it's fine--we use some FOAF
properties in the NSDL Registry, for example, for user management.  In
the library world, there's not usually a need (or a desire, either) to
manage information like email address, which people sometimes change as
often as they change their underwear.  Things like alternative forms of
name are important, because folks who write things often change the way
they express their names over time, for a variety of reasons.  And in
libraries, the notion that when you search for an author you should be
able to get everything associated with that author is important.  FOAF
isn't a good match for those needs, and despite Dan's flexibility about
adding stuff, I'm not sure he should.

As we all know, there's this big glob of name authority data, built by
the library community over decades, managed by LC, which we'd all (or
mostly all) like to have available for this task. It could be used with
FOAF, not necessarily instead of, since the current MARC21 expression of
the information doesn't parse names very well, for instance.  We've been
told that the exposure of this data as a web service with URIs is
coming, but we don't know when. So, should we just ignore this
information, or should we acknowledge it, and suggest ways that people
can do what they need to do in their DCAP to ensure that they'll be able
to take advantage of this when it comes?  I'd go for the latter, myself.
> I think there is a danger in trying to make this document digestible to
> the (more conservative?) elements of an existing metadata community, it
> becomes a 'library guide to DCAP' - there might be a place for a
> document like this, but I don't think this is it.
>
>
I'd like to make the document relevant to the broadest swath of the
community that we can, without having to build a "library guide to
DCAP."  I frankly don't see the point of ignoring the needs we already
know about in probably the largest constituency that DCMI has.  Trust
me, the conservative types will never even look at this, but the ones
who want to participate in these newer options will look, and I would
like them to be able to understand that they don't need to "dumb down"
their data in order to participate.  This is a concern I hear regularly,
in fact, and though I understand the desire not to go too far into the
bushes, I think we ignore those concerns at our peril.
> In general I'd support the comments about examples used in this draft -
> examples are just examples - they could all be replaced with
> 'example.com/1234' etc. but I think the use of real world examples is
> better - but it shouldn't be taken as a recommendation for a particular
> set of elements.
>
>
Agreed, but in order to avoid the possibility that real-world examples
be taken for recommendations, we need to be really clear about what's
what and not assume that readers know the difference.

Diane

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

February 2024
May 2022
April 2022
March 2022
March 2020
February 2019
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
September 2003
August 2003
July 2003
June 2003
May 2003
April 2003
March 2003
February 2003
January 2003
December 2002
November 2002
October 2002
September 2002
August 2002
July 2002
June 2002
May 2002
April 2002
March 2002
February 2002
January 2002
December 2001
November 2001
October 2001
September 2001
August 2001
July 2001
June 2001
May 2001
April 2001
March 2001
February 2001
January 2001
December 2000
November 2000
October 2000
September 2000
August 2000
July 2000
June 2000
May 2000
April 2000
March 2000
February 2000
January 2000
December 1999
November 1999
October 1999
September 1999
August 1999
July 1999
June 1999
May 1999
April 1999
March 1999
February 1999
January 1999
December 1998
November 1998
October 1998
September 1998
August 1998
July 1998
June 1998
May 1998
April 1998
March 1998
February 1998
January 1998
December 1997
November 1997
October 1997
September 1997
August 1997
July 1997
June 1997
May 1997
April 1997
March 1997
February 1997
January 1997
December 1996
November 1996
October 1996
September 1996
August 1996
July 1996
June 1996
May 1996
April 1996
March 1996


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager