[osis-core] <catchWord> can't be a child of <div>

[Todd Tillinghast]

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!