Dublin Core 9/23/03

Changes 9/23/03 by Clay Templeton

1)replaced “identifier” and “identifier.alternate” with “identifier.persistent” and “identifier.url”. Rationale: the name “identifier.persistent” explicitly identifies this field as the proper place for a persistent identifier. Additional “identifier” refinements may be negotiated in the future. (definitions also changed)

2) rights.resourceAvailability was deleted. Rationale: making the NLM resourceAvailability element a refinement of DC:rights led to a rather bizarre interpretation. There is agreement that resourceAvailability is a useful element, but consensus has not been reached on which DC element it should refine or whether perhaps it ought to stand as an extension.

3) The format definition was changed to be more in line with DC definitions; the word “medium” was replaced with the word “structure”.

Note: At the second MRG meeting 9/22, it was agreed that a media element is desirable. However, it is unclear what DC element this would extend or if it would stand alone as an extension.

Changes 9/14/3 by Clay Templeton:

1) eliminated format.medium element. Rationale: two format elements, format and format.medium, were being used so that a physical format could be indicated in the latter and the arrangement of information on that physical format (e.g. mime type in the case of computer disks), could be given in the former. It seems that since mime type occurs in only a certain class of resources while all resources have some physical format to speak of (even if that physical format is the vague ‘internet’) it makes more sense for the unqualified format element to contain an indication of physical format. An area of future exploration is whether this should be supplemented by a qualified format term and what it ought to look like.

2) Simplified definitions. Rationale: The old ones were unnecessarily confusing and made a lot of assumptions that were not warranted by any existing circumstance at Goddard. The new, simplified definitions are easier to apply intuitively. Specifically, references to the FRBR rules have been eliminated, as have assumptions about the use of persistent identifiers and medium specific details.

3) Began documenting changes

I. Descriptive Elements

title

title.alternate

creator

creator.employee

creator.organization

creator.code

creator.contract

creator.missionsProjects

creator.instrument

contributor

contributor.employee

contributor.organization

contributor.code

contributor.contract

contributor.missionsProjects

contributor.instrument

subject

subject.employee

subject.organization

subject.missionsProjects

subject.disciplines

subject.instrument

subject.functions

subject.industries

subject.uncontrolled

description

date

date.created

date.available

date.modified

publisher

publisher.organization

type

type.information

type.contentInvariance

format

identifier.persistent

identifier.url

source

language

relation.hasVersion

coverage.spatial

coverage.chronology

coverage.projectPhase

rights

audience

The Title element contains a name of the resource.

The Title.alternate element contains some other name of the resource.

The Creator element contains the name of an entity that participated in the creation of the resource.

The Creator.employee element contains the name of an employee that participated in the creation of the resource.

The Creator.code element contains a Goddard organizational code under which the work was created.

The Creator.contract element contains a value that identifies a contract under which the work was created.

The Creator.project element contains a value that identifies a project under which the work was created.

The Creator.organization element contains a value that identifies an organization under whose auspices the resources was created.

The Creator.instrument element contains a value that identifies an instrument that created the resource.

The Contributor element contains the name of an entity that contributed to the present state of the resource.

The Contributor.employee element contains the name of an employee who contributed to the present state of the resource.

The Contributor.code element contains a Goddard organizational code under which contributions were made to the present state of the resource.

The Contributor.contract element contains a value that identifies a contract under which contributions were made to the present state of the resource.

The Contributor.project element contains a value that identifies a project under which contributions were made to the present state of the resourse.

The Contributor.organization element contains a value that identifies the organization under the auspices of which contributions were made to the present state of the resource.

The Contributor.instrument element contains a value that identifies a piece of equipment that contributed to the present state of the resource.

The Subject element contains a designation of what the resource is about.

The Subject.employee element contains the name of an employee whom the resource is about.

The Subject.organization element contains the name of an organization that the resource is about.

The Subject.missionsProjects element contains the name of a project that the resource is about.

The Subject.disciplines element contains the name of a discipline that the content of the expression is about.

The Subject.instrument element contains the name of an instrument that the content of the expression is about.

The Subject.functions element contains the name of a business function that the content of the expression is about.

The Subject.industries element contains the name of an industry that the content of the expression is about.

The Subject.uncontrolled element contains a characterization of the subject matter of the expression.

The Description element contains information useful in evaluating the relevance of the expression to the user's need. This information may include but is not limited to “abstracts, table of contents, reference to a graphical representation of content or a free-text account of the content”.

The Date.created element contains the date on which the resource was created.

The Date.available element contains the date on which the resource became available.

The Publisher.organization element contains the name of an organization responsible for producing and/or distributing the resource.

The Type.information element contains an indication of the intellectual genre of the resource.

The Type.contentInvariance element is imported from the National Library of Medicine’s permanence ratings and is defined as “the extent to which the content of a given resource and the links it contains will remain unchanged”.

The Format element gives information about the structure of the resource.

The Identifier.persistent element contains a means of uniquely identifying the resource in a

persistent identification system.

The Identifier.url element contains a current url for the resource.

The Source element contains the title of a broader resource within which the resource is found.

The Language element contains the name of the language used in the resource.

Each Relation.hasVersion element contains a reference to other versions of the resource

The Coverage.temporal element specifies a project phase to which the content of the object is relevant.

The Coverage.chronology element specifies the period in which the expression was generated.

The Coverage.spatial element specifies an area covered the resource

The Rights element contains a formal statement of copyright and access controls that apply to the resource.

The Audience element contains a designator of a group by whom it is expected that the resource to be used.

II. Administrative Elements

date.recordCreated

creator.recordCreator

contributor.rno

contributor.contentowner

contributor.webmaster

The date.recordCreated element contains the date that this metadata record was created.

The creator.recordCreator element contains an indicator of an entity that created this record.

The Contributor.rno – this tag is intended for use with web pages, and reflects the rno tag required by Goddard web policy as of May 2003. It contains the name of the NASA official who is responsible for the content of the object.

The Contributor.contentOwner – this tag is intended for use with web pages, and reflects the content-owner tag required by Goddard web policy as of May 2003. It contains the name of the owner of the content that is pointed to by record.

The Contributor.webmaster - this tag is intended for use with web pages, and reflects the webmaster tag required by Goddard web policy as of May 2003.