Dear ERC/Kernel Metadata Working Group,
You've all waited patiently for this group to begin its work, and I hope
you'll find your patience rewarded. Some time ago I asked you all for
prioritized issues lists. I merged those lists, acted on some items,
and now return with a proposed work plan and call for volunteers.
(To unsubscribe, visit http://www.jiscmail.ac.uk/lists/dc-kernel.html .)
** Draft Work Plan **
1. To do: formally document kernel metadata, including the
who | what | when | where elements, qualifiers, different values
of "missing", and clarification of value syntax rules.
* So far: draft is now available at  for expansion and review.
This is a key piece. Please let me know if you're interested in
joining a small subgroup to help with editorial responsibility.
( I've also attached this draft in case there's a procedural
holdup in getting them onto the DCMI web site. )
2. To do: define and implement a process for anyone to publish new
vocabulary terms. New terms will be marked as 'draft'.
* So far: initial process is to create an email message following
the format described in  and submit via email; policy is that any
conforming submission that passes the laugh test will be published.
3. To do: define and maintain an ERC-equivalent external format
based on XML and perhaps HTML/XHTML for the purpose of easy
record exchange with other systems.
* So far: not started -- volunteers welcome.
4. To do: add a "how" element, equivalent to DC Description.
* So far: done -- see .
5. To do: create open-source software for manipulating kernel metadata.
* So far: sample Perl module at  available, but just the display
and formatting stuff for now with some date normalization thrown in.
As with any format, it's easier to dish it out than to interpret,
so interpretation code is pending. On the plus side, you can see
this module in a production system by visiting any of the URLs:
Prototype ERC mappings are also viewable for biomedical literature
using PubMed identifiers (use "pm" plus id) as follows:
Remove the question mark to access a described object, and double
it to see a larger record. Any such identifiers should return
eye- and machine-readable ERC/Kernel metadata.
* Wanted: disciplined hackers to create growing test suites.
6. To do: create best-practices for applying who | what | when | where
to different object types, e.g.,
erc/book: author | title | pub. year | ISBN or URL
erc/photo: photographer | caption | date taken | URL
erc/map: cartographer | region | mod. date | URL
erc/article: author | title | pub. date | article URL
( + in: journal name | volume / issue | journal URL )
erc/painting: artist | identifier | date created | URL
erc/artifact: discoverer | identifier | date found | URL
erc/specimen: discoverer | identifier | date found | URL
erc/code: programmer | title | mod. date | URL
* Wanted: subject and application area specialists to think through
and debug foundation mappings of kernel elements in their areas.
I invite responses, additions, and changes to the proposed action plan.
The original ERC/Kernel paper is still found at .
( The first 3 references may not be available at first, depending
on how quickly the staging DC server is copied into production.
I'll email them out if they don't appear within a day or two. )
 Draft Kernel Metadata Specification (August 2004)
 Draft Vocabulary Proposal Form (July 2004)
 ERC.pm Demonstration Perl Module (May 2004)
 A Metadata Kernel for Electronic Permanence
John A. Kunze +1 510-987-9231 California Digital Library
415 20th St, 4th Floor [log in to unmask] University of California
Oakland, CA 94612-3550 Fax: 510-893-5212 Office of the President
If you wish to unsubscribe from this email list, please visit