search

openscriptures / morphhb

Open Scriptures Hebrew Bible
https://hb.openscriptures.org
Other
178 stars 64 forks source link

BibleTechnologies.net #45

Open DavidHaslam opened 6 years ago

DavidHaslam commented 6 years ago

The BibleTechnologies website went AWOL several weeks ago.

This was the home for the official OSIS 2.1.1 XML schema.

Does anyone know what happened or whom to contact?

btw. I've asked Steve DeRose if he could find out, but as yet he's not been successful.

DavidTroidl commented 6 years ago

This has been MIA for some time now. It happened once before, hence the repo at ebible.org. I have been validating by hand, with a local copy of the XSD. You might try osis-users@crosswire.org, if you can get any response.

DavidHaslam commented 6 years ago

I sent a message.

It awaits admin moderation as I'm not a registered list member.

DavidHaslam commented 6 years ago

Meanwhile, you can validate to any of those listed here:

https://crosswire.org/wiki/OSIS_211_CR#CrossWire_updated_schema

The .xsd files available include:

JohnnyErnest commented 3 years ago

In C# when trying to run SelectNodes(string xpath) on an XmlDocument node it expects a valid xsd to run any XPath queries i.e. “//chapter” to query all nodes with a chapter tag, otherwise they return null. The XML files in the wlc directory need to be updated to reflect the new path to osisCore.2.2.1-orig.xsd since it looks like they still point to the old site. The workaround was that I could still navigate by ChildNodes, but just wanted to let you know that you may want to update the XML files to reflect the path change.

e.g. In 1Chr.xml it still reads:

<osis xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.bibletechnologies.net/2003/OSIS/namespace" xsi:schemaLocation="http://www.bibletechnologies.net/2003/OSIS/namespace http://www.bibletechnologies.net/osisCore.2.1.1.xsd"&gt;

I’ve been working on converting the WLC and Strong’s dictionaries in JSON/XML over to Excel xslx format and Microsoft SQL Server as well as SQLite perhaps for various analytics and a nice tabular format that’s readily SQL queryable.

DavidTroidl commented 3 years ago

I'm looking into a possible resolution.