enumerated attributes requested

<osis:q (at)type='letter'>

This is used in NIV ACT 15, REV 2

And a concurrent problem is how do you mark the words of Christ often 
displayed in red?

Jim Albright
704 843-0582
Wycliffe Bible Translators

I just came across the WEB (World English Bible). They do it like this:

<q sID="Matt.26.50.138" who="Jesus" n="" type="x-doNotGeneratePunctuation"
/>"Friend, why are you here?"<q eID="Matt.26.50.138" n="" />

The header says they know it's not the way it should be. That is exactly
what I meant by ambiguity. And thre are probably half a dozen other ways to
do it in still be spec-compliant. Without more guidance in the OSIS spec,
this might easily be a stumbling block for the whole thing (in my humble
opinion).

Cheers,
Thomas

----- Original Message ----- 
From: <Jim_Albright(at)wycliffe.org>
To: <osis-user(at)whi.wts.edu>
Sent: 04 June 2004 20:09
Subject: [osis-user] USFM \pi --> TE 'Letter Paragraph' <--OSIS

[...]
osis-user(at)whi.wts.edu.[...]

On Fri, 4 Jun 2004 Jim_Albright(at)wycliffe.org wrote:
[...]

I agree completely that this should be added.  I think I made the same 
suggestion at the last meeting, but it didn't gain any appeal.  I also 
suggested removing the <inscription> element from the Schema and
replacing 
it with an "inscription" enumerated type on <q>, since it simplifies 
things considerably (such as needing to mirror the content model of <q> 
for <inscription>).
 [...]

There is only a small amount of ambiguity here.  I have always used <q
who="Jesus">, have seen others use it, and recommend its use.  The "Jesus"  
part is the ambiguous bit, since we haven't actually released any kind of
enumerated biblical cast list.  But personally, I think that if we ever do
release such a cast list, there's a really good chance that Jesus will be
referred to as "Jesus".  (As opposed or "Christ" or "Christ, Jesus" or
"Larry".)

--Chris

On Fri, 4 Jun 2004, Thomas BOEHME wrote:
[...]

Actually, this an example of the opposite of ambiguity.  BTG clearly
defined how quotations should be encoded in OSIS.  Michael Paul Johnson
(author/encoder of the WEB) disagrees, so he did something else.  There's
no ambiguity.  Michael's documents are simply not conformant to the OSIS
specification, a fact he realizes well enough to have documented their
non-conformance in his header.

Some aspects of the specification cannot be encoded in the Schema itself 
and enforced by Schema validation.  Those aspects are detailed in the 
manual, in prose.

One of those details is that quotations are marked with <q> elements, not

typographic quotation marks.  Michael doesn't like allowing/relying on 
style sheets to generate typographic quotation marks, so he encodes 
typographic quotation marks in his document.  But, since the only way to 
mark the speaker of a quotation is with the who attribute of a <q> 
element, he also adds <q> elements for the words of Christ, but adds a 
type to the <q> element in order to explain that they shouldn't result in

(redundant) typographic quotation mark generation.

--Chris

Hopefully OSIS will add enumerations for attributes that cover cases that 
otherwise may be coded with an extension (x-) and thus non-standard.

Jim Albright
704 843-0582
Wycliffe Bible Translators






"Thomas BOEHME" <catb(at)gmx.net>
06/04/2004 03:37 PM
Please respond to osis-user

 
        To:     <osis-user(at)whi.wts.edu>
        cc: 
        Subject:        Re: [osis-user] USFM \pi --> TE 'Letter Paragraph'
<--OSIS


I just came across the WEB (World English Bible). They do it like this:

<q sID="Matt.26.50.138" who="Jesus" n="" type="x-doNotGeneratePunctuation"
/>"Friend, why are you here?"<q eID="Matt.26.50.138" n="" />

The header says they know it's not the way it should be. That is exactly
what I meant by ambiguity. And thre are probably half a dozen other ways 
to
do it in still be spec-compliant. Without more guidance in the OSIS spec,
this might easily be a stumbling block for the whole thing (in my humble
opinion).

Cheers,
Thomas

----- Original Message ----- 
From: <Jim_Albright(at)wycliffe.org>
To: <osis-user(at)whi.wts.edu>
Sent: 04 June 2004 20:09
Subject: [osis-user] USFM \pi --> TE 'Letter Paragraph' <--OSIS

