[osis-core] Questions

[Todd Tillinghast]

Patrick,

This seems to be taking about <identifier type="OSIS"> values.  Correct
me if I am mistaken.

There is a one hour session on this topic in the up coming meeting.  I
can put it on the agenda.

Todd

> -----Original Message-----
> From: osis-core-admin@bibletechnologieswg.org [mailto:osis-core-
> admin@bibletechnologieswg.org] On Behalf Of Patrick Durusau
> Sent: Thursday, January 15, 2004 1:40 PM
> To: osis-core@bibletechnologieswg.org
> Subject: [osis-core] Questions
> 
> Guys,
> 
> A host of material has been posted to the osis-editors list that I am
> just now reaching. I am doing the corrections, inserted suggested
> examples, etc. but thought we might need to discuss some of the
> following questions by Daniel Englbauer (Thanks Daniel!):
> 
> 29. Standard OSIS Codes for Bible Editions
> All Bible Edition codes must have the language code for the
> target language in question, then a colon, then the abbreviation
> shown here.
> 
> 29.1. Ancient language editions
> Steph Stephanus GNT, 1551
> Vul Latin Vulgate, 1405
> Erasmus Latin translation by Desiderius Erasmus Roterodamus, 1516
> Mas Masoretic text (various, ~900-1100)
> BHS Biblia Hebraica Stuttgartsiensa
> NA Nestle-Aland Greek New Testament (may suffix edition number,
> such as "NA27")
> LXX Greek Septuagint
> 
> <question>
>      Which language code has to be used to specify the
> translation?
>      IANA, IETF, ISO-639-1, ISO-639-2, ISO-639-2-B, ISO-639-2-T,
>      LINGUIST or SIL?
>      What is the language code for the "BHS"? The 'hebrew' bible
>      contains biblical hebrew and biblical aramaic.
>      Is the Code for LXX "gr:LXX" or "GKO:LXX" or "GRK:LXX"?
> </question>
> 
> 
> 29.1.2. Non-English Modern Languages
> Thousands of additional languages have Bibles or portions; most
> of these have only one translation in the language. In those
> cases the language code as defined elsewhere in OSIS may be used,
> with no following name required.
> 
> <comment>
>      It sure is simple to handle it that way, but what will
> happen,
>      in case someone offers another translation in this language?
>      Then there are two versions and you would have to find
> another
>      way to give a translation type or the first written version
>      will block the short form. Older versions of OSIS-texts have
>      to be modified. I think it's better to build a type of
>      database of OSIS standard codes over the time with a name for
>      every known bible translation.
> </comment>
> 
> Luther       German by Martin Luther, 1534
> Algonquin    Tr. John Eliot, 1662
> ReinaV       Spanish Reina Valera
> 
> <question>
>      The German translation of the bible by Luther in 1534 is
>      "de:Luther". Is the 1984 revision then "de:Luther1984" if
>      there is no standard OSIS codes for bible editions yet?
>      So I make a recommendation for German versions next section.
> </question>
> 
> <question>
>      There is a default value for the optional osisRefWork-
>      attribute (Bible). Are there other given standard attributes
>      like "comment", "lexica", "book" or "article"?
> </question>
> 
> <question>
>      How to mark up verses within a text that are not directly
>      taken from a given (published) translation, but are
> translated
>      by the author of the book or article?
> </question>
> 
> I am writing back to Daniel to thank him for his contribution.
> 
> While I am doing the corrections, anyone care to take a stab at the
> questions?
> 
> Hope everyone is in good health and spirits!
> 
> Patrick
> 
> --
> Patrick Durusau
> Director of Research and Development
> Society of Biblical Literature
> Patrick.Durusau@sbl-site.org
> Chair, V1 - Text Processing: Office and Publishing Systems Interface
> Co-Editor, ISO 13250, Topic Maps -- Reference Model
> 
> Topic Maps: Human, not artificial, intelligence at work!
> 
> 
> _______________________________________________
> osis-core mailing list
> osis-core@bibletechnologieswg.org
> http://www.bibletechnologieswg.org/mailman/listinfo/osis-core