[osis-core] Question and suggestion - RE: Draft of steps for creating a printed version of Luke

[Todd Tillinghast]

I gave myself a challenge Friday to see what sort of PDF I could
generated using FO (formatting objects), existing style sheets and OSIS
1.1.1 documents in an hour's time.  I was able to get a basic PDF
created without all of the bells and whistles like footnotes, the
copyright page, etc...

I have one suggestion and one scope question as a result of the effort.

SUGGESTION:  (Based on Thursday's conference call, there was consensus
that the target was PDF and that FO was the appropriate way to get there
from an OSIS 1.1.1 encoded document.)  I would like to suggest that we
manually create "proof" FO files that render to PDF the required
formatting before writing an XSL style sheet to generate FO from an OSIS
1.1.1 document.  Any problems in generating the PDF required will almost
certainly be due to a limitation in what can be expressed in FO and NOT
in an XSL style sheet's ability to generate the FO.  Also the approach
to the style sheet might be different based on any "tricks" that have to
be employed to get FO to do what we need it to do.

SCOPE QUESTION:  Is the objective to write a style sheet that will work
with any OSIS 1.1.1 encoded document, an OSIS 1.1.1 encoded document
that conforms to a set of encoding practices, OR just the encoding
developed for this effort?  (I don't think the first is possible.
Examples of "encoding practices" would be (a) only splitting <q>, <p>,
and <verse> and ignoring all milestoneStart/End pairs other than those
for verse and quotes, (b) putting the text to present for verse numbers
in the "n" attribute when osisID is a list, AND (c) using value(s) for
the "type" attribute of <div> and <p> elements that contain text other
than the Bible like introductions and teaching commentary.)

Thoughts?

Todd

-----Original Message-----
From: Mike Perez [mailto:mperez@forministry.com] 
Sent: Monday, December 09, 2002 7:04 AM
To: 'Todd Tillinghast'; osis-core@bibletechnologieswg.org;
deblois@zeelandnet.nl; Robert Hodgson; klowery@wts.edu; Adina Hamik;
John Walter
Subject: RE: Draft of steps for creating a printed version of Luke

This is a good start.  I've put names by the steps where I think the
person
who should have responsibility is obvious.

I didn't have access to my email on Thursday or Friday, so I'll be
responding to emails as I receive them.  I assume we will address markup
of
the TEV, KJV and RV as well (though perhaps that is someone besides
Todd).

Hope and pray all is well.

Mike

-----Original Message-----
From: Todd Tillinghast [mailto:todd@contentframeworks.com]
Sent: Thursday, December 05, 2002 12:27 PM
To: osis-core@bibletechnologieswg.org; Mike Perez;
deblois@zeelandnet.nl; Robert Hodgson; klowery@wts.edu; Adina Hamik;
John Walter
Subject: Draft of steps for creating a printed version of Luke


Steps for creating a printed version of Luke

1) Determine desired result
   A) Determine and acquire "model" printed texts - MIKE
   B) Document desired result - MIKE

2) Encode OSIS documents
   A) Determine quantifiable acceptance criteria and parties to accept
result - JOHN AND MIKE
   B) Acquire source texts 
      1) CEV as SFM - MIKE
      2) CEV as Word - MIKE
      3) Troy's Encoding of the CEV
      4) Images - MIKE
      5) Learning Bible specific content - MIKE

   C) Determine method and source text to use to encode OSIS documents 
   D) Plan sub tasks, estimate costs, assign work, and funding
   E) Encode OSIS documents for only Luke 1
   F) Review and Test encoding of Luke 1
   G) Encode OSIS documents for all of Luke
   H) Deliver OSIS encoded documents

3) Produce PDF documents 
   A) Determine quantifiable acceptance criteria and parties to accept
result - MIKE AND JOHN
   B) Estimate costs, assign work, and funding - JOHN AND STEVE
   C) Write style sheets to produce PDF from the documents delivered in
2.E
   D) Review and test PDF results
   E) Adjust style sheets to produce PDF from the documents delivered in
2.H
   F) Deliver PDF documents

Hope this helps get the ball rolling.

Todd