[...]
osis-user(at)whi.wts.edu.[...]

[...]

Thank you for your comments .... <<<<<<<<< mine
below

Jim Albright
704 843-0582
Wycliffe Bible Translators






Chris Little <chrislit(at)crosswire.org>
06/04/2004 08:41 PM
Please respond to osis-user

 
        To:     osis-user(at)whi.wts.edu
        cc: 
        Subject:        Re: [osis-user] USFM \pi --> TE 'Letter Paragraph'
<--OSIS


On Fri, 4 Jun 2004 Jim_Albright(at)wycliffe.org wrote:
[...]

I agree completely that this should be added.  I think I made the same 
suggestion at the last meeting, but it didn't gain any appeal.  I also 
suggested removing the <inscription> element from the Schema and
replacing 

it with an "inscription" enumerated type on <q>, since it simplifies 
things considerably (such as needing to mirror the content model of <q> 
for <inscription>).
 
<<<<<<<<what was the reason for not including letter?

<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
Inscriptions can be inline or formatted as centered text, either way they 
are all small caps.
So having an inscription element allows for either formatting.
<p><inscription>This would be centered all small
caps</inscription></p>
<p>This is normal text <inscription>Jesus Christ King of the 
Jews</inscription> and more normal text.</p>

This could also be encoded
<p><q type='inscription'>This would be centered all small
caps</q></p>
<p>This is normal text <q type='inscription'>Jesus Christ King of
the 
Jews</q> and more normal text.</p>

I have no objection to either model. But there should be one clear 
definition of how to do things.

Mirroring a content model is very easy to do so should not restrict your 
choices. We should be aiming for 
make OSIS easy for the end user, NOT easy for the programmer, as a model 
to strive for. 
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<,
[...]

There is only a small amount of ambiguity here.  I have always used <q
who="Jesus">, have seen others use it, and recommend its use.  The "Jesus" 
 
part is the ambiguous bit, since we haven't actually released any kind of
enumerated biblical cast list.  But personally, I think that if we ever do
release such a cast list, there's a really good chance that Jesus will be
referred to as "Jesus".  (As opposed or "Christ" or "Christ, Jesus" or
"Larry".)

--Chris
<<<<<<<<<<<
But is this specified in the spec or documentation? If it is not, then we 
are free to choose anything we want. Thus creating many standards. I heard 
one person say that their organization was in favor of standards, in fact 
they had LOTS of them. 
We only need one good standard.
<<<<<<<<<<<<

[...]

Jim and Chris,

I think it was mostly a matter of not having time to fully consider the
complete set of potential <q> enumerated types AND not having a concrete
set of cases and/or champions for particular enumerated type values.

I believe it was "left to be resolved on the list".

I am not opposed to "letter" we just need to come up with a concrete
list of the other <q> enumerated types and make sure we don't have
overlapping cases.

Todd
[...]
Paragraph'[...]
replacing[...]
<q>[...]
they[...]
caps</inscription></p>[...]
your[...]
model[...]
often[...]
"Jesus"[...]
of[...]
ever do[...]
be[...]
we[...]
heard[...]
fact[...]

Briefly, my personal oppositions to using <q> for anything that wouldn't 
be a " (quote) are: a) it's not a quote as we define a quote with " 
syntax; b) first level OSIS supporters will probably just transform all 
<q> to ".


	-Troy.


Todd Tillinghast wrote:[...][...][...][...]
>>>enumerated attributes requested
>>>
>>><osis:q (at)type='letter'>
>>>
>>>This is used in NIV ACT 15, REV
2[...][...][...][...][...][...][...][...][...][...][...][...][...]
>>>And a concurrent problem is how do you mark the words of
Christ[...]
>>>displayed in
red?[...][...][...][...][...][...][...][...][...][...][...][...][...][...][...][...]

Troy,

Thanks for you input. Not all quotes... even direct quotes, resolve to ". 
Try the dialogue quote, long dash in Spanish, and block quotes in English. 
Check out French quotes with using chevrons, and Russian ........


Jim Albright
704 843-0582
Wycliffe Bible Translators






"Troy A. Griffitts" <scribe(at)crosswire.org>
06/05/2004 02:24 PM
Please respond to osis-user

 
        To:     osis-user(at)whi.wts.edu
        cc: 
        Subject:        Re: [osis-user] USFM \pi --> TE 'Letter Paragraph'
