[osis-core] OSISCore_1.test6 osisCorpus/osisText/Header
Chris Little
osis-core@bibletechnologieswg.org
Thu, 23 May 2002 22:15:36 -0700
This is a multi-part message in MIME format.
------=_NextPart_000_0033_01C202A7.5DEE2F80
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit
-----Original Message-----
From: owner-osis-core@bibletechnologieswg.org
[mailto:owner-osis-core@bibletechnologieswg.org] On Behalf Of Patrick
Durusau
Sent: Thursday, May 23, 2002 8:59 PM
To: osis-core@bibletechnologieswg.org
Subject: Re: [osis-core] OSISCore_1.test6 osisCorpus/osisText/Header
Chris,
Good call, although I like the alternative solution better. Probably
because I see a corpus as needing a common header and yet allowing
individual headers for the various texts. With your second solution, we
know the location of a header, corpus or single text and that seems like
a good thing to me. Done and done.
Patrick
Patrick,
FWIW, I prefer that solution also, but the first solution seemed less
radical.
--Chris
------=_NextPart_000_0033_01C202A7.5DEE2F80
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<TITLE>Message</TITLE>
<META content=3D"MSHTML 6.00.2716.2200" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT> </DIV>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
<DIV></DIV>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft><FONT=20
face=3DTahoma size=3D2>-----Original Message-----<BR><B>From:</B>=20
owner-osis-core@bibletechnologieswg.org=20
[mailto:owner-osis-core@bibletechnologieswg.org] <B>On Behalf Of =
</B>Patrick=20
Durusau<BR><B>Sent:</B> Thursday, May 23, 2002 8:59 PM<BR><B>To:</B>=20
osis-core@bibletechnologieswg.org<BR><B>Subject:</B> Re: [osis-core]=20
OSISCore_1.test6 osisCorpus/osisText/Header<BR><BR></FONT></DIV>
<DIV>Chris, <BR><BR>Good call, although I like the alternative =
solution=20
better. Probably because I see a corpus as needing a common header and =
yet=20
allowing individual headers for the various texts. With your second =
solution,=20
we know the location of a header, corpus or single text and that seems =
like a=20
good thing to me. Done and done.<BR><BR>Patrick<SPAN=20
class=3D807381305-24052002><FONT face=3DArial color=3D#0000ff=20
size=3D2> </FONT></SPAN></DIV></BLOCKQUOTE>
<DIV><SPAN class=3D807381305-24052002><FONT face=3DArial=20
size=3D2>Patrick,</FONT></SPAN></DIV>
<DIV><SPAN class=3D807381305-24052002></SPAN> </DIV>
<DIV><SPAN class=3D807381305-24052002><FONT face=3DArial size=3D2>FWIW, =
I prefer=20
that solution also, but the first solution seemed less=20
radical.</FONT></SPAN></DIV>
<DIV><SPAN class=3D807381305-24052002></SPAN> </DIV>
<DIV><SPAN class=3D807381305-24052002><FONT face=3DArial=20
size=3D2>--Chris</FONT> </SPAN><B r><B r><B=20
r></DIV></B></B></B></BODY></HTML>
------=_NextPart_000_0033_01C202A7.5DEE2F80--