John-
Thanks for the followup. That the development of Dublin Core has been
tasked to Working Groups, each focused on one element has the obvious
*plus* of fast tracking the process overall.
Until a given set of recommendations is synthesized from the Working
Groups and adopted as a standard practice, no matter how fast track the
development, those of us in the field, the DC Implementors, if you will,
do realize we are working with an elastic product and that our
implementation serves as something of a voluntary testing ground in
practical application by those who have a high interest level but who
are not necessarily involved in the development process itself.
Joyce
John A. Kunze wrote:
>
> > Date: Tue, 30 Mar 1999 16:30:13 -0800
> > From: [log in to unmask] (Joyce Mcmullin)
> >
> > On the whole, I found John Kunze's "Encoding Dublin Core Metadata in
> > HTML" easy to follow and even easier to implement and I am in the
> > process of completing implementation on a number of my library's web
> > pages using this document as a guide. Thank you.
>
> Joyce,
>
> I'm glad you found it helpful, but please bear in mind that this is a
> draft document that is not yet reviewed to the point where it may be
> considered standard practice.
>
> > There are two points which stand out.
> >
> > 1) Use of the ADMIN prefix.
> >
> > Examples elsewhere (*not* in "Encoding Dublin Core...") of Dublin Core
> > suggest the following as the first line implementing Dublin Core in
> > <HEAD>:
> >
> > <META NAME="package" CONTENT="(TYPE=begin)Dublin Core">
> >
> > with a similar line as the last line of the code sequence. Does this
>
> The practice you describe is no longer recommended. I don't recall
> where it appeared, but it has been replaced by the LINK tag mechanism
> described in the "DC in HTML" draft.
>
> > not present an anomaly for the use of the ADMIN core prefix within a
> > package which is described as Dublin Core? The example provided in
>
> There is no longer any anomaly because the LINK tag mechanism simply
> identifies each element set that has a prefix appearing in the resource
> description.
>
> > ... could the matter, in this
> > example, be handled by way of extension: <META NAME="DC.Creator.Email"
> > CONTENT="..."> and so on, to include any number of points of contact
> > such as: MailingAddress; TelephoneNumber, etc?
>
> No. That style of extension was considered (at length) and dropped.
>
> >
> > 2) DC.Type CONTENT
> >
> > What struck me as being less a controlled vocabulary than I had
> > anticipated were the CONTENT examples which were provided for DC.Type.
> > This led me to describe some of our digital resources as: "index,"
> > "directory," "finding aid," "photographic exhibition," and
> > "exhibition."
>
> Work on extending Type vocabularies is ongoing. The DCT1 Type list
> at http://www.loc.gov/marc/typelist.html will be updated to reflect
> the DC Type working group's progress. You may contact them if you
> wish to get involved.
>
> Thanks for the comments,
>
> -John
--
Joyce A. McMullin, Branch Manager
Alexandria Library, Lloyd House
220 N. Washington St.
Alexandria, VA 22314 USA
Phone: 703.838.4577
FAX: 703.706.3912
http://www.alexandria.lib.va.us/exhibit.htm
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
|