<div>I know Jeff Klassen of UBS ICAP. <caret></caret></div><div><br></div><div>We met in 2012 at the DB Summit. </div><div><br></div><div>David</div><div><br></div><div id="protonmail_mobile_signature_block"><div>Sent from ProtonMail Mobile</div></div> <div><br></div><div><br></div>On Tue, May 5, 2020 at 05:33, Michael H <<a href="mailto:cmahte@gmail.com" class="">cmahte@gmail.com</a>> wrote:<blockquote class="protonmail_quote" type="cite"> <div dir="ltr"><div class="gmail_default" style="font-family:garamond,serif;font-size:large">The Short answer about the OSIS spec tho<br><br>For now, I've been coding the PDF -> text -> USFM intending to ultimately convert it to either markdown or OSIS for longterm maintenance. markdown if UBS maintains it, and OSIS if it's maintained at Crosswire. <br><br>But my work in progress is: <br><br><a href="https://drive.google.com/file/d/12TMgc_h4DWCWWjZ3B6dBOoynvyzMp4q-/view?usp=sharing">https://drive.google.com/file/d/12TMgc_h4DWCWWjZ3B6dBOoynvyzMp4q-/view?usp=sharing</a><br></div><div class="gmail_default" style="font-family:garamond,serif;font-size:large"><br>I intend to get it to paragraphs with character styling, and the images present. At that point it can turn into USFM, or OSIS, or Markdown. and once a long term direction for ownership and maintainer becomes clear, the right place to land it into a repo should be obvious and easy. <br><br>But... does anyone have contact with Patrick and could query him for the source? If not, does anyone have contact with Jeff Klassen and could ask him or have enough knowledge already to know that UBS won't have anything like source code for OSIS manuals?</div><div class="gmail_default" style="font-family:garamond,serif;font-size:large"><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, May 4, 2020 at 11:24 PM Michael H <<a href="mailto:cmahte@gmail.com">cmahte@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_default" style="font-family:garamond,serif;font-size:large">1. What I mean by 'encoding' a copy (for my own use originally, but after trying to find the list of corrections... i'm on this thread thinking the work needs to be shared.) <br><br>Problem: <br>The PDF has issues when you try to copy tabular information.. it was not generated to be reused digitally at all.. random text sequencing is present. (at least for me using both Adobe PDF REader and Ubuntu default PDF reader on Ubuntu 18.04, but I remember this from my windows days 12 years ago. <br><br>My Personal Use: <br>I need those tables to become data tables for programming. I 'code' in spreadsheets as much as possible. So, this morning I started trying to squeeze the lemon. And just like everyone, I run into text integrity issues, and thought this isn't working well enough, I need to find the source text. Query 1 was to Patrick Durasau, but the email in the spec is non-functional. I traced him til 2013 when he was let go as the document manager of OASIS (of OpenDocument/OpenOffice.) But while he crafted the text, he wasn't the owner. American Bible Society holds the copyright, so the logical first step is to query the guy managing USX and USFM about it. But even before that, the only live document on the web seems to be from crosswire (and ebible too... ) so that led me to this thread asking <br>a. Does crosswire have ownership of the OSIS spec now? (can we initiate changes, maintain it?) <br>b. does a project to at least bugfix the OSIS spec already exist?<br><br>I think I've seen enough to understand that niether is true, so the logical next step (unless someone who was involved directly in 2006 can correct me) is to ask Jeff Klassen at UBS if there is source available from UBS, and what would we need to be able to become the maintainers or primary contributors to a project if they want to continue owning it. However, sending that email when I've tried to draft it, I come across speaking for crosswire, which again prompted me to create this thread. <br><br><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, May 4, 2020 at 2:49 PM DM Smith <<a href="mailto:dmsmith@crosswire.org">dmsmith@crosswire.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>Can you clarify what you mean by “I’m encoding the entire spec for storage in a source form….”?<div><br></div><div>What has happened so far is that we’ve been responding with the 2006 2.1.1 version of the OSIS Spec. We host the file at <a href="https://crosswire.org/osis/OSIS%202.1.1%20User%20Manual%2006March2006.pdf">https://crosswire.org/osis/OSIS%202.1.1%20User%20Manual%2006March2006.pdf</a>. If I remember correctly, the PDF is generated from a different document to which we don’t have access. If we wish to fix and improve that document, I think we should see if we can formally take responsibility for it by contacting Patrick Duruasau.</div><div><br></div><div>Short of that we’ve been documenting shortcomings in the wiki.</div><div><br></div><div>We do require valid OSIS. There have been bugs and shortcomings in the schema. I’m the pumpkin keeper of that and have made a few changes that are agreeable to this mailing list. We’ve attempted to document that in the wiki. One of the considerations is whether the suggested change works with how the SWORD and JSword engines understand the spec.</div><div><br></div><div>You are right that the wiki is not issue tracker and gets harder to understand as more gets added to it. David and I have tried to have the wiki on OSIS be an addendum to the spec. And guidance on how to build a SWORD module using it.</div><div><br></div><div>Do you have a suggestion on to get from where we are to where you think we should be? </div><div><br></div><div>In Him,</div><div><span style="white-space:pre-wrap"> </span>DM<br><div><br><blockquote type="cite"><div>On May 4, 2020, at 3:12 PM, Michael H <<a href="mailto:cmahte@gmail.com">cmahte@gmail.com</a>> wrote:</div><br><div><div dir="ltr"><div class="gmail_default" style="font-family:garamond,serif;font-size:large">David, <br><br>That page you refer to is the problem that created this email. <br><br>The page you refer to shouldn't exist like it does.. that information should be going onto a problem ticket system. (Think the 'issue tracker' on the USFM 3 list. It's searchable and the status of most items is clear, and anything already acted on is already on the official documentation pages.) <br><br>That collection of pages in its current form provides little information. it's not sorted by status of investigation/implementation, nor by the spec's organization, but rather by the impression of the author as to it's nature. It seems to be a collection of writings, some of which describe real problems that have been acted on already, some that describe misspellings (but can safely be ignored for module creation.), and some that fit into "wishlist" meaning even if they're in the 'bug' category and actually bugs, they aren't affecting what happens today. Each writing in the wiki will have to be processed before I can code. I can't see any clear status marker present so I can sort the already dones from the wishlist. <br><br>THATS what I'm suggesting/working toward. I'm encoding the entire spec for storage in a source form, so that implemented bugfixes can be updated into the spec. We should not have to go through megabytes of text to find 3 misleading characters in the spec that will break every module someone trying to follow the spec will run into. I've seen enough in the wiki that I'm pretty sure there's at least on issue listed there that is likely to be in that class, but I'm going to have to sort through each and every sentence on each and every page to find them all. <br><br><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, May 4, 2020 at 1:25 PM David Haslam <<a href="mailto:dfhdfh@protonmail.com">dfhdfh@protonmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> <div>Have you looked at our Wiki page?</div><div><br></div><div>OSIS 211 CR</div><div><br></div><div>It was even edited again today!</div><div><br></div><div>The Bible Technologies Group has not met for years & the original website went AWOL. </div><div><br></div><div>It may well be the case that CrossWire is the only remaining de facto maintainer of OSIS. </div><div><br></div><div>Best regards,<u></u><u></u></div><div><br></div><div>David </div><div><br></div><div id="gmail-m_3675160690083512852gmail-m_-2606729850874945535gmail-m_-5427179157435549713gmail-m_7956110292232337925protonmail_mobile_signature_block"><div>Sent from ProtonMail Mobile</div></div> <div><br></div><div><br></div>On Mon, May 4, 2020 at 19:07, Michael H <<a href="mailto:cmahte@gmail.com">cmahte@gmail.com</a>> wrote:<blockquote type="cite"> <div dir="ltr"><div class="gmail_default" style="font-family:garamond,serif;font-size:large">I've got 40 works and growing that I've been meaning to look at creating Sword Modules. All of these are genbooks. Almost 100% currently are works by Andrew Murray (but the list is much bigger.) <br><br>But, as I try to make sense of the OSIS spec, I'm facing a 2006 spec in not very well done PDF, and another one with comments, and an xslt file, and a mountain of comments on the wiki that span from outright errors, to support gaps, to wishlist. <br><br>What is the status of OSIS? Is there a draft or official source, or even Crosswire source that we can at least fix typos to? I've started one, just to turn Appendix F into a real table... but as I read through the wiki, now it seems I'm going to have to process everything to be able to trust what I'm reading, and it makes sense that I should be dropping the result somewhere more official than my google drive. </div><div class="gmail_default" style="font-family:garamond,serif;font-size:large"><br>If we have permission to host the OSIS spec, do we have permission to bugfix it (at least the spelling gaps, and fixing the tables of information to be tabular?) </div></div>
</blockquote><div><br></div><div><br></div>_______________________________________________<br>
sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a><br>
<a href="http://www.crosswire.org/mailman/listinfo/sword-devel" rel="noreferrer">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
Instructions to unsubscribe/change your settings at above page</blockquote></div>
_______________________________________________<br>sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a><br><a href="http://www.crosswire.org/mailman/listinfo/sword-devel">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>Instructions to unsubscribe/change your settings at above page</div></blockquote></div><br></div></div>_______________________________________________<br>
sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a><br>
<a href="http://www.crosswire.org/mailman/listinfo/sword-devel" rel="noreferrer">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
Instructions to unsubscribe/change your settings at above page</blockquote></div>
</blockquote></div>
</blockquote><div><br></div><div><br></div>