2 ms·
This specific API doesn’t attempt to handle any of the even vaguely interesting problems like versification translation or footnotes, or even more basic things
by chrismorgan 5y ago
This specific API doesn’t attempt to handle any of the even vaguely interesting problems like versification translation or footnotes, or even more basic things like where paragraph breaks lie. Instead, it’s just verse-per-line stuff loaded into a relational database of four tables: verse ∈ chapter ∈ book ∈ translation, all indexed by auto-generated IDs rather than anything sane, leading to a supremely awkward and remarkably inefficient ID-based REST API that’s unreliable to boot. I’m afraid the more I look at it the more I say it’s simply bad, having been implemented rather than designed, so that it’s unfortunately just about useless for any actual purpose.