TEI-L List

Re: help with superscripts

Paul Schaffner — 2013-06-17T19:04:42-04:00

On Sun, Jun 16, 2013, at 13:10, Lou Burnard wrote:
...
> Then you can make life easier for your linguistic processiong by
> representing e.g. superscript x as
> x (i assume you want the processor to treat this like
> any other x), while still having available ( in the that #xSup
> is pointing to) all that a smart rendering engine will need to use to
> make it look nice.
... [...]

FINAL Call for Nominations: DM Board

Takako Kato — 2013-06-17T17:37:00+01:00

Dear colleagues,

This is a reminder to say that the call for nomination for the DM board
will close on Wed June 19. Please let Orietta Da Rold (odr1@leicester.ac.uk)
and Takako Kato (TakakoKato123@gmail.com) have names of the nominees by
this week Wed.

Thanks and best wishes,
Takako and Orietta

On 6 June 2013 12:36, Takako Kato wrote: [...]

Re: a two-page print in a manuscript edition

Werner Stangl — 2013-06-17T15:37:49+00:00

But beside the issue of @n, which probably should be replaced by @quantity, the other commentators also consider as the way to go?

Btw., there is one more problematic issue considering the structure: There are 4 footnotes in the print, with the notes placed under each column under a decoration line. [...]

Proposal for a change in the TEI governance

Pierazzo, Elena — 2013-06-17T14:40:33+00:00

Dear TEI Community,

This email is rather long, so apologies in advance for this. However, it contains a few rather important points about the way the TEI is proposing to change the way it works, so please spare a couple of minutes to read what follows.

In the past few months the Board of Directors in consultations with the Technical Council has worked on a revision of the TEI governance. We have already shared the below proposal with the TEI members and subscribers and we are now sharing it with the whole community. We will vote on this proposal shortly, [...]

Re: a two-page print in a manuscript edition

Lou Burnard — 2013-06-17T14:56:28+01:00

there is further discussion of this recurrent issue/old chestnut at
http://sourceforge.net/p/tei/bugs/519/

On 17/06/13 14:13, Torsten Schassan wrote:
>> you can extrapolate the number of columns by counting the number of
>> between
>> milestones.
>
> The description in the guidelines varies from
>
> - "marks the point in ... at which a ... begins" (gb)
> - "marks the boundary between" (pb/cb)
> - "marks the start of a new ..." (lb)
>
> Maybe these need to be harmonised?
>
>
> Otherwise we face the old discussions [1] whether a(ny) block level
> element begins [...]

Re: a two-page print in a manuscript edition

Torsten Schassan — 2013-06-17T15:13:57+02:00

> you can extrapolate the number of columns by counting the number of between
> milestones.

The description in the guidelines varies from

- "marks the point in ... at which a ... begins" (gb)
- "marks the boundary between" (pb/cb)
- "marks the start of a new ..." (lb)

Maybe these need to be harmonised? [...]

Re: a two-page print in a manuscript edition

Lou Burnard — 2013-06-17T13:44:07+01:00

On 17/06/13 13:41, Sebastian Rahtz wrote:
> On 17 Jun 2013, at 13:34, Gerrit Brüning
> wrote:
>>>>
>>> this is a very strange way of using @n, to indicate a quantity. It should provide
>>> a label.
>> I agree, but see "Exhibit 1" here:
>> http://accesstei.apexcovantage.com/Content/documents/TEI-Tite_guidelines__1.2_.pdf
>>
> hmm. that's evil. Whatever was Tite thinking when it said
> " with the n attribute (denoting new number of columns) is used to mark
> where a document changes columnar layout"? Surely I am not
> alone in thinking this is a complete abuse of [...]

Re: a two-page print in a manuscript edition

Sebastian Rahtz — 2013-06-17T12:41:35+00:00

On 17 Jun 2013, at 13:34, Gerrit Brüning
wrote:
>>>
>> this is a very strange way of using @n, to indicate a quantity. It should provide
>> a label.
> I agree, but see "Exhibit 1" here:
> http://accesstei.apexcovantage.com/Content/documents/TEI-Tite_guidelines__1.2_.pdf
>

hmm. that's evil. Whatever was Tite thinking when it said
" with the n attribute (denoting new number of columns) is used to mark
where a document changes columnar layout"? Surely I am not
alone in thinking this is a complete abuse of the global @n attribute?

Re: a two-page print in a manuscript edition

Gerrit Brüning — 2013-06-17T14:34:56+02:00

Am 17.06.2013 14:04, schrieb Sebastian Rahtz:
> On 17 Jun 2013, at 12:57, Gerrit Brüning
> wrote:
>
>> Dear Werner, dear Peter,
>>
>> I learned that a change in the number of colums is expressed with , and so on:
>>

>>
>> REMITIDO
>>
> this is a very strange way of using @n, to indicate a quantity. It should provide
> a label.
I agree, but see "Exhibit 1" here:
http://accesstei.apexcovantage.com/Content/documents/TEI-Tite_guidelines__1.2_.pdf [...]

Re: a two-page print in a manuscript edition

Sebastian Rahtz — 2013-06-17T12:04:09+00:00

