LISTSERV mailing list manager LISTSERV 16.5

Help for TEI-L Archives


TEI-L Archives

TEI-L Archives


TEI-L@LISTSERV.BROWN.EDU


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

TEI-L Home

TEI-L Home

TEI-L  January 2007

TEI-L January 2007

Subject:

Re: interesting castlist problem

From:

Julia Flanders <[log in to unmask]>

Reply-To:

Julia Flanders <[log in to unmask]>

Date:

Sun, 28 Jan 2007 16:26:00 -0500

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (67 lines)

Very interesting. My own feeling is that in both cases (the "friends of 
Mathias" and the "twin brothers"), they are clearly role descriptions 
and would be recognized and encoded as such instantly if they were 
presented in the context of an ordinary cast item; the following 
encoding wouldn't raise any eyebrows:

<castItem><role>Walter</role> <roleDesc>friend of 
Mathias</roleDesc></castItem>
<castItem><role>Hans</role> <roleDesc>friend of 
Mathias</roleDesc></castItem>

and in fact if in an introductory TEI class you pointed to the following 
text and asked "so, what is 'friend of Mathias'?"

    Walter, friend of Mathias

you would very much hope for a chorus of students answering "a <roleDesc>!"

So <head> and <trailer> equally puzzle me. From a processing standpoint, 
I would like to imagine that all the role descriptions might be encoded 
alike so that I know where I can grab them. I guess one might answer 
that "within <castGroup>, if there's a <head> or a <trailer>, that's 
where the role description is" but this seems unsatisfying somehow. And 
what if one really did find a text with something resembling a true head 
or trailer inside a cast group?

many thanks--Julia

Michael Beddow wrote:
> I suspect that the impression of abusiveness comes as much from the
> nomenclature as anything else, which I imagine was probably inspired (along
> with <head> which can precede the <castItems>) by the div-like nature of
> this structure. If we look at one of the examples in the body text of P5
> (10.1.4) , we see
> <castGroup rend="braced">
>   <head>friends of Mathias</head>
>   <castItem>
>    <role>Walter</role>
>    <actor>Mr Frank Hall</actor>
>   </castItem>
>   <castItem>
>    <role>Hans</role>
>    <actor>Mr F.W. Irish</actor>
>   </castItem>
>  </castGroup>
>
> The implication of the rend value of "braced" applied to the whole group is
> that the text of the <head> should be rendered in such a way that it visibly
> applies to all the contained <castItem>s. And presumably the same would hold
> good about the rendering of any <trailer> that might be added after the
> <castItem>s, which would take care of the general alignment problem of the
> element ensemble, while remaining agnostic about  specific line-breaks
> within any of the text nodes. My point re nomenclature is that semantically
> (though not in this case particular case syntactically) "friends of Mathias"
> could be construed as a role description, in much the same way as "Twin
> brothers..." could also be interpreted as such. But the Guidelines here show
> that conjoined role description assigned to a <head> And if that is
> legitimate (despite it not being all that much like the content of <head>s
> we find elsewhere) I think there's a parallel case for assigning the "Twin
> Brothers..." to a <trailer>, possibly with some mention, indeed maybe an
> additional example, in the Guidelines, to indicate that it is indeed
> available for such conjoint labelling, all governed by the value of "rend"
> on the enclosing grouping element.
>
> Michael Beddow
>   

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

ATOM RSS1 RSS2



LISTSERV.BROWN.EDU

CataList Email List Search Powered by the LISTSERV Email List Manager