DAO is not allowed in a mixed content element.
So the short answer is no. No you will not be able to code DAO
directly into a text element in your EAD document.
But dao is allowed as a child of all the main elements. Given this
requirement, you can search for the dao using an @id. Validation
demands that all @id's be unique. Thus you can really have some fun
and not worry too much about reproducing the same image every time.
Transforming your EAD into HTML means that your stylesheet can pluck
the DAO and put it in the text at some point and wrap it in a table.
It is possible to do this with and empty abbr element in your p.
Something like this. (below)
Library of Congress
<p>This collecter was so incredible. He was so awesome. <abbr
Hangsworthington, was an avid collector of "stuff".</p>
<xsl:apply-templates select="@* | * | text()"/>
<xsl:template match="expan" mode="special_expan">
--- Mark Carlson <[log in to unmask]> wrote:
> But this doesn't really address the issue of positioning a DAO at a
> particular point within the text of a <p> element. For instance,
> in your
> <bioghist><p> element, you may want to embed an image within the
> flow of
> <p>John Smith was born on Feb. 14, 1898 in Dallas, Texas... [embed
> <table> seems the logical way to accomplish this and is available
> <p>. It also seems the most standardized way (i.e. a way that most
> sheets would be able to render it correctly) rather than making a
> style sheet change based on local practice. I guess my question
> is, why
> isn't <dao> available within a <table>...<entry> while <extptr> is?
> was the reasoning behind this decision?
> On Thu, 17 Jun 2004, Fox, Michael wrote:
> > You can always open a <daodesc> within <dao> and it has <table>
> and <p>
> > available within it. So the horse comes after the cart and not
> before it in
> > this case. Otherwise, if you have a standard pattern for the
> display of
> > such images, that could be built into a stylesheet. Whether one
> uses a
> > table in the HTML output to position text and image is another
> > There are other options.
> > Michael Fox
> > -----Original Message-----
> > From: Mark Carlson [mailto:[log in to unmask]]
> > Sent: Thursday, June 17, 2004 3:38 PM
> > To: [log in to unmask]
> > Subject: <dao> and embedded images
> > I would like to get some input about embedding images within the
> body of a
> > finding aid. These would be images from the collection of
> materials being
> > described, so <dao> (or <daogrp>) seems to be the appropriate
> element to
> > use. In this situation, it looks like the only place that <dao>
> can be
> > used as a standalone element is within <scopecontent>, <bioghist>
> > <odd>, but there are no attributes within <dao> (other than
> > that control *how* the image displays, such as alignment and
> whether it
> > should flow with the text or be displayed separately from it.
> > For an image that should display within the flow of text (for
> > within a <p> element) or for the ability to control the display
> > precisely, the logical solution seems to be to put it within a
> > element. In this scenario you could control width, alignment and
> > display features via a combination of specific attributes
> available in
> > <table> and its child elements. However, <dao> is not a valid
> > within <table>...<entry>. This seems inconsistent, since a
> > linking element <extptr> is valid within <table>...< entry>.
> > What would the recommendation be considering the current
> limitations about
> > where <dao> (daogrp) can be used? It seems that for consistency
> > <dao> should be valid within a <table>...<entry> element just as
> > is.
> > Thanks.
> > Mark Carlson
> > Computer Support Analyst I
> > Special Collections Division
> > University of Washington Libraries
> > Seattle, WA, USA
> > http://www.lib.washington.edu/specialcoll/findaids/
Do you Yahoo!?
New and Improved Yahoo! Mail - 100MB free storage!