From westonruter at gmail.com  Tue Feb  9 00:02:40 2010
From: westonruter at gmail.com (Weston Ruter)
Date: Mon, 8 Feb 2010 23:02:40 -0800
Subject: [osis-users] Work osisIDs
Message-ID: <fb8299e11002082302s176b155ch50b9ede75cf9daaa@mail.gmail.com>

I'm looking into how osisIDs can be used to unambiguously and precisely
identify an exact edition/revision of a work. The manual states:

The parts of an osisID may contain any mixture of numbers, letters, and
> underscores.
> [?]
>
The prefix to an osisID must contain at least one letter, number or
> underscore, that may be followed by any
> number of letters, numbers or underscores, separated by periods, and
> concluding in a colon ":"
>

The example prefixes found in the manual are:

Bible.en.ABS.CEV.1995
Bible.en.NIV.1984
Bible.en.KJV
Bible.KJV

The following illustrates the components:

Bible(.$lang)?(.$publisher)?.$abbr(.$year)?

It would seem that all components are needed to unambiguously identify a
work. Furthermore, in order to precisely identify a particular revision,
some more granularity should be possible (these numbers I am making up):

Bible.en.ABS.CEV.19950123123000

And not only ISO timestamp, but also a revision number (or edition number)
seems like it would be necessary:

Bible.en.ABS.CEV.19950123123000.r273
or
Bible.en.ABS.CEV.ed2.19950123123000

Is there some standard for constructing these more granular osisIDs to
precisely identify works? Having a standard format would be ideal so that
the information can be parsed out of the osisID.

Thanks!
Weston
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.crosswire.org/pipermail/osis-users/attachments/20100208/6c298760/attachment.html>

From westonruter at gmail.com  Thu Feb 11 08:43:51 2010
From: westonruter at gmail.com (Weston Ruter)
Date: Thu, 11 Feb 2010 07:43:51 -0800
Subject: [osis-users] Encoding Hebrew Psalm Titles
Message-ID: <fb8299e11002110743v2c136cd7tfea4adfd2f2310fb@mail.gmail.com>

In the OSIS manual, an English translation of a Psalm is encoded like this:

<div type='section' scope='Ps.7.1-Ps.7.2'>
    <title>The LORD Always Does Right</title>
    <verse osisID='Ps.7.1'>
        You, LORD God, are my protector.
        Rescue me and keep me safe from all who chase me.
    </verse>
    <verse osisID='Ps.7.2'>
        Or else they will rip me apart like lions
        attacking a victim, and no one will save me.
    </verse>
</div>

However, in the Hebrew versification tradition, the title is actually verse
one. So could it be encoded like this?

<div type='section' scope='Ps.7.1-Ps.7.3'>
    <verse osisID='Ps.7.1'>
        <title>The LORD Always Does Right</title>
    </verse>
    <verse osisID='Ps.7.2'>
        You, LORD God, are my protector.
        Rescue me and keep me safe from all who chase me.
    </verse>
    <verse osisID='Ps.7.3'>
        Or else they will rip me apart like lions
        attacking a victim, and no one will save me.
    </verse>
</div>

Weston
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.crosswire.org/pipermail/osis-users/attachments/20100211/1f1ef117/attachment.html>

From chrislit at crosswire.org  Thu Feb 11 11:19:16 2010
From: chrislit at crosswire.org (Chris Little)
Date: Thu, 11 Feb 2010 10:19:16 -0800
Subject: [osis-users] Work osisIDs
In-Reply-To: <fb8299e11002082302s176b155ch50b9ede75cf9daaa@mail.gmail.com>
References: <fb8299e11002082302s176b155ch50b9ede75cf9daaa@mail.gmail.com>
Message-ID: <4B744A24.8000601@crosswire.org>

>
> I'm looking into how osisIDs can be used to unambiguously and precisely
> identify an exact edition/revision of a work. The manual states:
>
> The parts of an osisID may contain any mixture of numbers, letters, and
>> underscores.
>> [?]
>>
> The prefix to an osisID must contain at least one letter, number or
>> underscore, that may be followed by any
>> number of letters, numbers or underscores, separated by periods, and
>> concluding in a colon ":"
>>
> The example prefixes found in the manual are:
>
> Bible.en.ABS.CEV.1995
> Bible.en.NIV.1984
> Bible.en.KJV
> Bible.KJV
>
> The following illustrates the components:
>
> Bible(.$lang)?(.$publisher)?.$abbr(.$year)?
>
> It would seem that all components are needed to unambiguously identify a
> work. Furthermore, in order to precisely identify a particular revision,
> some more granularity should be possible (these numbers I am making up):
>
> Bible.en.ABS.CEV.19950123123000
>
> And not only ISO timestamp, but also a revision number (or edition number)
> seems like it would be necessary:
>
> Bible.en.ABS.CEV.19950123123000.r273
> or
> Bible.en.ABS.CEV.ed2.19950123123000
>
> Is there some standard for constructing these more granular osisIDs to
> precisely identify works? Having a standard format would be ideal so that
> the information can be parsed out of the osisID.
>
> Thanks!
> Weston
>
>    

