Print

Print


--simple boundary
Content-Type: text/plain; charset=US-ACSII
Content-Transfer-Encoding: 7bit

Message is undeliverable.
Reason: User "[log in to unmask]" is not found in the cc:Mail Directory.
Original text follows:
---------------------


--simple boundary
Content-Type: text/plain; charset=US-ACSII
Content-Transfer-Encoding: 7bit

Received: from rs8.loc.gov by library.sos.state.il.us (ccMail Link to SMTP R8.00.01)
        ; Wed, 22 Oct 97 15:37:37 -0600
Return-Path: <[log in to unmask]>
Received: from rs8 (rs8.loc.gov [140.147.248.8])
          by rs8.loc.gov (8.8.4/8.8.4) with SMTP
          id QAA138582; Wed, 22 Oct 1997 16:19:15 -0400
Received: from RS8.LOC.GOV by RS8.LOC.GOV (LISTSERV-TCP/IP release 1.8b) with
          spool id 219005 for [log in to unmask]; Wed, 22 Oct 1997 16:19:13 -0400
Received: from uclink2.berkeley.edu (uclink2.Berkeley.EDU [128.32.136.72]) by
          rs8.loc.gov (8.8.4/8.8.4) with ESMTP id QAA107570 for <[log in to unmask]>;
          Wed, 22 Oct 1997 16:19:11 -0400
Received: from [128.32.252.42] (manray.BAMPFA.Berkeley.EDU [128.32.252.42]) by
          uclink2.berkeley.edu (8.8.4/8.6.12) with SMTP id NAA27421 for
          <[log in to unmask]>; Wed, 22 Oct 1997 13:12:22 -0700
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Message-ID:  <v02130507b073a98d5c52@[128.32.252.42]>
Date:         Wed, 22 Oct 1997 13:12:22 -0700
Reply-To: Encoded Archival Description List <[log in to unmask]>
Sender: Encoded Archival Description List <[log in to unmask]>
From: Richard Rinehart <[log in to unmask]>
Subject:      (last minute) DTD feedback
Comments: To: Encoded Archival Description List <[log in to unmask]>
To: Multiple recipients of list EAD <[log in to unmask]>

Hi all,

I recently taught a workshop at the conference of the Museum Computer
Network on how to implement the EAD in museums. I'm happy to say that the
class was full and enthusiasm continues to grow in the museum community
about potential use of the EAD.

In using the EAD in our museum we have come upon one suggestion for the
next version of the DTD: to add "label" and "source" attributes to the
PHYSFACET element. I've emailed about this before, but wanted to simplify
the thought to just one clear suggestion.

These attributes are already available in the PHYSDESC element, but could
be just as useful in the more granular PHYSFACET element for describing
collections with detailed physical descriptions like those in museums (and
it sounds like many archives). If for some reason, adding a "source"
attribute to PHYSFACET is not a good strategy, perhaps allowing one to use
the "source" attribute of the PHYSDESC element to inherit downward to apply
to all the "label" attributes in the contained PHYSFACETs would work, but
the former model seemed to be more straightforward.

Thanks for this opportunity to contribute something back toward a tool
we've found very useful.



Richard Rinehart              | Berkeley Art Museum/Pacific Film Archive
Systems Manager & Education   | University of California
Technology Specialist         | 2625 Durant, Berkeley, CA 94720-2250
[log in to unmask] | http://www.bampfa.berkeley.edu/
& President-Elect, Museum Computer Network, http://www.mcn.edu/


--simple boundary--