[osis-core] Best practice to encode multiple endings to Mark, Rev, Ester, and Ps.151
Todd Tillinghast
osis-core@bibletechnologieswg.org
Fri, 25 Apr 2003 17:23:55 -0600
There are two ending to Bible.CEV.Mark, my question is what is the best
way to encode both of the alternate endings in the same document.
Here are what I see as options:
1) Identify the alternant section by assigning different osisIDs to one
of the two alternates.
2) Use the "subType" attribute with a value of "alternant" for the
non-dominant ending.
3) Use the "subtype" attribute with a value of "alternant-primary" and
"alternant-secondary" OR "alternant-A", "alternant-B", "alternant-C",
etc...
If the subtype is used, on which elements should it be used? At then
end of Mark there are <div> sections that contain the two alternant
endings. We could use the "subtype" attribute on only the <div> section
elements and/or we could also mark the child elements with the same
"subtype" attribute values.
In Rev there is a single verse that is marked as an alternant but it is
really just an additionally verse and not an alternant. Should we use
the same sort of strategy here? If so should the "subtype" attribute
value be "alternant", "alternant-additional", ...?
Ps.151 although usually kept separate from Ps.1-150, seems to really be
an alternant ending to Ps. Thoughts?
Lastly, Greek Esther also has the flavor of an alternant ending to
Ester.
How much of the separation of Greek Esther from Esther and Ps.151 from
Ps.1-Ps.150 is a function of how they have traditionally been render vs
the fact that they are truly separate "works" that happen to have the
same name. Naturally it is possible create a "Protestant" version that
did not have these portions to make the document more comfortable to
groups that do not believe they are canonical.
Todd