Yes. <chronlist> is a child of <index>, not <indexentry>
On Mon, 23 Feb 2004, Leah Prescott wrote:
> Well, this is what I have:
>
> <index>
> <head>Index to Dates</head>
> <p>blah, blah, blah</p>
> <indexentry>
> <chronlist>
> <chronitem>
> <date>1906 Dec 3</date>
> <event>G12</event>
> </chronitem>
> </chronlist>
> </indexentry>
> </index>
>
> and XMLSpy tells me that <chronlist> is an unexpected child element - do
> I have them nested incorrectly?
>
> Leah Prescott
> Manuscripts and Archives Librarian
> Collections Information Technology Coordinator
>
> MYSTIC SEAPORT
> The Museum of America and the Sea
> G.W. Blunt White Library
> 75 Greenmanville Avenue
> PO Box 6000
> Mystic CT 06355-0990
>
> tel: 860.572.0711 x5263
> fax: 860.572.5394
> [log in to unmask]
> http://www.mysticseaport.org
>
>
> -----Original Message-----
> From: Encoded Archival Description List [mailto:[log in to unmask]] On Behalf
> Of J. Tomás Nogales
> Sent: Monday, February 23, 2004 11:44 AM
> To: [log in to unmask]
> Subject: Re: date index
>
>
> Hello, Leah.
> Note that the content model for <index> is:
> -----
> <!ELEMENT index (head?, (address | chronlist | list | note | table |
> blockquote | p)*, ((listhead?, indexentry+) | index+))>
> -----
> and therefore, within an <index> element you MUST use one or more
> <indexentry> elements (or an <index> child element), AFTER your
> <chronlist> if you use it. The message from XMLSpy will disappear if you
> do so.
> Maybe you are trying to insert your <chronlist> in the wrong place.
> Note that <chronlist> may appear within more than 30 other elements too,
> without loss of hyperlink ability: your <date>s can contain ptr's and
> your <event>s can contain all the ref's you need as well.
> Excuse my english.
> Best regards,
> Tomás.
>
> Leah Prescott wrote:
>
> > I am in the process of converting our finding aids from EAD version 1
> > to version 2. One of the things that I am happy about is that I can
> > now imbed indexes right into the finding aid - previously we had
> > separate html indexes and when a person found the index through
> > Google, for instance, it wasn't always clear exactly what they were
> > looking at. My problem is that we have one collection that has an
> > important index to dates. In looking at the tag library I see that a
> > <chronlist> may occur within an <index> element but when I try to do
> > this I get an error message from XMLSpy that it is an unexpected child
>
> > element. Do I need to edit my copy of the DTD to do this, or am I
> > missing something? Does anyone else have any date indexes within a
> > finding aid and do you put it somewhere other than <index>?
> >
> >
> > Leah Prescott
> > Manuscripts and Archives Librarian
> > Collections Information Technology Coordinator
> >
> > MYSTIC SEAPORT
> > The Museum of America and the Sea
> > G.W. Blunt White Library
> > 75 Greenmanville Avenue
> > PO Box 6000
> > Mystic CT 06355-0990
> >
> > tel: 860.572.0711 x5263
> > fax: 860.572.5394
> > [log in to unmask]
> > <mailto:[log in to unmask]>
> > http://www.mysticseaport.org
>
>
> --
> ------------------------------+--------------------------------
> 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 | http://www.bib.uc3m.es/~nogales
> E-28903 Getafe (Madrid)-SPAIN |
> ------------------------------+--------------------------------
>
|