[sword-devel] Status of OSIS?

[Michael H]

David,

That page you refer to is the problem that created this email.

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.)

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.

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.



On Mon, May 4, 2020 at 1:25 PM David Haslam <dfhdfh at protonmail.com> wrote:

> Have you looked at our Wiki page?
>
> OSIS 211 CR
>
> It was even edited again today!
>
> The Bible Technologies Group has not met for years & the original website
> went AWOL.
>
> It may well be the case that CrossWire is the only remaining de facto
> maintainer of OSIS.
>
> Best regards,
>
> David
>
> Sent from ProtonMail Mobile
>
>
> On Mon, May 4, 2020 at 19:07, Michael H <cmahte at gmail.com> wrote:
>
> 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.)
>
> 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.
>
> 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.
>
> 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?)
>
>
>
> _______________________________________________
> sword-devel mailing list: sword-devel at crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.crosswire.org/pipermail/sword-devel/attachments/20200504/e3a5e28d/attachment.html>