On 27/08/10 08:23, Greg Hellings wrote:
The first step is deciding on a markup method. I like the sound of
DM's, but I don't see why it couldn't be handled in OSIS already? A
verse could have something along the lines of<verse
osisID="Gen.1.1">{file: "sounds/Genesis/1.aac", start_time: "0:0:15",
end_time: "0:0:23"}</verse>.
One problem with encoding this information in the OSIS file is that the
audio might not be as fixed/permanent as the written text of a
particular version. For example, what if two audio versions are
available for the same text, with male and female readers, or with
readers with different voice qualities or accents? Once start/stop times
are in the OSIS file, you have limited the audio (and one day video) to
one very specific version.
Is stand-alone markup not better in this case? i.e., put the start/stop
times in a separate place/module/database -- easily linked to by verse
references. Then this separate repository could easily contain files for
multiple audio/video versions for the same written text, etc.
Robert.
_______________________________________________
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page
