<div>Thanks Horst for explaining. </div>
<div>
<br />
</div>
<div>Why is osisRef used rather than osisID ?</div>
<div>
<br />
</div>
<div>The latter would be valid to the schema. </div>
<div>
<br />
</div>
<div>David</div>
<div>
<br />
</div>
<div id="protonmail_mobile_signature_block">Sent from ProtonMail Mobile</div>
<div>
<br />
<div>
<div>
<br />
</div>On Mon, Sep 17, 2018 at 06:22, Horst Sclemmer <<a href="mailto:schlemmerhorst1731@gmail.com" class="">schlemmerhorst1731@gmail.com</a>> wrote:</div>
<blockquote class="protonmail_quote" type="cite">Hi all,
<br />
<br />It's good to see this discussion going on.
<br />I try to briefly explain the need for having the osisRef in a milestone.
<br />As many people are able to read Russian, most translations for languages
<br />in the former Soviet Union use the SynadalProt versification. So, people
<br />comparing their translation with Russian scriptures won't be confused.
<br />On the other hand most of the (former Soviet Union) scriptures don't
<br />follow the versification in every detail.
<br />A very common difference is the problem you see in the Uighur Cyrillic
<br />with Romans 14 and 16.
<br />As Peter already mentioned, there is an anomalie with the last three
<br />verses of Romans 14 and 16. Most western translations (KJV) follow
<br />manuscripts that have these verses in Romans 16:25-27, whereas
<br />SynodalProt has them in Romans 14:24-26.
<br />Romans 16:25-27 seems to be the better place to have them, so most
<br />Central Asian translations decided, not to follow the SynodalProt
<br />versification here.
<br />
<br />The milestone types "x-vsys-..." and annotateRef
<br />annotateTypes="x-vsys-..." are used to reference these moved verses to
<br />the right verses.
<br />See
<br />https://github.com/JohnAustinDev/osis-converters/blob/master/scripts/bible/osis2sourceVerseSystem.xsl
<br />for all the details and possible types.
<br />These milestone and annotateRef types are already used in a lot of OSIS
<br />files for scriptures in the IBT repository
<br />(http://ibt.org.ru/ftpmirror/pub/).
<br />
<br />I can remove the parts that are currently not supported by the OSIS schema.
<br />But as this is a general solution to deal with translations that vary
<br />from their versification, I would suggest to take the effort to adjust
<br />the OSIS schema and add the osisRef attribute to the milestone element.
<br />
<br />Kind regards
<br />
<br />Horst
<br />
<br />
<br />
<br />On 9/13/2018 6:21 PM, David Haslam wrote:
<br />> In the OSIS 2.1 Users Manual, for the milestone element only three attribute names are mentioned: type, n, marker
<br />>
<br />> The osisRef attribute is currently defined only for the following OSIS elements: catchWord, chapter, div, figure, note, q, reference
<br />>
<br />> If we wish to enhance the CrossWire updated OSIS schema, the request should be added as a new subsection in this wiki page:
<br />> https://wiki.crosswire.org/OSIS_211_CR
<br />>
<br />> What does the Uighur translation team envisage as the practical use of osisRef in the OSIS example given?
<br />> What would we expect SWORD to do with it?
<br />>
<br />> Best regards,
<br />>
<br />> David
<br />>
<br />> Sent with ProtonMail Secure Email.
<br />>
<br />> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
<br />> On Thursday, 13 September 2018 10:01, Peter von Kaehne <refdoc@gmx.net> wrote:
<br />>
<br />>> Deal all,
<br />>>
<br />>> I am in the process of uploading an update to our cyrillic Uygyur
<br />>> module.
<br />>>
<br />>> There are a few instances where the new text does not validate due to
<br />>> use of osisRef in the milestone element. The author asserts that
<br />>> osisRef should be possible inside the milestone element and I can not
<br />>> see any reason indeed why it should not - other than "the schema does
<br />>> not allow it". Below an example. The textual background is a manuscript
<br />>> anomaly in Romans 14 and 16, where a couple of verses appear commonly
<br />>> at the end of Romans 16, but in some manuscript in Romans 14.
<br />>>
<br />>> 30965 <verse osisID="Rom.14.23 Rom.14.24 Rom.14.25 Rom.14.26"
<br />>> sID="Rom.14.23 Rom.14.24 Rom.14.25 Rom.14.26" type="x-vsys-
<br />>> fitted"/><milestone type="x-vsys-verse-start" annotateRef="Rom.14.23"
<br />>> annotateType="x-vsys-source"/>Лекин бирәр йемәкликкә шәк кәлтүрүп
<br />>> туруп, йәнә шу йемәкликни йегән киши вижданиниң әйиплишигә учрайду.
<br />>> Чүнки у киши өзи йегән йемәкликниң тоғра екәнлигигә ишәнч қилалмиди.
<br />>> Тоғра екәнлигигә ишәнч йоқ һалда қилинған һәр қандақ иш
<br />>> гунадур.</p><milestone type="x-vsys-movedto" annotateRef="Rom.16.25"
<br />>> annotateType="x-vsys-source" osisRef="Rom.14.24"/><milestone type="x-
<br />>> vsys-movedto" annotateRef="Rom.16.26" annotateType="x-vsys-source"
<br />>> osisRef="Rom.14.25"/><milestone type="x-vsys-movedto"
<br />>> annotateRef="Rom.16.27" annotateType="x-vsys-source"
<br />>> osisRef="Rom.14.26"/><verse eID="Rom.14.23 Rom.14.24 Rom.14.25
<br />>> Rom.14.26" type="x-vsys-fitted"/><milestone type="x-vsys-verse-end"
<br />>> annotateRef="Rom.14.23" annotateType="x-vsys-source"/>
<br />>>
<br />>> Any views? Should the schema be updated or should I reject the module
<br />>> in its current form?
<br />>>
<br />>> Peter
<br />>>
<br />>> sword-devel mailing list: sword-devel@crosswire.org
<br />>> http://www.crosswire.org/mailman/listinfo/sword-devel
<br />>> Instructions to unsubscribe/change your settings at above page
<br />>
<br />>
<br />> _______________________________________________
<br />> sword-devel mailing list: sword-devel@crosswire.org
<br />> http://www.crosswire.org/mailman/listinfo/sword-devel
<br />> Instructions to unsubscribe/change your settings at above page
<br />
<br />
<br />
</blockquote>
</div>