Print

Print


The locus attributes aren't exactly searchable when they're used to encode
manuscript folios anyway... or have others had success in doing this?

Dr Jill Seal Millman
Perdita Project
English & Media Studies
Nottingham Trent University
http://human.ntu.ac.uk/perdita

-----Original Message-----
From: M. J. Driscoll [mailto:[log in to unmask]]
Sent: Monday, November 04, 2002 8:08 AM
To: [log in to unmask]
Subject: Re: multiple page range in master


The other alternative, and what we have tended to do here at the
Arnamagnaean Institute, is to follow the manuscript in dividing what
we would otherwise like to see as a single work into two (or more)
parts, making each a separate item; <id>s can be used to hold the bits
together, e.g.:

<msItem n="1" id="NN-1">
    <locus from="1r" to="23v">ff. 1r-23v</locus>
    <title>The saga of Noggin the Nog (part 1)</title>
</msItem>
<msItem n="2" id="NB">
    <locus from="24r" to="27v">ff. 24r-27v</locus>
    <title>The tale of Nogbad the Bad</title>
</msItem>
<msItem n="3" id="NN-2">
    <locus from="28r" to="35v">ff. 28r-35v</locus>
    <title>The saga of Noggin the Nog (part 2)</title>
</msItem>

This is very common in Old Norse manuscripts, incidentally, and for
some genres more the rule than the exception.

M. J. Driscoll
Copenhagen


> Subject: Re: A Master problem
> To: [log in to unmask]
> Message-Id: <[log in to unmask]>
>
> The current Master scheme requires you to  put both page
> ranges within the body of a single <locus>:
>
> <msItem n="3">
> >   <locus from="189r" to="229v">ff. 189r-191v; ff.
> >   226r-229v</locus>
>
> You might not like that, but that's how it is currently
> defined.
>
> Lou
>
> In message <[log in to unmask]>
> [log in to unmask] writes: > How should a msItem in
> master be encoded, if the intellectual content > described
> streches across more than one page (or folio) range. The >
> following example > > <msItem n="3"> >   <locus from="189r"
> to="191v">ff. 189r-191v</locus> >   <locus from="226r"
> to="229v">ff. 226r-229v</locus> >   <author>Alphonsus de
> Jaen</author> >   <title type="uniform">Epistula solitarii
> ad reges</title> >   <rubric>Jncipit epistula solitarii ad
> Reges (in upper margin)</rubric> >   <incipit>O serenissimmi
> reges vtinam veri reges in christo ... </incipit> >
> <explicit>Qui rex est  regum et dominus dominancium in
> secula seculorum >   amen.</explicit> >   <note><p>On f.
> 229r: <q>Jncipit prologus libri celestis imperatoris ad >
>  reges</q></p> >     <p>On f. 229v: <q>Ad presentis quippe
> nunc iam materiam ... </q></p> >   </note> > </msItem> > >
> doesn't validate, since msItem is defined as > > ELEMENT
> msItem
>          (locus?, (author | respStmt | title | rubric |
>          summary |
> >         incipit | explicit | colophon | textLang | q |
> >         decoNote | bibl | listBibl | note | msItem)*) >
> >
> > It seems to me that master would be more useful if this
> > was redefined
> >
> > ELEMENT msItem
>          (locus*, (author | respStmt | title | rubric |
>          summary |
> >         incipit | explicit | colophon | textLang | q |
> >         decoNote | bibl | listBibl | note | msItem)*) >
> >
> > or is there an established other way of solving this
> > problem?
> >
> > Yours
> >
> > Sigge
> >
> > ________________
> > Sigfrid Lundberg, Ph.D.;        [log in to unmask]
> > Lund University Libraries;
> > http://bourree.lub.lu.se/SigfridLundberg/ PO Box 134,
> > S-221 00 Lund       phone +46 (0)46 222 36 83 Sweden
> >
>
>
> ----- End forwarded message -----