Re: Use of <q> within <rs>

Elisa Beshero-Bondar <[email protected]>
Newsgroups gmane.text.tei.general
Message-ID <CAP1szn5QeynxKuvBCEyw1vKBZOmOUVurfU_3H6111xLHHDdtYA@mail.gmail.com>
Lou: I was thinking that the use of rs looked a little long here, too, but
might make sense in the project. But <rs> with an @type set to "findspot"
seems a lot more precise than to use an <ab> (anonymous block, or "any
arbitrary component-level unit of text"). I can see how an archaeology
project would want to look at referring strings of text associated with
location.

But even if rs is usually something of a shorter phrase, why shouldn't it
contain quoted material? So, for example, what about:

<rs>The town <quote>formerly known as Princeton</quote></rs>?

We can't simultaneously indicated quotation from another source, or the
presence of quotation marks (with <q>) in this. Come to think of it, one of
my student project-teams ran into this problem last year in coding a series
of newspaper articles with quoted dialogue.

Elisa

On Sun, Oct 30, 2016 at 12:55 PM, Lou Burnard <[email protected]>
wrote:

> I think this is quite a strange use of <rs> : the phrases you quote are
> some way away from things like "the village" or "over there" or even "The
> town formerly known as Princeton", in that though they do refer to a
> location, they don't really name it. So (in the absence of a specific
> <findspot> element) I think I'd argue for using an <ab> here, with an
> appropriate type i.e. <ab type="findspot">. In which case <q> and indeed
> <rs> would all be unequivocally available.
>
>
>
>
>  On 30/10/16 16:47, Elisa Beshero-Bondar wrote:
>
> Hello, Scott--
> I was a little surprised to find that <rs> couldn't contain either a <q>
> or (perhaps more precisely here) a <quote> element, but that's so. I
> imagine this is because <rs> is thought to be sitting below the level of
> the quotation marks. As defined in Chapter 3 of the Guidelines, rs
> (referring string) is a "a phrase which refers to some person, place,
> object, etc." So the question is, are your examples of <rs> holding a
> little too much, and should they be sitting inside the <q> elements? In
> your first example, maybe, but in your second example, clearly not--we'd be
> losing referential information about your findspot if we wrapped only
> chalet in the rs.
>
> This is perhaps a good opportunity for a ticket to permit <q> and <quote>
> inside <rs>. What do others think? I'm happy to take this to my colleagues
> on Council.
>
> Best,
> Elisa
>
> On Sun, Oct 30, 2016 at 12:24 PM, Scott Vanderbilt (TEI-L) <
> [email protected]> wrote:
>
>> Is there any particular reason why <q> is not permitted within <rs>?
>>
>> I am attempting to mark-up archaeological findspots that occasionally
>> quote from another text, e.g.:
>>
>>    <rs type="findspot">said to have been found <q>5 km from centre
>>    [of <placeName>Bath</placeName>], near a quarry near a villa</q></rs>
>>
>> and
>>
>>    <rs type="findspot">in excavation, re-used in a fourth-century
>>    <q>chalet</q></rs>
>>
>> However, <rs> does not permit such usage of <q> (or <quote> for that
>> matter), notwithstanding its being defined as "a _general purpose_ name or
>> referring string".
>>
>> Is there some other sanctioned method of accomplishing my goal of
>> distinguishing the quoted text from the passages within which they appear?
>>
>> Thank you.
>>
>
>
>
> --
> Elisa Beshero-Bondar, PhD
> Director, Center for the Digital Text | Associate Professor of English
> University of Pittsburgh at Greensburg | Humanities Division
> 150 Finoli Drive
> Greensburg, PA  15601  USA
> E-mail: [email protected] <[email protected]>
> Development site: http://newtfire.org
>
>
>


-- 
Elisa Beshero-Bondar, PhD
Director, Center for the Digital Text | Associate Professor of English
University of Pittsburgh at Greensburg | Humanities Division
150 Finoli Drive
Greensburg, PA  15601  USA
E-mail: [email protected] <[email protected]>
Development site: http://newtfire.org
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.