On 17 Jun 2013, at 12:57, Gerrit Brüning
wrote:

> Dear Werner, dear Peter,
>
> I learned that a change in the number of colums is expressed with , and so on:
>

>
> REMITIDO
>

this is a very strange way of using @n, to indicate a quantity. It should provide
a label. [...]

Re: a two-page print in a manuscript edition

Gerrit Brüning — 2013-06-17T13:57:48+02:00

Dear Werner, dear Peter,

I learned that a change in the number of colums is expressed with
, and so on:

REMITIDO

TILIN TILIN TILIN [Ring, ring, ring]
2 de mayo. Un ave maría por la Marina
Colombiana

...

Peter's

seems dubious to me because I see no new
division of text, but only a change of columnar layout between headings. [...]

Re: help with superscripts

Martin Holmes — 2013-06-17T04:46:35-07:00

On 13-06-17 02:36 AM, Martin de la Iglesia wrote:
> Dear list,
>
> on a related note, I wonder if anyone else has considered using
> @style="vertical-align:super".

That's what we do in several of our projects. We usually combine it with
a font-size setting if that's appropriate.

If absolute precision is required, you could also use something like this: [...]

Re: help with superscripts

Martin de la Iglesia — 2013-06-17T11:36:19+02:00

Dear list,

on a related note, I wonder if anyone else has considered using
@style="vertical-align:super". The CSS specification
()
explicitly says that vertical-align:super has no effect on text size,
and I'm not sure if a reduction of text size is considered essential in
the definition of superscript (if there is consensus in the scholarly
community about the definition, that is). Although the word
"superscript" in itself only implies a higher vertical alignment and not
smaller text size, the two things seem to have become entwined in common
usage of that term. In other words, would you say that
@style="vertical-align:super" conveys [...]

Re: talk about extension to TEI ODD language, and Saxon CE

Sebastian Rahtz — 2013-06-17T08:57:21+00:00

On 16 Jun 2013, at 22:29, "Stuart A. Yeates"
wrote:

>
>
> On page 6 of the talk you mention "equivalences (eg to formal ontologies like FRBR or CIDOC CRM)"
>
> Is there a good link for that?

you might be amused by the talk I gave at the 2011 members meeting
http://tei.oucs.ox.ac.uk/Talks/2011-10-teimm/

Re: US National Archives "Founders Online" powered by TEI

Daniel O'Donnell — 2013-06-16T21:09:04-06:00

But a productive one. Congratulations, David!

On 13-06-16 07:23 PM, David Sewell wrote:
> On Sun, 16 Jun 2013, David Sewell wrote:
>
>> So for now I'll just offer it as one example of the many places where
>> the plays a critical role.
>
> read, "where the TEI"--sorry, long week!

Re: US National Archives "Founders Online" powered by TEI

David Sewell — 2013-06-16T21:23:31-04:00

On Sun, 16 Jun 2013, David Sewell wrote:

> So for now I'll just offer it as one example of the many places where the
> plays a critical role.

read, "where the TEI"--sorry, long week!

US National Archives "Founders Online" powered by TEI

David Sewell — 2013-06-16T21:20:34-04:00

I'd like to share with TEI-L the information that the new Founders Online
website sponsored by the US National Archives (http://founders.archives.gov/),
containing digital versions of ca. 120,000 documents from nearly 200 letterpress
volumes of the papers of six major American founders, is powered on the back end
by TEI encoding. And several members of the TEI community (myself, Tim Finney,
Markus Flatscher, and our editorial assistant Annie Kinniburgh) have been the
lead developers and content manangers. [...]

Re: talk about extension to TEI ODD language, and Saxon CE

Stuart A. Yeates — 2013-06-17T10:04:42+12:00

On Mon, Jun 17, 2013 at 9:55 AM, Lou Burnard
wrote:

> On 16/06/13 22:29, Stuart A. Yeates wrote:
>
> On Mon, Jun 17, 2013 at 8:44 AM, Sebastian Rahtz <
> sebastian.rahtz@it.ox.ac.uk> wrote:
>
>> Following on the recent post about Pure ODD, some may like to look at
>> the talk I gave today at the XML London conference on the subject. It is
>> at http://tei.oucs.ox.ac.uk/Talks/2013-06-london/
>
>
> On page 6 of the talk you mention "equivalences (eg to formal ontologies
> like FRBR or CIDOC CRM)"
>
> Is there a good link for [...]

Re: talk about extension to TEI ODD language, and Saxon CE

Lou Burnard — 2013-06-16T22:55:08+01:00

On 16/06/13 22:29, Stuart A. Yeates wrote:
> On Mon, Jun 17, 2013 at 8:44 AM, Sebastian Rahtz
> > wrote:
>
> Following on the recent post about Pure ODD, some may like to look at
> the talk I gave today at the XML London conference on the subject.
> It is
> at http://tei.oucs.ox.ac.uk/Talks/2013-06-london/
>
>
> On page 6 of the talk you mention "equivalences (eg to formal
> ontologies like FRBR or CIDOC CRM)"
>
> Is there a good link for that?
> [...]

