<div dir="ltr">Thanks DM. It helps a lot.<div><br></div><div>I have a different XML format which seems to match more closely the BSP paradigm. Unless I'm mistaken it's quite hard using an XSLT to transform from BSP to BCP (although the reverse feels instinctively easier). </div>
<div><br></div><div>Chris</div><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On 14 February 2014 21:54, DM Smith <span dir="ltr"><<a href="mailto:dmsmith@crosswire.org" target="_blank">dmsmith@crosswire.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">We refer to the two formats as BSP and BCV, or Book/Section/Paragraph and Book/Chapter/Verse.<br>
<br>
All of our programs use BCV and osis2mod ensures that the module's representation internally is BCV.<br>
<br>
Given BSP, osis2mod will convert it to BCV.<br>
<br>
If you need markup that crosses Chapter boundaries (starts in one chapter and ends in another) or Verse boundaries (starts and ends in different verses) then you'll want to do BSP.<br>
<br>
If you merely have text but little or no markup, BCV may do just fine.<br>
<br>
Typically, I'll use containers for everything and see what breaks when validated against the schema. If needed I convert verse start and ends to milestoned version. And try again.<br>
<br>
One of the advantages of starting in this form is you can find silly assumptions about the input that simply were not true.<br>
<br>
Things to watch out for:<br>
Ending things immediately after a verse start, when it should be before a verse start. E.g. a section div, a line group, a paragraph<br>
Ending things immediately before a verse end, when it should be after a verse end. E.g. a section div<br>
Starting things immediately after a verse start, when it should be before a verse start. E.g. a section div<br>
Starting things immediately before a verse end, when it should be after a verse end. E.g. a section div, a title<br>
<br>
By and large, elements of document structure should be between verses.<br>
<br>
Hope this helps.<br>
<br>
In His Service,<br>
DM<br>
<div><div class="h5"><br>
<br>
On Feb 14, 2014, at 3:22 PM, Chris Burrell <<a href="mailto:chris@burrell.me.uk">chris@burrell.me.uk</a>> wrote:<br>
<br>
> Hello<br>
><br>
> I'm looking to create some OSIS modules from some proprietary format. I recall seeing two types of OSIS markups. The fully nested version (i.e. 1 verse element contains all verse contents) and a more linear version (1 verse element contains sID and eID and the contents are not nested).<br>
><br>
> I'm assuming the latter is the more formal/correct version and more flexible as it would allow to mark-up cross-verse content?<br>
><br>
> Is there any reason why I've come across both formats? Do the Sword utilities convert from the latter to the former?<br>
><br>
> Chris<br>
><br>
</div></div>> _______________________________________________<br>
> sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a><br>
> <a href="http://www.crosswire.org/mailman/listinfo/sword-devel" target="_blank">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
> Instructions to unsubscribe/change your settings at above page<br>
<br>
</blockquote></div><br></div>