From: Bruce D'Arcus <bdarcus@fa...> - 2004-11-13 13:42:25
As I was thinking about handling parts again, I'm thinking maybe it
should be pretty simple; that it shouldn't require anything in
particular, except maybe a way to identify the part location within a
larger work (page or chapter numbers, for example).
Let's take an example of an episode of a TV show that is contained on a
DVD (not coincidentally the same structure as a book chapter).
episode is a work
it is manifest (or expressed?) as:
A. partOf a television show (a serial), with identifier of "broadcast
B. partOf a DVD, with identifier of "chapter number" (and perhaps
While I was first thinking the linking relationship would happen
strictly at the work level, I guess in this case, the idea might be to
link the episode manifestation to the other two "isPartOf" containers,
which are works?
I really don't get SQL, but can this now be represented in the
database? Put differently, notwithstanding the initial UI focus on
movies, can the database now handle a journal article, complete with
volume, issue and page numbers in their own fields?