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  December 1996

DC-GENERAL December 1996

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: SUBJECT and DESCRIPTION

From:

[log in to unmask] (Stu Weibel)

Reply-To:

dc-general

Date:

Wed, 11 Dec 1996 10:50:38 -0500

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (169 lines)

 
Well, the sense of the list has moved away from my original reading of
the consensus, to the point that I believe there is good reason to
declare another element.

Please review the 'official' list of elements and make any suggestions 
that you think might clarify the wording or intent.

thanks

stu
--------------------------------------------

	  Dublin Core Metadata Element Set: Reference Description

The following comprises the reference definition of the Dublin Core
Metadata Element set as of December, 1996.  The elements or their names
are not expected to change substantively from this list, though the
application of some of them are currently experimental and subject to
interpretation.  Further, it is expected that practice will evolve to
include sub-elements for certain of the elements.

Note that elements have a descriptive name intended to convey a common
semantic understanding of the element.  In addition, a formal,
single-word label is specified to make syntactic specification of
elements simpler in encoding schemes.


Element Descriptions 

   1 Title			Label: TITLE

     The name given to the resource by the CREATOR or PUBLISHER.

   2 Author or Creator		Label: CREATOR

     The person(s) or organization(s) primarily responsible for the
     intellectual content of the resource.  For example, authors in the
     case of written documents, artists, photographers, or illustrators
     in the case of visual resources.

   3 Subject and Keywords       Label: SUBJECT

     The topic of the resource, or keywords or phrases that describe
     the subject or content of the resource.  The intent of the
     specification of this element is to promote the use of controlled
     vocabularies and keywords.  This element might well include
     scheme-qualified classification data (for example, Library of
     Congress Classification Numbers or Dewey Decimal numbers) or
     scheme-qualified controlled vocabularies (such as MEdical Subject
     Headings or Art and Architecture Thesaurus descriptors) as well.
   
   4 Description		Label: DESCRIPTION

     A textual description of the content of the resource, including
     abstracts in the case of document-like objects or content
     descriptions in the case of visual resources.  Future metadata
     collections might well include computational content description
     (spectral analysis of a visual resource, for example) that may not
     be embeddable in current network systems.  In such a case this
     field might contain a link to such a description rather than the
     description itself.

   5 Publisher			Label: PUBLISHER

     The entity responsible for making the resource available in its
     present form, such as a publisher, a university department, or a
     corporate entity.   The intent of specifying this field is to
     identify the entity that provides access to the resource.
     
   6 Other Contributors		Label: CONTRIBUTORS

     Person(s) or organization(s) in addition to those specified in the
     CREATOR element who have made significant intellectual
     contributions to the resource but whose contribution is secondary
     to the individuals or entities specifed in the CREATOR element
     (for example, editors, transcribers, illustrators, and
     convenors).

   7 Date			Label: DATE

     The date the resource was made available in its present form.  The
     recommended best practice is an 8 digit number in the form
     YYYYMMDD as defined by ANSI X3.30-1985. In this scheme, the date
     element for the day this is written would be 19961203, or December
     3, 1996.  Many other schema are possible, but if used, they should
     be identified in an unambiguous manner.
   

     [does the group wish to specify RFC 822 dates here as well, or instead of?]   
     
   8 Resource Type 		Label: TYPE

     The category of the resource, such as home page, novel, poem, working
     paper, technical report, essay, dictionary.  It is expected that
     RESOURCE TYPE will be chosen from an enumerated list of types. A
     preliminary set of such types can be found at the following URL:
     
     http://www.roads.lut.ac.uk/Metadata/DC-ObjectTypes.html

   9 Format  			Label: FORMAT
   
     The data representation of the resource, such as text/html, ASCII,
     Postscript file,  executable application, or JPEG image.  The
     intent of specifying this element is to provide information
     necessary to allow people or machines to make decisions about the
     usability of the encoded data (what hardware and software might be
     required to display or execute it, for example).  As with RESOURCE TYPE,
     FORMAT will be assigned from enumerated lists such as registered
     Internet Media Types (MIME types).  In principal, formats can include
     physical media such as books, serials, or other non-electronic media. 

      
  10 Resource Identifier 	Label: IDENTIFIER

     String or number used to uniquely identify the resource.  Examples
     for networked resources include URLs and URNs (when implemented). Other
     globally-unique identifiers,such as International Standard
     Book Numbers (ISBN) or other formal names would also be candidates for 
     this element.

  11 Source			Label: SOURCE

     The work, either print or electronic, from which this resource is
     derived, if applicable. For example, an html encoding of a
     Shakespearean sonnet might identify the paper version of the
     sonnet from which the electronic version was transcribed.

  12 Language 			Label: LANGUAGE

     Language(s) of the intellectual content of the resource.  Where practical,
     the content of this field should coincide with the Z39.53 three character
     codes for written languages. 
     
     See: http://www.sil.org/sgml/nisoLang3-1994.html

     
  13 Relation			Label: RELATION 

     Relationship to other resources.  The intent of specifying this
     element is to provide a means to express relationships among
     resources that have formal relationships to others, but exist as
     discrete resources themselves.  For example, images in a
     document,  chapters in a book, or items in a collection.  A formal
     specification of RELATION is currently under development.  Users
     and developers should understand that use of this element should
     be currently considered experimental.

  14 Coverage			Label: COVERAGE

     The spatial locations and temporal durations characteristic of the
     resource.    Formal specification of COVERAGE is currently under
     development. Users and developers should understand that use of
     this element should be currently considered experimental.

  15 RIGHTS MANAGEMENT 		Label: RIGHTS
   
     The content of this element is intended to be a link (a URL or
     other suitable URI as appropriate) to a copyright notice, a
     rights-management statement, or perhaps a server that would
     provide such information in a dynamic way.  The intent of
     specifying this field is to allow providers a means to associate
     terms and conditions or copyright statements with a resource or
     collection of resources.   No assumptions should be made by users
     if such a field is empty or not present.

 
 

Top of Message | Previous Page | Permalink

JISCMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

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


WWW.JISCMAIL.AC.UK

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