Thank you for your reply. Please take a look at my comments below:
<<<<It looks to me like you want two different views of the collection
of video files, one of which I would characterize as more-or-less
physical (here are the video segments composing the collection,
in order), and one more-or-less logical (here are the events and
scenes users will want to look at within the collection).
You are on the mark in using two structMaps, although I'd be
tempted to assign a TYPE attribute of "physical" to the first
(I'll concede the attribute value is a debatable point, and not that
Segments are also a logical division of a collection and don't represent
the files that actually make up the collection.
<<<<If a scene always consists of one or more segments, and the segment
boundaries always match scene boundaries (i.e., you're never going to
have a scene which begins or ends in the middle of a segment), then yes,
I would do as you propose, a logical hierarchy in the second structMap
which would go:
The overall logical relationship of Event/Segment/Scene is as follows:
1] Segments are created as logical divisions at collection level in a
2] Segments are then combined in any possible order (not connected to
their original ordering in the collection) to create Events.
3] After Events are defined they are further divided into Scenes.
So, Scenes defined within an event, will surely cross Segment boundaries
that make up an Event. Also, some Segments may not belong to any Event.
For example, a user divides a set of video files into contiguous
segments Seg1, Seg2, Seg3 and Seg4. Then the user defines Event1 as a
combination of Seg1 and Seg3, and Event2 as a combination of Seg2 and
Seg4. Here, Seg1 and Seg3 are "completely" part of Event1. Now Event1 is
further divided into Scenes and these scenes will not correspond to the
segment boundaries making up an event.
Given this logical structuring, and avoiding the use of StructLink, how
will this structure be captured in the StructMap area?