|
/
Zope
/
WHI Hosted Mailing Lists
/
osis-user
/
Archive
/
2005
/
2005-01
/
div types in OSIS
[
XML schema for versification variations / Mete ... ]
[
Re: OSIS Encoding of SIL Translator's Notes for ... ]
div types in OSIS
Jim_Albright(at)wycliffe.org |
2005-01-03 15:45:09 |
[ FULL ]
|
Here are the divs found in the wild in SIL commentary: Translator's Notes
on 2TI.
name in TN level current working name OSIS
================================================================================
p-TitleCenterMedium a > main type="main"
b* > majorSection
type="majorSection"
p-Box3Section c > section
type="section"
p-Box4ParaNoSpace|p-Box4Paragraph d >
paragraph type="paragraph"
p-VerseReference
e > verseFragment type="???"
p-MarginSpaceB4[child::TextCited] f >
verseFragment2 type="???"
p-IndentBlockSpaceB4[child::TextCited] g* >
verseFragment3 type="???"
p-Indent1stSpaceB4[child::TextCited] h*>
verseFramgent4 type="???"
* not in current work but projected to be found in other commentaries
based on style sheet info
Here are my ponderings.
So I need to have a good OSIS name for the div's concerning
verseFramgments. I propose using "verseFragment" and then nesting
verseFragment to get the verseFragment2, verseFragment3, verseFragment4
as my first thought but I really don't like that solution.
I considered using the 'n" attribute and using it to assign levels but
that is abusing the "n" attribute.
If there were a generic "level" attribute I could use that.
The following might work:
level current working name OSIS
==================================
a > main subtype="1"
b* > majorSection
subtype="2"
c > section
subtype="3"
d > paragraph
subtype="4"
e > verseFragment
subtype="5"
f > verseFragment2
subtype="6"
g > verseFragment3
subtype="7"
h*> verseFramgent4
subtype="8"
I can't use just plain <div><div> and count how many level's are
above it
as majorSection can be omitted. I guess I could use
a plain <div> for verseFragment and then nest <div>s for the other
verseFragments.
level current working name OSIS
==================================
a > main div[(at)type="main"]
b* > majorSection
div{(at)type="majorSection"]
c > section div[(at)type="section"]
d > paragraph div[(at)type="paragraph"]
e > verseFragment
div[(at)type="paragraph"]/div
f > verseFragment2
div[(at)type="paragraph"]/div/div
g > verseFragment3
div[(at)type="paragraph"]/div/div/div
h*> verseFramgent4
div[(at)type="paragraph"]/div/div/div/div
*********************************************************************************
*********************************************************************************
*********************************************************************************
I still would prefer:
level current working name OSIS
==================================
a > main div[(at)type="main"]
b* > majorSection
div{(at)type="majorSection"]
c > section div[(at)type="section"]
d > paragraph div[(at)type="paragraph"]
e > verseFragment
div[(at)type="verseFragment"]
f > verseFragment2
div[(at)type="verseFragment2"]
g > verseFragment3
div[(at)type="verseFragment3"]
h*> verseFramgent4
div[(at)type="verseFragment4"]
*********************************************************************************
*********************************************************************************
*********************************************************************************
or possibly
level current working name OSIS
==================================
a > main div[(at)type="main"]
b* > majorSection
div{(at)type="majorSection"]
c > section div[(at)type="section"]
d > paragraph div[(at)type="paragraph"]
e > verseFragment div[(at)subtype="verseFragment"]
f > verseFragment2
div[(at)subtype="verseFragment2"]
g > verseFragment3
div[(at)subtype="verseFragment3"]
h*> verseFramgent4
div[(at)subtype="verseFragment4"]
but this seems a bit strange to me.
Since there are so may div types I would prefer to add some more in order
to handle commentaries.
*********************************************************************************
I still would prefer:
level current working name OSIS
==================================
a > main div[(at)type="main"]
b* > majorSection
div{(at)type="majorSection"]
c > section div[(at)type="section"]
d > paragraph div[(at)type="paragraph"]
e > verseFragment div[(at)type="verseFragment"]
Grace, mercy and peace from God the Father and Christ Jesus our Lord:
f > verseFragment2
div[(at)type="verseFragment2"]
Grace:
mercy:
peace:
God the Father:
g > verseFragment3 div[(at)type="verseFragment3"]
h*> verseFramgent4 div[(at)type="verseFragment4"]
*********************************************************************************
Jim Albright
704 843-0582
Wycliffe Bible Translators
|
Re: div types in OSIS
Jim_Albright(at)wycliffe.org |
2005-01-03 22:27:02 |
[ FULL ]
|
This is a commentary. The normal book chapter verse reference is
sufficient.
I don't see how annotateRef really helps me. My goal is to encode the
commentary so that I have preserved all the logical divisions and then be
able to round trip the OSIS document to Word ML.
What I need is several sub levels to hold the verseFragment and
verseFragment2, etc in.
Jim Albright
704 843-0582
Wycliffe Bible Translators
Todd Tillinghast <todd(at)snowfallsoftware.com>
01/03/2005 04:33 PM
To: Jim_Albright(at)wycliffe.org
cc: Patrick.Durusau(at)sbl-site.org, Dennis Drescher
<dennis_drescher(at)sil.org>,
Jeff_Gayle(at)sil.org, Larry_Waswick(at)sil.org,
osis-core(at)bibletechnologieswg.org, osis-user(at)whi.wts.edu,
sderose(at)acm.org,
todd(at)contentframeworks.com
Subject: Re: div types in OSIS
Jim,
Is this a Bible or a Commentary (or a thing structurally like a
Commentary) you are trying to encode? (Possibly, translators helps?)
If it is the later you can use the annotateRef attribute (most likely
with grain references) to precisely indicate not only the levels but
also the exact portion of sub-text you are annotating. (You should be
using annotateRef anyway if you are doing what I suspect you are doing.)
Further if this is not a Bible you are free to define your own internal
reference system and use osisID="A.A.1" then for its children
osisID="A.A.1.1" and osisID="A.A.1.2", etc...
Todd
Jim_Albright(at)wycliffe.org wrote:[...]
Notes [...]
OSIS[...]
================================================================================[...]
type="majorSection"[...]
type="paragraph"[...]
type="???"[...]
verseFragment2 type="???"[...]
verseFragment3 type="???"[...]
verseFramgent4 type="???"[...]
[...]
it [...]
div[(at)type="paragraph"]/div/div[...]
div[(at)type="paragraph"]/div/div/div[...]
div[(at)type="paragraph"]/div/div/div/div[...]
*********************************************************************************[...]
*********************************************************************************[...]
*********************************************************************************[...]
div[(at)type="verseFragment2"][...]
*********************************************************************************[...]
*********************************************************************************[...]
*********************************************************************************[...]
div[(at)subtype="verseFragment2"][...]
order [...]
*********************************************************************************[...]
div[(at)type="verseFragment2"] [...]
*********************************************************************************[...]
|
Re: div types in OSIS
Jim_Albright(at)wycliffe.org |
2005-01-03 23:36:01 |
[ FULL ]
|
Well my face is red as I found that the p-VerseReference should not map to
VerseFragment but to VerseReference and thus renaming all the divs below
it.
Below is revised suggestion. The hierarchy is derived from the Word style
sheet and from the outline view in Word of the data. The encoders want to
show the divs in the suggested levels as given below.
Jim Albright
704 843-0582
Wycliffe Bible Translators
Jim Albright
01/03/2005 03:42 PM
To: OSIS Patrick Durusau
cc: "Dennis Drescher" <dennis_drescher(at)sil.org>,
Jeff_Gayle(at)sil.org,
Larry_Waswick(at)sil.org, osis-core(at)bibletechnologieswg.org,
osis-user(at)whi.wts.edu, sderose(at)acm.org, todd(at)contentframeworks.com
Subject: div types in OSIS
Here are the divs found in the wild in SIL commentary: Translator's Notes
on 2TI.
(trying to align the text better)
name in TN level current working name OSIS
================================================================================
p-TitleCenterMedium a > main
type="main"
b* > majorSection type="majorSection"
p-Box3Section c >
section type="section"
p-Box4ParaNoSpace|p-Box4Paragraph d > paragraph
type="paragraph"
p-VerseReference e >
verseReference type="???"
p-MarginSpaceB4[child::TextCited] f > verseFragment
type="???"
p-IndentBlockSpaceB4[child::TextCited] g* > verseFragment2
type="???"
p-Indent1stSpaceB4[child::TextCited] h*> verseFramgent3
type="???"
* not in current work but projected to be found in other commentaries
based on style sheet info
*********************************************************************************
*********************************************************************************
I still would prefer:
level current working name OSIS
==================================
a > main div[(at)type="main"]
b* > majorSection
div{(at)type="majorSection"]
c > section div[(at)type="section"]
d > paragraph div[(at)type="paragraph"]
e > verseReference div[(at)type="verseReference"]
1:1a
f > verseFragment
div[(at)type="verseFragment2"]
Grace, mercy and peace from God the Father and Christ Jesus our Lord:
g > verseFragment2 div[(at)type="verseFragment3"]
Grace:
mercy:
peace:
God the Father:
h*> verseFramgent3 div[(at)type="verseFragment4"]
*********************************************************************************
Jim Albright
704 843-0582
Wycliffe Bible Translators
|
RE: [osis-user] Re: div types in OSIS
"Maurice Manktelow" <maurice(at)manktelow.net> |
2005-01-04 03:29:49 |
[ FULL ]
|
Jim
Welcome to the 'Red Faced Club'.
I am a life-long member, and regularly renew my membership! The club has a
large membership - but most like to keep their affiliation a secret. You are
in very good company [trust me - you would be surprised at who else belongs]
Maurice
P.S. I take comfort from the saying "He who has not made a mistake has
probably never made anything"
-----Original Message-----
From: Jim_Albright(at)wycliffe.org [mailto:Jim_Albright(at)wycliffe.org]
Sent: Tuesday, January 04, 2005 4:35 AM
To: Patrick.Durusau(at)sbl-site.or
Cc: Dennis Drescher; Jeff_Gayle(at)sil.org; Larry_Waswick(at)sil.org;
osis-core(at)bibletechnologieswg.org; osis-user(at)whi.wts.edu;
sderose(at)acm.org;
todd(at)contentframeworks.com
Subject: [osis-user] Re: div types in OSIS
Well my face is red as I found that the p-VerseReference should not map to
VerseFragment but to VerseReference and thus renaming all the divs below
it.
Below is revised suggestion. The hierarchy is derived from the Word style
sheet and from the outline view in Word of the data. The encoders want to
show the divs in the suggested levels as given below.
Jim Albright
704 843-0582
Wycliffe Bible Translators
Jim Albright
01/03/2005 03:42 PM
To: OSIS Patrick Durusau
cc: "Dennis Drescher" <dennis_drescher(at)sil.org>,
Jeff_Gayle(at)sil.org,
Larry_Waswick(at)sil.org, osis-core(at)bibletechnologieswg.org,
osis-user(at)whi.wts.edu, sderose(at)acm.org, todd(at)contentframeworks.com
Subject: div types in OSIS
Here are the divs found in the wild in SIL commentary: Translator's Notes
on 2TI.
(trying to align the text better)
name in TN level current working name OSIS
============================================================================
====
p-TitleCenterMedium a > main
type="main"
b* > majorSection type="majorSection"
p-Box3Section c >
section type="section"
p-Box4ParaNoSpace|p-Box4Paragraph d > paragraph
type="paragraph"
p-VerseReference e >
verseReference type="???"
p-MarginSpaceB4[child::TextCited] f > verseFragment
type="???"
p-IndentBlockSpaceB4[child::TextCited] g* > verseFragment2
type="???"
p-Indent1stSpaceB4[child::TextCited] h*> verseFramgent3
type="???"
* not in current work but projected to be found in other commentaries
based on style sheet info
****************************************************************************
*****
****************************************************************************
*****
I still would prefer:
level current working name OSIS
==================================
a > main div[(at)type="main"]
b* > majorSection
div{(at)type="majorSection"]
c > section div[(at)type="section"]
d > paragraph div[(at)type="paragraph"]
e > verseReference div[(at)type="verseReference"]
1:1a
f > verseFragment
div[(at)type="verseFragment2"]
Grace, mercy and peace from God the Father and Christ Jesus our Lord:
g > verseFragment2 div[(at)type="verseFragment3"]
Grace:
mercy:
peace:
God the Father:
h*> verseFramgent3 div[(at)type="verseFragment4"]
****************************************************************************
*****
Jim Albright
704 843-0582
Wycliffe Bible Translators
[...]
|
Re: div types in OSIS
Jim_Albright(at)wycliffe.org |
2005-01-05 13:54:12 |
[ FULL ]
|
It seems like we are working on two different levels here.
1. The div and their types
2. The internal reference system.
1. The div and their types
In replicating the Translator's Notes I need to be able to express the
various div levels (think of them as outline of the text).
That is the need for the divs of type equals
main
majorSection
section
paragraph
verseReference
verseFragment
verseFragment2
verseFragment3
2. The internal reference system.
Having an internal reference system that is close to the Bible IS very
important as that is the way we are able to display appropriate material
to the translator. This is not a need to internally just to the
verseFrament2 from within the document. Jumping to the verseReference is
sufficient.
The commentary does mirror the Bible text so using
osisID="Translator'sNotes:2Tim.1.1!a"
makes sense.
I don't understand what we gain with annotateRef/annotateType ... the
whole work is commentary.
current snapshot of OSIS file
<?xml version="1.0" encoding="UTF-8"?>
<document>
<div type="commentary" osisID="Translator'sNotes:2Tim"
annotateRef="2Tim">
<div xmlns:w="http://schemas.microsoft.com/office/word/2003/wordml"
xmlns:o="urn:schemas-micro
<title>TRANSLATOR'S NOTES ON 2 TIMOTHY</title>
<div type="section">
<title>Section 1:1-2 Paul sent greetings to
Timothy</title>
<p>The people who wrote letters during the time when Paul
lived began the letters that t
<div type="paragraph">
<title>Paragraph 1:1-2</title>
<div type="verseReference">
<title osisID="Translator'sNotes:2Tim.1.1!a">Paul, an
apostle of Christ Jesus by t
<div type="verseFragment">
<title>Paul, an apostle of Christ
Jesus:</title>
<p>Paul began this letter to Timothy by stating his
own name first. Then he sai
<p type="example">
<transChange type="added">This letter is from
me,</transChange>Paul.<transCh
<p type="example">
<transChange
type="added">I,</transChange>Paul,<transChange type="added">am
<div type="verseFragment2">
<title>an apostle of Christ Jesus:</title>
<p>The
word<c-mentioned>apostle</c-mentioned>means
"a person whom someone ha
<div type="verseFramgent3">
<title>Christ Jesus:</title>
<p>The
word<c-mentioned>Christ</c-mentioned>is
used two ways in the New T
<p>Notice that in this verse Paul referred
to<c-mentioned>Jesus</c-mentio
</div>
</div>
</div>
I am hoping that
<transChange type="added">
can be replaced by
<implied>
Jim Albright
704 843-0582
Wycliffe Bible Translators
Todd Tillinghast <todd(at)snowfallsoftware.com>
01/03/2005 11:39 PM
To: Jim_Albright(at)wycliffe.org
cc: Dennis Drescher <dennis_drescher(at)sil.org>,
Jeff_Gayle(at)sil.org,
Larry_Waswick(at)sil.org, osis-core(at)bibletechnologieswg.org,
osis-user(at)whi.wts.edu, Patrick.Durusau(at)sbl-site.org, sderose(at)acm.org,
todd(at)contentframeworks.com
Subject: Re: div types in OSIS
Jim,
If it is a commentary then the normal book chapter verse reference
system is sufficient for what you are commenting on ("annotating") but
is not sufficient for the commentary itself.
The commentary is not ITSELF a Bible and as such would not naturally
take on book/chapter/verse type values for ITS osisID values. Rather it
would specify the reference range(s) that it is talking about using the
annotateRef attribute.
This leaves the osisID of the commentary open for your own "reference
system" (not likely to be widely used externally but could be useful).
You are free to declare a reference system identical to the Bible and
use it for your commentary but I wouuld caution you that it is unlikely
to give you the results you want because the document you are working on
is not three levels (book/chapter/verse) but rather many more levels.
I would suggest something like [BookName].[section name or section
number].[paragraph/line group/list/table number].[fragment
number].[fragment number] etc...
That way you would have osisIDs like 2Tim.S1.P1.1.2 for the second
fragment in the first fragment in the first paragraph in the first
section in 2Tim.
Todd
Jim_Albright(at)wycliffe.org wrote:[...]
be [...]
<dennis_drescher(at)sil.org>, [...]
sderose(at)acm.org, [...][...][...][...][...]
================================================================================[...][...][...][...][...][...][...][...][...][...][...][...][...][...]
[...][...][...][...][...][...][...][...][...][...]
*********************************************************************************[...]
*********************************************************************************[...]
*********************************************************************************[...][...][...][...][...]
*********************************************************************************[...]
*********************************************************************************[...]
*********************************************************************************[...][...][...][...][...][...][...]
*********************************************************************************[...][...][...][...][...]
*********************************************************************************[...][...][...]
|
|
