The following changes to the EAD DTD are proposed to facilitate
using EAD as a data structure for RAD descriptions.  (For the
most part, the concerns raised also apply to ISAD(G).)  It is
likely not exhaustive, but deals with the main problems of which
I am aware.  A more detailed analysis is certainly in order, to
make EAD a useful data structure for RAD (and ISAD(G))-compliant
descriptions.


create tag <ASSOCIATEDMATERIAL>
     to occur within: <ADD>, <ASSOCIATEDMATERIAL>, and
     <RELATEDMATERIAL>
     to contain: same tags as <RELATEDMATERIAL>
     attributes: same as <RELATEDMATERIAL>

     rationale: RAD distinguishes between "related groups of
     records in different fonds" which are in the same repository
     (1.8B20), and "associated material", "records of another
     institution" (1.8B17).  See also ISAD(G) 3.4.3 and 3.4.4.

allow <RELATEDMATERIAL> to occur within
     <ASSOCIATEDMATERIAL>

     rationale: for consistency with other nesting possibilities

allow <ADD> to occur within:
     <ARCHDESC>, <C>, <C01>, <C02>, <C03>, <C04>, <C05>, <C06>,
     <C07>, <C08>, <C09>, <C10>, <C11>, <C12>

     rationale:  RAD allows "related groups of records" (1.8B20)
     to be indicated at both the fonds and series level; <ADD> (a
     wrapper for <RELATEDMATERIAL>) may currently only occur
     within <FINDAID>, i.e. at the first level of description.
     If a <FINDINGAIDS> tag is created (see below) and occurs
     within <ADD>, this nesting would also be necessary for that
     reason.

create tag <FINDINGAIDS>
     to indicate existence of finding aids (paper or electronic)
     in cases when the full finding aid is not part of the EAD
     record.

     to occur within: <ADD>, <FINDINGAIDS>
     to contain: <ARCHREF>, <PTR>, <EXTPTR>, <BIBREF>, ...

create tag <PROVENANCE>
     to contain corporate or personal name of creator of records

     same nestings and attributes as <CORPNAME>, <PERSNAME>, etc.
     optionally: allow <PROVENANCE> to contain <PERSNAME>,
          <CORPNAME>, <FAMNAME>, <NAME>**

     rationale: RAD prescribes "provenance access points", not
     requiring one to distinguish between personal and corporate
     names.

     **similarly, <SUBJECT> could contain the same elements

create tag <ACCRUALS>
     to indicate frequency of accruals, or the fact that further
          accruals are expected.
     to occur within: <ADMININFO>

     rationale: RAD and ISAD(G) distinguish between this
     information and acquisition information ("immediate source
     of acquisition")