[Eac-l] Re: EAC DTD error

[AJDGOMEZ at telefonica.net]

Barbara, Daniel,
I think I understand both arguments, and, in my opinion, some day EAC 
will have to face this refinement (names/entities). However, from my 
point of view, at the moment the DTD is ok, as a beta version, and 
further refinements before testing it would generate confusion.
Regards
Alejandro Delgado-Gómez
City Council of Cartagena
3000 Informatics

----- Mensaje Original -----
De: Daniel Pitti <dpitti at virginia.edu>
Fecha: Viernes, Octubre 29, 2004 5:24 pm
Asunto: [Eac-l] Re: EAC DTD error

> Barbara,
> 
> I am just about to rush off to a meeting which will occupy me for 
> most of 
> the afternoon. The distinction you make about names vs entity 
> brings back 
> my library authority work. This well may be a point of divergence 
> between 
> library authority control and archival authority control, that is, 
> whether 
> it is about the name or the entity (or perhaps entities) bearing 
> the name 
> (or same names). I'll wait to hear more from the archivists before 
> venturing much further out on the limb.
> 
> Daniel
> 
> At 11:02 AM 10/29/2004, you wrote:
> >I cannot quite follow what the issue is here as my version of the DTD
> >and Tag Library information both show "corpname", etc.   Can you 
> tell me
> >where in the DTD and the Tag Library you are trying to make this
> >correction?  I can't find it.
> >
> >I'm also not clear about what you are asking.  As you know, in
> >authority records or packages of authoritative information about an
> >identity (EAC recognizes identities) the focus is on the names to be
> >used to represent that entity (the identity) - and those in turn 
> can be
> >associated with one or more actual persons (or corporate bodies, or
> >families).  An entity of "person", "corporate body", or "family" can
> >certainly exist, but in the EAC context, the EAC instance is not
> >actually the person, but rather the name(s) associated with that 
> person>within a particular identity - possibly linked to the name 
> of a real
> >individual which could be seen as the surrogate for the "person," 
> but it
> >is not actually the person (and sometimes not even a real person -
> as for
> >fictitious characters, etc.).   So if you are giving names to the
> >entities - won't you need both the persname, corpname, famname as 
> well>as person, corporate body, family?
> >
> >I feel I'm not following the goal of the argument...can you help
> >explain what's issue here?  (I wish we could talk and not email...are
> >you by a phone today?) - bt
> >
> >Dr. Barbara B. Tillett, Ph.D.
> >Chief, Cataloging Policy and Support Office
> >Library of Congress
> >101 Independence Ave., S.E.
> >Washington, D.C. 20540-4134
> >U.S.A.
> >
> >tel.: +1 (202) 707-4714
> >fax: +1 (202) 707-6629
> >email: btil at loc.gov
> >
> > >>> Daniel Pitti <dpitti at virginia.edu> 10/29/2004 10:09:41 AM >>>
> >
> > >Per-Gunnar Ottosson has pointed out to me that the @type values on
> ><eac>
> > >in the beta dtd are different from the values listed in the Tag
> >Library.
> > >After a bit of discussion, we concluded that the Tag Library is
> >correct
> > >and the DTD (and thus the two schemas) are in error.
> > >
> > >We would like to change the values in the DTD from:
> > >
> > >corpname | persname | famname
> > >
> > >to
> > >
> > >corporatebody | person | family
> > >
> > >The logic: an EAC instance describes the corporate body, 
> person, or
> > >family, and not the name, as such.
> > >
> > >Does anyone have any counter arguments to this correction?
> > >
> > >Daniel
> 
> _______________________________________________
> Eac-l mailing list
> Eac-l at mailman.yale.edu
> http://mailman.yale.edu/mailman/listinfo/eac-l
>