The DC User Guide Working Group has reached the
point where it needs other working groups to
review relevant portions of the draft User
Guide, which is at:
http://128.253.70.110/DC5/UserGuide3.html
This email is a request for review of the
Relation section. A copy of it is at the end
of this email, following my name.
Please send your suggestions by April 15, since
the goal date for the DC User Guide Working
Group for redrafts to go in to the reflector is
April 17).
FYI, the next deadline for the User Guide group is
April 30, by which date we intend to have redrafted
guidelines distributed for general comments on Meta2.
Thanks for your assistance.
Mary Larsgaard
-------
>
>4.13. Relation
>
>Label: RELATION
>
>Element Description: The relationship of this resource to other resources.
The
>intent of 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.
>
>Relationships between resources fall into a number of classes, such as
>parent-child, aggregations, etc. A list of types which
>accomodates most expected relationships is:
>
>
> IsPartOf
> HasPart
> IsVersionOf
> HasVersion
> IsFormatOf
> HasFormat
> References
> IsReferencedBy
> IsBasedOn
> IsBasisFor
> Requires
> IsRequiredBy
>
>Guidelines for content creation:
>
>The recommended method for expressing a relationship in unqualified DC is:
>
>IDENTIFIER = "unique identifer for the present resource"
>RELATION = "relationship-type; unique identifer for the related resource"
>
>where "relationship-type" is a token drawn from the list above.
>
>Note: In the case where the DC metadata is embedded in the present
resource, the
>value for IDENTIFIER is implied (i.e. the
>present resource). In qualified DC the two components given in RELATION here
>will be structured using sub-elements for
>easier automated processing.
>
>Examples:
>
>IDENTIFIER = "Mt. Kosciusko"
>RELATION = "IsPartOf; Snowy Mountains in Australia"
>
>[Part/Whole relations are those in which one resource is a physical or
logical
>part of another]
>
>IDENTIFIER = "Elton John's 1997 song Candle in the Wind"
>RELATION = "IsVersionOf; Elton John's 1976 song Candle in the Wind"
>
>IDENTIFIER = "Gombrich's Story of Art"
>RELATION = "HasVersion; 13th Edition, 1972"
>
>[Version relations are those in which one resource is an historical state or
>edition, of another resource by the same
>creator]
>
>IDENTIFIER = "paper.html"
>RELATION = "IsFormatOf; paper.doc"
>
>IDENTIFIER = "Landsat TM dataset of Arnhemland, NT, Australia"
>RELATION = "HasFormat; arnhem.gif"
>
>[Format transformation relations are those in which one resource has been
>derived from another by a reproduction or
>reformatting technology which is not fundamentally an interpretation but
>intended to be a representation.]
>
>IDENTIFIER = "Morgan's Ancient Society"
>RELATION = "IsReferencedBy; Engels' Origin of the Family, Private Property
and
>the State"
>
>IDENTIFIER = "Movie Review A"
>RELATION = "References; Movie G"
>
>[Reference relations are those in which the author of one resource cites,
>acknowledges, disputes or otherwise make
>claims about another resource.]
>
>IDENTIFIER = "Peter Carey's novel Oscar and Lucinda"
>RELATION = "IsBasisFor; 1998 movie Oscar and Lucinda"
>
>IDENTIFIER = "The movie My Fair Lady"
>RELATION = "IsBasedOn; Shaw's play Pygmalion"
>
>[Creative relations are those in which one resource is a performance,
>production, derivation, adaptation or
>interpretation of another resource.]
>
>IDENTIFIER = "program.c"
>RELATION = "Requires; stdio.h"
>
>IDENTIFIER = "List of Internet Media Types" RELATION = "IsRequiredBy; Dublin
>Core FORMAT element"
>
>[Dependency relations are those in which one resource requires another
resource
>for its functioning, delivery, or
>content and cannot be used without the related resource being present.]
>
>
>
>------- End of Forwarded Message
>
>
>
David Bearman
President
Archives & Museum Informatics
5501 Walnut St., Suite 203
Pittsburgh, PA 15232
tel. +1-412-683-9775; fax +1-412-683-7366
http://www.archimuse.com
------- End of Forwarded Message
|