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 matter.
There are other options.
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> and
<odd>, but there are no attributes within <dao> (other than "altrender")
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 instance,
within a <p> element) or for the ability to control the display more
precisely, the logical solution seems to be to put it within a <table>
element. In this scenario you could control width, alignment and other
display features via a combination of specific attributes available in
<table> and its child elements. However, <dao> is not a valid element
within <table>...<entry>. This seems inconsistent, since a similar
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 that
<dao> should be valid within a <table>...<entry> element just as <extptr>
Computer Support Analyst I
Special Collections Division
University of Washington Libraries
Seattle, WA, USA