Re: talk about extension to TEI ODD language, and Saxon CE

Stuart A. Yeates — 2013-06-17T09:29:19+12:00

On Mon, Jun 17, 2013 at 8:44 AM, Sebastian Rahtz <
sebastian.rahtz@it.ox.ac.uk> wrote:

> Following on the recent post about Pure ODD, some may like to look at
> the talk I gave today at the XML London conference on the subject. It is
> at http://tei.oucs.ox.ac.uk/Talks/2013-06-london/

On page 6 of the talk you mention "equivalences (eg to formal ontologies
like FRBR or CIDOC CRM)" [...]

talk about extension to TEI ODD language, and Saxon CE

Sebastian Rahtz — 2013-06-16T20:44:36+00:00

Following on the recent post about Pure ODD, some may like to look at
the talk I gave today at the XML London conference on the subject. It is
at http://tei.oucs.ox.ac.uk/Talks/2013-06-london/

Much more experimentally, I was stimulated by a talk from Saxonica
at the same conference to experiment with the Saxon CE setup,
which is the Saxon XSLT processor expressed as Javascript. If you look at
http://tei.oucs.ox.ac.uk/Talks/2013-06-london/talk.html, you'll see the same
talk as above, but this time rendered into HTML using XSLt in the browser.
The rendition is a bit crude (sorry, I was in a hurry), but it was [...]

Re: help with superscripts

Sebastian Rahtz — 2013-06-16T20:21:34+00:00

On 16 Jun 2013, at 21:02, Lou Burnard wrote:

>>>
>> It might help you decide how to mark it up.
>
> Or not. I am not sure what you mean by "explicitly designed to fit at eye level". How do you know how it was designed?

by comparison with the same character elsewhere on the page. they are often quite recognizable. [...]

Re: help with superscripts

Lou Burnard — 2013-06-16T21:02:33+01:00

On 16/06/13 20:55, Sebastian Rahtz wrote:
>
> Carved in stone on my iPad
>
> On 16 Jun 2013, at 20:48, "Lou Burnard" wrote:
>
>> On 16/06/13 20:46, Sebastian Rahtz wrote:
>>> I have difficulty in seeing all superscript as the same. The superscripted "th" in "13th feb" would hardly seem right as two consecutive , but there are plainly other occasions when there s a variant form of a letter which is up in the air. Mathematical superscripts would be better off with a MathML markup.
>> "th" would be a single glyph wouldn't it?
> [...]

Re: help with superscripts

Sebastian Rahtz — 2013-06-16T19:55:17+00:00

Carved in stone on my iPad

On 16 Jun 2013, at 20:48, "Lou Burnard" wrote:

> On 16/06/13 20:46, Sebastian Rahtz wrote:
>> I have difficulty in seeing all superscript as the same. The superscripted "th" in "13th feb" would hardly seem right as two consecutive , but there are plainly other occasions when there s a variant form of a letter which is up in the air. Mathematical superscripts would be better off with a MathML markup.
>
> "th" would be a single glyph wouldn't it?
Um. That way madness lies, surely? You glyphize a phrase based [...]

Re: help with superscripts

Lou Burnard — 2013-06-16T20:48:52+01:00

On 16/06/13 20:46, Sebastian Rahtz wrote:
> I have difficulty in seeing all superscript as the same. The superscripted "th" in "13th feb" would hardly seem right as two consecutive , but there are plainly other occasions when there s a variant form of a letter which is up in the air. Mathematical superscripts would be better off with a MathML markup. [...]

Re: help with superscripts

Sebastian Rahtz — 2013-06-16T19:46:53+00:00

I have difficulty in seeing all superscript as the same. The superscripted "th" in "13th feb" would hardly seem right as two consecutive , but there are plainly other occasions when there s a variant form of a letter which is up in the air. Mathematical superscripts would be better off with a MathML markup. [...]

Re: help with superscripts

Lou Burnard — 2013-06-16T18:10:50+01:00

My recommendation, if you want consistency, would be to use for all
superscripts, and define an appropriate set of s

Then you can make life easier for your linguistic processiong by
representing e.g. superscript x as
x (i assume you want the processor to treat this like
any other x), while still having available ( in the that #xSup
is pointing to) all that a smart rendering engine will need to use to
make it look nice. [...]

Re: help with superscripts

Julia Flanders — 2013-06-16T13:02:54-04:00

The WWP uses the @rend option, including superscript information as part of a rendition ladder:

th

and so forth. But I don't know whether this gets us optimal layout results; superscripts are not very extensively used in our texts, and those texts present other even more challenging layout problems, so our expectations may not be very high :-) [...]

Re: help with superscripts

Syd Bauman — 2013-06-16T13:02:36-04:00

For WWO we use rendition (i.e., rend=, rendition=, , or
style=) on an element, never the Unicode code-point directly.

> How do people handle superscripted characters in TEI-encoded texts?
> I ask this question in the context of a project to provide
> linguistically annotated versions EEBO-TCP texts. In a more
> consistent universe there would either be no Unicode superscripted
> characters or there would be a whole alphabet. As it is, there is a
> consistent set of the numbers 0-9, a patched-together lower-case
> alphabet that lacks the letter 'q', whose members are drawn from
> different [...]

