Michelle -- We're using an identifier with attribute value being the name of the xml file for the ead finding aid:
<eadid countrycode="us" mainagencycode="rpb" identifier="ms77.10.xml">ms77.10</eadid>
 
Pro is that this is a stable file name.  For our purposes, it's redundant to the eadid text, but we only need to key it in once and our clip library in NoteTab Pro generates the identifier with .xml extension.  
 
Con to using a URL:  if you migrate your finding aid site to another address (another server, for instance), I believe you'd need to update the url in each ead file.
 
-- Sarah Shaw
Digital Initiatives Librarian / Brown University / Providence, Rhode Island

________________________________

From: Encoded Archival Description List on behalf of Michele Rothenberger
Sent: Wed 9/14/2005 12:19 PM
To: [log in to unmask]
Subject: Question about eadid



Hello Collective Wisdom --

The EAD Report Card has the following to say about the EADID element:

"The content of this element, together with its attributes, must
uniquely identify the EAD instance. The <eadid> should include at least
one of the following attributes: publicid, identifier, url. See BPG for
additional guidance. If using publicid, content is defined in ISO/IEC
9070:1991, intended to be universally unique. If using identifier,
content is a machine-readable unique identifier. If using url, content
should be expressed in absolute terms (e.g.,
http://www.loc.gov/ead/ms99999.xml)."

Just wondering what most people are using - publicid, identifier or URL
-- and pros/cons of the three options.

Thanks

Michele

-=--=--=--=--=--=--=--=--=--=--=--=--=--=-
Michele Rothenberger
Syracuse University
Special Collections Research Center
Syracuse, NY
-=--=--=--=--=--=--=--=--=--=--=--=--=--=-