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

[Mike Perez]

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