[osis-core] OSIS_0105:18 Pointers on milestones, other

[Troy A. Griffitts]

Patrick Durusau wrote:
> 
> Troy,
> 
> Troy A. Griffitts wrote:
> 
> >New cut at the bottom...
> >
> 
> >
> >I would think the link would go the other way: commentary -> Bible
> >
> >Is it normal to have an attribute called the same as its element?  might
> >we remove VerseStart and keep reference?  It might be easier to write
> >code if we have the same attribute for all these type of milestone tags:
> ><chapterStart /> <verseStart /> <bookStart /> <chapterEnd /> <verseEnd
> >/> <bookEnd />
> >
> Comments on reference, referenceEnd for all milestones and other
> attachments?



><bookStart ID="John" />
>  <chapterStart ID="John.1" />
>    <verseStart ID="John.1.1" />
>      <w ID="John.1.1.1">In</w>
>       ...
>    <verseEnd refID="John.1.1" />
>  <chapterEnd refID="John.1" />
><bookEnd refID="John" />


Actually, something like the above is for what I was hoping.

Same 'ID', 'refID' on each milestone.

Now, I don't care if it's ID/refID, or reference/referenceEnd, just
didn't care for VerseStart/refVerseEnd, ChapterStart/refChapterEnd,
etc., for the same function.  I think it will trim our attribute number
down, along with our learning curve.  And I KNOW Patrick's goal is to
have less elements/attributes!


> Actually I like the implied semantics (makes it clear that it is
> referring to something else) and as Troy points out, has advantages for
> coding.

Now that I've expounded, were we still liking the same thing?


> A psychological or moral weakness is one you don't suffer from! ;-)

You have twisted but strangely clever sense of humor ;)