Mete wrote in mid December:
[...]
[...]

I'm wondering if that means that:
a) There will be an official set of abbreviations for the various books;
b) An official way to convert verses between Bible versions.
c) An official way to specify Bible Versions/Translations.
d) An official way to specify the underlying manuscript collection. 

An example of "a" would be "Ge: Genesis".

An example of "b" would "Daniel 3:91(JB) = Daniel 3:24(KJV).

An example of "c" would be "JB: Jerusalem Bible".

An example of "d" would be "LXX: Septuagint".

I'm basing this on some of the specs for STEP files, and ThML.

If you have found out exactly what that passage means, could you
elucidate the rest of us?

[I ran across this message looking for some other OSIS Documentation.]

xan

jonathon[...]

Op 10-apr-05 om 5:39 heeft Jonathon Blake het volgende geschreven:
[...][...][...]

Also, how is the progress in making such a schema. Especially what 
Jonathon called "b" is a major annoyance that caused me to postpone 
working on several projects.

I understand that differences in versification is a problem with a 
history of centuries. It is quite messy and there is very few info on 
this topic. So we shouldn't expect BibleTechnologies to come up with an 
elegant and reliable fix soon. So I wonder who is working on this and 
is there any way we can help?

Terry

Jonathan,

See below.

Todd

Jonathon Blake wrote:

 > Mete wrote in mid December:
 >
 >
 >> explain what is exactly meant by the XML schema referenced below:
 >
 >
 >
 >> "BTG intends to develop an XML schema for declaration
 >> files that can express such systems, and their mapping
 >
 >

This refers to the creation of an XML syntax for mapping between the 
different versification schemes.


 >
 > I'm wondering if that means that:
 > a) There will be an official set of abbreviations for the various books;


This is already well established along with the syntax for chapter, 
verse, ranges, and character and/or word offsets within a verse.

 > b) An official way to convert verses between Bible versions.


As long as the versions share the same versification/reference system 
then all is well.  If an individual translation is encoded with multiple 
reference systems then too all is well.

 > c) An official way to specify Bible Versions/Translations.


This has been established already.

 > d) An official way to specify the underlying manuscript collection.


I am not sure what you mean by "underlying".  Do you mean the 
manuscript(s) from which a translation was translated or do you mean a 
way to reference an manuscript that was used in a translation?

If you mean the later then each underlying manuscript is a work in its 
own right and can be referenced directly and precisely.

 >
 > An example of "a" would be "Ge: Genesis".
 >
 > An example of "b" would "Daniel 3:91(JB) = Daniel 3:24(KJV).
 >
 > An example of "c" would be "JB: Jerusalem Bible".
 >
 > An example of "d" would be "LXX: Septuagint".
 >
 > I'm basing this on some of the specs for STEP files, and ThML.
 >
 > If you have found out exactly what that passage means, could you
 > elucidate the rest of us?
 >
 > [I ran across this message looking for some other OSIS Documentation.]
 >
 > xan
 >
 > jonathon

Hello Todd,
[...]

Will this XML syntax be able to account for variations
in versifications in manuscript collections that
emulate the same versification system in general but
differ in a handful of cases?

Thanks,
Mete

--- Todd Tillinghast <todd(at)contentframeworks.com>
wrote:[...]

Mete,

Yes, the syntax for mapping between two translations that both use the 
same versification system can be used to define an individual reference 
system for two translations and then define a mapping between them.

However, this should not be necessary in most cases.

If the differences are things like Matt.1.6!a and Matt.1.6!b then the 
mapping between Matt.1.6 in one translation and Matt.1.6!a and 
Matt.1.6!b is already taken care of with the use of the "!" that 
indicates an extension to the "standard" reference system.

Can you provide some specific details regarding the case(s) you are 
considering?  (With more details the appropriate direction should be 
more clear.)

Todd

Mete Kural wrote:

 > Hello Todd,
 >
 >
 >> This refers to the creation of an XML syntax for mapping between the 
different versification schemes.
 >
 >
 >
 > Will this XML syntax be able to account for variations
 > in versifications in manuscript collections that
 > emulate the same versification system in general but
 > differ in a handful of cases?
 >
 > Thanks,
 > Mete
 >
 > --- Todd Tillinghast <todd(at)contentframeworks.com>
 > wrote:
 >
 >> Jonathan,
 >>
 >> See below.
 >>
 >> Todd
 >>
 >> Jonathon Blake wrote:
 >>
 >> > Mete wrote in mid December:
 >> >
 >> >
 >> >> explain what is exactly meant by the XML schema
 >> referenced below:
 >> >
 >> >
 >> >
 >> >> "BTG intends to develop an XML schema for
 >> declaration
 >> >> files that can express such systems, and their
 >> mapping
 >> >
 >> >
 >>
 >> This refers to the creation of an XML syntax for
 >> mapping between the different versification schemes.
 >>
 >>
 >> >
 >> > I'm wondering if that means that:
 >> > a) There will be an official set of abbreviations
 >> for the various books;
 >>
 >>
 >> This is already well established along with the
 >> syntax for chapter, verse, ranges, and character and/or word offsets
 >> within a verse.
 >>
 >> > b) An official way to convert verses between
 >> Bible versions.
 >>
 >>
 >> As long as the versions share the same
 >> versification/reference system then all is well.  If an individual 
translation is
 >> encoded with multiple reference systems then too all is well.
 >>
 >> > c) An official way to specify Bible
 >> Versions/Translations.
 >>
 >>
 >> This has been established already.
 >>
 >> > d) An official way to specify the underlying
 >> manuscript collection.
 >>
 >>
 >> I am not sure what you mean by "underlying".  Do you
 >> mean the manuscript(s) from which a translation was
 >> translated or do you mean a way to reference an manuscript that was 
used in a
 >> translation?
 >>
 >> If you mean the later then each underlying
 >> manuscript is a work in its own right and can be referenced directly
and
 >> precisely.
 >>
 >> >
 >> > An example of "a" would be "Ge: Genesis".
 >> >
 >> > An example of "b" would "Daniel 3:91(JB) = Daniel
 >> 3:24(KJV).
 >> >
 >> > An example of "c" would be "JB: Jerusalem Bible".
 >> >
 >> > An example of "d" would be "LXX: Septuagint".
 >> >
 >> > I'm basing this on some of the specs for STEP
 >> files, and ThML.
 >> >
 >> > If you have found out exactly what that passage
 >> means, could you
 >> > elucidate the rest of us?
 >> >
 >> > [I ran across this message looking for some other
 >> OSIS Documentation.]
 >> >
 >> > xan
 >> >
 >> > jonathon
 >>
 >>
 >>
 >> --
 >> To unsubscribe send an email with subject
 >> unsubscribe to osis-user(at)whi.wts.edu.
 >> Please contact klowery(at)whi.wts.edu for questions.
 >>
 >
 >
 >