________________
Docent Sigfrid Lundberg, Fil. Dr. [log in to unmask]
Lunds Universitets Bibliotek http://www.ub.lu.se/~siglun/
Netlab, Box 3, 221 00 Lund 046-222 36 83
On Mon, 23 Mar 1998, Roland Schwaenzl wrote:
>
> Dear Sigfrid, dear Meta2's
>
> isn't it, that
>
> the RFC3 draft [http://www.roads.lut.ac.uk/lists/meta2/1998/02/0002.html] implies
> in a clean way the encoding in HTML,
>
> whereas the subelement draft is vague about it?
>
> isn't it, that
>
> <META NAME="DC.Relation.IsBasedOn" CONTENT="http://www.foo.bar/">
>
> is the intented encoding?....Exactly as was decided already at Canberra.
>
That is the way other things than Relation things should be encoded in
HTML should be encoded. The current proposal states that Relation has two
and only two subelements: Type and Identifier.
That means that Relation necessarily has to be expressed in the extended form
Relation:
Type: IsBasedOn
Identifier: http://www.foo.bar/
Various Types are proposed to be taken from an enumerated list, of which
IsBasedOn is one member. Please inspect
http://purl.oclc.org/metadata/dublin_core/wrelationdraft.html
> Again according to Canberra a harvester treating this information as equivalent with
>
> <META NAME="DC.Relation" CONTENT="http://www.foo.bar/">
>
> is ``unqualified'' DublinCore compliant.
>
> OR??
>
>
> Best
> Roland
Cheers
Sigfrid
|