Leif:
We have encountered similar difficulties: How to encode what is
essentially additional title information.?
In library cataloging, volume and number information are treated as part
of the title.
If we adopt this basic premise, then an unqualified dc.title for a
particular serial issue might look like this:
<dc.title>D-Lib Magazine: The magazine of digital library research
July/August 1998</>
Alternatively, it seems reasonable to desire more structure in the title
element such as might be achieved through additional elements:
<title>The title
<vol>1</vol>
<no>2</no>
</title>
"Vol" and "no" would have to be defined in an XML namespace.
I would encourage you to think along these lines rather than using the
Relation element.
--Erik
Erik Jul
[log in to unmask]
> -----Original Message-----
> From: Leif Andresen [SMTP:[log in to unmask]]
> Sent: Monday, August 03, 1998 12:04 PM
> To: [log in to unmask]
> Subject: Version of actual doc. - Title or relation?
>
> To the meta2-list
>
> Belongs version of actual document DC.Title or DC.Relation?
>
> In Denmark we are working with a "Recommended use af Dublin Core" as a
> national sollution of metadata. The project is part of implementation
> of legal deposit of electronic static publications. The project
> include publication of a specification of editors for making
> html-documents. We will use the specification in this a campaign with
> publishers and web-designers as target group.
>
> We only use subelements in DC.Relation (until now):
>
> IsVersionOf Parallel printed edition
> HasPart File-list
> Requires Needed software for using this document
>
> We have a problem. We need some space in the format for
> Version/Release of a publication. First we don*t like to use
> DC.Relation because it is for relation to others documents. As we see
> it, it could be a part of the title. Our idea was a subelement in
> DC.Title:
> DC.Title.Version or DC.Title.Release. E.g.:
> META NAME="DC.Title" CONTENT="Textbook of metadata*
> META NAME="DC.Title.Release" CONTENT="Version 2.3"
>
> But may be DC.Relation is the right place. A proposal:
>
> In the report of Relations Working Group you have six pairs of
> relations. IsPartOf make a pointer UP from a part of a document to the
> whole document and HasPart make a pointer DOWN to the parts.
> IsFormatOf/HasFormat, References/IsReferenvedBy, IsBasedOn/IsBasisFor
> and Requires/IsRequiredBy works in the same way. IsVersionOf is a
> pointer to an earlier version. But is HasVersion a pointer to a
> following version - or a number for the version of the actual
> document? Most logic is a pointer to another document.
>
> So: I think that my proposel may be IsVersion for relation to the
> document itselfs, e.g.:
> META NAME="DC.Relation.IsVersion" CONTENT="2.3"
> and e.g.:
> META NAME="DC.Relation.IsVersion" CONTENT="Second Edition"
>
> I have exchanges emails about this question with some different people
> - with different views.
>
> We have to decide in a few weeks - so comments on the list are very
> welcome.
>
>
> 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
> ********************************************************
>
>
>
>
>
>
>
|