On Wed, 27 Jan 1999, Debbie Campbell wrote:
>
> Renato and I would be very happy to receive comments on our proposal, so
> please fire away,
This is certainly the type of metadata we will need in the future when we
seek to ascertain the origin of a given resource description and
to determine whether this description can be trusted or not.
I agree with Rachel that this set should not be part of the DC set and
with your proposal to define a separate ADMIN-set.
I miss an element for copyright information in the ADMIN-set.
I have one question concerning the example given:
<? xml version="1.0" ?>
<RDF xmlns = "http://www.w3.org/TR/WD-rdf-syntax#"
xmlns:DC = "http://metadata.net/dc/#"
xmlns:ADMIN = "http://metadata.net/admin/#" >
<Description xml:lang="en"
about = "http://metadata.net/admin/elements.html">
<DC:Title> Admin Core Metadata Element Specification </DC:Title>
<DC:Creator> Crystal, Jacky </DC:Creator>
<DC:Date> 1998-01-01 </DC:Date>
<ADMIN:CreatorCorporate> Rubble Corp <ADMIN:CreatorCorporate>
<ADMIN:CreatorEmail> [log in to unmask] </ADMIN:CreatorEmail>
<ADMIN:DateCreated> 1998-01-15 </ADMIN:DateCreated>
<ADMIN:DateValidFrom> 1998-02-01 </ADMIN:DateValidFrom>
<ADMIN:DateValidTo > 1999-02-01 </ADMIN:DateValidTo>
</Description>
</RDF>
How can you be sure that the admin-set relates to the DC-set? is it enough
that both are within the same <Description> </Description> tag? Or should
the DC-set contain a Relation tag with a pointer to the ADMIN-set and vice
versa should the ADMIN-tag contain a Relation-tag pointing to the DC-set?
If the ADMIN set is separate from the DC-set you'll need a pointer anyway.
So I guess you need to add an element Relation to the ADMIN-set.
gr., Titia
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
|