[osis-core] Esth. corrected

[Todd Tillinghast]

Chris,

I am not saying that the KJV will not require milestones but only having
two overlapping hierarchies (BCV and quotes) rather than three (BSP,
BCV, and quotes) does make it a little simpler.

I have some experience in helping _newbies_ encode OSIS documents (one
training class in TX and one in the UK) and people did not struggle with
using <chapter> and <verse> milestones.  

I think the first thing we show users should be two examples:
1) Book/section/paragraph: This should include <chapter> and <verse>
milestones and containers for books, sections, and paragraphs.

2) Book/chapter/verse:  This example should be of a translation that
does not include sections and paragraphs as they must be encoded in the
style of the first example, if quotes that cross chapter and/or verse
containers are present they should be encoded as milestones.

With these two examples we should make the reader aware that they must
use the style of example #1 if sections and paragraphs are present in
the encoding.

If we don't present the overlapping markup issue at the very first, it
will only make things much harder for people later on.

Todd

> -----Original Message-----
> From: osis-core-admin@bibletechnologieswg.org [mailto:osis-core-
> admin@bibletechnologieswg.org] On Behalf Of Chris Little
> Sent: Monday, November 03, 2003 4:05 PM
> To: osis-core@bibletechnologieswg.org
> Subject: Re: [osis-core] Esth. corrected
> 
> Todd,
> 
> It sounds like you're advocating using milestones everywhere all of
the
> time, at least for <verse>.  If that were our desire, why would we
have
> included <verse> as a container at all?
> 
> The KJV is every bit as complex as any other Bible in terms of its
> needing milestones to mark structures such as quotations, which will
> cross verse boundaries.  But the real issue here is to make the
example
> as simple as humanly possible.  To that end, I think it should be
> limited to containers.  From that point, the manual can build more
> complicated structures and detail to the user why to use milestones
> instead of containers in certain circumstances, etc.
> 
> --Chris
> 
> Todd Tillinghast wrote:
> 
> >Chris and Patrick,
> >
> >I think we would be doing a disservice to the newbies if we were to
take
> >out the milestones.  Better to start them off right and not have to
> >relearn later.  Most real Bible's other than the KJV will require the
> >use of milestones?
> >
> >Let's show them a real but simple example.
> >
> >Todd
> >
> >
> >
> >>-----Original Message-----
> >>From: osis-core-admin@bibletechnologieswg.org [mailto:osis-core-
> >>admin@bibletechnologieswg.org] On Behalf Of Chris Little
> >>Sent: Sunday, November 02, 2003 12:17 PM
> >>To: osis-core@bibletechnologieswg.org
> >>Subject: Re: [osis-core] Esth. corrected
> >>
> >>Patrick,
> >>
> >>Why not just use container markup for the <verse>'s instead of the
> >>milestones (to avoid scaring the newbies).  I'd also recommend
> >>
> >>
> >stripping
> >
> >
> >>out anything that uses the attribute extension mechanism
> >>
> >>
> >(x-copyright).
> >
> >
> >>If we're giving it in our "minimal" example, it implies we omitted
> >>something very basic.
> >>
> >>--Chris
> >>
> >>Patrick Durusau wrote:
> >>
> >>
> 
> 
> 
> _______________________________________________
> osis-core mailing list
> osis-core@bibletechnologieswg.org
> http://www.bibletechnologieswg.org/mailman/listinfo/osis-core