[osis-core] <catchWord> can't be a child of <div>
Patrick Durusau
osis-core@bibletechnologieswg.org
Wed, 01 Oct 2003 10:01:48 -0400
Todd,
OK, but then the question is: Do you agree with Chris's suggestion that
you wrap your material in a <p>?
Hope you are having a great day!
Patrick
Todd Tillinghast wrote:
> Patrick,
>
> You are correct about the usage as a decendant of <note>. As Chris
> pointed out we also agreed that <catchWord> would be used in an
> "annotation" where the text of the "annotated" text was being "quoted".
> The behavior is pretty much the same as in <note> but it is related to
> the text referred to by annotateRef.
>
> Todd
>
>
>>-----Original Message-----
>>From: osis-core-admin@bibletechnologieswg.org [mailto:osis-core-
>>admin@bibletechnologieswg.org] On Behalf Of Patrick Durusau
>>Sent: Tuesday, September 30, 2003 2:02 PM
>>To: osis-core@bibletechnologieswg.org
>>Subject: Re: [osis-core] <catchWord> can't be a child of <div>
>>
>>Todd,
>>
>>Todd Tillinghast wrote:
>>
>>>Patrick,
>>>
>>>We said that we would use <catchWord> in cases where the text being
>>>"annotated" was "quoted" and that the reference on <catchWord> would
>>>have to be contained by one of the references in annotateRef.
>>>
>>
>>I think we understand the semantics of <catchWord> differently. It is
>>true that the text being "annotated" is being "quoted" in your
>
> examples
>
>>but that is only one condition for something being a <catchWord>. You
>>could easily extend the argument to make every quotation in a
>>commentary, say one that includes the biblical text to make them
>><catchWord>s.
>>
>>What distinguishes the cases, to me at any rate, is that a <catchWord>
>>appears in a <note> or a <p> in a <note>. In running text it is just a
>>quote.
>>
>>Is there some disadvantage that I am not seeing to treating it as a
>
> quote?
>
>>Hope you are having a great day!
>>
>>Patrick
>>
>>
>>
>>
>>>In the case I used as an example each verse is individually treated
>>
> by
>
>>>one or two sentences in most cases. The use of the annotateRef
>>>attribute at the level of granularity of the text seem obvious (an
>>>annotateRef for each element that contains the annotation of the
>>>individual verse). I choose to use <div> as the containing element
>>>because these are not necessarily paragraphs and the use of
>>>type="commentary" also seems appropriate and was not available on
>>
> <p>.
>
>>>As a result I ended up with <catchWord> as a direct child of <div>.
>>>
>>>Do you think I should have encoded this text differently?
>>>
>>>Todd
>>>
>>>
>>>
>>>>-----Original Message-----
>>>>From: osis-core-admin@bibletechnologieswg.org [mailto:osis-core-
>>>>admin@bibletechnologieswg.org] On Behalf Of Patrick Durusau
>>>>Sent: Monday, September 29, 2003 5:46 PM
>>>>To: osis-core@bibletechnologieswg.org
>>>>Subject: Re: [osis-core] <catchWord> can't be a child of <div>
>>>>
>>>>Todd,
>>>>
>>>>Why are you using <catchWord> here? The element is designed for use
>>>>primarily in notes or paragraphs in notes where there is a word or
>>>>phrase from the text to which the note applies.
>>>>
>>>>Look at the NSRV, Amos 1:1 and the note that is listed as 1.1-2, it
>>>
>>>has
>>>
>>>
>>>>"The words of Amos," "Uzziah," "Jeroboam," and "two years before the
>>>>earthquake" set off in italics. Those are catchwords that direct the
>>>>reader to a part of that verse.
>>>>
>>>>What you have here looks like a quote to me.
>>>>
>>>>Hope you are having a great day!
>>>>
>>>>Patrick
>>>>
>>>>Todd Tillinghast wrote:
>>>>
>>>>
>>>>>Patrick,
>>>>>
>>>>>In the following commentary is not legal:
>>>>><div type="commentary" annotateRef="1Tim.1.1"><catchWord
>>>>>osisRef="1Tim.1.1@s[Paul]">Paul an apostle</catchWord> -
>>>>
> Familiarity
>
>>>is
>>>
>>>
>>>>>to be set aside where the things of God are concerned. According
>>>>
> to
>
>>>the
>>>
>>>
>>>>>commandment of God - The authoritative appointment of God the
>>>>
>>>Father.
>>>
>>>
>>>>>Our Saviour - So styled in many other places likewise, as being the
>>>>>grand orderer of the whole scheme of our salvation. And Christ our
>>>>
>>>hope
>>>
>>>
>>>>>- That is, the author, object, and ground, of all our hope.</div>
>>>>>
>>>>>
>>>>>I don't think we should force the addition of a <p> element.
>>>>><div type="commentary" annotateRef="1Tim.1.1"><p><catchWord
>>>>>osisRef="1Tim.1.1@s[Paul]">Paul an apostle</catchWord> -
>>>>
> Familiarity
>
>>>is
>>>
>>>
>>>>>to be set aside where the things of God are concerned. According
>>>>
> to
>
>>>the
>>>
>>>
>>>>>commandment of God - The authoritative appointment of God the
>>>>
>>>Father.
>>>
>>>
>>>>>Our Saviour - So styled in many other places likewise, as being the
>>>>>grand orderer of the whole scheme of our salvation. And Christ our
>>>>
>>>hope
>>>
>>>
>>>>>- That is, the author, object, and ground, of all our
>>>>
>>>hope.</p></div>
>>>
>>>>><catchWord> can not be a child of <div>.
>>>>>
>>>>>
>>>>>Should we add <catchWord> as a child of <div>?
>>>>>Todd
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>-----Original Message-----
>>>>>>From: osis-core-admin@bibletechnologieswg.org [mailto:osis-core-
>>>>>>admin@bibletechnologieswg.org] On Behalf Of Patrick Durusau
>>>>>>Sent: Wednesday, September 24, 2003 5:43 PM
>>>>>>To: osis-core@bibletechnologieswg.org
>>>>>>Subject: [osis-core] osisCore.1.9 (bumps, bruises and all)
>>>>>>
>>>>>>Guys,
>>>>>>
>>>>>>Version 1.9, along with a draft of the users manual is attached.
>>>>>
>>>Note
>>>
>>>
>>>>>>that the users manual is very rough and I have included the XML
>>>>>
>>>source
>>>
>>>
>>>>>>along with an HTML rendering.
>>>>>>
>>>>>>Suggest that if you have changes to the users manual, send me XML
>>>>>
>>>that
>>>
>>>
>>>>>>conforms to the TEIxLite DTD so I can paste it in more easily.
>>>>>>
>>>>>>Schema has some cleaning up to be done, but I have redone the
>>>>>
> osisID
>
>>>>>>Type to use the list mechanism Todd suggested for osisRefs. Should
>>>>>
>>>be
>>>
>>>
>>>>>>backwards compatible on that score.
>>>>>>
>>>>>>Couple of things to look for in the docs.
>>>>>>
>>>>>>1. Should we drop discussion of fall-back on resolving references?
>>>>>
>>>Not
>>>
>>>
>>>>>>really relevant to the beginning user.
>>>>>>
>>>>>>2. Should we drop the complete relator list and either point to it
>>>>>
>>>or
>>>
>>>
>>>>>>host a copy on the OSIS site?
>>>>>>
>>>>>>3. Does the manual appear to take you through encoding a text?
>>>>>>Suggestions for how to make it more that way?
>>>>>>
>>>>>>Should be working on the schema and users manual for the next six
>>>>>
>>>days
>>>
>>>
>>>>>>save for teleconferences and a couple of reports I can't get out
>>>>>
> of,
>
>>>>>so
>>>>>
>>>>>
>>>>>
>>>>>>comment early and often.
>>>>>>
>>>>>>We are almost there with a very robust release plus documentation!
>>>>>>
>>>>>>Can't tell you how proud I am of all the work you have done on
>>>>>
> this
>
>>>>>>project!
>>>>>>
>>>>>>Well, at 11+ for today so about to stop for the night.
>>>>>>
>>>>>>Hope everyone is having a great evening!
>>>>>>
>>>>>>Patrick
>>>>>>--
>>>>>>Patrick Durusau
>>>>>>Director of Research and Development
>>>>>>Society of Biblical Literature
>>>>>>Patrick.Durusau@sbl-site.org
>>>>>>Chair, V1 - Text Processing: Office and Publishing Systems
>>>>>
> Interface
>
>>>>>>Co-Editor, ISO 13250, Topic Maps -- Reference Model
>>>>>>
>>>>>>Topic Maps: Human, not artificial, intelligence at work!
>>>>>
>>>>>
>>>>>_______________________________________________
>>>>>osis-core mailing list
>>>>>osis-core@bibletechnologieswg.org
>>>>>http://www.bibletechnologieswg.org/mailman/listinfo/osis-core
>>>>>
>>>>
>>>>
>>>>--
>>>>Patrick Durusau
>>>>Director of Research and Development
>>>>Society of Biblical Literature
>>>>Patrick.Durusau@sbl-site.org
>>>>Chair, V1 - Text Processing: Office and Publishing Systems Interface
>>>>Co-Editor, ISO 13250, Topic Maps -- Reference Model
>>>>
>>>>Topic Maps: Human, not artificial, intelligence at work!
>>>>
>>>>
>>>>_______________________________________________
>>>>osis-core mailing list
>>>>osis-core@bibletechnologieswg.org
>>>>http://www.bibletechnologieswg.org/mailman/listinfo/osis-core
>>>
>>>
>>>_______________________________________________
>>>osis-core mailing list
>>>osis-core@bibletechnologieswg.org
>>>http://www.bibletechnologieswg.org/mailman/listinfo/osis-core
>>>
>>
>>
>>--
>>Patrick Durusau
>>Director of Research and Development
>>Society of Biblical Literature
>>Patrick.Durusau@sbl-site.org
>>Chair, V1 - Text Processing: Office and Publishing Systems Interface
>>Co-Editor, ISO 13250, Topic Maps -- Reference Model
>>
>>Topic Maps: Human, not artificial, intelligence at work!
>>
>>
>>_______________________________________________
>>osis-core mailing list
>>osis-core@bibletechnologieswg.org
>>http://www.bibletechnologieswg.org/mailman/listinfo/osis-core
>
>
> _______________________________________________
> osis-core mailing list
> osis-core@bibletechnologieswg.org
> http://www.bibletechnologieswg.org/mailman/listinfo/osis-core
>
--
Patrick Durusau
Director of Research and Development
Society of Biblical Literature
Patrick.Durusau@sbl-site.org
Chair, V1 - Text Processing: Office and Publishing Systems Interface
Co-Editor, ISO 13250, Topic Maps -- Reference Model
Topic Maps: Human, not artificial, intelligence at work!