> Karen Coyle wrote:
> > This doesn't mean that we can't do:
> > Creator.Author=Shakespeare, William, 1564-1616
> > But we can't break out the date into a different Creator field.
>
> James Weinheimer wrote:
> I hope you're right. But if "date range" has been specifically ruled out,
can
> we put the "DC." at the beginning of: Creator.Author=Shakespeare, William,
> 1564-1616? In other words, would it be valid DC if we add the date?
> I would think so, but if it "breaks the datamodel," (using a date range in
a
> highly unorthodox way) would the Shakespeare heading be invalid DC?
Within the limitations of HTML, I think we can include whatever we want in
CONTENTS=" ". Structured data values haver always been accepted in DC (ISO
date, vCard, etc.) since the SCHEME notation of HTML4 became available. Why
not (qualified or unqualifed):
<META NAME="DC.Creator" SCHEME="AACR2" CONTENT="Felix V, Antipope,
1383-1451">
or
<META NAME="DC.Creator" SCHEME="AACR2" CONTENT="Tolkien, J. R. R. (John
Ronald Reuel), 1892-1973">
or
<META NAME="DC.Creator.Illustrator" SCHEME="AACR2" CONTENT="Kent, Rockwell,
1882-1971">
or (I suppose)
<META NAME="DC.Creator" SCHEME="AACR2" CONTENT="Kent, Rockwell, 1882-1971,
ill.">
In any case, we cannot really deal with subfield relationships in a
hierarchical way without XML/RDF (?).
David K. Titus, Librarian
Bryant & Stratton - Albany Campus
1259 Central Avenue
Albany, New York 12205-5230
Voice: 518.437.1802 Fax: 518.437.1048
e-mail: [log in to unmask]
Visit The New York Library Association: www.nyla.org
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
|