...

should be allowed.

s within this div could be handled differently. ---------------------------------------------------------------- Cross-Reference example Description: Cross-Reference Example: 1 2 3 Also shown: Citation Line1, Citation Line2, Attribution Picture scanned from: ACT 7:49-50 (NIV) --------------- In order to get this would I mark this as a inside of . ----------------------------------------------------------------------------------------------- So Called example Description: So Called Example: 1 2 Also shown: Paragraph Picture scanned from: MRK 2:15-17 (NIV) ------ I don't find a way of marking up these "quotes". Possibly or or ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Hand example Description: Hand Example: 1 2 Also shown: Paragraph Picture scanned from: PHM 1:19 (TEV) ----------- I don't find a way of marking this up. Suggest or ------------------------------------------------------------------------------------------------------------- See In Glossary example Description: See In Glossary Also shown: Title Main, Intro Paragraph, Intro List Item1 Picture scanned from: MAT introduction (Bible du Semeur) ------- Is a see in glossary ? --------------------------------------------------------------------------- Section Head Series example Description: Section Head Series Example: 1 2 3 Also shown: Paragraph Picture scanned from: PRO 22:21-27 (TEV) ----------------- How do you handle the series? I would suggest

. ----------------------------------------------------------------------------------------------------------------------------- Verse Number Alternate example Description: Verse Number Alternate Also shown: Verse Number, Chapter Number Picture scanned from: GEN 32:1-2 (VP) --------------------------- How do you handle a verse number alternate? ----------------------------------------------------------------------- Chapter Number Alternate example Description: Chapter Number Alternate Also shown: Chapter Head, Section Head, Line1 Picture scanned from: PSA 10 (VP) ------------------ How do you handle chapter number alternate? ------------------------------------------------------------------------- Inscription example Description: Inscription Also shown: Paragraph Picture scanned from: MRK 15:26 (NIV) ----------------- handles this nicely. Thanks for adding it. ------------------------------------------------------------------------------ Inscription Paragraph example Description: Inscription Paragraph Example: 1 2 Also shown: Paragraph, Paragraph Continuation Picture scanned from: REV 17:5 (NIV) ----------------- Would this be handled by

mysterybabylon the greatthe mother of prostitutesand of the abominations of the earth.

? ------------- Inscription Paragraph example 2 Description: Inscription Paragraph Example: 1 2 Also shown: Paragraph, List Item1, Foreign Picture scanned from: DAN 5:25 (NIV) -------- And

mene, mene, tekel, parsin

? ------------------------------------------------------------------------------------------------ Chapter Head example Description: Chapter Head Example: 1 2 Also shown: Line1, Doxology, Section Head Major, Chapter Number, Hebrew Title, Section Head, Line2 Picture scanned from: PSA 42 (CEV) ------------------------------------------------------------- I suggest using

to handle this _______________________________________________ Thanks for looking over these examples and questions. ----------------------------------------------------------------- In order to preserve information that is richer in TE and OSIS I suggest adding a style in USFM called something like: \_TE_reserved ...\ _TE_reserved* \_reserved ... \_reserved* \reserved ... \reserved* \comment ... \comment* \xml ... \xml* TE would likely store information inside this tag in an XML form (that is why the suggested name of XML). The name isn't as important as having a place to store information. The \rem doesn't work as it is a paragraph tag and this new tag is needed to go inside of paragraph tags. Round tripping could then occur without loss of information for OSIS and TE. Jim Albright 704 843-0582 Wycliffe Bible Translators From chrislit at crosswire.org Tue Apr 5 22:21:02 2005 From: chrislit at crosswire.org (Chris Little) Date: Tue Apr 5 22:17:09 2005 Subject: [osis-core] Re: USFM to OSIS mapping: Next Steps (last steps) In-Reply-To: References: Message-ID: <425371BE.9070703@crosswire.org> Jim_Albright@wycliffe.org wrote: > The and seem to be out of place. That makes sense to me (that they are out of place). (Apologies if I suggested either of these.) There is a situation in Lamentations, where the acrostic letters appear to occur before every line. Something that can occur within a line, like or , makes better sense here to me than . <title> makes good sense in Psalms, but not Lamentations (just my opinion). > hi types: > > acrostic > bold > emphasis > illuminated > italic > line-through > normal > small-caps > sub > super > underline > > All other types describe format to apply to a segment. <hi > type='emphasis'> is not italic. It is emphasis. > Will these work? yes. <seg type'emphasis'> seems more logical if you want > to make it a type on something and not <emphasis>. Or <emph>, as in TEI, I believe. But given the schema as it is (2.01 or 2.1pre), I would probably use <hi> without a type to encode generic emphasis. --Chris From chrislit at crosswire.org Sat Apr 16 19:15:41 2005 From: chrislit at crosswire.org (Chris Little) Date: Sat Apr 16 19:16:11 2005 Subject: [osis-core] chapterTitle In-Reply-To: <42523E63.7050105@snowfallsoftware.com> References: <425239E8.2040902@crosswire.org> <42523E63.7050105@snowfallsoftware.com> Message-ID: <4261C6CD.50707@crosswire.org> Possibly this is supposed to handle Chapter vs. Psalm. You don't want to title the chapters of Psalms "Chapter #" but rather "Psalm #". Just a guess. :) --Chris Todd Tillinghast wrote: > Chris, > > Is it for the case where there is a title like "Chapter" for a chapter. > > I believe that we are saying that <chapter> followed by <title > type="chapter">... fulfills that role. > > Are these redundant cases? > > Todd > > Chris Little wrote: > >> Does anyone remember what chapterTitle is for? It's an attribute of >> chapter elements, but I'm at a loss for its purpose and am starting to >> think it's a leftover from one of the early releases. Or does it have >> something to do with publishing? I don't find any other title >> attributes in the schema (2.0.1 or 2.0.9_almost7). >> >> --Chris >> >> _______________________________________________ >> 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 From scribe at crosswire.org Fri Apr 22 20:42:23 2005 From: scribe at crosswire.org (Troy A. Griffitts) Date: Fri Apr 22 20:42:04 2005 Subject: [osis-core] Message-ID: <4269C41F.1090303@crosswire.org> Hey guys, A while back we dicussed NOT restricting the morph attribute of to osisGenType, but rather merely xs:string. I would like this to happen. I have to modify the schema to get most of our modules which include morphology to validate. We use Robinson morphology codes which are exemplified by the likes of: V-PAP-GSN (Verb- Present Active Participle- Genitive Singular Nominitive) V-2AAM-2S (Verb- 2nd Aorist Active Imparative- 2nd Person Singular) N-NSM (Noun- Nominitive Singular Masculine) We're about to release a few new modules (e.g., Wescott-Hort Accented Greek NT with Morphology) and would like them to validate against the upcoming schema. -Troy. From todd at snowfallsoftware.com Sun Apr 24 16:15:45 2005 From: todd at snowfallsoftware.com (Todd Tillinghast) Date: Sun Apr 24 16:16:10 2005 Subject: [osis-core] The prefix for the element in the attribute "path" of element be required. Message-ID: <426C28A1.5080505@snowfallsoftware.com> Patrick, The prefix for the element in the attribute "path" of element be required. Because OSIS elements must be namespace qualified it makes sense to allow only valid XPath for the value "path". Natually the element prefix would need to be declared with an xmlns attribute. The current regex optionally allows the namespace prefix. Todd