[jsword-devel] osis and jaxb

[Troy A. Griffitts]

Hey guys, I sent your xslt to the osis-core team for comments, you might 
get some useful feedback from them.  You can follow the archive at:

http://www.crosswire.org/pipermail/osis-core/

We'll also approve any useful replies you might send to 
osis-core@bibletechnologieswg.org so feel free to post.


Eric Galluzzo wrote:
> On Sun, 2003-01-05 at 04:59, Joe Walker wrote:
> 
>>>Sounds reasonable, although I usually distrust autogenerated bindings
>>>(or autogenerated anything else) until I've seen how good they are. :)
>>>
>>
>>The good thing about jaxb is that you can give the schema compiler a 
>>binding customization document. So we ought to be able to get just what 
>>we want.
> 
> 
> Fair enough; that sounds great.
> 
> Have you thought about using something more lightweight, like Digester
> from Jakarta Commons (http://jakarta.apache.org/commons/digester.html)? 
> I have no idea which is actually better suited to this task; I just
> thought I'd bring up the alternative in case you had not considered it.
> 
> 
>>Yes, although in this case I hope we don't need much in the way of 
>>business methods. The point of using OSIS is very much data based - to 
>>allow the bits of code that know about generating textual data to pass 
>>it on to the bits of code that know how to display it.
>>So I guess the most likely things we would want to add would be 
>>something along the lines of "merge the contents of these 2 documents" 
>>(although there is a better way of doing even that). I wouldn't mind 
>>having a utility class for that sort of thing.
> 
> 
> OK; that sounds reasonable.  I suppose there are always ways around it
> if we do end up needing to add those methods (e.g. autogenerating
> interfaces).
> 
> 
>>>Also, I've got a work-in-progress stylesheet
>>>to convert OSIS to HTML for viewing (requires a Xalan-specific extension
>>>in order to break long documents up). [snip]
>>>
>>
>>Very interested.
> 
> 
> A zip file containing the XSLT stylesheet (html.xsl), an accompanying
> CSS stylesheet (osis.css), and a shell script to generate HTML
> (bin/generate) is attached.  (Sorry, I haven't made an Ant script yet.) 
> Note that this stylesheet currently only works for Bibles and lexicons. 
> It should also theoretically work for dictionaries and morphologies, but
> I haven't tried it.  It definitely does not work for general works like
> the Summa Theologica, but I'm working on that. :)  In addition, you will
> need to download Xalan 2.4 from http://xml.apache.org/xalan-j/ and put
> the xalan.jar and xercesImpl.jar in a lib/ directory inside the
> osis-xslt/ directory before running the generate script.
> 
> 
>>In theory all I need to do to enable OSIS support is to 
>>make the various modules create jaxb generate OSIS trees rather than my 
>>hand-written version of the same. And from what I have glanced at so far 
>>there is a virtually 1-1 corresponsance between the two.
> 
> 
> That's great!
> 
> 
>>However I'm working on polishing off Dict/Conc support which is more 
>>important so I'm not going to do anything with it for a few days.
> 
> 
> Fair enough.
> 
> Is there any area that I could help out with?  I don't have a huge
> amount of free time, but I'm sure I could help out with some small stuff
> to get started, at least. :)
> 
>     - Eric