help with superscripts

Martin Mueller — 2013-06-16T16:28:42+00:00

How do people handle superscripted characters in TEI-encoded texts? I ask this question in the context of a project to provide linguistically annotated versions EEBO-TCP texts. In a more consistent universe there would either be no Unicode superscripted characters or there would be a whole alphabet. As it is, there is a consistent set of the numbers 0-9, a patched-together lower-case alphabet that lacks the letter 'q', whose members are drawn from different ranges, and don't always play together nicely from a layout perspective. [...]

Cross referencing readings

António Rito Silva — 2013-06-15T12:05:58+01:00

Dear All,

In our project we are encoding both authorial and editorial witnesses and we'd appreciate your advise in the following cases (somehow related):

~~bem~~
certo

certo

In this encoding it is not explicit (we don't want to do a string compare in the software we are developing) the decision of the editors (Fr1.WIT.MS is an authorial witness and Fr1.WIT.ED1 and Fr1.WIT.ED2 are editorial witnesses). [...]

Re: [ann] oXygen XML Editor version 15

George Cristian Bina — 2013-06-14T08:34:37+03:00

Hi all,

I just want to mention that you may be interested to know also that we
made available starting with version 15 also a subscription option for
the Academic license:

" XML Editor Academic 12-month Subscription"
USD 59
http://www.oxygenxml.com/buy_subscription_a12_editor.html

Best Regards,
George

Re: Colons in CSS vs TEI

Ondine LeBlanc — 2013-06-13T20:14:54+00:00

Thanks, Radu--it worked!

-----Original Message-----
From: TEI (Text Encoding Initiative) public discussion list [mailto:TEI-L@LISTSERV.BROWN.EDU] On Behalf Of Radu Coravu
Sent: Thursday, June 13, 2013 10:23 AM
To: TEI-L@LISTSERV.BROWN.EDU
Subject: Re: Colons in CSS vs TEI

Hi Ondine,

We provide a CSS for editing TEI out of the box but I guess you want to customize it.

In your CSS after all the imports you add this declaration: [...]

Re: Colons in CSS vs TEI

Ondine LeBlanc — 2013-06-13T14:33:33+00:00

Thank you, Radu. I will give it a try.

Best,
O.

-----Original Message-----
From: TEI (Text Encoding Initiative) public discussion list [mailto:TEI-L@LISTSERV.BROWN.EDU] On Behalf Of Radu Coravu
Sent: Thursday, June 13, 2013 10:23 AM
To: TEI-L@LISTSERV.BROWN.EDU
Subject: Re: Colons in CSS vs TEI

Hi Ondine,

We provide a CSS for editing TEI out of the box but I guess you want to customize it. [...]

Re: Colons in CSS vs TEI

Radu Coravu — 2013-06-13T17:23:07+03:00

Hi Ondine,

We provide a CSS for editing TEI out of the box but I guess you want to
customize it.

In your CSS after all the imports you add this declaration:

> @namespace xml "http://www.w3.org/XML/1998/namespace";

and then in the CSS selector you match a certain attribute or attribute
value on an element like this:

> abbr[xml|id='someValue']{
> content:"abcdef";
> } [...]

Colons in CSS vs TEI

Ondine LeBlanc — 2013-06-13T14:16:40+00:00

Hi all--

I have written some CSS to display a TEI document in the Author view in oXygen.

Despite being able to do such a thing, my ability to write CSS is pretty rudimentary, and there is one bit that I can't get to work well: allowing for a colon in the attribute xml:id. The CSS seems not to allow it. [...]

Re: a two-page print in a manuscript edition

Peter Stadler — 2013-06-13T14:50:07+02:00

Hi Werner,

what about nesting

s? That way you can distinguish between text in columns and the "wrapper" text (and the headings fit nicely, too):

REMITIDO

TILIN TILIN TILIN [Ring, ring, ring]
2 de mayo. Un ave maría por la Marina Colombiana

...

All the best
Peter

Am 13.06.2013 um 10:25 schrieb Werner Stangl : [...]

a two-page print in a manuscript edition

Werner Stangl — 2013-06-13T08:25:33+00:00

Hi all,

I'm working on a manuscript edition of letters. I'm an auto-didact, so my understanding of the TEI-paradigm is very much concentrated on the necessities of my corpus.
Now, one of my letters had a political news print as attachment, which troubles me much for being an odd case. I have no experience how to mark it up.
My common practice is to put envelopes and attachment notes as separate

s in the . So, the print is something like

.
Now, the print has a centered one word title (REMITIDO), and below text in two columns. [...]

[ann] oXygen XML Editor version 15

Radu Coravu — 2013-06-13T10:55:02+03:00

Hi all,

I am happy to announce that a new version of oXygen XML Editor is
available from our website:
http://www.oxygenxml.com

For the complete list of new additions and
more details please see:

http://www.oxygenxml.com/index.html#new-version

Here are some specific features the TEI community might find useful:

1) The tooltip documentation which appears when hovering over TEI XML
tags or in content completion window for each element now contains a
link to the TEI Guidelines which shows precisely the definition of that
particular element. This is also available when hovering attributes in
the Attributes view.
In order to click the link the [...]

