[osis-core] Should we allow <divineName> in <catchWord>
Wed, 14 May 2003 09:56:44 -0600
You accurately represented the issue.
<catchWork> only exists as a child of <note>, so there should be no
problem in determining context.
> -----Original Message-----
> From: firstname.lastname@example.org [mailto:osis-core-
> email@example.com] On Behalf Of Patrick Durusau
> Sent: Wednesday, May 14, 2003 4:13 AM
> To: firstname.lastname@example.org
> Subject: Re: [osis-core] Should we allow <divineName> in <catchWord>
> Chris Little wrote:
> >On Tue, 13 May 2003, Patrick Durusau wrote:
> >I actually see a problem with not allowing <divineName> inside of
> ><catchWord>. As I recall, we added <divineName> largely to indicate
> >meaning behind small caps rendering of Lord, etc. If Lord occurs as
> >of <catchWord> text, currently it either cannot indicate that it
> >rendered with small caps or it would need to do so through some
> >non-standard method, like <seg type="divineName">, which would make
> >creating generalized style-sheets more difficult.
> Yes, but what do you think about duplicate search "hits" for
> <divineName> in the text as well as in the <catchWord>? Offer a search
> option to exclude/include <note> (the most likely place for
> to appear)?
> Will create an issues list, this one being:
> Add <divineName> to <catchWord>. Reason: To capture styling for
> <divineName> in <catchWord>. Use of non-standard <seg> with attribute
> will complicate stylesheets, as well as lead to inconsistent encoding.
> Does that capture the issue?
> Hope everyone is at the start of a great day!
> Patrick Durusau
> Director of Research and Development
> Society of Biblical Literature
> Co-Editor, ISO 13250, Topic Maps -- Reference Model
> osis-core mailing list