<--OSIS


Briefly, my personal oppositions to using <q> for anything that wouldn't 
be a " (quote) are: a) it's not a quote as we define a quote with " 
syntax; b) first level OSIS supporters will probably just transform all 
<q> to ".


                 -Troy.


Todd Tillinghast wrote:[...][...][...][...]
>>>enumerated attributes requested
>>>
>>><osis:q (at)type='letter'>
>>>
>>>This is used in NIV ACT 15, REV
2[...][...][...][...][...][...][...][...][...][...][...][...][...]
>>>And a concurrent problem is how do you mark the words of
Christ[...]
>>>displayed in
red?[...][...][...][...][...][...][...][...][...][...][...][...][...][...][...][...]


[...]

Jim,
	Humbly and ignorantly from a non-linguist's point of view, I still 
believe that 98% of all usages for <q> could be rendered with " and not 
confuse the reader; they might be rendered better if type="block" was 
observed, et. al.  In the past, we had discussed using <q> for old 
testament allusions (not quotes) and other things.  I find one of my 
convictions is to consider what mistakes are likely to arise from 
someone not having a complete understanding of the schema.  If that 
mistake encourages a misunderstanding of Scripture, I make every effort 
to seek to provide a better mechanism.

This obviously doesn't apply to 'letter'.  In fact, I'm not sure letter, 
song, inscription, or any other 'media' used for encapsulating someone's 
quote makes it any different than a quote.  But with this discussion 
reopening, and the proponents of using <q type="allusion"> (and many 
other non-quote usages) speaking in favour of opening up usage for <q> 
again, I just wanted to make my motivations clear for the discussion.

	-Troy.



Jim_Albright(at)wycliffe.org wrote:[...][...]
>>>From: Jim_Albright(at)wycliffe.org
[mailto:Jim_Albright(at)wycliffe.org]
>>>Sent: Friday, June 04, 2004 10:28 PM
>>>To: osis-user(at)whi.wts.edu
>>>Subject: Re: [osis-user] USFM \pi --> TE 'Letter Paragraph'
<--OSIS
>>>
>>>Thank you for your comments ....
<<<<<<<<< mine below
>>>
>>>Jim Albright
>>>704 843-0582
>>>Wycliffe Bible Translators
>>>
>>>
>>>
>>>
>>>
>>>
>>>Chris Little <chrislit(at)crosswire.org>
>>>06/04/2004 08:41 PM
>>>Please respond to osis-user
>>>
>>>
>>>       To:     osis-user(at)whi.wts.edu
>>>       cc:
>>>       Subject:        Re: [osis-user] USFM \pi --> TE
'Letter[...]
>>><--OSIS
>>>
>>>
>>>On Fri, 4 Jun 2004 Jim_Albright(at)wycliffe.org wrote:
>>>
>>>
>>>
>>>>enumerated attributes requested
>>>>
>>>><osis:q (at)type='letter'>
>>>>
>>>>This is used in NIV ACT 15, REV 2
>>>
>>>I agree completely that this should be added.  I think I made the
same
>>>suggestion at the last meeting, but it didn't gain any appeal.  I
also
>>>suggested removing the <inscription> element from the Schema
and[...]
>>>it with an "inscription" enumerated type on <q>, since it
simplifies
>>>things considerably (such as needing to mirror the content model
of[...]
>>>
>>><<<<<<<<what was the reason for not
including letter?
>>>
>>><<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
>>>Inscriptions can be inline or formatted as centered text, either
way[...]
>>>are all small caps.
>>>So having an inscription element allows for either formatting.
>>><p><inscription>This would be centered all small[...]
>>>Jews</inscription> and more normal text.</p>
>>>
>>>This could also be encoded
>>><p><q type='inscription'>This would be centered all
small caps</q></p>
>>><p>This is normal text <q type='inscription'>Jesus
Christ King of the
>>>Jews</q> and more normal text.</p>
>>>
>>>I have no objection to either model. But there should be one clear
>>>definition of how to do things.
>>>
>>>Mirroring a content model is very easy to do so should not
restrict[...]
>>>choices. We should be aiming for
>>>make OSIS easy for the end user, NOT easy for the programmer, as
a[...]
>>>to strive for.
>>><<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<,
>>>
>>>
>>>
>>>>And a concurrent problem is how do you mark the words of
Christ[...]
>>>>displayed in red?
>>>
>>>There is only a small amount of ambiguity here.  I have always used
<q
>>>who="Jesus">, have seen others use it, and recommend its use. 
The[...]
>>>part is the ambiguous bit, since we haven't actually released any
kind[...]
>>>enumerated biblical cast list.  But personally, I think that if
we[...]
>>>release such a cast list, there's a really good chance that Jesus
will[...]
>>>referred to as "Jesus".  (As opposed or "Christ" or "Christ, Jesus"
or
>>>"Larry".)
>>>
>>>--Chris
>>><<<<<<<<<<<
>>>But is this specified in the spec or documentation? If it is not,
then[...]
>>>are free to choose anything we want. Thus creating many standards.
I[...]
>>>one person say that their organization was in favor of standards,
in[...]
>>>they had LOTS of them.
>>>We only need one good standard.
>>><<<<<<<<<<<<
>>>
>>>
>>>--
>>>To unsubscribe send an email with subject 'unsubscribe' to
>>>osis-user(at)whi.wts.edu.
>>>Please contact klowery(at)whi.wts.edu for questions.
>>>http://127.0.0.1:9673/mailingLists/osis-user/archive/2004/2004-
>>>06/1086372657530/1086395740941
>>>
>>>
>>>
>>>
>>>
>>>--
>>>To unsubscribe send an email with subject 'unsubscribe' to osis-
>>>user(at)whi.wts.edu.
>>>Please contact klowery(at)whi.wts.edu for questions.
>>>http://127.0.0.1:9673/mailingLists/osis-user/archive/2004/2004-
>>>06/1086372657530/1086409697921[...][...]

(My apologies for my clock always being off... need a new laptop... :) )