CFP: Practical Experiences with CIDOC CRM and its Extensions (CRMEX)

Øyvind Eide — 2013-06-11T08:32:51+02:00

Dear all,

It would be great to have text encoding as one of the implementation types for this workshop.

CALL FOR PAPERS
Practical Experiences with CIDOC CRM and its Extensions (CRMEX)
http://www.ontotext.com/CRMEX
26th September 2013 in Valetta, Malta

A workshop affiliated with the 17th International Conference on Theory and Practice of Digital Libraries (TPDL 2013)
http://www.tpdl2013.info/

Background and Objectives
The CIDOC CRM (international standard ISO 21127:2006) is a conceptual model and ontology with a fundamental role in many data integration efforts in the Digital Libraries and Cultural Heritage (CH) domain. It has spawned various CRM-compliant extensions, such as: [...]

2nd Call for Participation: CAMP-4-DATA Workshop @ DC-2013

DCMI Announce — 2013-06-10T09:19:23-07:00

*Apologies for cross-posting*

=== *2nd Call for Participation: CAMP-4-DATA Workshop @ DC-2013* ===

Dublin Core-Science and Metadata Community and Research Data Alliance are
hosting a day-long Metadata Interest Group workshop, CAMP-4-DATA, on Sept.
6, 2013 in Lisbon, Portugal. The workshop is part of DC-2013. Submissions
for participation are currently open in the areas of short papers,
abstracts, and position statements. The intent of this workshop is to
discuss and forward challenges and opportunities relating to metadata
standards for the management of scientific data, and how policies,
applications, and infrastructure can foster creation of and access to
sustainable, open, and collective [...]

10 Days left to book: Digital.Humanities @ Oxford Summer School 2013

James Cummings — 2013-06-10T17:06:50+01:00

(apologies for cross posting; please forward to anyone interested)

*Only 10 days left to book!*

Places for this year's Digital.Humanities @ Oxford Summer School
are filling up already, so book your place soon! Visit
http://digital.humanities.ox.ac.uk/dhoxss/2013/ for more information.

If you are awaiting the results of local funding and want to to
see whether your chosen workshop is almost full, email
courses@it.ox.ac.uk to find out! [...]

DC-2013/iPRES-2013 registration is now open!

DCMI Announce — 2013-06-09T15:43:14-07:00

*Apologies for cross-posting*

=== DC-2013/iPRES 2013 INVITATION TO REGISTER ===

Registration for DC-2013 --Linking to the Future-- is now open. The
conference will take place 2-6 September 2013 in Lisbon, Portugal. The
conference website: http://purl.org/dcevents/dc-2013.

The DC-2013 conference theme explores questions regarding the persistence,
maintenance, and preservation of metadata and descriptive vocabularies. The
need for stable representations and descriptions spans all sectors
including cultural heritage and scientific data, eGovernment, finance and
commerce. In addition to the theme, presentations and discussion will cover
a broad range of topics on innovation in metadata design and practice. [...]

ProDoc@DocEng -- Doctoral consortium deadline extension

Tamir Hassan (DocEng13) — 2013-06-10T00:12:26+02:00

Just to let you know that the deadline for submissions to ProDoc@DocEng,
the Doctoral Consortium to be held at the ACM Symposium on Document
Engineering (DocEng 2013), September 10-13 in Florence, Italy, has been
extended to June 28.

ProDoc@DocEng will take place during the Symposium and is an excellent
opportunity for doctoral students to present their dissertation project
and receive feedback from a panel of senior researchers as well as from
the general audience. [...]

Re: characters per scene - how to encode?

Andreas Triantafillidis — 2013-06-09T11:28:25+03:00

of course, triples!

Thanks Sebastian and Lou (still no "interoperability vs tei argument")

Sent from my iPad

On 9 Ιουν 2013, at 12:43 π.μ., Sebastian Rahtz wrote:

>> On 8 Jun 2013, at 22:11, Lou Burnard wrote:
>>
>>>> You could use the "relation" element to link a person to a scene, in my opinion. Others may disagree.
>>>
>>> What's wrong with generic ?
>>>
>>> Assuming S1 identifies a scene in which P1 and P2 both appear
>>>
>>>
>>>
>>>
>>>
>
> Though note [...]

Re: characters per scene - how to encode?

Sebastian Rahtz — 2013-06-08T21:43:31+00:00

> On 8 Jun 2013, at 22:11, Lou Burnard wrote:
>
>>> You could use the "relation" element to link a person to a scene, in my opinion. Others may disagree.
>>
>> What's wrong with generic ?
>>
>> Assuming S1 identifies a scene in which P1 and P2 both appear
>>
>>
>>
>>
>> [...]

Re: characters per scene - how to encode?

Sebastian Rahtz — 2013-06-08T21:17:20+00:00

On 8 Jun 2013, at 22:11, Lou Burnard wrote:

>> You could use the "relation" element to link a person to a scene, in my opinion. Others may disagree.
>
> What's wrong with generic ?
>
> Assuming S1 identifies a scene in which P1 and P2 both appear
>
>
>
>
> [...]

