[osis-core] markup guidelines
Todd Tillinghast
osis-core@bibletechnologieswg.org
Mon, 2 Sep 2002 00:04:55 -0600
Troy,
I agree with you that it will be diffucult to write code or a style sheet
that will work for ANY style in which a document is encoded. I see your
point of wanting to put the quotes at the lowest level. I do think that it
make sense to put thing like <div>, <p>, <lg>, and <l> at a higher level
than <verse>. This of course coming from a perspective not simply trying to
get verses as a single string for each verse but intending to do some style
treatment based on the <p>, <lg>, etc... There will be a number of
prespectives.
It is easier to manually encode with the <q> on the outside in this case,
maybe I was lazy! But we can expect that from encoders in the future.
It seems to me that style sheets and the like will only work for documents
encoded in the style we expect. Unfortunate but true.
Todd
>
> Todd,
> But *practically* to you understand that if the user asks
> for Ps.1.1, it
> would be much easier to render to the user if the quote were in the node
> that was returned to me from a query for osisID Ps.1.1? Maybe you don't
> see it being harder. Not sure. But... Doesn't it also make sense that
> if you ask me to write out the text for Ps.1.1, I would include the
> quotation marks (and line breaks, if I was anal about it). Not sure.
> I'm just getting ready to write some real code against this spec and an
> dreading all the things I have to take into account for the most basic
> operations. I'm lucky enough to be preprocessing the docs into my own
> custom formats, so I can take care of these things, but just the
> preprocess these docs is going to be tough in many circumstances. But
> HEY, that's our life, right? And it only has to be written once.
> That's the beauty of OSIS-- at least once the whole starts using it
> tomorrow! :)
>
> -Troy.
>
>
>
> Todd Tillinghast wrote:
> > Troy,
> >
> > The quote is of Ps.1.1, Ps.1.2, and Ps.1.3. The quote mark
> would likely be
> > renderered after the numeral "1" marker, but in this case the
> opening <q>,
> > the opening <verse osisID="Ps.1.1"> and <lg splitID="LG-Ps.1-A"> are all
> > have no text between them and are at the same point in the
> text. I see the
> > <q> as being in one logical heirarchy, the (<div>, <lg>, and
> <l>) as being
> > in another logical heirarchy and the <verse> markers as being in a third
> > logical heirarchy. As a result it does not matter which of
> contains which.
> > I just put the <q> on the outside because it resulted in the least split
> > elements.
> >
> > Todd
> >
> >
> >>-----Original Message-----
> >>From: owner-osis-core@bibletechnologieswg.org
> >>[mailto:owner-osis-core@bibletechnologieswg.org]On Behalf Of Troy A.
> >>Griffitts
> >>Sent: Sunday, September 01, 2002 4:51 PM
> >>To: osis-core@bibletechnologieswg.org
> >>Subject: Re: [osis-core] markup guidelines
> >>
> >>
> >>Todd Tillinghast wrote:
> >>
> >>>A more recent example:
> >>
> >>...
> >>
> >>That's the example for which I was originally looking.
> >>
> >>Your alternalte still has quote OUTSIDE verse. It still seems to me
> >>that the <q> is 'in' Ps.1.1.
> >>
> >>
> >>
> >>
> >>
> >>>An alternative would be:
> >>><div osisID="Ps.1">
> >>> <title type="x-head">True Happiness</title>
> >>> <q type="x-blockQuote">
> >>> <verse osisID="Ps.1.1">
> >>> <lg splitID="LG-Ps.1-A">
> >>> <l>Happy are those</verse></l>
> >>> <l>who reject the advice of evil people,</l>
> >>> <l>who do not follow the example of
> >>
> >>sinners</l>
> >>
> >>> <l>or join those who have no use
> >>
> >>for God.</l>
> >>
> >>> </lg>
> >>> </verse>
> >>> <verse osisID="Ps.1.2">
> >>> <lg splitID="LG-Ps.1-A">
> >>> <l>Instead, they find joy in
> >>
> >>obeying the Law of the <divineName
> >>
> >>>type="yhwh">LORD</divineName>,</l>
> >>> <l>and they study it day and night.</l>
> >>> </lg>
> >>> </verse>
> >>> <verse osisID="Ps.1.3">
> >>> <lg splitID="LG-Ps.1-A">
> >>> <l><note type="x-xref"
> >>
> >>osisRef="Ps.1.3-Ps.1.3">
> >>
> >>> <note type="x-link">
> >>> <reference
> >>
> >>osisRef="Jer.17.8"/>
> >>
> >>> </note>
> >>> </note> They are like trees that
> >>
> >>grow beside a stream,</l>
> >>
> >>> <l>that bear fruit at the right time,</l>
> >>> <l>and whose leaves do not dry up.</l>
> >>> <l>They succeed in everything they do.</l>
> >>> </lg>
> >>> </verse>
> >>> </q>
> >>> .....
> >>></div>
> >>>
> >>>
> >>>Of course the other alternative is to use milestones for verse markers.
> >>>
> >>>Does this help?
> >>>
> >>>Does this still look troublesome to you?
> >>>
> >>>Todd
> >>>
> >>>
> >>>
> >>>>-----Original Message-----
> >>>>From: owner-osis-core@bibletechnologieswg.org
> >>>>[mailto:owner-osis-core@bibletechnologieswg.org]On Behalf Of Troy A.
> >>>>Griffitts
> >>>>Sent: Sunday, September 01, 2002 3:19 PM
> >>>>To: osis-core
> >>>>Subject: [osis-core] markup guidelines
> >>>>
> >>>>
> >>>>I know I'm gonna have to deal with ALL KINDS of markup to
> this standard,
> >>>>when I write code to handle OSIS, so I shouldn't complain about this,
> >>>>but... this isn't really the preferred way to markup osisIDs is it?
> >>>>
> >>>>old excerpt from Todd's example:
> >>>>
> >>>>
> >>>><lineGroup>
> >>>> <line>
> >>>> <verse osisID="Matt.13.14" segID="Matt.13.14@b"
> prev="Matt.13.14@a"
> >>>>next="Matt.13.14@c">This people will listen and listen, but not
> >>>>understand;</verse>
> >>>> </line>
> >>>> <line>
> >>>> <verse osisID="Matt.13.14" segID="Matt.13.14@c"
> >>>>prev="Matt.13.14@b">they will look and look, but not see,</verse>
> >>>> </line>
> >>>> <line>
> >>>> <verse osisID="Matt.13.15" segID="Matt.13.15@a"
> >>>>next="Matt.13.15@b">because their minds are dull,</verse>
> >>>> </line>
> >>>>
> >>>>...
> >>>>
> >>>></lineGroup>
> >>>>
> >>>>
> >>>>maybe I'm thinking of things differently from the rest, but doesn't it
> >>>>seem extraordinarily difficult to display 'Matt.13.14'?
> >>>>
> >>>>
> >>>>Shouldn't the <lineGroup> and <line> be considered 'in'
> Matt.13.14? It
> >>>>sure seems to make more sense to put the <lineGroup> inside
> the <verse>
> >>>>tag, and will make my life a while lot easier to process.
> >>>>
> >>>> -Troy.
> >>>>
> >>>>
> >>>
> >>
> >>
> >>
>
>
>
>