--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)
; Thu, 23 Oct 97 08:54:53 -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 JAA33854; Thu, 23 Oct 1997 09:36:11 -0400
Received: from RS8.LOC.GOV by RS8.LOC.GOV (LISTSERV-TCP/IP release 1.8b) with
spool id 219651 for [log in to unmask]; Thu, 23 Oct 1997 09:36:10 -0400
Received: from sos.state.il.us (ftp.sos.state.il.us [199.15.1.2]) by
rs8.loc.gov (8.8.4/8.8.4) with SMTP id JAA39226 for <[log in to unmask]>;
Thu, 23 Oct 1997 09:26:08 -0400
Received: from library.sos.state.il.us (ccgate.sos.state.il.us [199.15.1.5]) by
sos.state.il.us (8.6.12/8.6.12) with SMTP id JAA17167 for
<[log in to unmask]>; Thu, 23 Oct 1997 09:43:04 -0500
Received: from ccMail by library.sos.state.il.us (ccMail Link to SMTP R8.00.01)
id AA877613677; Thu, 23 Oct 97 08:34:39 -0600
X-Mailer: ccMail Link to SMTP R8.00.01
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="simple boundary"
Message-ID: <[log in to unmask]>
Date: Thu, 23 Oct 1997 08:34:37 -0600
Reply-To: Encoded Archival Description List <[log in to unmask]>
Sender: Encoded Archival Description List <[log in to unmask]>
From: [log in to unmask]
Subject: cc:Mail Link to SMTP Undeliverable Message
Comments: To: [log in to unmask]
To: Multiple recipients of list EAD <[log in to unmask]>
--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 19:22:32 -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 UAA37978; Wed, 22 Oct 1997 20:04:36 -0400
Received: from RS8.LOC.GOV by RS8.LOC.GOV (LISTSERV-TCP/IP release 1.8b) with
spool id 219321 for [log in to unmask]; Wed, 22 Oct 1997 20:04:33 -0400
Received: from index.umdl.umich.edu ([log in to unmask] [141.212.2.201])
by rs8.loc.gov (8.8.4/8.8.4) with ESMTP id TAA77730 for
<[log in to unmask]>; Wed, 22 Oct 1997 19:54:32 -0400
Received: from localhost (blandis@localhost [127.0.0.1]) by
index.umdl.umich.edu (8.8.7/8.8.3) with SMTP id TAA12970 for
<[log in to unmask]>; Wed, 22 Oct 1997 19:54:30 -0400 (EDT)
X-Sender: [log in to unmask]
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Message-ID: <[log in to unmask]>
Date: Wed, 22 Oct 1997 19:54:28 -0400
Reply-To: Encoded Archival Description List <[log in to unmask]>
Sender: Encoded Archival Description List <[log in to unmask]>
From: Bill Landis <[log in to unmask]>
Subject: Re: (last minute) DTD feedback
Comments: To: Encoded Archival Description List <[log in to unmask]>
To: Multiple recipients of list EAD <[log in to unmask]>
In-Reply-To: <v02130507b073a98d5c52@[128.32.252.42]>
On Wed, 22 Oct 1997, Richard Rinehart wrote:
>
> 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.
Just wanted to clarify, since I haven't worked with the <physfacet>
element at all.
First, in looking at the tag library, it appears that the "source"
attribute can be supplied on both the <physdesc> and <physfacet> elements
and that the range of values is the same for both usages.
Second, I wonder if by the nature of its hierarchical containment, the
attribute information on the <physdesc> tag isn't automatically inherited
by any <physfacet> elements contained within it? So that
<physdesc source="aat">
<physfacet>facet1</physfacet>
<physfacet>facet2</physfacet>
</physdesc>
necessarily implies that the source for both facet1 and facet2 is "aat".
The only reason one would need a source attribute on a <physfacet> in the
above scenario would be to note exceptions to the source declared on the
<physdesc> element, as in
<physdesc source="aat">
<physfacet>facet1</physfacet>
<physfacet>facet2</physfacet>
<physfacet source="lctgm">facet3</physfacet>
</physdesc>
Does this address part of Richard Rinehart's question?
As for the label attribute, which is currently only available on
<physdesc> and not on <physfacet>...perhaps Richard could give us an
example? I'm not sure I really understand how this attribute would be
used by someone describing a museum item (or any other item for that
matter!) I guess, based on the above examples, that currently if one puts
a label attribute onto the <physdesc> tag then all <physfacet>s contained
within that <physdesc> would inherit that label information. Are there
examples of cases in which one or more of the <physfacet>s would need an
exception noted to that label?
Thanks for the clarification!
________ [Bill Landis] ___________________________ [[log in to unmask]]
Graduate School of Education & Information Studies
University of California, Los Angeles
--simple boundary--
--simple boundary--