PS.  I realize different languages have different methods for rendering 
the concept of a quotation.  That's a debate between Steve, Chris, MPJ, 
and others whether or not the actual rendering characters for that 
language should remain in the text.

MY PERSONAL OPINION, as a software engineer who will have to render 
English, Spanish, and Russian documents, is to NOT HAVE TO KNOW how 
these languages render quotes.  I guess this would be in favour of 
leaving the markings in the document, or at least provide hints in the 
tag for software.  I don't think one should have to be a linguist to 
write OSIS software.

	-Troy.



Jim_Albright(at)wycliffe.org wrote:[...][...]
>>>From: Jim_Albright(at)wycliffe.org
[mailto:Jim_Albright(at)wycliffe.org]
>>>Sent: Friday, June 04, 2004 10:28 PM
>>>To: osis-user(at)whi.wts.edu
>>>Subject: Re: [osis-user] USFM \pi --> TE 'Letter Paragraph'
<--OSIS
>>>
>>>Thank you for your comments ....
<<<<<<<<< mine below
>>>
>>>Jim Albright
>>>704 843-0582
>>>Wycliffe Bible Translators
>>>
>>>
>>>
>>>
>>>
>>>
>>>Chris Little <chrislit(at)crosswire.org>
>>>06/04/2004 08:41 PM
>>>Please respond to osis-user
>>>
>>>
>>>       To:     osis-user(at)whi.wts.edu
>>>       cc:
>>>       Subject:        Re: [osis-user] USFM \pi --> TE
'Letter[...]
>>><--OSIS
>>>
>>>
>>>On Fri, 4 Jun 2004 Jim_Albright(at)wycliffe.org wrote:
>>>
>>>
>>>
>>>>enumerated attributes requested
>>>>
>>>><osis:q (at)type='letter'>
>>>>
>>>>This is used in NIV ACT 15, REV 2
>>>
>>>I agree completely that this should be added.  I think I made the
same
>>>suggestion at the last meeting, but it didn't gain any appeal.  I
also
>>>suggested removing the <inscription> element from the Schema
and[...]
>>>it with an "inscription" enumerated type on <q>, since it
simplifies
>>>things considerably (such as needing to mirror the content model
of[...]
>>>
>>><<<<<<<<what was the reason for not
including letter?
>>>
>>><<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
>>>Inscriptions can be inline or formatted as centered text, either
way[...]
>>>are all small caps.
>>>So having an inscription element allows for either formatting.
>>><p><inscription>This would be centered all small[...]
>>>Jews</inscription> and more normal text.</p>
>>>
>>>This could also be encoded
>>><p><q type='inscription'>This would be centered all
small caps</q></p>
>>><p>This is normal text <q type='inscription'>Jesus
Christ King of the
>>>Jews</q> and more normal text.</p>
>>>
>>>I have no objection to either model. But there should be one clear
>>>definition of how to do things.
>>>
>>>Mirroring a content model is very easy to do so should not
restrict[...]
>>>choices. We should be aiming for
>>>make OSIS easy for the end user, NOT easy for the programmer, as
a[...]
>>>to strive for.
>>><<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<,
>>>
>>>
>>>
>>>>And a concurrent problem is how do you mark the words of
Christ[...]
>>>>displayed in red?
>>>
>>>There is only a small amount of ambiguity here.  I have always used
<q
>>>who="Jesus">, have seen others use it, and recommend its use. 
The[...]
>>>part is the ambiguous bit, since we haven't actually released any
kind[...]
>>>enumerated biblical cast list.  But personally, I think that if
we[...]
>>>release such a cast list, there's a really good chance that Jesus
will[...]
>>>referred to as "Jesus".  (As opposed or "Christ" or "Christ, Jesus"
or
>>>"Larry".)
>>>
>>>--Chris
>>><<<<<<<<<<<
>>>But is this specified in the spec or documentation? If it is not,
then[...]
>>>are free to choose anything we want. Thus creating many standards.
I[...]
>>>one person say that their organization was in favor of standards,
in[...]
>>>they had LOTS of them.
>>>We only need one good standard.
>>><<<<<<<<<<<<
>>>
>>>
>>>--
>>>To unsubscribe send an email with subject 'unsubscribe' to
>>>osis-user(at)whi.wts.edu.
>>>Please contact klowery(at)whi.wts.edu for questions.
>>>http://127.0.0.1:9673/mailingLists/osis-user/archive/2004/2004-
>>>06/1086372657530/1086395740941
>>>
>>>
>>>
>>>
>>>
>>>--
>>>To unsubscribe send an email with subject 'unsubscribe' to osis-
>>>user(at)whi.wts.edu.
>>>Please contact klowery(at)whi.wts.edu for questions.
>>>http://127.0.0.1:9673/mailingLists/osis-user/archive/2004/2004-
>>>06/1086372657530/1086409697921[...][...]

In this vain then it would be good to add opening, closing, and 
interrupting markings for each level plus dialogue within the document 
itself. Then the XSLT would just reference which type of quote marker to 
use at the appropriate level. This should include nbsp added to quote 
marker as in French versions.

Jim Albright
704 843-0582
Wycliffe Bible Translators






"Troy A. Griffitts" <scribe(at)crosswire.org>
06/07/2004 12:36 AM
Please respond to osis-user

 
        To:     osis-user(at)whi.wts.edu
        cc: 
        Subject:        Re: [osis-user] USFM \pi --> TE 'Letter Paragraph'
<--OSIS


(My apologies for my clock always being off... need a new laptop... :) )

