As chair of the relations working group I would note that I believe our
original intention, although it is fine to revise it, was:
if the item being described is the 13th edition, this is part of its title,
if it points to another item of which is is a version (such as the 12th
edition), that would be in relation.
>Gotcha. That all makes sense, so am I right in thinking that in DC Simple,
the current edition information all goes into Title, as <META
NAME="DC.Title" CONTENT="Dorland's Illustrated Medical Dictionary, 25th
edition"> (or Twenty-fifth Edition, which is actually how it's described on
the title page). Lief Anderson has suggested a "Release" subelement for the
purposes of identifying the edition separately, presumably within DC
Qualified, and I guess this should be discussed in the DC-6 break-out
session on Title, Subject and Description.
Cliff
At 04:52 PM 10/29/98 +0100, Leif Andresen wrote:
>To meta2 list
>
>Citiation from User Guide:
>* Title="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]
>
>In this exampel the present resource is NOT 13th Edition. That is a
pointer >to another version of same author.
>
>There is six pairs of relations - all are pointers "up" or "down" - e.g.
>IsBasedOn and IsBasisFor.
>
>What we need is Release/Version/Release of actual/present document.
>
>regards
>Leif
>
>
>>>> <[log in to unmask]> 29-10-98 11.23 >>>
>
>IsVersionOf doesn't let us specify a version, does it?
>Misha
>
>>You're quite right. I should have said HasVersion (as in the User Guide's
>example Relation="HasVersion 13th Edition, 1972"). Sorry about confusing
>these two relationship types. However, my point that this information
>belongs in Relation rather than Title still stands.
>
>>Cliff
>
>
>> Two immediate points spring to mind:
>>
>> 1) This information properly belongs in DC.Relation ("IsVersionOf").
>>
>> 2) It is inappropriate to invent unapproved DC tags, whether at the
>element > or subelement level. That is, "DC.Title.Release" has no
authority >as a DC > tag. If you want to invent tags, you must treat them
as *local* >extensions > and not bless them with the DC prefix.
>>
>> Cliff Morgan
>>
>> Publishing Technologies Director
>>
>> John Wiley & Sons Ltd
>>
>> Chichester, UK
>>
>
>> [log in to unmask] on 23/10/98 16:30:02
>>
>> Subject: Release/Version/Release of a document
>>
>> To the meta2-list
>>
>> In August this year we send a mail to the meta2-liste with the question:
>>
>> Belongs version of actual document DC.Title or DC.Relation?
>>
>> Our conclusion was to implement a subelement to Title:
>>
>> DC.Title.Release
>>
>> E.g.:
>> META NAME="DC.Title" CONTENT="Textbook of metadata"
>> META NAME="DC.Title.Release" CONTENT="Version 2.3"
>> and
>> META NAME="DC.Title" CONTENT="Another Textbook of something"
>> META NAME="DC.Title.Release" CONTENT="Second Edition"
>> and
>> META NAME="DC.Title" CONTENT="Manual for programme ZZ"
>> META NAME="DC.Title.Release" CONTENT="Release 2.3.56"
>>
>> We think it is a general problem and not a national danish problem.
>>
>> So: if somebody have a better solution, we would like to hear about it.
>>
>> And hopefully: can we find a common solution on DC-6?
>>
>>
>> regards
>> Leif
>>
>>
>> ********************************************************
>> Leif Andresen * Email: [log in to unmask]
>> Library Advisory Officer
>> Danish National Library Authority
>> Nyhavn 31 E, DK-1051 Copenhagen K
>> Phone direct: +45 3373 3354
>> Phone: +45 3373 3373 * Telefax: +45 3373 3372
>> ********************************************************
>
>
>
>
>
David Bearman
President
Archives & Museum Informatics
2008 Murray Ave, Suite D
Pittsburgh, PA 15217 USA
Phone: +1 412 422 8530
Fax: +1 412 422 8594
[log in to unmask]
http://www.archimuse.com
|