[osis-core] osis1.1 about to leave the station!
Kees F. de Blois
osis-core@bibletechnologieswg.org
Wed, 18 Sep 2002 11:59:37 +0200
Todd,
Yes, except for the first line of Ps.2.7.
Why do you let the splitD "Q-Ps.2.7-A" begin in the first line of vs 7,
as attribute for 'what the LORD has declared', since the nested quote
has not yet begun?
Kees
> -----Original Message-----
> From: owner-osis-core@bibletechnologieswg.org
> [mailto:owner-osis-core@bibletechnologieswg.org] On Behalf Of
> Todd Tillinghast
> Sent: 17 September 2002 22:04
> To: osis-core@bibletechnologieswg.org
> Subject: RE: [osis-core] osis1.1 about to leave the station!
>
>
> Kees,
>
> Let me know if the previous two posts clear up your questions
> related to how to encode Matt.13.
>
> Todd
>
> > -----Original Message-----
> > From: owner-osis-core@bibletechnologieswg.org [mailto:owner-osis-
> > core@bibletechnologieswg.org] On Behalf Of Kees F. de Blois
> > Sent: Tuesday, September 17, 2002 2:35 AM
> > To: osis-core@bibletechnologieswg.org
> > Subject: RE: [osis-core] osis1.1 about to leave the station!
> >
> > Thanks, Todd, but I still need help. Is it possible to provide
> examples
> > of OSIS-encoded text representing the various possibilities
> listed in
> > your message. I thought I had understood the markup of MAT
> 13 in the
> > previous encoding, but when I compare that with Ps 1:1 and Ps 2:7, I
> get
> > confused.
> > Sorry,
> >
> > Kees
> >
> > > -----Original Message-----
> > > From: owner-osis-core@bibletechnologieswg.org
> > > [mailto:owner-osis-core@bibletechnologieswg.org] On
> Behalf Of Todd
> > > Tillinghast
> > > Sent: 16 September 2002 19:09
> > > To: osis-core@bibletechnologieswg.org
> > > Cc: Nathan Miles
> > > Subject: RE: [osis-core] osis1.1 about to leave the station!
> > >
> > >
> > > Kees and Nathan,
> > >
> > > > Todd,
> > > >
> > > > Another question from Nathan re. the Psalm 2 example:
> > > >
> > > > "I don't really understand these examples.
> > > >
> > > > If osisID always equals splitID why are they both present. If
> they
> > > are
> > > > Sometimes different where is there an example of this and
> > > what does it
> > > > mean when they are different.
> > >
> > > It is possible (common) to have elements that don't have osisIDs
> > > that are split. Examples would be quotes, paragraphs, and
> > > divisions. As a result to have a consistent strategy for
> handling
> > > split elements the splitID is used.
> > >
> > > It is also possible for two elements to have the same
> osisID and NOT
> > > be a split element!
> > >
> > > As a result, osisID and splitID will not always be the same. The
> > > encoder is free to use whatever value they choose as
> splitIDs. The
> > > rule is that when an element is split due to overlapping
> hierarchies
> > > that the splitID attribute will be the same value for all of the
> > > split fragments and unique from all other split elements.
> > >
> > > I chose to use the same value as the osisID for the
> splitID WHEN the
> > > osisID is a single identifier and the element is a verse. If the
> > > osisID were to be multiple, space separated identifiers
> then I would
> > > choose the first identifier.
> > >
> > > In Ps.2 you will as see split quotes. In these cases I used
> > > splitID="Q-Ps..2.7-A". The leading "Q-" makes the quote
> unique from
> > > other split elements and the trailing "-A" and "-B" make the two
> > > nested quotes that start in the same verse unique from each other.
> > >
> > > Bible.TEV:Matt.13 is the perfect text to demonstrate
> split elements.
> > > I have encoded it for prior schema versions but haven't
> updated it
> > > for the current version. I am also interested in seeing
> Isaiah 52
> > > and 53 encoded due to the "single discourse" from Isaiah
> > > 52:12-Isaiah 53:12 that spans chapters. (This is the
> example that
> > > Kees pointed out
> > > earlier.) This should result in either a split chapter
> or a split
> > > "section". What would be even more interesting would be
> an entire
> > > "Modern" translation encoded with all of the notes,
> figures, cross
> > > references, etc..!
> > >
> > > I hope this helps clear things up. Let me know if this
> leaves you
> > > more confused or you have more questions.
> > >
> > > Todd
> > >
> > > >
> > > > Also there are two <verse> elements with id "Ps.2.2" I
> > > would have thot
> > > > it would be illegal for two elements to have the same
> Id since the
> > > main
> > > > purpose of an Id (I would have thot) is to have a unique way of
> > > refering
> > > > to an element."
> > > >
> > > >
> > > > Kees
> > > >
> > > >
> > > > > -----Original Message-----
> > > > > From: owner-osis-core@bibletechnologieswg.org
> > > > > [mailto:owner-osis-core@bibletechnologieswg.org] On
> > > Behalf Of Todd
> > > > > Tillinghast
> > > > > Sent: 03 September 2002 05:38
> > > > > To: osis-core@bibletechnologieswg.org
> > > > > Subject: RE: [osis-core] osis1.1 about to leave the station!
> > > > >
> > > > >
> > > > > No arguments with the current schema. Let's release it.
> > > > >
> > > > > I think we should trim the elements we put global
> > > attributes on as a
> > > > > refinement to the model in the future, particularly
> > > elements in the
> > > > > header.
> > > > >
> > > > > Attached is a sample doc of Ps.1, Ps.2, Ps.3, and Matt.1.
> > > > >
> > > > > Todd
> > > > >
> > > > > > Guys,
> > > > > >
> > > > > > Final version attached.
> > > > > >
> > > > > > If you see obvious typos, send a note with the typo only. Or
> > > > > completely
> > > > > > inconsistent text (I will read one more time before sending
> > > > > to the ABS
> > > > > > for posting so hopefully I will notice any completely wrong
> > > > > names but
> > > > > > don't count on it.
> > > > > >
> > > > > > If you think more examples or illustrations are needed,
> > > > > great, write
> > > > > > them up as HTML pages and we can post them to the website.
> > > > > >
> > > > > > Starting on the linguistic model in Philly later
> this week so
> > > enjoy
> > > > > the
> > > > > > short break. ;-)
> > > > > >
> > > > > > Could not have done it at all without you guys!
> > > > > >
> > > > > > Thanks seems so inadequte but thanks anyway!
> > > > > >
> > > > > > Patrick
> > > > > >
> > > > > > --
> > > > > > Patrick Durusau
> > > > > > Director of Research and Development
> > > > > > Society of Biblical Literature
> > > > > > pdurusau@emory.edu
> > > > >
> > > > >
> > > >
> > >
> > >
> > >
> >
>
>
>