These would certainly be legal. Only the format used by 
Bible.en.ABS.CEV.1995 has been defined, though, so I'd recommend keeping 
all additions to the workID format to the right of that. For example:

Bible.en.ABS.CEV.1995.0123123000
Bible.en.ABS.CEV.1995.r273
Bible.en.ABS.CEV.1995.0123123000.r273


--Chris



From chrislit at crosswire.org  Thu Feb 11 11:23:29 2010
From: chrislit at crosswire.org (Chris Little)
Date: Thu, 11 Feb 2010 10:23:29 -0800
Subject: [osis-users] Encoding Hebrew Psalm Titles
In-Reply-To: <fb8299e11002110743v2c136cd7tfea4adfd2f2310fb@mail.gmail.com>
References: <fb8299e11002110743v2c136cd7tfea4adfd2f2310fb@mail.gmail.com>
Message-ID: <4B744B21.1050408@crosswire.org>

>
> In the OSIS manual, an English translation of a Psalm is encoded like this:
>
> <div type='section' scope='Ps.7.1-Ps.7.2'>
>      <title>The LORD Always Does Right</title>
>      <verse osisID='Ps.7.1'>
>          You, LORD God, are my protector.
>          Rescue me and keep me safe from all who chase me.
>      </verse>
>      <verse osisID='Ps.7.2'>
>          Or else they will rip me apart like lions
>          attacking a victim, and no one will save me.
>      </verse>
> </div>
>
> However, in the Hebrew versification tradition, the title is actually verse
> one. So could it be encoded like this?
>
> <div type='section' scope='Ps.7.1-Ps.7.3'>
>      <verse osisID='Ps.7.1'>
>          <title>The LORD Always Does Right</title>
>      </verse>
>      <verse osisID='Ps.7.2'>
>          You, LORD God, are my protector.
>          Rescue me and keep me safe from all who chase me.
>      </verse>
>      <verse osisID='Ps.7.3'>
>          Or else they will rip me apart like lions
>          attacking a victim, and no one will save me.
>      </verse>
> </div>
>
> Weston
>    

These are both correct, except that <title> should be <title 
type="psalm" canonical="true"> in both examples.

--Chris



From westonruter at gmail.com  Sat Feb 27 10:40:37 2010
From: westonruter at gmail.com (Weston Ruter)
Date: Sat, 27 Feb 2010 09:40:37 -0800
Subject: [osis-users] Non-contiguous osisRefs
Message-ID: <fb8299e11002270940k501e48bo8b09708ce2b2b7d9@mail.gmail.com>

(Cross-post on Open Scriptures and OSIS Users)

A common use case for looking up passages is to not only use a range (Exodus
2:1-3) but also to include non-consecutive verses (Exodus 2:1,3; 4:3-5).

I am thinking that for addressing verses in a REST API, the use of
osisIDs/osisRefs are the best bet. How about extending the osisRef to allow
for non-contiguous verses? For example, separating ranges with semicolons:

/api/rest/osis/Bible.hbo.WLC.2009:Exod.2.1;Exod.2.3;Exod.4.3-Exod.4.5

The work_prefix would apply to all subsequent osisIDs listed until another
one is introduced.

/api/rest/osis/Bible.hbo.WLC.2009:Exod.2.1;Exod.2.3;Bible.grc.LXX:Exod.4.3-Exod.4.5

Thoughts?
Weston
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.crosswire.org/pipermail/osis-users/attachments/20100227/057611ea/attachment.html>

From woschultz at googlemail.com  Sun Feb 28 02:59:36 2010
From: woschultz at googlemail.com (Wolfgang Schultz)
Date: Sun, 28 Feb 2010 10:59:36 +0100
Subject: [osis-users] OSIS-Repository online again
Message-ID: <3d5883061002280159gf770e7bk747528d6639864c6@mail.gmail.com>

Hello,

the worlds biggest collection of  OSIS-Bibles is online again.

http://zefania.blogspot.com/2010/02/where-to-get-osis-xml-files.html


greettings

wolfgang
http://www.zykloide.de