OK. I said to Marsha Maguire (who started this thread) about my proposal
of using @ALTRENDER: "Of course, [this will do the job] if you feel you
have a display problem; this is a poor solution if you think of it as a
semantic matter...".

But we have to remember that ISAD(G) makes no distinction: "3.2.2
Administrative / Biographical history"

Greetings from Spain.

M. Carlson wrote:

> But since <head> elements are not *required* elements, that seems to imply
> that a style sheet should at least provide a "default" on its own without
> "assuming" anything and that "tests" should be performed on whether a
> particular combination of parent/child elements exist, not on whether a
> <head> element exists among those parent/child elements.
> The benefit of having a "type" attribute would be that some consistency in
> encoding it could be suggested among repositories who want to distinguish
> between different types of <bioghist> notes.  This is best handled by an
> attribute (consistently applied among repositories) rather than a value in
> a <head> element which will vary (or perhaps omitted) among those
> repositories.
> I don't think any such consistency could be imposed on an attribute such
> as 'altrender'.  According to the tag library, the attribute's definition
> is:
> "The content of the element should be displayed or printed differently
> than the rendering established in a style sheet for other occurrences of
> the element"
> In this case, it's not so much to print a different heading (although that
> may be a result) but to indicate the type of data that <bioghist>
> contains.

J. Tomas Nogales              |         voz: (+34) 91 624 92 50
Dpto. Bibl. y Documentacion   |         fax: (+34) 91 624 92 12
UNIV. CARLOS III DE MADRID    |     e-mail: [log in to unmask]
C/ Madrid, 126                |
E-28903 Getafe (Madrid)-SPAIN |