As a point of clarification:
> Making <odd>
> available directly within <c>s (rather than following the <did>, as
> MacKenzie illustrates in her example) would violate the hierarchical
> structure of EAD, and, as I understand it, would have the effect of making
> it a "floating" element.
This is not true. The <odd> is _already_ defined as a valid element in the
<c>, as is plain from the content model of the <c>, and from the tag
library that was published for version 1. As I said, the <odd> was
defined to be valid in the <c>, but only _before_ any nested <c> elements.
We simply need it to be valid before or _after_ nested <c> elements, and
that doesn't make it a "floating" element or in any way violate the structural
or hierarchical integrity of the DTD. I wouldn't suggest this change if it
did... it's just an issue of subelement ordering.
The change we're asking for is really not a big deal. And yes of course,
we'll come up with a good example of the problem.
_____________________________________________________________________________
MacKenzie Smith [log in to unmask]
Digital Library Projects Manager phone: (617)495-3724
Office for Information Systems fax: (617)495-0491
Harvard University Library %\%\%\%\%\%\%\%\%\%\%\%\%\%
-----------------------------------------------------------------------------
|