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

Help for DC-USAGE Archives


DC-USAGE Archives

DC-USAGE Archives


DC-USAGE@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-USAGE Home

DC-USAGE Home

DC-USAGE  September 2005

DC-USAGE September 2005

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Something to look at re: Coverage

From:

Andrew Wilson <[log in to unmask]>

Reply-To:

A mailing list for the Dublin Core Metadata Initiative's Usage Board <[log in to unmask]>

Date:

Mon, 5 Sep 2005 14:43:38 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (69 lines)

Hey Pete

I hope you're not suggesting dc:date and dc:coverage have overlapping
semantics?

Andrew

-----Original Message-----
From: A mailing list for the Dublin Core Metadata Initiative's Usage
Board [mailto:[log in to unmask]]On Behalf Of Pete Johnston
Sent: 05 September 2005 14:33
To: [log in to unmask]
Subject: Re: Something to look at re: Coverage


Hi Diane,

I must admit I think that document oversimplifies things, because it
glosses over the fact that rather than having "geographic place or
location field(s)", metadata formats may have _multiple_ "fields" to
express _different_ types of relationship between the described resource
and a place/location.

e.g. as we've already discussed, "aboutness" and
"relevance/applicability" relationships are different; a format might
also deploy different fields to distinguish "place of origin", "place of
access" etc etc etc.

So the use of a particular "field" depends on whether it is appropriate
for that _particular_ type of relationship between the described
resource and the place.

If an application is using dc:coverage as a "geographic place bucket" -
i.e. to capture a relationship of _any_ type - between the described
resource and a place or location - then (it seems to me) that
application is really mis-using the dc:coverage property: even given the
current permissive definition of dc:coverage, it is _not_ a
"geographical bucket".

And the "it's just a bucket" approach becomes even worse if you take
into account that dc:coverage has a temporal aspect too: if it is a
"temporal bucket", then values may include any date or period associated
in any way with the resource - just like dc:date :-(

Pete

-----Original Message-----
From: A mailing list for the Dublin Core Metadata Initiative's Usage
Board [mailto:[log in to unmask]] On Behalf Of Diane I. Hillmann
Sent: 02 September 2005 22:35
To: [log in to unmask]
Subject: Something to look at re: Coverage


Folks:


You might want to look at:
http://oai-best.comm.nsdl.org/cgi-bin/wiki.pl?GeographicPlaces


as an example of how implementors are recommending use of Coverage.  As
I mentioned earlier in the conversation, in most situations the
recommendation is to use Coverage as a geographic place bucket, without
reference to "aboutness."


Diane

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

April 2024
March 2024
February 2024
January 2024
February 2023
January 2023
September 2022
July 2022
April 2022
March 2022
February 2022
November 2021
October 2021
September 2021
July 2021
June 2021
May 2021
October 2020
August 2020
July 2020
June 2020
January 2020
October 2019
September 2019
July 2019
June 2019
May 2019
March 2019
February 2019
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
March 2018
May 2015
November 2014
October 2014
April 2014
February 2014
June 2012
May 2012
April 2012
September 2011
May 2011
March 2011
February 2011
January 2011
October 2010
September 2010
August 2010
June 2010
May 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
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
December 2000
September 2000
August 2000
June 2000
May 2000
April 2000
March 2000
February 2000
January 2000
December 1999
November 1999


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