--- Kate Bowers <[log in to unmask]> wrote:
> Has anyone else had this problem with blockquote or with other
> elements?
> In one .xml finding aid (using an ead.xsd), I can insert a
> <bioghist> and I
> am offered in the element list box <blockquote>.  In another
> finding aid,
> if I insert <bioghist> <blockquote> is not offered as a possible
> sub-element, and, in fact, even if I try typing it in in plain text
> view,
> it won't validate.
> Any ideas for why this behavior?
> Kate

Please send you bioghist code.

Without seeing it, I would suggest the following:

bioghist must have head as its first child if there is a head.
Other block elements are next (address ; chronlist ; list ; note ;
table ; blockquote ; p ; bioghist ; dao ; daogrp).

Groupings by dtd order are as follows:
1. head (if there is one)
2. address ; list; note; table; p; dao; daogrp; bioghist
    (if bioghist is a child no other children may appear except
bioghist then return to 1)
3. chronlist (no other children can follow this child)

2. Blockquote MUST have children. It is a complextype.
(@mixed="false"). (schema blockquote node below)

Mike Ferrando
Library Technician
Music Division
Library of Congress
Washington, DC

  <xs:element name="blockquote">
        <xs:element ref="address" minOccurs="1" maxOccurs="1" />
        <xs:element ref="chronlist" minOccurs="1" maxOccurs="1" />
        <xs:element ref="list" minOccurs="1" maxOccurs="1" />
        <xs:element ref="note" minOccurs="1" maxOccurs="1" />
        <xs:element ref="table" minOccurs="1" maxOccurs="1" />
        <xs:element ref="p" minOccurs="1" maxOccurs="1" />
      <xs:attribute name="audience" use="optional">
          <xs:restriction base="xs:NMTOKEN">
            <xs:enumeration value="external" />
            <xs:enumeration value="internal" />
      <xs:attribute name="altrender" type="xs:string" use="optional"
      <xs:attribute name="id" type="xs:ID" use="optional" />

Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around