Loads of options for XML to JSON:Blessings,PeterOn Wednesday, November 21, 2018 at 11:01:49 AM UTC-8, Eric S. Wong wrote:@Ben, Oh so I just took a look at the link you sent me and XML is definitely prevalent. I must've misread but you meant that we convert the XML to JSON. Yeah there's got to be a way!On Wed, Nov 21, 2018 at 10:52 AM Eric S. Wong <erics...@gmail.com> wrote:Thank you for all the replies. I'm glad that you guys are active in this work.I'll take a look at the resources mentioned.@Peter, I'm not sure what you're saying. But the only source I found was on Ben's opensource javascripture. Other than that you guys mentioned some resources that I'm going to take a look at.@Ben, yeah if you can share with me the fork that would be great! Thank you for the link to you source. I'm not sure how crosswire's module works but it doesn't necessarily seem too bad if we just cross match strong's words with a Westminster Leningrad Codex for the Hebrew then something like a Codex Sinaiticus for Greek. That way we can have most if not all the words having a strong tag from our algorithm. From there we can cross check from a more accurately done file by human filter. Yeah we can definitely run a script to convert to JSON. I'm literally just using iOS's JavaCore Framework, changing your variable and using your whole file as a massive JSON import into my app lol!@All - Definitely make a slack, this would make the process a lot smoother. Setup is so fast... Hit us up and I'll join asap!On Wed, Nov 21, 2018 at 10:30 AM Jesse Griffin <jag...@gmail.com> wrote:Yes, this is a good place for that discussion Tahor.The Open Scriptures Hebrew Bible is tagged with Strong's numbers and has most of the forms parsed, you can download it from https://github.com/openscriptures/morphhb/releases .We'll have another release soon (maybe January time frame) with 100% of the forms parsed.Thank you,Jesse GriffinOn Wed, Nov 21, 2018 at 12:52 PM 'Tahor SuiJuris Ben' via Open Scriptures <openscr...@googlegroups.com> wrote:I need to create a database with both the original languages with English parallel including Strongs #.I am very hopeful that the data resources may prove a solution.Thank you Ben, shall view the github link you shared.My question actually was about a central discussion area, would the Open Scriptures Google groups be an appropriate place to discuss the data?Tahor SuiJuris Ben BerithYadah Yasha Ahayahh3034 h3467 h1961A MANDATORY verbal "confession" in sequence Colossians 3:17 / John 14:6)Proverbs 15:32Acts 17:26, 27 / Judges 2:3, 22• a TIME limit for all to SEEK •Deuteronomy 4:28, 29 / Isaiah 55:6, 7---------------------------------------------------------------------Electronic Privacy Notice. This e-mail, and any attachments, contains information that is, or may be, covered by electronic communications privacy laws, and is also confidential and proprietary in nature. If you are not the intended recipient, please be advised that you are legally prohibited from retaining, using, copying, distributing, or otherwise disclosing this information in any manner. Instead, please reply to the sender that you have received this communication in error, and then immediately delete it. Thank you in advance for your cooperation.---------------------------------------------------------------------‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐On Wednesday, November 21, 2018 9:11 AM, Ben Dwyer <b...@scruffian.com> wrote:The code for javascripture is open source, so anyone can access it here:On Wed, 21 Nov 2018 at 16:34, Peter Passchier <pe...@passchier.net> wrote:Why have these most important recources not been shared in a more accessible way..? It seems Christians in the past have tended towards proprietary solutions and formats, which is very sad. Let this be the generation to change this all, and make the word and crucial tools and utilities accessible as openly and freely as possible, so collaboration and access gets easier and more abundant.Blessings on you all,Peter
--You received this message because you are subscribed to the Google Groups "Open Scriptures" group.To unsubscribe from this group and stop receiving emails from it, send an email to openscripture...@googlegroups.com.To post to this group, send email to openscr...@googlegroups.com.Visit this group at https://groups.google.com/group/openscriptures.For more options, visit https://groups.google.com/d/optout.
--You received this message because you are subscribed to the Google Groups "Open Scriptures" group.To unsubscribe from this group and stop receiving emails from it, send an email to openscripture...@googlegroups.com.To post to this group, send email to openscr...@googlegroups.com.Visit this group at https://groups.google.com/group/openscriptures.For more options, visit https://groups.google.com/d/optout.
--You received this message because you are subscribed to the Google Groups "Open Scriptures" group.To unsubscribe from this group and stop receiving emails from it, send an email to openscripture...@googlegroups.com.To post to this group, send email to openscr...@googlegroups.com.Visit this group at https://groups.google.com/group/openscriptures.For more options, visit https://groups.google.com/d/optout.
--You received this message because you are subscribed to a topic in the Google Groups "Open Scriptures" group.To unsubscribe from this topic, visit https://groups.google.com/d/topic/openscriptures/_K_t1HcHG8A/unsubscribe.To unsubscribe from this group and all its topics, send an email to openscripture...@googlegroups.com.To post to this group, send email to openscr...@googlegroups.com.Visit this group at https://groups.google.com/group/openscriptures.For more options, visit https://groups.google.com/d/optout.---Eric Wong---Eric Wong
--You received this message because you are subscribed to the Google Groups "Open Scriptures" group.To unsubscribe from this group and stop receiving emails from it, send an email to openscripture...@googlegroups.com.To post to this group, send email to openscr...@googlegroups.com.Visit this group at https://groups.google.com/group/openscriptures.For more options, visit https://groups.google.com/d/optout.
Hi guys,
May I make a humble suggestion with regard to converting XML to JSON?
If you'd rather have a JSON structure as opposed to an XML structure, I don't think you will be served well by a blind conversion.
JSON alone doesn't capture well (if even sanely), all things from our (CrossWire / OSIS) documents. Here is a simple example of a few verses with words of Christ marked, and a few footnotes. I could come up with a much more difficult example which would include lemma and morphology tagging, along with poetry and paragraph, but I wanted to keep it simple for an example:
<div type="book" osisID="Matt">
...
<div type="chapter" osisID="Matt.4>
...
<verse osisID="Matt.4.18" n="18">
<title subType="x-preverse" type="section">The First Disciples</title> <note n="A" osisID="Matt.4.18.xref.A" type="crossReference"><reference osisRef="Matt.4.18-Matt.4.20">Matt 4:18-22: <hi type="italic">Mark 1:16-20</hi></reference>; <reference osisRef="Luke.5.2-Luke.5.11">Luke 5:2-11</reference>; <reference osisRef="John.1.40-John.1.42">John 1:40-42</reference></note>Now as Jesus was walking by <note n="B" osisID="Matt.4.18.xref.B" type="crossReference"><reference osisRef="Matt.15.29">Matt 15:29</reference>; <reference osisRef="Mark.7.31">Mark 7:31</reference>; <reference osisRef="Luke.5.1">Luke 5:1</reference>; <reference osisRef="John.6.1">John 6:1</reference></note> the Sea of Galilee, He saw two brothers, <note n="C" osisID="Matt.4.18.xref.C" type="crossReference"><reference osisRef="Matt.10.2">Matt 10:2</reference>; <reference osisRef="Matt.16.18">16:18</reference>; <reference osisRef="John.1.40-John.1.42">John 1:40-42</reference></note> Simon who was called Peter, and Andrew his brother, casting a net into the sea; for they were fishermen.
</verse>
<verse osisID="Matt.4.19" n="19">
<transChange type="tenseChange">And He said</transChange> to them, <q who="Jesus">“<note n="1" osisID="Matt.4.19.note.1" type="explanation">Lit <hi type="italic">Come here after Me</hi></note> Follow Me, and I will make you fishers of men.”</q>
</verse>
...
</chapter>
...
</div>
A straight XML to JSON conversion will change all the quotes and references within a verse to json properties, maybe split the verse up into an array of verses because the text segments are divided by these... I actually have no idea of any kind of sanity JSON alone would produce.
As I mentioned before, you probably just want the book chapter verse structer to be converted to JSON. All the other markup, you are better off leaving as XML within your JSON structure or changing to markdown or something else.
I know the cool kids these days like JSON, but for representing rich document markup, I am not sure how much sense this actually makes.
If easy verse retrieval is what you are after, you should be able to simply say something like:
$('verse [osisID=Matt.4.18]') to retrieve the content directly from the document... but I would suggest even that.
Our opensource tools allow you to do something like:
var book = SWORD.mgr.getModuleByName("NASB");
book.setKeyText("Matt.4.18");var verseHTML = book.getRenderText();
I hope this helps and might encourage you to investigate our free open-source tools and large library of resources.
Blessings and Happy Thanksgiving!!!
Troy
XML to JSON conversion will change all the quotes and references within a verse to json properties, maybe split the verse up into an array of verses because the text segments are divided by these... I actually have no idea of any kind of sanity JSON alone would produce
{ "chapter": 4, "verse": 19, "name": "Matthew 4:19", "text": "<w lemma=\"strong:G2532 lemma.TR:και\" morph=\"robinson:CONJ\" src=\"1\">And</w> <w lemma=\"strong:G3004 lemma.TR:λεγει\" morph=\"robinson:V-PAI-3S\" src=\"2\">he saith</w> <w lemma=\"strong:G846 lemma.TR:αυτοις\" morph=\"robinson:P-DPM\" src=\"3\">unto them</w>, <q marker=\"\" who=\"Jesus\"><w lemma=\"strong:G1205 lemma.TR:δευτε\" morph=\"robinson:V-XXM-2P\" src=\"4\">Follow</w> <w lemma=\"strong:G3694 lemma.TR:οπισω\" morph=\"robinson:ADV\" src=\"5\"/><w lemma=\"strong:G3450 lemma.TR:μου\" morph=\"robinson:P-1GS\" src=\"6\">me</w>, <w lemma=\"strong:G2532 lemma.TR:και\" morph=\"robinson:CONJ\" src=\"7\">and</w> <w lemma=\"strong:G4160 lemma.TR:ποιησω\" morph=\"robinson:V-FAI-1S\" src=\"8\">I will make</w> <w lemma=\"strong:G5209 lemma.TR:υμας\" morph=\"robinson:P-2AP\" src=\"9\">you</w> <w lemma=\"strong:G231 lemma.TR:αλιεις\" morph=\"robinson:N-APM\" src=\"10\">fishers</w> <w lemma=\"strong:G444 lemma.TR:ανθρωπων\" morph=\"robinson:N-GPM\" src=\"11\">of men</w>.</q>"}
{ "chapter": 4, "verse": 19, "name": "Matthew 4:19", "text": "And he saith unto them, Follow me, and I will make you fishers of men."}
--
Dear OpenScriptures,
Just a short note about CrossWire and what we do.
All software we write is open source.
We are NOT the authoritative source or copyright holder for any Biblical material (save a very few exceptions, e.g., the KJV2003 Project which we spearheaded to produce the first open and freely available KJV text with Strongs markup http://crosswire.org/sword/kjv2003/ )
CrossWire exists as a community of engineers who wish to come together and build free software to support Bible researchers, translators, missionaries, and other ministry organizations. We are a non-income organization.
The important point is that we are NOT a source for Bible texts themselves. We never hold an authoritative source of texts on our server (excluding a very few (one or two) as mentioned above).
Don't forget there is a difference between "storage format" and "markup format." A SWORD module is typically a compressed and index blob which can be used with our open source engine. That blob contains text which is marked up (often richly) in a number of different formats: OSIS, ThML, GBF, TEI are the major markup formats our engine supports. Our engine can get you the data for any verse and all the metadata associated with that verse and output that verse in a number of output formats we support: HTML/CSS, RTF, LaTeX.There is not 1 installation source for CrossWire modules. Our open source software engine supports autodiscovery of Remote Installation Repositories and we encourage publishers to host their own. Here is a helpful diagram of data flow at CrossWire:
http://crosswire.org/sword/develop/dataflow/
We try to ALWAYS list in our data module where we obtained the text and where we recommend anyone else obtain the text who wishes to use the same text outside of our community.
We don't want to discourage you from working outside of our community. We only wish to discourage you from using CrossWire as an authoritative data source for biblical material outside of our community, and it is only from good intentions. We have already converted the material from the authoritative source and often reconvert the material when we find errors in our tools or when the authoritative source makes an update. We don't wish to encourage a conversion to another format from our conversion of the authoritative format.
Again, we don't with to discourage you from working outside our community. You are always welcome to share with us, or do your own thing, but please don't consider our project a data source of biblical material. That is not our purpose and our desire for you to not use our converted data isn't because we are selfish. It is because we don't want to propagate conversion errors we may have made and we don't want to BECOME or BE SEEN as an authoritative data source of biblical material. We are not. You should contact the publishers of you wish to use their text directly and gain their permission, if they require it. You are welcome to use our module library as a means to find all those sources. We try to make that easy for other projects by including a "Source=" entry in each module's .conf file.
Finally, there are other projects who may consider themselves as a source for biblical material. Please see Michael Johnson's great work at https://ebible.org/download.php
Sharing in Christ's work,
Troy
Copyright © Vast Development Method | Terms of Service | Privacy Policy | Company
Copyright © Vast Development Method | Terms of Service | Privacy Policy | Company--
You received this message because you are subscribed to the Google Groups "Open Scriptures" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openscripture...@googlegroups.com.
To post to this group, send email to openscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/openscriptures.
For more options, visit https://groups.google.com/d/optout.
Aloha,
Michael Johnson
PO BOX 881143 • PUKALANI HI 96788-1143 • USA
mljohnson.org • Phone: +1
808-333-6921 • Skype: kahunapule
Copyright © Vast Development Method | Terms of Service | Privacy Policy | Company
--
--
You received this message because you are subscribed to the Google Groups "Open Scriptures" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openscripture...@googlegroups.com.
To post to this group, send email to openscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/openscriptures.
To view this discussion on the web visit https://groups.google.com/d/msgid/openscriptures/9ea5a0e938777ac155d9bc34ad06e1640b6682a4.camel%40gmx.net.