PS.  I realize different languages have different methods for rendering 
the concept of a quotation.  That's a debate between Steve, Chris, MPJ, 
and others whether or not the actual rendering characters for that 
language should remain in the text.

MY PERSONAL OPINION, as a software engineer who will have to render 
English, Spanish, and Russian documents, is to NOT HAVE TO KNOW how 
these languages render quotes.  I guess this would be in favour of 
leaving the markings in the document, or at least provide hints in the 
tag for software.  I don't think one should have to be a linguist to 
write OSIS software.

                 -Troy.



Jim_Albright(at)wycliffe.org wrote:[...]
". [...]
English. [...]
Paragraph' <--OSIS[...]
[...][...]
>>>From: Jim_Albright(at)wycliffe.org
[mailto:Jim_Albright(at)wycliffe.org]
>>>Sent: Friday, June 04, 2004 10:28 PM
>>>To: osis-user(at)whi.wts.edu
>>>Subject: Re: [osis-user] USFM \pi --> TE 'Letter Paragraph'
<--OSIS
>>>
>>>Thank you for your comments ....
<<<<<<<<< mine below
>>>
>>>Jim Albright
>>>704 843-0582
>>>Wycliffe Bible Translators
>>>
>>>
>>>
>>>
>>>
>>>
>>>Chris Little <chrislit(at)crosswire.org>
>>>06/04/2004 08:41 PM
>>>Please respond to osis-user
>>>
>>>
>>>       To:     osis-user(at)whi.wts.edu
>>>       cc:
>>>       Subject:        Re: [osis-user] USFM \pi --> TE
'Letter[...]
>>><--OSIS
>>>
>>>
>>>On Fri, 4 Jun 2004 Jim_Albright(at)wycliffe.org wrote:
>>>
>>>
>>>
>>>>enumerated attributes requested
>>>>
>>>><osis:q (at)type='letter'>
>>>>
>>>>This is used in NIV ACT 15, REV 2
>>>
>>>I agree completely that this should be added.  I think I made the
same
>>>suggestion at the last meeting, but it didn't gain any appeal.  I
also
>>>suggested removing the <inscription> element from the Schema
and[...]
>>>it with an "inscription" enumerated type on <q>, since it
simplifies
>>>things considerably (such as needing to mirror the content model
of[...]
>>>
>>><<<<<<<<what was the reason for not
including letter?
>>>
>>><<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
>>>Inscriptions can be inline or formatted as centered text, either
way[...]
>>>are all small caps.
>>>So having an inscription element allows for either formatting.
>>><p><inscription>This would be centered all small[...]
>>>Jews</inscription> and more normal text.</p>
>>>
>>>This could also be encoded
>>><p><q type='inscription'>This would be centered all
small caps</q></p>
>>><p>This is normal text <q type='inscription'>Jesus
Christ King of the
>>>Jews</q> and more normal text.</p>
>>>
>>>I have no objection to either model. But there should be one clear
>>>definition of how to do things.
>>>
>>>Mirroring a content model is very easy to do so should not
restrict[...]
>>>choices. We should be aiming for
>>>make OSIS easy for the end user, NOT easy for the programmer, as
a[...]
>>>to strive for.
>>><<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<,
>>>
>>>
>>>
>>>>And a concurrent problem is how do you mark the words of
Christ[...]
>>>>displayed in red?
>>>
>>>There is only a small amount of ambiguity here.  I have always used
<q
>>>who="Jesus">, have seen others use it, and recommend its use. 
The[...]
>>>part is the ambiguous bit, since we haven't actually released any
kind[...]
>>>enumerated biblical cast list.  But personally, I think that if
we[...]
>>>release such a cast list, there's a really good chance that Jesus
will[...]
>>>referred to as "Jesus".  (As opposed or "Christ" or "Christ, Jesus"
or
>>>"Larry".)
>>>
>>>--Chris
>>><<<<<<<<<<<
>>>But is this specified in the spec or documentation? If it is not,
then[...]
>>>are free to choose anything we want. Thus creating many standards.
I[...]
>>>one person say that their organization was in favor of standards,
in[...]
>>>they had LOTS of them.
>>>We only need one good standard.
>>><<<<<<<<<<<<
>>>
>>>
>>>--
>>>To unsubscribe send an email with subject 'unsubscribe' to
>>>osis-user(at)whi.wts.edu.
>>>Please contact klowery(at)whi.wts.edu for questions.
>>>http://127.0.0.1:9673/mailingLists/osis-user/archive/2004/2004-
>>>06/1086372657530/1086395740941
>>>
>>>
>>>
>>>
>>>
>>>--
>>>To unsubscribe send an email with subject 'unsubscribe' to osis-
>>>user(at)whi.wts.edu.
>>>Please contact klowery(at)whi.wts.edu for questions.
>>>http://127.0.0.1:9673/mailingLists/osis-user/archive/2004/2004-
>>>06/1086372657530/1086409697921[...][...]


[...]

I am considering changing this tag in TE to 
Embedded Text Paragraph

Embedded Text is a linguistic term that describes letter, prayer, song, 
and some speeches that are embedded in other text (that interrupt the flow 
of the text) .... usually formatted with left and right indents. As in the 
letters to the 7 churches in REV and Paul's defense in Acts. 

<osis:q (at)type='embeddedText'>

It is legally a type of quote.


Jim Albright
704 843-0582
Wycliffe Bible Translators

Jim,

For the words of Jesus (or anyone else by using a different value for
"who"):
<q who="Jesus">

<speech> also has a "who" attribute as well as the related
<speaker>
element.

At present there is not standardized set of "tokens" for the who
attribute.  

It would be nice to have a language independent "token".

Todd
[...]