Hello,<br><br>It looks like Xindice doesn't work as well with documents up to or over 5 MB. I would imagine uncompressed OSIS Bible text would be at least that large. Also, I wonder how well XPath would work very well with the OSIS format.
<br><br>-Bill<br><br><div><span class="gmail_quote">On 11/7/06, <b class="gmail_sendername">Martin Gruner</b> <<a href="mailto:mg.pub@gmx.net" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">mg.pub@gmx.net
</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
This sounds very interesting. Is there something similar for C++?<br><br>mg<br><br>Am Dienstag, 7. November 2006 20:24 schrieb Yiguang Hu:<br>> If you have to think of other repository than sword<br>> module, how about xindice. It stores XML directly and
<br>> you can access the data using XPATH. Sure xindice is<br>> young also.<br>><br>> <a href="http://xml.apache.org/xindice/" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://xml.apache.org/xindice/
</a><br>><br>> --- <a href="mailto:sword-devel-request@crosswire.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
sword-devel-request@crosswire.org</a> wrote:<br>> > Send sword-devel mailing list submissions to<br>> > <a href="mailto:sword-devel@crosswire.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
sword-devel@crosswire.org</a><br>> ><br>> > To subscribe or unsubscribe via the World Wide Web,
<br>> > visit<br>><br>> <a href="http://www.crosswire.org/mailman/listinfo/sword-devel" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://www.crosswire.org/mailman/listinfo/sword-devel
</a><br>><br>> > or, via email, send a message with subject or body
<br>> > 'help' to<br>> > <a href="mailto:sword-devel-request@crosswire.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">sword-devel-request@crosswire.org</a><br>> ><br>> > You can reach the person managing the list at
<br>> > <a href="mailto:sword-devel-owner@crosswire.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
sword-devel-owner@crosswire.org</a><br>> ><br>> > When replying, please edit your Subject line so it<br>> > is more specific<br>> > than "Re: Contents of sword-devel digest..."<br>> >
<br>> ><br>> > Today's Topics:<br>> ><br>> > 1. Re: modules to relational database (Gabriel M.<br>> > Beddingfield)<br>><br>> ----------------------------------------------------------------------
<br>><br>> > Message: 1<br>> > Date: Tue, 7 Nov 2006 12:27:57 -0600 (CST)<br>> > From: "Gabriel M. Beddingfield" <<a href="mailto:gabriel@teuton.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
gabriel@teuton.org</a>><br>> > Subject: Re: [sword-devel] modules to relational
<br>> > database<br>> > To: "SWORD Developers' Collaboration Forum"<br>> > <<a href="mailto:sword-devel@crosswire.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
sword-devel@crosswire.org</a>><br>> > Message-ID:<br>><br>
> <<a href="mailto:1539.65.197.90.190.1162924077.squirrel@www.teuton.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">1539.65.197.90.190.1162924077.squirrel@www.teuton.org</a>><br>>
<br>> > Content-Type: text/plain;charset=iso-8859-1<br>> ><br>
> > > You can split up any XML document at its nodes<br>> ><br>> > like <osisID>, <div> etc.<br>> ><br>> > > into<br>> > > rows of a database that also holds the rendering
<br>> ><br>> > context for each of these<br>> ><br>> > > nodes, and also information about the tree<br>> ><br>> > structure of the xml document<br>> ><br>> > > (parent-children etc.). How deep you want to split
<br>> ><br>> > it beyond osisID<br>> ><br>> > > depends<br>> > > on what you want to do.<br>> > ><br>> > >From what I've seen, a lot (maybe most) of the<br>> ><br>
> > "serious" bible texts have<br>> > structured their documents like you would a book,<br>> > and then littered it<br>> > with "milestones" to mark where chapters and verses<br>
> > begin. E.g.<br>> ><br>> > <!-- my aplologies for butchering ThML --><br>> > <p><br>> > <ScripRef verse='Gen 1:1' />In the beginning, God<br>> > created<br>> > the heavens and the earth. <ScripRef verse='Gen
<br>> > 1:2' /><br>> > And the earth was shapeless and void...<br>> > </p><br>> ><br>> > On the one hand, you can store the XML document in a<br>> > relational database<br>> > as an XML document... preserving each tag, location,
<br>> > attributes, etc. On<br>> > the other hand, I would expect someone (like me or<br>> > the OP) to try and<br>> > divide things up by Book/Chapter/Verse:<br>><br>> +------+----+-------+---------------------------------------+
<br>><br>> > | Book | Ch | Verse | Text<br>><br>> +------+----+-------+---------------------------------------+<br>><br>> > | Gen | 1 | 1 | In the beginning, God created<br>> ><br>> > the |
<br>> ><br>> > | | | | heavens and the earth.<br>><br>> +------+----+-------+---------------------------------------+<br>><br>> > | Gen | 1 | 2 | And the earth was shapeless
<br>
> ><br>> > and |<br>> ><br>> > | | | | void...<br>><br>> +------+----+-------+---------------------------------------+<br>><br>> > To be clear on what I'm getting at... IMHO, I just
<br>> > don't think there's a<br>> > large advantage to converting a module to a RDMS.<br>> > If you preserve the<br>> > original document (OSIS, ThML, etc.)... why not just<br>> > leave it in OSIS,
<br>> > ThML, etc.? If you redo the schema to the RDMS, I<br>> > think you'll end up<br>> > with a lot of headaches that the XML/SGML schemas<br>> > solve well. I can be<br>> > convinced otherwise (after all, I really do love
<br>> > RDMS's)... but this is<br>> > how I see it.<br>> ><br>> ><br>> > --<br>> > G a b r i e l M B e d d i n g f i<br>> > e l d<br></blockquote></div>