Re: characters per scene - how to encode?

Lou Burnard — 2013-06-08T22:11:48+01:00

On 08/06/13 21:25, Sebastian Rahtz wrote:
> You could use the "relation" element to link a person to a scene, in my opinion. Others may disagree.

What's wrong with generic ?

Assuming S1 identifies a scene in which P1 and P2 both appear

Re: characters per scene - how to encode?

Sebastian Rahtz — 2013-06-08T20:25:09+00:00

You could use the "relation" element to link a person to a scene, in my opinion. Others may disagree.

You list of names inside a note is fine, for humans reading it, and for your ad hoc processing. For interoperability, I would say its weak.

(We haven't had an interoperability vs tei argument for weeks and weeks now...) [...]

characters per scene - how to encode?

Andreas Triantafillidis — 2013-06-08T23:02:32+03:00

hello

I'd like to encode the presence of characters within scenes in a novel or similar type work (I don't mind if they actually talk, act, or whatever, I just care that they are in the particular "scene"). I am thinking of -roughly- the following approach:

- list all persons in header or front/back-matter (with xml:id)
- mark "scenes" using

- add list of persName (or similar) in

Re: The Rabat Genizah Project - TEI header

Oren Kosansky — 2013-06-07T12:48:12-07:00

Thanks to everyone who has responded to my query!

The feedback is much appreciated and hugely helpful.

I've received important pointers on specific aspects of the header. I'd
also be interested to know if anyone has used the TEI plugin for Omeka
and/or dealt with the relationship between TEI and DCMI.

Again, thanks.

Oren

On Fri, Jun 7, 2013 at 10:01 AM, Saašha Metsärantala wrote: [...]

Re: The Rabat Genizah Project - TEI header

Saašha Metsärantala — 2013-06-07T19:01:25+02:00

Hello!

The TEI document has a language element with an @ident attribute with a
value of "other". According to
http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-language.html this
should be:

> language code constructed as defined in BCP 47

For better expandability and portability (especially to other parts of the
huge XML world), I would suggest a higher granularity and the use of
either mis, mul, und, zxx and / or the qaa-qtz zone (all of these being
defined in RFC-5646) instead of "other". [...]

Re: The Rabat Genizah Project - TEI header

Kevin Hawkins — 2013-06-07T12:35:33-04:00

Hello Oren,

Instead of using type= on , I suggest calendar=.

Your use of is interesting. I recommend not including ...

http://www.iana.org/assignments/language-subtag-registry

