[osis-core] Should we allow <divineName> in <catchWord>
Tue, 13 May 2003 06:29:57 -0600
<catchWord> has been pretty difficult to work with. I think we should
either include all of the options available in normal text OR make
catchWord have only a sequence of one or more <reference> elements that
refer to the current document AND use the grain. Multiple <reference>
elements would be used if there are ellipsis are desired.
> -----Original Message-----
> From: firstname.lastname@example.org [mailto:osis-core-
> email@example.com] On Behalf Of Patrick Durusau
> Sent: Tuesday, May 13, 2003 4:33 AM
> To: firstname.lastname@example.org
> Subject: Re: [osis-core] Should we allow <divineName> in <catchWord>
> Todd Tillinghast wrote:
> >Currently <catchword> does not allow <divineName> as a child. I have
> >case where LORD is a part of a <catchWord>.
> >Should we add <divineName> as a child of <catchword>.
> Not sure why you would want to add <divineName> to <catchword>.
> Tis true that the <divineName> occurs in the catchword but probably
> that every other structure could possibly occur there as well, at
> if you consider what is in the main text. The question to me revolves
> around what you consider to be the function of the <catchword>
> I see it as capturing the text string that appears in the main text as
> prompt to the reader, an implied hyperlink if you like, as to what is
> being discussed. It is not meant to represent the structure of the
> that appears in the main text.
> Is the problem one of display? Actually <catchWord> lacks <hi>, which
> think would be the better candidate to add to <catchWord> for such
> (current content model is: a <cid:email@example.com>
> abbr <cid:firstname.lastname@example.org> foreign
> <cid:email@example.com> index
> <cid:firstname.lastname@example.org> note
> <cid:email@example.com> reference
> <cid:firstname.lastname@example.org> seg
> <cid:email@example.com> w
> >See the footnote of CEV 1Kgs.8.62.
> >osis-core mailing list
> Patrick Durusau
> Director of Research and Development
> Society of Biblical Literature
> Co-Editor, ISO 13250, Topic Maps -- Reference Model