[jsword-devel] Verse markup in OSIS modules

[DM Smith]

I misunderstood an example in OSIS 2.0 User's Manual where I saw:
<p osisID="Matt.1.1 Matt.1.2 Matt.1.3>...</p>
And I thought that the p tag was being used to markup verses.
According to the manual the use here indicates what verses are 
contained. I am not sure how such an attribute would be useful.

WRT to sID and eID verse milestones being a best practice. All I saw in 
the OSIS User Manual section 11 was a rule that within a document that 
one either uses a verse container model or a verse milestone model but 
not both.

Since structural markup can span several verses and even split verses it 
seems to me that any richly tagged Bible will have to use the verse 
milestone model.

The same document said that there are various levels of conformance. 
Each level of conformance required more and more elements. And I think 
level 2 conformance elements (poetry, paragraphs, block quotes, ...) 
imply that verse milestones will be used.

But I did not find any place that stated milestones was a best practice. 
Section 11 stated that the verse container model was the norm. Can you 
point me to such a statement? I would appreciate it.

WRT to using verse markup as the means of rendering verse numbers, I am 
not sure I fully understand. If I go to the OSIS portal and download a 
Bible and then render a chapter of it in XSLT, what would I use to 
render the verse number? And if two or more verses are spanned by a 
single verse element how would that be rendered? E.g. (from the manual)
<verse sID="Esth.1.1-Esth.1.2" osisID="Esth.1.1 Esth.1.2" n="1-2"/>
King Xerxes of Persia lived in his capital city of Susa and ruled one
hundred twenty-seven provinces from India to Ethiopia.
<verse eID="Esth.1.1-Esth.1.2"/>

(As I re-read all this I think it comes across as argumentative, but I 
don't mean it to be. I really am looking for a greater understanding of 
OSIS.)

Chris Little wrote:

> DM Smith wrote:
> 
>> The reason to look for an osisID is that <verse> is not the only way 
>> to specify a verse according to OSIS 2.0. The various filters should 
>> not care whether the data came from a Sword module or from some other 
>> system.
> 
> 
> I don't understand what you mean here.  There are two valid ways to 
> express <verse> elements: either as a container (<verse>...</verse>) or 
> as a pair of milestones (<verse sID="..."/>...<verse eID="..."/>), but 
> the only way to specify a verse is with the <verse> element. 
> Furthermore, if you are creating best practice OSIS, there is only one 
> way to encode verses: <verse/> milestones.  (In other words, the WLC 
> module, while valid, is not best practice-conformant.)
> 
>> I did some more reading of the sword-devel archives and it seems that 
>> there is a bit of disagreement on whether the stored text should 
>> contain verse markup.
>>
>> If WLS is any indication on the final disposition of that 
>> disagreement, then the OSIS modules should be fully marked up.
> 
> 
> It indicates nothing and the jury is still out.  But I think the 
> disagreement is less about whether text should contain verse markup and 
> more about whether the markup should be used as the basis for rendering 
> verse numbers.
> 
> --Chris
> 
> 
> _______________________________________________
> jsword-devel mailing list
> jsword-devel at crosswire.org
> http://www.crosswire.org/mailman/listinfo/jsword-devel
>