... because the TEI itself says to use BCP 47 for the values of
xml:lang= and ident=, so you don't need to specify the source for these
values. (Furthermore, if you ever begin using a script subtag or
regional subtag, you will end up going beyond what is documented at
http://www.iana.org/assignments/language-subtag-registry .) [...]

2013 DARIAH-DE International Digital Humanities Summer School

Munson, Matthew — 2013-06-07T12:55:26+00:00

Dear TEI-Lers,

We have had an excellent response to our call for applications to the 2013 DARIAH-DE International Digital Humanities Summer School. There are still a few spaces available and the application deadline is next Friday, June 14. You can find more information about the summer school and how to apply here: http://www.gcdh.de/en/events/calendar-view/2013-dariah-de-international-digital-humanities-summer-school/. [...]

I: Call for Papers DH-CASE 2013 - Extended deadlines and ACM conference proceedings

Francesca Tomasi — 2013-06-07T12:31:31+02:00

*apologies for cross posting*

Re: The Rabat Genizah Project - TEI header

stuart yeates — 2013-06-07T08:54:42+12:00

In relation to you names (, , etc) I strongly suggest<br>that you link these to an authority list of some description, because in<br>a multi-lingual context there will be little textual consistency to the<br>names due to translation, different scripts, etc. There are a number of<br>different approaches to this, depending on where you authority<br>information is stored and how systematic you want to be. [...] </article> <article> <h1>The Rabat Genizah Project - TEI header</h1> <p>Oren Kosansky — 2013-06-06T13:13:50-07:00</p> Hello,<br><br>I am leading a project that involves the encoding of multilingual documents<br>from Morocco. Having initially consulted with several people familiar with<br>TEI, I am posting here to invite broader feedback on our working TEI<br>template (see attached).<br><br>By way of brief introduction, here are some aspects of The Rabat Genizah<br>Project:<br><br>1) The project works with assorted documents - including published works,<br>ephemera, and manuscripts - collected by the Jewish community of Rabat,<br>Morocco at the beginning of the twenty-first century. The collection<br>includes materials in French, Hebrew, Judeo-Arabic, English, Spanish, and<br>Arabic dating from the 18th century [...] </article> <article> <h1>Call for Nominations: DM Board</h1> <p>Takako Kato — 2013-06-06T11:36:11+00:00</p> Dear colleagues,<br><br>Digital Medievalist will be holding elections at the end of June for four<br>positions to its Executive Board. Board positions are for two year terms<br>and incumbents may be re-elected (for a maximum of three terms in a row).<br>Members of the Board are responsible for the overall direction of the<br>organisation and leading the Digital Medievalist's many projects and<br>programmes. This is a working board, and so it would be expected that you<br>are willing and able to commit a little bit of time to helping Digital<br>Medievalist undertake some of its activities<br>(such as helping to [...] </article> <article> <h1>Re: quote extraction</h1> <p>Vincent Jolivet (Algone) — 2013-06-05T12:45:44+02:00</p> Thanks a lot for all your very useful answers. Following your advice, I will use <seg> rather than the <span> tag (it's already in our schemas) and choose the second solution (tag the entire passage as <quote> and mark off the comments), for all the good reasons explained by Paul (because of our incremental process of tagging, the @next/@prev solution is difficult to implement). I would add a fifth argument to his message, which is that this solution seems to be much easier to process in order to extract the quotations. [...] </article> <article> <h1>Re: quote extraction</h1> <p>Paul F. Schaffner — 2013-06-04T16:44:26-04:00</p> Given the two choices (to tag only the quotation as q/quote), or to tag<br>the entire passage as q/quote and then mark off the bits that aren't<br>really quoted), I can think of four circumstances at the moment that<br>might incline me to do the latter:<br><br>(1) if the source renders the entire passage distinctively, i.e.<br>if the narrative interpositions are caught up in the rendering of<br>the quotation (as, for example in many types of 'blcck quotation'),<br>it might be more desirable to tag the entire blcok as <quote>,<br>since the entire blcck is rendered together. [...] </article> <article> <h1>Re: mapping TEI header to FRBRoo</h1> <p>Stuart A. Yeates — 2013-06-05T08:28:10+12:00</p> I'm looking at FRBRoo, but have recently been doing some work in BIBFRAME<br>(which is the new MARC). To be honest I'm close to the point of giving up<br>on BIBFRAME, since they are duplicating the work / item structure of MARC<br>rather than sacrifice round-trip interoperability. I have a worked example<br>with some NZETC docs on the TEI wiki (already a little out of date, I fear): [...] </article> <article> <h1>Re: quote extraction</h1> <p>Frederik Elwert — 2013-06-04T22:10:33+02:00</p> Dear Vincent,<br><br>> On 04/06/13 11:28, Vincent Jolivet (Algone) wrote:<br>> > Dear all,<br>> ><br>> > In a large set of critical literature, we need to extract all the quotations. For this purpose we use <quote> and <cit> elements.<br>> > Such a aim looks easy but a quote is often interrupted by a comment, which prevents extracting this quote precisely:<br>> > What is the best way to encode the following quote, in order to extract this quote only (we need to exclude "disait Térence")?<br>> > "Homo sum, disait Térence, et nil humani a me alienum [...] </article> <article> <h1>Re: quote extraction</h1> <p>Lou Burnard — 2013-06-04T18:15:26+01:00</p> On 04/06/13 11:28, Vincent Jolivet (Algone) wrote:<br>> Dear all,<br>><br>> In a large set of critical literature, we need to extract all the quotations. For this purpose we use <quote> and <cit> elements.<br>> Such a aim looks easy but a quote is often interrupted by a comment, which prevents extracting this quote precisely:<br>> What is the best way to encode the following quote, in order to extract this quote only (we need to exclude "disait Térence")?<br>> "Homo sum, disait Térence, et nil humani a me alienum puto"<br>><br>> Is this encoding relevant ?<br>> [...] </article> <article> <h1>Re: quote extraction</h1> <p>Paul Flo Williams — 2013-06-04T15:06:52+01:00</p> Vincent Jolivet (Algone) wrote:<br>><br>> What is the best way to encode the following quote, in order to extract<br>> this quote only (we need to exclude "disait Térence")?<br>> "Homo sum, disait Térence, et nil humani a me alienum puto"<br>><br>> Is this encoding relevant ?<br>> -> <quote>Homo sum<span ana="exquote">, disait Térence,</span> et nil<br>> humani a me alienum puto</quote> [...] </article> <article> <h1>Re: quote extraction</h1> <p>James Cummings — 2013-06-04T13:35:04+01:00</p> Hi Vincent,<br><br>I think the general approach should be fine. (I would recommend<br>the <seg> element instead of <span> here though, and your @ana<br>value you be a pointer pointing to a description of 'exquote'...<br>you might just need a @type.<br><br>So something like:<br><quote>Homo sum<seg type="exquote">, disait Térence,</seg> et nil<br>humani a me alienum puto</quote><br><br>Or you could do the reverse, marking the parts of the quote with<br><said>:<br><quote><said>Homo sum</said>, disait Térence, <said>et nil humani<br>a me alienum puto</said></quote> [...] </article> <article> <h1>quote extraction</h1> <p>Vincent Jolivet (Algone) — 2013-06-04T12:28:27+02:00</p> Dear all,<br><br>In a large set of critical literature, we need to extract all the quotations. For this purpose we use <quote> and <cit> elements.<br>Such a aim looks easy but a quote is often interrupted by a comment, which prevents extracting this quote precisely:<br>What is the best way to encode the following quote, in order to extract this quote only (we need to exclude "disait Térence")?<br>"Homo sum, disait Térence, et nil humani a me alienum puto" [...] </article> <article> <h1>mapping TEI header to FRBRoo</h1> <p>Sebastian Rahtz — 2013-06-04T10:04:39+00:00</p> I confess that I should know this already, so apologies. But who has done<br>specific mapping from elements in the TEI header to classes and properties in<br>FRBRoo? I want to extend the work done in stylesheets on TEI to RDF to<br>cover more elements, but of course other people have most likely<br>invented those wheels. </article> <article> <h1>Open Repositories 2013, July 8-12 - Book Now!</h1> <p>Mark Leggott — 2013-06-03T16:12:37-03:00</p> The premiere conference for digital repositories is being held in Charlottetown PEI, July 8-12. I encourage you to register and book your accommodation as soon as possible so you can join your colleagues for a week of stimulating discussion. The full schedule of events is now online and we have 2 great keynotes: [...] </article> <article> <h1>Re: Coding advice</h1> <p>Paul F. Schaffner — 2013-06-03T11:24:47-04:00</p> There is, I suspect, considerable variation in the interpretation<br>and application of <label> (one of those early-strata vaguely defined<br>elements that have had a long time to 'drift.'). Locally, I think that<br>we would resist an interpretation broad enough to include just any kind<br>of label. We interpret it roughly as a floating head: i.e., it is<br>a word or phrase that 'heads' or labels its context, usually the element<br>in which it appears, or the text that immediately follows it. So<br>we would use it basically in three situations, all of which are<br>sanctioned by the examples in the [...] </article> <article> <h1>Re: Coding advice</h1> <p>Lou Burnard — 2013-06-02T17:51:15+01:00</p> Yes and no. I don't see why both kinds of "proposition A" s shouldnt be<br>tagged as a label. However, I agree with Kevin that <ref> would probably<br>be more useful!<br><br>On 02/06/13 15:29, Kevin Hawkins wrote:<br>> I think Lou is interpreting Jeffrey's description different from the<br>> others who have responded so far.<br>><br>> I think Lou imagines something like this in the source document:<br>><br>> Proposition A: The present king of France lives at the Elysee Palace.<br>><br>> Here, "Proposition A" is probably best tagged as <label>.<br>><br>> On the other hand, I [...] </article> <article> <h1>Re: Coding advice</h1> <p>Kevin Hawkins — 2013-06-02T10:29:27-04:00</p> I think Lou is interpreting Jeffrey's description different from the<br>others who have responded so far.<br><br>I think Lou imagines something like this in the source document:<br><br>Proposition A: The present king of France lives at the Elysee Palace.<br><br>Here, "Proposition A" is probably best tagged as <label>.<br><br>On the other hand, I think the others assume something like this in the<br>source document: [...] </article> <article> <h1>more TEI XSL stylesheets (release 6.32)</h1> <p>Sebastian Rahtz — 2013-06-01T18:43:21+00:00</p> following on Tomas' notes about docx to TEI, I will note that I just tidied up and did another release of the TEI stylesheet<br>family, with all of the fixes to docx to TEI up to date (stimulated by Tomas' requests; though I have not managed to meet<br>all of them).<br><br>more importantly, if you use this XSL to make LaTeX from TEI XML, you'll get a shock - they<br>now generate more standard LaTeX markup, in that the characters ^$_{}\#% which are MAGIC<br>in normal TeX, are now MAGIC again in the output. Previously, I had set them to [...] </article> <article> <h1>Re: docx2tei</h1> <p>Sebastian Rahtz — 2013-06-01T15:35:15+00:00</p> On 1 Jun 2013, at 10:53, Tomaz Erjavec <tomaz.erjavec@IJS.SI> wrote:<br><br>> True again, but with tei: styles on paragraphs and spans you can mark quite a lot TEI elements in Word.<br>> Again, the idea is that the author can't be bothered to learn XML, but is willing to put extra annotation in their book for a good cause but in the environment they are used to, i.e. Word. Then comes along the editor (so far, mostly Matija) who can do fixes and additions in the XML, and/or I run some stylesheet over it to e.g. tie together the diplomatic [...] </article> <article> <h1>Re: Coding advice</h1> <p>Sebastian Rahtz — 2013-06-01T13:34:12+00:00</p> it strikes me as a <name> mostly; which is more specific than <rs>, so to be preferred if it fits.<br><br><label>, Lou? isn't that normally used in association with some other part of the text (eg in a label/item pair)? I don't<br>see it in this context. </article> <article> <h1>Re: docx2tei</h1> <p>Tomaz Erjavec — 2013-06-01T11:53:36+02:00</p> Hi,<br>>> http://nl.ijs.si/tei/convert/<br>> It's really great to see someone else pushing this along.<br>Well, I'm lucky to have people that actually find this useful and have projects to support the development.<br><br>>Lou Burnard for the Agora project has also done quite a lot which is worth looking at.<br>Did already have a look, and there's lots of interesting tricks there, and in other profiles.<br>The problem I see with the current profiles is that they were made for very particular projects and that they don't seem to be documented. Which is what I'd like to do, i.e. make a [...] </article> </main></body></html>