> I would suggest to have two structMap sections: One for logical
> and one
> for physical structure. When I understood the METS-schema
> correctly, I
> may have several structMap-sections and may even use the type-
> attributewitht he values "PHYSICAL" and "LOGICAL".
> The question is: How may I point from one div in one structMap section
> to another div (in the physical structMap section)?
>
There's no direct linking mechanism between structMaps; you'd
have to infer it from the data files each are pointing to.
But in the example you've provided, I don't really think
two structmaps are necessary. If we take you're
provided example:
> <div type="book" id="p0001">
> <div type="page" id="p0002"/>
> <div type="page" id="p0003"/>
> <div type="page" id="p0004"/>
> <div type="page" id="p0005"/>
> <div type="page" id="p0006"/>
> </div>
>
> And have the following logical structure:
>
> <div type="book" id="L001">
> <div type="chapter" id="L002">
> point to page with ID="p0002"
> </div>
> <div type="chapter" id="L003">
> <div type="drawing> id="L004">
> </div>
> </div>
> </div>
>
I would encode the above as follows using a single structMap:
<div type='book'>
<div type='chapter'>
<div type='page' />
<div type='page' />
<div type='page' />
</div>
<div type='chapter'>
<div type='page' />
<div type='page'>
<div type='drawing'>
</div>
<div type='page' />
</div>
</div>
You'll note that I've included your 'drawing' element as
a subpart of a page, assuming that the drawing didn't
consume the entire page and should be considered as a subpart
of it. If the drawing did take an entire page, I'd probably
just have a page <div> element for it and let the viewers
figure out that they're looking at a drawing rather than
text; alternatively, you could have a <div> element of
type 'drawing' at the same element as the page elements, if
you wanted to distinguish between pages with drawings
and other types of pages, e.g.
<div type='chapter'>
<div type='page' />
<div type='page' />
<div type='drawing' />
</div>
|