The type attribute value "single" was valid in EAD Version 1.0, but was deprecated in Version 2002 (I don't recall why at this point), so is no longer a valid value for <unitdate type="">. Kris Kris Kiesling Elmer L. Andersen Director of Archives and Special Collections and Assistant University Librarian for Special Collections Advancement 305 Andersen Library 222 21st Ave. S. University of Minnesota Minneapolis, MN 55455 voice: 612-626-5776 fax: 612-625-5525 -----Original Message----- From: Encoded Archival Description List [mailto:[log in to unmask]] On Behalf Of Michele R Combs Sent: Wednesday, July 28, 2010 10:49 AM To: [log in to unmask] Subject: Question about unitdate type attribute For unitdate, the RLG best practices document mentions three kinds: bulk, inclusive, and single. (See page 14 here http://www.oclc.org/research/activities/past/rlg/ead/bpg.pdf ). However, the EAD Tag Library only mentions bulk and inclusive (see http://www.loc.gov/ead/tglib/elements/unitdate.html ). Is 'single' in fact a legitimate option for the 'type' attribute? Since the RLG BP also says the type attribute is mandatory, we've just been using type=inclusive for all dates regardless, but now that I've noticed this in the RLG doc, it's made me wonder. Michele (be green - don't print this email!) ~~~~~~~~~~~~~~~~~~ Michele Combs Manuscripts Librarian Special Collections Research Center Syracuse University Libraries 222 Waverly Ave. Syracuse, NY� 13244 315-443-2081 [log in to unmask] ~~~~~~~~~~~~~~~~~~