<div dir="ltr">I had a conversation with Troy about osisWork identifiers like:<br><br>Bible.LXX<br>Bible.en.KJV<br>Bible.en.NIV.1984<br>Bible.en.ABS.CEV.1995<br><br>I'm trying to nail down what the specific order that the segments should appear in so that these identifiers can be constructed and recognized programmatically based on the various information available. The goal would be to be able to construct unique unambiguous work identifiers.<br>
<div class="gmail_quote"><div dir="ltr"><br><div class="gmail_quote"><div class="im">On Sun, Jun 20, 2010 at 11:10 PM, Troy A. Griffitts <span dir="ltr"><<a href="mailto:scribe@crosswire.org" target="_blank">scribe@crosswire.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div bgcolor="#ffffff" text="#000000">
<br>
Oh, it's a long debate about what the meaning of each segment of an
osisWord id should be. I think everyone agrees Bible.KJV and likely
Bible.en.KJV are valid, but then I can't remember. I think we punted
and said the rest is publisher preference. I have always argued for a
sane fallback, so a very specific osisRef which requests an osisWork
like Bible.en.KJV.CrossWire.2003 would yield progressively less useful
results as you fall back segment by segment to a module available in
the user's library. That's my reasoning for the syntax I used and
prefer. I'm not sure how Patrick chose his example in the user guide.
Are there prose detailing the meaning of each segment anywhere that
you've seen? I can try to get clarity from the guys.<br></div></blockquote></div><div><br>This is very helpful. It makes sense to consider the segments to be increasingly narrowing in scope; the question is whether or not the publisher is at a higher scope than the work itself, i.e. if the publisher acts as a namespace prefix for the work abbreviation or if it serves as a supplemental disambiguator for what the work abbreviation refers to.<br>
<br>I have not run across any prose detailing the order and possible values for the osisWork segments. The manual merely says:<br><br><blockquote style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;" class="gmail_quote">
The osisWork attribute of each work element provides a short name used to refer that work and its declaration as a whole. As of version 2.1, OSIS specifies the recommended format described below for those short names.<br>
</blockquote><div><br>But I can't find where "below" refers to, and I'm not sure this is referring to the prose that is needed to document what the osisWork segments are.<br><br>Getting clarity regarding this would be a huge help!<br>
<br>The way I've written OsisWork in osis.py currently, I'm probably doing it wrong: <a href="http://github.com/openscriptures/api/blob/41ba6ad7b0d11346e9beff9e9cb7f623be00e8f1/osis.py#L166" target="_blank">http://github.com/openscriptures/api/blob/41ba6ad7b0d11346e9beff9e9cb7f623be00e8f1/osis.py#L166</a><br>
<br>Anyone have any insights?<br></div> </div></div></div>
</div><br>-- <br><div dir="ltr"><b>Weston Ruter</b><br>Founder<br>Open Scriptures<br><a href="http://openscriptures.org/">http://openscriptures.org/</a><br></div>
</div>