TEI-L List

Re: can a corpus have a facsimile?

Sebastian Rahtz — Thu, 23 May 2013 16:29:23 +0000

On 23 May 2013, at 17:23, Martin Holmes
wrote:

>
> But should it also allow sourceDoc or fsdDecl, like this?
>
> element teiCorpus
> {
> att.global.attributes,
> att.global.linking.attributes,
> att.global.analytic.attributes,
> att.global.facs.attributes,
> att.global.change.attributes,
> attribute version { data.version }?,
> ( teiHeader, model.resourceLike, (TEI | teiCorpus )+ )
> }
>
> The same arguments apply as for facsimile, surely?
>

yes, definitely. use model.resourceLike. I don't think
there will be any knock-on effects.

Re: can a corpus have a facsimile?

Martin Holmes — Thu, 23 May 2013 09:23:49 -0700

+1 from me too. It would presumably go from:

element teiCorpus
{
att.global.attributes,
att.global.linking.attributes,
att.global.analytic.attributes,
att.global.facs.attributes,
att.global.change.attributes,
attribute version { data.version }?,
( teiHeader, ( TEI | teiCorpus )+ )
}

to

element teiCorpus
{
att.global.attributes,
att.global.linking.attributes,
att.global.analytic.attributes,
att.global.facs.attributes,
att.global.change.attributes,
attribute version { data.version }?,
( teiHeader, facsimile, (TEI | teiCorpus )+ )
}

But should it also allow sourceDoc or fsdDecl, like this?

element teiCorpus
{
att.global.attributes,
att.global.linking.attributes,
att.global.analytic.attributes,
att.global.facs.attributes,
att.global.change.attributes,
attribute version { data.version }?,
( teiHeader, model.resourceLike, (TEI | teiCorpus )+ )
} [...]

Re: can a corpus have a facsimile?

Gabriel Bodard — Thu, 23 May 2013 11:14:14 -0400

That sounds eminently sensible to me. We explicitly sanction the use of
'facsimile' to encode images of objects and settings, not necessarily
just the text-bearing part of them, so a facsimile of a corpus is
absolutely as appropriate as a facsimile of a monument bearing several
inscriptions, a folder containing many documents, or an anthology
collecting multiple novels... [...]

can a corpus have a facsimile?

Sebastian Rahtz — Thu, 23 May 2013 14:46:21 +0000

I find myself in a position where i have element and want to have a
child. Why, you ask? because I have 2500 gravestones, which are "documents" in their
own right, so I have them as a each; but I also have a plan of the whole cemetery which
I represent as a with nice s and s. I want to wrap them all up together. [...]

Re: encoding choices for a particular document in ?

Andreas Triantafillidis — Thu, 23 May 2013 16:04:20 +0300

> If you want to document down to this level, which I hope you do, then the place for it is your project-specific ODD!

i was hoping you wouldn't send me down the ODD path just yet :) Do you suggest a specific starting point for a complete newbie like myself? [...]

Re: encoding choices for a particular document in ?

Lou Burnard — Thu, 23 May 2013 13:58:42 +0100

If you want to document down to this level, which I hope you do, then
the place for it is your project-specific ODD!

On 23/05/13 13:57, Andreas Triantafillidis wrote:
> hi laurent
>
>> tagUsage is the perfect tool for this, isn't it?
> it would seem so, but how would i go about describing more complex element+attribute cases (ie

) or even moreso nested element and attribute templates?
>
> thanks btw
>
>
>> Laurent
>>
>> Le 23 mai 2013 à 14:07, Andreas Triantafillidis a écrit :
>>
>>> hi
>>>
>>> we would like [...]

Re: encoding choices for a particular document in ?

Lou Burnard — Thu, 23 May 2013 13:57:23 +0100

is for recording your *actual usage* of TEI elements. It
isn't the place for an explanatory essay saying why you chose to
use rather than for example.

Discussion of your editorial principles, choices, praxis does seem to
belong rather in

On 23/05/13 13:11, Laurent Romary wrote:
> tagUsage is the perfect tool for this, isn't it?
> Laurent
>
> Le 23 mai 2013 à 14:07, Andreas Triantafillidis a écrit :
>
>> hi
>>
>> we would like to document, within each file, the choices we make regarding usage of TEI elements and attributes. Sometimes we [...]

Re: encoding choices for a particular document in ?

Andreas Triantafillidis — Thu, 23 May 2013 15:57:06 +0300

hi laurent

> tagUsage is the perfect tool for this, isn't it?

it would seem so, but how would i go about describing more complex element+attribute cases (ie

) or even moreso nested element and attribute templates?

thanks btw

> Laurent
>
> Le 23 mai 2013 à 14:07, Andreas Triantafillidis a écrit :
>
>> hi
>>
>> we would like to document, within each file, the choices we make regarding usage of TEI elements and attributes. Sometimes we even would like to list TEI alternatives for encoding the same thing, and why we chose one over [...]

Re: encoding choices for a particular document in ?

Laurent Romary — Thu, 23 May 2013 14:11:37 +0200

tagUsage is the perfect tool for this, isn't it?
Laurent

Le 23 mai 2013 à 14:07, Andreas Triantafillidis a écrit :

> hi
>
> we would like to document, within each file, the choices we make regarding usage of TEI elements and attributes. Sometimes we even would like to list TEI alternatives for encoding the same thing, and why we chose one over the others
>
> these are really meant for editors and developers so I suppose it would be better to store in the header (they are in no way part of body)
>
> i'm thinking [...]

encoding choices for a particular document in ?

Andreas Triantafillidis — Thu, 23 May 2013 15:07:40 +0300

hi

we would like to document, within each file, the choices we make regarding usage of TEI elements and attributes. Sometimes we even would like to list TEI alternatives for encoding the same thing, and why we chose one over the others

these are really meant for editors and developers so I suppose it would be better to store in the header (they are in no way part of body) [...]

Re: placeName types

Tom Elliott — Tue, 21 May 2013 10:02:43 -0500

Thanks Stuart, will do.

Tom Elliott, Ph.D.
Associate Director for Digital Programs and Senior Research Scholar
Institute for the Study of the Ancient World (NYU)
http://isaw.nyu.edu/people/staff/tom-elliott

On May 20, 2013, at 4:05 PM, stuart yeates wrote:

> On 21/05/13 08:32, Tom Elliott wrote:
>
>> Does one file a bug?
>
> I would encourage you to file a bug, preferably with an exemplar which contrasts with the existing exemplars in the standard.
>
> cheers
> stuart
> --
> Stuart Yeates
> Library Technology Services http://www.victoria.ac.nz/library/

Blackwell Companion to Digital Literary Studies

Susan Schreibman — Tue, 21 May 2013 14:15:12 +0100

The editors of The Companion to Digital Literary Studies, first published
by Blackwell in 2008, are pleased to announce that it has just been
released in paperback.

At $49.95, €36.00, and £29.99, it is now affordable for classroom use. Its
31 chapters -- ranging from ePhilology to e-Literature, from digital
poetry to cybertextuality -- are as provocative and pertinent now as when
the volume was first released. TEI is covered in many chapters. [...]

ProDoc@DocEng 2013: Call for Submissions to the Doctoral Consortium

Tamir Hassan (DocEng13) — Tue, 21 May 2013 13:22:02 +0200

Full message available at: ProDoc@DocEng 2013: Call for Submissions to the Doctoral Consortium

Re: placeName types

Tomaz Erjavec — Tue, 21 May 2013 10:01:15 +0200

Dear Thomas, all,
thanks for the suggestions - I personally am convinced now that we should indeed extract the places and have them, with geo, and, preferably, pointers to geonames and Wikipedia, stored separately.
However, as I said, we are now only putting together a first prototype, where we hoped we could get away with being a bit sloppy - extracting and merging the placeNames will be a bit of work, some of the names are quite structured, in several languages, historical spellings, etc.
Btw, the current set of coordinates we have were extracted from Google - the reason was [...]

Re: placeName types

stuart yeates — Tue, 21 May 2013 09:05:58 +1200

On 21/05/13 08:32, Tom Elliott wrote:

> Does one file a bug?

I would encourage you to file a bug, preferably with an exemplar which
contrasts with the existing exemplars in the standard.

cheers
stuart

Re: placeName types

Lou Burnard — Mon, 20 May 2013 21:42:55 +0100

To be fair, the argument for saying that @type on xxxName could be
providing information about the type of xxx rather than the type of name
is not entirely stupid. We all say "London is a capital city",
"Liverpool is a port", etc. without pausing for thought, because the
mapping of name to named entity is transparent in natural language. And
there are even situations where we use an xxxName precisely to indicate
a @type of xxx -- as in "Cherbourg is the Liverpool of Northern France"
(well, kind of) [...]

Re: placeName types

Tom Elliott — Mon, 20 May 2013 15:32:04 -0500

Dear all:

My original post has prompted an interesting and important tangential discussion that I have no wish to undermine. In fact, I'd like to note here that the EpiDoc community considers it best practice to mark up place names in text and metadata with the form where URI targets a linked data resource for the geographic feature in question (for Greek and Roman inscriptions, we encourage the use of "place" resources defined by http:/pleiades.stoa.org). This usage has been taught in EpiDoc training sessions for years, and will be more clearly reflected in revisions of the EpiDoc Guidelines [...]

Re: placeName types

Saašha Metsärantala — Mon, 20 May 2013 19:48:56 +0200

Hello!

> cover historic places and regions
One other problem occurs when a village or city moves: the administrative
unit is (almost) the same, the inhabitants are (almost) the same and the
name of the village (or city) is often the same, but the coordinates are
not. As a recent example, you may want to check
http://www.wikidata.org/wiki/Q83232 where about 15,000 to 20,000 persons
moved for the sake of mining. If you point your browser to
http://www.geonames.org/advanced-search.html?q=kiruna&featureClass=P&continentCode=EU
and choose the first name there, you will find a map: The Swedish word
"centrum" means "the center of the city" ... (or DOWNtown). [...]

Digital.Humanities@Oxford Summer School 2013

James Cummings — Mon, 20 May 2013 16:26:39 +0100

Only a few weeks 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!

====
The Digital.Humanities@Oxford Summer School (DHOxSS) is an annual
event for anyone working in the Digital Humanities. This year's
Summer School will be held on 8 - 12 July, at the University of
Oxford. If you are a researcher, project manager, research
assistant, or student of [...]

Re: Poetess Archive Question

Paul F. Schaffner — Mon, 20 May 2013 11:10:56 -0400

I agree that this is a question of @rend or @rendition of
quotations and/or quoted (direct) speech. As usual, it is up
to you how much to preserve as literal text and how much to
encode as 'meta' information. Using literals can get very
messy, or impossible (especially if you are not encoding
line breaks); but encoding as @rend can also get a bit hairy,
since there are several competing and overlapping schemes
of punctuation as one moves from the 17th through the 18th
century, and several ways in which printers can fail to abide
by their scheme. Among the [...]

Re: Poetess Archive Question

James Cummings — Mon, 20 May 2013 15:58:45 +0100

On 20/05/13 15:23, Mandell, Laura wrote:
> Dear All:
>
> One of the PA editors sent me the following question, and I
> don't know how to answer it.
>
> In eighteenth-century printed texts, a quoted bit has
> quotation marks at the beginning of every line, like this:
> John F. Kennedy once said, "Ask
> "not what your country can do
> "for you but what you can do
> "for your country." It was a
> really good thing to say.
>
> She is eliminating those introductory quotation marks,
> silently: should she indicate [...]

Poetess Archive Question

Mandell, Laura — Mon, 20 May 2013 14:23:27 +0000

Dear All:

One of the PA editors sent me the following question, and I don't know how to answer it.

In eighteenth-century printed texts, a quoted bit has quotation marks at the beginning of every line, like this:
John F. Kennedy once said, "Ask
"not what your country can do
"for you but what you can do
"for your country." It was a really
good thing to say. [...]

Re: placeName types

Thomas A. Carlson — Mon, 20 May 2013 14:21:19 +0000

Dear Tomaž, I'm very new to TEI, but it strikes me that there is one big advantage of using Bormio, either importing your data into GeoNames or maintaining your own list of coordinates in another TEI file with as its body. That is that it will be apparent by comparing the @ref attribute whether two instances of a refer to the same place. It will also have the side benefit of allowing you to avoid re-encoding every instance of the same place. I imagine there are many repeated places in the SBL. I'm working on a [...]

Re: placeName types

Richard Light — Mon, 20 May 2013 10:37:28 +0100

Given that Geonames is a wiki, you can add [1] the place directly to
Geonames, then everyone benefits.

There seems to be a recurring "scope of TEI" question, which bubbles up
to the surface from time to time. Here it's geographical place
identity, in the past (IIRC) we've had issues of personal identity. We
start off from the text, find names in it, and describe them in some
detail. That's fine, because it is clearly "text encoding". We seem to
become increasingly uncomfortable as we move from naming things to
recording the entity the name represents, or perhaps from encoding [...]

Re: placeName types

stuart yeates — Mon, 20 May 2013 10:53:27 +1200

On 20/05/13 10:22, Sebastian Rahtz wrote:
> On 19 May 2013, at 23:34, stuart yeates
> wrote:
>
>> Maybe we can just agree that they have different approaches to modelling names, places and regions?
>
>
> I think we probably also agree that it is much better to link to a semantic web resource than take a copy
> of the coordinates and stash them in a local . [...]

Re: placeName types

Sebastian Rahtz — Sun, 19 May 2013 22:22:27 +0000

On 19 May 2013, at 23:34, stuart yeates
wrote:

> Maybe we can just agree that they have different approaches to modelling names, places and regions?

I think we probably also agree that it is much better to link to a semantic web resource than take a copy
of the coordinates and stash them in a local .

Re: placeName types

stuart yeates — Mon, 20 May 2013 10:34:17 +1200

On 20/05/13 10:04, Sebastian Rahtz wrote:
>
> On 19 May 2013, at 23:10, stuart yeates
> wrote:
>>
>> Depending on your temporal scope, wikipedia may be a better bet than geonames. Geonames doesn't cover historic places and regions, so for example has no knowledge of the "Republic of Venice" whereas the wikipedia does: http://www.wikidata.org/wiki/Q4948
>
>
> yes and no. geonames has plenty of scope for historical names. cf http://www.geonames.org/745044/istanbul.html.
> And it has plenty of names for Venice. I am not sure "Republic of Venice" is a good example - that is surely
> a political [...]

Re: placeName types

Sebastian Rahtz — Sun, 19 May 2013 22:04:34 +0000

On 19 May 2013, at 23:10, stuart yeates
wrote:
>
> Depending on your temporal scope, wikipedia may be a better bet than geonames. Geonames doesn't cover historic places and regions, so for example has no knowledge of the "Republic of Venice" whereas the wikipedia does: http://www.wikidata.org/wiki/Q4948

yes and no. geonames has plenty of scope for historical names. cf http://www.geonames.org/745044/istanbul.html.
And it has plenty of names for Venice. I am not sure "Republic of Venice" is a good example - that is surely
a political expression, like British Empire? I may be wrong.

Re: placeName types

stuart yeates — Mon, 20 May 2013 10:10:46 +1200

On 20/05/13 09:11, Sebastian Rahtz wrote:
> On 19 May 2013, at 21:21, Tomaz Erjavec wrote:
>
>> Hi,
>> we use placeName inside person//, e.g.
>>
>> 13. marca 1734
>>
>> Bormio
>> Lombardija
>> Italija
>> 46.4663571 10.3704671
>>
>>
> if I was going to do this, I'd link to the geonames entry for this, so I'd
> say
>
>
>
> which saves you the , and makes it much more useful, as you
> can link to the many other data sources which use geonames [...]

Re: placeName types

Sebastian Rahtz — Sun, 19 May 2013 21:39:23 +0000

On 19 May 2013, at 22:32, Tomaz Erjavec
wrote:
> this sounds very reasonable at first glance - but I'm not the one that did the mapping to coordinates, so I'm not in a position to say if this is doable in practice though; my hunch would be that not all the placeNames are in geonames and maybe it would be difficult to identify them there; it seems the source was different, as the coords don't correspond exactly. [...]

Re: placeName types

Tomaz Erjavec — Sun, 19 May 2013 23:32:13 +0200

Thanks Sebastian,
this sounds very reasonable at first glance - but I'm not the one that did the mapping to coordinates, so I'm not in a position to say if this is doable in practice though; my hunch would be that not all the placeNames are in geonames and maybe it would be difficult to identify them there; it seems the source was different, as the coords don't correspond exactly. Will ask.
Best,
Tomaž [...]

Re: placeName types

Sebastian Rahtz — Sun, 19 May 2013 21:11:29 +0000

On 19 May 2013, at 21:21, Tomaz Erjavec wrote:

> Hi,
> we use placeName inside person//, e.g.
>
> 13. marca 1734
>
> Bormio
> Lombardija
> Italija
> 46.4663571 10.3704671
>
>
if I was going to do this, I'd link to the geonames entry for this, so I'd
say

which saves you the , and makes it much more useful, as you
can link to the many other data sources which use geonames IDs

Re: placeName types

Tomaz Erjavec — Sun, 19 May 2013 22:21:54 +0200

Hi,
we use placeName inside person//, e.g.

13. marca 1734

Bormio
Lombardija
Italija
46.4663571 10.3704671

place is not allowed in birth, death, or flourit which is where we use it, and the usage in the g'lines is that it is used for a place taxonomy / DB.
We don't (yet) want to move the places into a separate TEI DB - this would require a major re-think, and
right now we are at the first prototype stage with places/geo. Also, the TEI is also being edited by hand so it might be safer keeping in-line [...]

Re: Introductory material for a primary source text

Martin Mueller — Sun, 19 May 2013 13:59:46 +0000

All important distinctions are subtle and/or fuzzy at the edges, but it
still matters to deal with them as best we can. On the 'primary' vs.
'secondary' distinction, there is an excellent discussion by Paolo D'Iorio
in the papers of the Online Humanities Scholarship: The Shape of Things to
Come Conference (http://shapeofthings.org/papers/). Some of the
difficulties disappear once you accept the fact that the distinction is
not absolute but always relative to some context or project. [...]

Re: Introductory material for a primary source text

Sebastian Rahtz — Sun, 19 May 2013 13:09:23 +0000

On 19 May 2013, at 13:24, Kevin Hawkins
wrote:

> How can you encode unambiguously (without relying on @type or other things that require a human to decipher) whether a certain XML node and its children -- or a certain XML document -- is for the modern commentary or the encoded original? [...]

Re: Introductory material for a primary source text

Julia Flanders — Sun, 19 May 2013 09:03:34 -0400

Since is declarable, it wouldn't be necessary to keep the modern and original materials on separate files just on that account (? hope I'm getting this right), although one might for other reasons. One could associate different source descriptions with different pieces of the file as appropriate.

But the formal distinguishability of "my" new materials from the "source" seems important to me. This is something that came up in the recent TAPAS beta-testing (thanks to all who participated!). At least one commentator felt it would be important to be able to distinguish in TAPAS between "primary" and "secondary" material, [...]

Re: Introductory material for a primary source text

Kevin Hawkins — Sun, 19 May 2013 08:24:25 -0400

Pardon the late reply on this message. If you subscribe to TEI-L in
digest mode like I do, you risk seeing certain messages (those on which
people cc'd you on the reply) before others!

I actually agree with Sebastian's word of caution about use of @type.
However, as he admits in a later message, the same problem of
disambiguating the modern commentary and the original occurs with use of
, and, as Sebastian hints at when discussing parsing of headers,
it even exists if you have separate headers. How can you encode
unambiguously (without relying on @type or other things [...]

Re: placeName types

Sebastian Rahtz — Sun, 19 May 2013 11:13:16 +0000

I think the fact that is allowed within is accidental, and is probably not very sensible usage.
allows a whole raft of stuff of stuff inside itself (macro.phraseSeq), which includes model.measureLike
("piece of text that conveys some numerical meaning"), which includes . I'd interpret that to mean that you
_could_ use to transcribe a piece of in the source which represents coordinates
(The Cafe At SK 97481 70947). [...]

Re: placeName types

Lou Burnard — Sun, 19 May 2013 11:37:19 +0100

Hi Tomaz

This seems inconsistent. On the one hand you are saying that you don't
think should be used inside , on the other you don't
want to use which is where it should be. What subordinate
elements do you need that are not available within ?

The use of @type on to say more about the rather than
about its name is a usage which I have frequently argued against,
unsuccessfully. I am biting back the temptation to say "told you so" now. [...]

Re: placeName types

Tomaz Erjavec — Sun, 19 May 2013 11:04:12 +0200

I've another inconsistency to add to placeName: we've recently started adding geo location to places in the Slovenian biographic lexicon (http://ezb.ijs.si/sbl), where we have places marked-up as placeName. I've now inserted the coordinates in the placeName/geo, which is valid TEI, but it nevertheless looks weird - the coordinates are surely not a characteristic of the place name, but of the place itself.
But I'm disinclined to change all our placeNames to places, as they don't offer the kinds of subordinate elements that we need - also, all the examples of places in the Guidelines have them in a structured database, [...]

Re: Introductory material for a primary source text

Martin Mueller — Sat, 18 May 2013 23:43:29 +0000

In a project I am supervising this summer, a Northwestern student will do an edition of "Fair Em" based on the EEBO-TCP text. I hope that this will be the first of many (or quite a few) Young Scholar Editions in a project I call Shakespeare His Contemporaries. We haven't settled on all the details, but I'm strongly inclined to keep all the stuff done by the editor in a separate element, whether it's an introduction, short glosses, or long interpretive notes. Maintaining a clean and easily seen division between 'editorial' and 'authorial' content seems to me to matter [...]

Re: Introductory material for a primary source text

Michelle Dalmau — Sat, 18 May 2013 17:22:06 -0400

Students provide critical introductions, biographies, and annotations for the Victorian Women Writers Project (http://www.dlib.indiana.edu/collections/vwwp/). The intros and bios are encoded in a separate TEI document and linked via the Header (see below). We did this for several reasons, not least maintaining the source text intact, but also to provide index access to these intros and bios irrespective of the source text, though they are linked from the source text and vice versa. We also have bibliographic metadata specific to these contributions and wanted to keep the Header as singular as possible. Finally, in the cases of the bios, they can [...]

Re: Introductory material for a primary source text

Kevin Hawkins — Sat, 18 May 2013 15:26:36 -0400

On 5/18/13 3:15 PM, Martin Mueller wrote:
> A comment on Kevin's remark that Martin H's model is "required" if your
> composite document needs to have more than one . Would it make
> sense to modify the content rules for so that you can say
> things like "this part of the document is born digital, while that part
> has the following printed source"?
> Martin Mueller [...]

Re: Introductory material for a primary source text

Sebastian Rahtz — Sat, 18 May 2013 19:24:22 +0000

On 18 May 2013, at 17:22, "McAulay, Elizabeth"
wrote:

> I have seen texts that include multiple introductions, each from a different time period. I would simply use divisions to separate different introductions or preliminary material from each other. And I would use a full description in the TEI Header to articulate that this is a new edition with new front matter, and therefore, if anyone wants to analyze the textual components, they are alerted via the TEI Header. [...]

Re: Introductory material for a primary source text

Martin Mueller — Sat, 18 May 2013 19:15:12 +0000

This has been an interesting thread, and the different views may to some
extent be a function of where people are coming from. Thus Kevin and, I
believe Elizabeth, are librarians, and Martin Holmes is (primarily) a
developer. I look at it as a scholar, and from that perspective an edition
with commentary etc. is "my" work, and I think of it as "one" thing, even
though it may be internally subdivided. Martin H's use case, where the
creator of the annotation is not the editor of the source text, is a
different use case from what I envisaged. It [...]

Re: Introductory material for a primary source text

Kevin Hawkins — Sat, 18 May 2013 14:31:36 -0400

If the source text being edited has its own front and back matter, I
would have different divs in the for each of them, much a 2013
print edition based on a 1971 edition contains the prefaces from both
versions, one after another.

That said, I don't actually think Martin Holmes's approach is wrong. It
just feels more complicated than is required for most cases. But, for
example, if you want to describe the source document (perhaps OCR'd
text) and the source of the modern commentary (perhaps a Word document
that you converted using OxGarage), you might want a [...]

Re: Introductory material for a primary source text

Martin Holmes — Sat, 18 May 2013 09:58:02 -0700

On 13-05-18 09:38 AM, Lou Burnard wrote:
> When you say "separate files" do you actually mean "different TEI
> documents"?
>
> For me a "file" is just a unit of physical storage, nothing to do with
> the XML element structure , which is what I thought we were discussing!

That's an important issue, but it's by no means a clear distinction. Two
separate standalone TEI files may be combined into a composite structure
in a variety of ways (a teiCorpus which XIncludes them; a third TEI
document which XPointers a set of selections from them to build
[...]

Re: Introductory material for a primary source text

Lou Burnard — Sat, 18 May 2013 17:38:34 +0100

When you say "separate files" do you actually mean "different TEI
documents"?

For me a "file" is just a unit of physical storage, nothing to do with
the XML element structure , which is what I thought we were discussing!

On 18/05/13 17:35, Martin Holmes wrote:
> I'm certainly not overloaded, but: When I asked this question I felt a
> bit embarrassed to do so, since it seemed such a novice-level thing to
> enquire about, but the range of disagreement amongst our most august
> authorities shows that even with such a simple scenario we still lack
> [...]

Re: Introductory material for a primary source text

McAulay, Elizabeth — Sat, 18 May 2013 16:38:05 +0000

Sounds like you have your solution.... That level of orderliness is beyond my capacity! :) ________________________________________ From: TEI (Text Encoding Initiative) public discussion list [TEI-L@LISTSERV.BROWN.EDU] on behalf of Martin Holmes [mholmes@UVIC.CA] Sent: Saturday, May 18, 2013 9:35 AM To: TEI-L@LISTSERV.BROWN.EDU Subject: Re: Introductory material for a primary source text I'm certainly not overloaded, but: When I asked this question I felt a bit embarrassed to do so, since it seemed such a novice-level thing to enquire about, but the range of disagreement amongst our most august authorities shows that even with such a simple scenario we still lack consensus on [...]

Re: Introductory material for a primary source text

Martin Mueller — Sat, 18 May 2013 16:37:51 +0000

I agree with Lou and Sebastian on these two points:

1. An edition of the kind discussed here is "composite object", consisting
of a modern text created for this occasion and a modern version of a
predigital one.

2. is the least worst alternative. It is counter-intuitive to put
into the element of the source text an independent document that
may well be longer and more complex than the source text. Consider a
critical edition of Lycidas (~200 lines), which might have a 60 page
introduction and 500 notes.Not to speak of the fact that the source text
[...]

Re: Introductory material for a primary source text

Martin Holmes — Sat, 18 May 2013 09:35:37 -0700

I'm certainly not overloaded, but: When I asked this question I felt a
bit embarrassed to do so, since it seemed such a novice-level thing to
enquire about, but the range of disagreement amongst our most august
authorities shows that even with such a simple scenario we still lack
consensus on best practices.

I think I'm with Sebastian at the moment: I don't like the idea of using
@type to distinguish s that are modern from those that are not,
and I'm reluctant to rely on prose in the header to alert a putative
text-analysis machine about which bits it [...]

Re: Introductory material for a primary source text

Sebastian Rahtz — Sat, 18 May 2013 16:23:07 +0000

On 18 May 2013, at 17:10, Lou Burnard
wrote:

>
> Well, what would you do?
> The truth of the situation is that we're dealing with a composite object, one part of which is a modern text and one part of which is a modern version of an pre-digital one. Using still seems like the right solution to me. If the source has its own that would still be distinct from the modern .
>
i agree that a in a is definitely preferable to . It would fine, if we had a [...]

Re: Introductory material for a primary source text

McAulay, Elizabeth — Sat, 18 May 2013 16:22:04 +0000

I have seen texts that include multiple introductions, each from a different time period. I would simply use divisions to separate different introductions or preliminary material from each other. And I would use a full description in the TEI Header to articulate that this is a new edition with new front matter, and therefore, if anyone wants to analyze the textual components, they are alerted via the TEI Header. So, I'm still lobbying for Kevin's approach. Normally I would say we've totally overloaded the poor questioner, but as it's Martin H., I think he'll survive! He's used to this listserv. [...]

Re: Introductory material for a primary source text

Lou Burnard — Sat, 18 May 2013 17:10:44 +0100

On 18/05/13 16:58, Sebastian Rahtz wrote:
> On 18 May 2013, at 16:53, Lou Burnard
> wrote:
>
>> However, I also think I disagree with you. What if the source text being edited has its own front and back matter? You don't want to confuse that with your modern front and back. Hence, I think the approach is generally to be preferred, if the modern parts are too big to be treated just as annotations.
>>
>
> you're just putting the problem up a stage - what if the source is composed of several s of [...]

Re: Introductory material for a primary source text

Sebastian Rahtz — Sat, 18 May 2013 15:58:05 +0000

On 18 May 2013, at 16:53, Lou Burnard
wrote:

> However, I also think I disagree with you. What if the source text being edited has its own front and back matter? You don't want to confuse that with your modern front and back. Hence, I think the approach is generally to be preferred, if the modern parts are too big to be treated just as annotations.
> [...]

Re: Introductory material for a primary source text

Lou Burnard — Sat, 18 May 2013 16:53:21 +0100

Yes, I was disagreeing with Martin, as you surmise.

However, I also think I disagree with you. What if the source text being
edited has its own front and back matter? You don't want to confuse that
with your modern front and back. Hence, I think the approach is
generally to be preferred, if the modern parts are too big to be treated
just as annotations. [...]

Re: Introductory material for a primary source text

Sebastian Rahtz — Sat, 18 May 2013 15:40:06 +0000

Kevin is recommending, as I understand it,

which I, as a consumer, find quite unsettling, because
it relies solely on an arbitrary value for the notoriously private @type
to convey to the user that this text is not in the original.

If I am doing an analysis of the language used in the original text,
I have no information here which will let me filter out the
commentary section. [...]

Re: Introductory material for a primary source text

McAulay, Elizabeth — Sat, 18 May 2013 15:29:23 +0000

I like Kevin's approach as described below. If there are footnotes or annotations, I would integrate those into the body and use either or both the "cert" and "resp" attributes to note the modern commentary. Best, Lisa ------------------------------------- Elizabeth "Lisa" McAulay Librarian for Digital Collection Development UCLA Digital Library Program http://digital.library.ucla.edu/ email: emcaulay [at] library.ucla.edu ________________________________________ From: TEI (Text Encoding Initiative) public discussion list [TEI-L@LISTSERV.BROWN.EDU] on behalf of Kevin Hawkins [kevin.s.hawkins@ULTRASLAVONIC.INFO] Sent: Saturday, May 18, 2013 7:34 AM To: TEI-L@LISTSERV.BROWN.EDU Subject: Re: Introductory material for a primary source text When Lou says that "this approach" seems exactly right, I assume [...]

Re: Introductory material for a primary source text

Kevin Hawkins — Sat, 18 May 2013 10:34:41 -0400

When Lou says that "this approach" seems exactly right, I assume he is
referring to what Martin Mueller and Rob suggested (and not what Martin
Holmes suggested).

I am more inclined to put the modern commentary in and, if
desired, also in , with the encoded source document in .
This is analogous to a scholarly edition in print, which would have the
commentary at the front, likely with page numbers in roman numerals, and
possibly also an index or two at the back. I personally don't think you
need separate headers: most of the header describes the digital [...]

Re: ALTO=>TEI experience or advice

Lou Burnard — Sat, 18 May 2013 08:27:54 +0000

This was true once. However when sourceDoc et al were added we also made it possible for surface zone and friends to carry coordinate information directly. So the mapping Alexander wants should be quite straightforwardif he maps to a soyrceDox rather than to a text.

----- Reply message -----
From: "Conal Tuohy"
To: "TEI-L@LISTSERV.BROWN.EDU"
Subject: ALTO=>TEI experience or advice
Date: Sat, May 18, 2013 04:07 [...]

Re: ALTO=>TEI experience or advice

Conal Tuohy — Sat, 18 May 2013 11:57:17 +1000

On 18/05/13 02:34, Alexandre Gefen wrote:
> Hi,
>
> has someone any experience with ALTO (or ALTO/METZ) to TEI conversion
> processes ?
>
> any advice or xslt welcome !
>
I wrote an XSLT for this some years ago, which, I'm sorry to say, I have
since lost in my travels.

The XSLT was an exercise at generating TEI "facsimile" markup. In
METS/ALTO, the cartesian coordinates are attached to textual content
directly, whereas in TEI the the textual content (transcript) and
coordinates are kept separate (within the tei:text and tei:facsimile
elements, respectively). [...]

Re: Introductory material for a primary source text

Martin Mueller — Fri, 17 May 2013 22:40:08 +0000

I'm with Lou on that point. I had also thought about teiCorpus but for
similar reasons concluded that an edition with commentary is not a corpus
of n texts, but a single entity

On 5/17/13 5:25 PM, "Lou Burnard" wrote:

>If you're producing a new electronic document, which combines annotation
>and commentary with an edited source text, this approach seems exactly
>right to me. I cannot see any need to treat this a corpus -- the
>"primary" text isn't in fact the same as the source from which it's
>encoded. For one thing, it's in digital form!
>
>
[...]

Re: Introductory material for a primary source text

Lou Burnard — Fri, 17 May 2013 23:25:12 +0100

If you're producing a new electronic document, which combines annotation
and commentary with an edited source text, this approach seems exactly
right to me. I cannot see any need to treat this a corpus -- the
"primary" text isn't in fact the same as the source from which it's
encoded. For one thing, it's in digital form! [...]

Re: Introductory material for a primary source text

Martin Holmes — Fri, 17 May 2013 15:22:04 -0700

This is an effective approach, although I would worry that the teiHeader
would now have to apply to both the modern and the primary texts. This
has me leaning towards teiCorpus with component TEI elements, so the two
headers could be kept completely separate (and the corpus header could
explain the relationship between the components). [...]

Re: Introductory material for a primary source text

Robert Whalen — Fri, 17 May 2013 18:04:43 -0400

This is precisely what we did for The Digital Temple, with the more
lengthy editorial materials referenced as separate files (though I
suppose one could include everything in one file with additional
sub-s):

Rob
On 5/17/13 5:46 PM, Martin Mueller wrote:
> I am wrestling with a very similar problem: an edition with an elaborate
> [...]

Re: Introductory material for a primary source text

Martin Mueller — Fri, 17 May 2013 21:46:00 +0000

I am wrestling with a very similar problem: an edition with an elaborate
introduction and complex notes is partly an encoding of an 'old' text and
partly the creation of a 'new' text. Would it be tag abuse to use group
and use one text element to contain the encoded document and another text
element to contain the commentary? [...]

Re: placeName types

Peter Stadler — Fri, 17 May 2013 22:11:15 +0200

Another (somehow related) inconsistency that struck me recently is the naming of tags from model.placeNamePart:
* placeName
* bloc
* country
* region
* district
* settlement
* geogName

Only within two appears "Name" although the others clearly denote a name as well (as can be seen from the element descriptions) and not the geographic entity (that would be ). [...]

Re: placeName types

Syd Bauman — Fri, 17 May 2013 14:27:59 -0400

You've stumbled across what I think of as a weakness, or at least an
inconsistency, in TEI encoding that has been around since (at least)
the days of P2. In some cases (like

), type= is used to mean
"the kind of thing I am"; in some cases (like ) type= is used
to mean "the kind of thing I'm referring to". I have long held that
the type= of should really be of=. (Or some such.) [...]

placeName types

Tom Elliott — Fri, 17 May 2013 13:10:18 -0500

Dear all:

I don't know why it hasn't struck me before, but I'm finding myself bothered by the use of the "type" attribute on and that's modeled in the Guidelines (http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ND.html#NDPLAC E.g., type="settlement", type="city" and so forth).

It seems to me at the moment that there's a potential muddle here between two notions: "type of place" and "type of place name". I don't see any clear examples for the latter use case (e.g., "this is a type=fictitious place name (for a real place)" or "this is a type=former place name"). My knee-jerk reaction is that we shouldn't be [...]

Introductory material for a primary source text

Martin Holmes — Fri, 17 May 2013 10:40:48 -0700

Hi all,

I'd like to get a sense of how and where people typically encode
substantial modern editorial content related to a primary source text.
For instance, if you have such things as a Critical Introduction, or a
lengthy Textual Note, where do you tend to put it?

My instinct is that this doesn't belong in the along with the
primary source transcription; mixing modern editorial content with the
primary source seems completely wrong. Shorter notes obviously belong in
the header in , but the structure of makes it
inadequate for longer critical material (it can't contain

[...]

ALTO=>TEI experience or advice

Alexandre Gefen — Fri, 17 May 2013 18:34:35 +0200

Hi,

has someone any experience with ALTO (or ALTO/METZ) to TEI conversion processes ?

any advice or xslt welcome !

many thanks,

regards,
Alexandre

2013 DARIAH-DE International Digital Humanities Summer School

Munson, Matthew — Fri, 17 May 2013 12:54:44 +0200

Dear TEIers,

The Göttingen Centre for Digital Humanities at the University of Göttingen,
Germany, is pleased to host the 2013 DARIAH-DE International Digital
Humanities Summer School. This summer school will be a one-week crash course
in using the scripting language Python and its Natural Language Toolkit to
perform in-depth computational analysis of digital texts. The summer school
will take place between August 19-23, 2013. The instructors will be Mike
Kestemont from the University of Antwerp
and Lars Wieneke from the
CVCE . The summer school is aimed primarily at Ph.D.
and post-doctoral researchers and others with advanced [...]

Re: Annotation of narrative sequences with TEI

Elisa Beshero-Bondar — Wed, 15 May 2013 13:22:53 -0400

PS: Apologies for consistently misspelling your name in this thread,
Riccardo! My eyes are bleary from too much time at my computer lately--and
I'd probably best not be coding today. Hope the discussion is
useful...Conflicting hierarchies of structure pose some serious--and very
interesting--challenges in using the TEI!

Best,
Elisa

On Wed, May 15, 2013 at 12:43 PM, Elisa Beshero-Bondar wrote: [...]

Re: Annotation of narrative sequences with TEI

Elisa Beshero-Bondar — Wed, 15 May 2013 12:43:26 -0400

This is intriguing about ...If you're considering Ricardo's coding
project about narrative structure of a fictional text, and reviewing the
TEI chapter 13 on Names, Dates, People, and Places, I wonder if it might be
appropriate to use in this context as a way simply of plotting
change and developments over time within a text being annotated--rather
than reserving its use for stand-off markup or a separate-but-related
collection of historic events that bear relevance to the text. This part of
Chapter 13 seems relevant: [...]

Re: Annotation of narrative sequences with TEI

Lou Burnard — Wed, 15 May 2013 16:52:01 +0100

is meant for use when documenting a historical event such as the
Battle of Waterloo, analagous to the elements or , so
the

s it contains are meant to be documentary rather than b eing the
actual text you're annotating. So I don't think it's what needed here,
because though you might want to link the span in your text to it. [...]

Re: Annotation of narrative sequences with TEI

Elisa Beshero-Bondar — Wed, 15 May 2013 11:42:25 -0400

@event looks especially useful for Ricardo because it can contain

elements--would seem to serve the purposes of literally spanning multiple
paragraphs.

Spanning across structural units like

and or seems a perennial
issue with TEI--which tags can sit outside the unit and which have to go
inside... I wonder if anyone maintains a list of handy spanning elements? [...]

Re: Annotation of narrative sequences with TEI

Agnes Thomas — Wed, 15 May 2013 17:31:09 +0200

Dear all,

what's about the element? It provides useful attributes, too,
like @type, @resp etc.
At the moment, we are encoding narrative sequences in the ancient text
of Thucydides like that (Hellespont Project, Berlin).

A second option is to go with for a much more adequate
annotation of events:
http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-listEvent.html

It contains that by itself may contain elements like ,
, , and many others. [...]

Re: Annotation of narrative sequences with TEI

Elisa Beshero-Bondar — Wed, 15 May 2013 11:11:59 -0400

Looking back at our coding, I see we actually have an array of 5 distinct
attributes in play for the referencing string:

@type, @subtype, @role, and @ana... Of these, we only had to use @type, and
the others designated optional and more specific kinds of info.

The kind of tagging you're doing is complicated, and it's quite a challenge
to sort out how to code sequences of different kinds of events...Using a
few related elements together in TEI, and working with the above attributes
might be useful for you. [...]

Re: Annotation of narrative sequences with TEI

Elisa Beshero-Bondar — Wed, 15 May 2013 11:04:58 -0400

Dear Ricardo,
I've recently been coding in a similar way, both editorial structure
elements and other kinds of information, to do with cultural interactions,
objects, time, and place. For the purposes you describe, I
recommend considering (referencing string), which takes a good range
of attributes in TEI, and to consider using a few other TEI elements
alongside it. [...]

Annotation of narrative sequences with TEI

Riccardo Tasso — Wed, 15 May 2013 15:48:36 +0200

Hi,
I'm working on a literary text. I'd like to divide it in some narrative
sequences (text portions composed by time, place and actors). This division
is transverse to the editorial structure (paragraphs, chapters, ...); e.g.
it happens that a sequence starts with a chapter and ends with another one,
or that a chapter is splitted in more sequences. [...]

Biblissima - Survey : XML editors for TEI/EAD

Biblissima questionnaire — Wed, 15 May 2013 09:15:05 -0400

Dear all,

As part of the Biblissima project, we are carrying out a survey on the user requirements for XML editors, especially for people doing TEI and/or EAD encoding. We would like to find out more about your habits and wishes, in order to develop tools that are best-suited to your needs. If you are involved with this kind of work, we would be pleased if you could answer our survey : [...]

new version of TEI bibliography now available

Kevin Hawkins — Tue, 14 May 2013 21:15:14 -0400

I am pleased to announce a major update to the TEI bibliography,
available at:

http://www.tei-c.org/Support/Learn/tei_bibliography.xml

This document, created many years ago by the SIG on Education, has been
revised and expanded over the years by contributions from a number of
people. The citations are now stored in a Zotero group library, from
which the data are exported and transformed into TEI s using
the Zotero plugin for Firefox (which incorporates code written by Stefan
Majewski). Big thanks to Stefan, Sebastian Rahtz, and David Sewell for
helping create the workflow for exporting. [...]

Re: encoding some summary like parts in texts (called sootitr)

Kevin Hawkins — Tue, 14 May 2013 09:32:15 -0400

I just noticed that Saeed asked another question at the end of his most
recent post ...

On 5/13/13 1:34 AM, Saeed Sarrafzadeh wrote:
> Do you really think that the element is appropriate for cases
> where we have some summarization or key points in parallel to the
> text? If all of you agree with that I'll transfer this suggestion for
> final action to that group. I had another view of note before as an
> additive intellectual content not a summary-like content which is
> present already in a detailed form in the main text [...]

Re: teiHeader and CIP

Kevin Hawkins — Mon, 13 May 2013 18:49:37 -0400

Responses below ...

On 5/13/13 5:48 PM, Matija Ogrin wrote:
> Dne 13. 05. 2013 06:27, piše Kevin Hawkins:
>> So my preferred solution is still a new child of . I
>> almost put in a SourceForge feature request when I first replied to
>> Matija's message, but then I realized that a project-specific
>> customization will probably suffice.
> A project-specific customization is something I would like to avoid
> here, if possible. After all, a CIP record is a very general thing,
> inserted in nearly every printed book and surely in every scholarly
> edition, dictionary, [...]

Re: teiHeader and CIP

Sebastian Rahtz — Mon, 13 May 2013 22:41:16 +0000

On 13 May 2013, at 23:32, Kevin Hawkins
wrote:

> I think there are many people who will want to insert non-TEI metadata in a header,

the XML-namespace devil in me says: "if you want to put non-TEI content (CIP, DC, whatever) in your header,
go right ahead, using a namespace appropriate to the context. a decent XML validator will validate the TEI
for what it is, and your CIP record separately. that is why they have us tools like NVDL" [...]

Re: teiHeader and CIP

Kevin Hawkins — Mon, 13 May 2013 18:32:14 -0400

I think there are many people who will want to insert non-TEI metadata
in a header, so I would support a new element (which I'll call
for now) for this as a child of .
We might also include some examples in the Guidelines where @corresp
is used on a TEI header element to point to the equivalent data found in
. [...]

Re: teiHeader and CIP

Matija Ogrin — Mon, 13 May 2013 23:49:45 +0200

Hello,

Thanks to all who shared their views on this topic. I don't know which
encoding would be most appropriate ... Kevin's proposition about a
element as a direct child of is the most clear, of
course, and also Lou's suggestion to generalise the new element is to
the point. Some further discussion will be needed, I guess.-- [...]

Re: teiHeader and CIP

Lou Burnard — Mon, 13 May 2013 10:54:37 +0100

If we go along with the idea of a new child for should
we not maybe try to generalise it a bit? e.g.
or maybe just

(which could
be a direct child of teiHeader)

Hey, it could also serve as a place to put some Dublin Core style
metadata to be exposed to dim-witted search engines! I've been droning
about the need for that for ages... [...]

Re: encoding some summary like parts in texts (called sootitr)

Saeed Sarrafzadeh — Mon, 13 May 2013 01:34:07 -0400

Thanks Kevin for your help and advise
On Sun, 12 May 2013 13:18:23 -0400, Kevin Hawkins wrote:

>Saeed emailed me his files directly and gave me permission to share. I
>have put them here (though renamed them for ease of reference):
>
>http://www.ultraslavonic.info/saeed/
>
>Here's how I would handle each:
>
>== bbc.jpg ==
>
>
>
> If we lose reefs we lose an opportunity to create new
>species by evolutionary processes
> Wolfgang KiesslingHumboldt
>University, Berlin
>
>
>
>== formula.png ==
>
>
>
>== textbook.png ==
>
>I assume Saeed is interested [...]

Re: teiHeader and CIP

Kevin Hawkins — Mon, 13 May 2013 00:27:59 -0400

On 5/12/13 3:19 PM, Lou Burnard wrote:
> From Kevin's remarks, it's also evident that the actual format required
> for the CIP is going to be quite different in different contexts -- just
> like the model for is fine in some contexts and useless in
> others.

For what it's worth, I actually think that the format of CIP data is
more standard around the world than the various citation formats that we
struggle to fit into or . [...]

Re: teiHeader and CIP

Kevin Hawkins — Mon, 13 May 2013 00:23:47 -0400

I hope Linde won't be offended if I decipher her message for the many
readers of this list who aren't catalogers.

It's true that the Library of Congress was previously done according to
AACR2R but is now being done using RDA. One of her links explains that.
In either case, the data is structured. [...]

Re: teiHeader and CIP

Sebastian Rahtz — Sun, 12 May 2013 20:17:18 +0000

On 12 May 2013, at 20:19, Lou Burnard
wrote:

> you could almost imagine rewriting the CIP as a bunch of xPath expressions pulling various bits out of a well-constructed header to avoid the duplication.

that was my thought too, to make it a transformation of the header in a content negotiated web transaction. but my heart failed
me at the thought. [...]

Re: teiHeader and CIP

Lou Burnard — Sun, 12 May 2013 20:19:28 +0100

I think there's a more worrying aspect of this problem. I took a quick
peek around the internet to see what sort of stuff actually appears in a
British CIP and I found a nice example (at
http://www.bl.uk/bibliographic/pdfs/cip.pdf if you want to check). This
showed me that almost all of the data contained in the CIP data would
(or could) also appear somewhere in the TEI Header: you could almost
imagine rewriting the CIP as a bunch of xPath expressions pulling
various bits out of a well-constructed header to avoid the duplication.
Almost, but probably not quite. [...]

Re: teiHeader and CIP

Sebastian Rahtz — Sun, 12 May 2013 19:01:59 +0000

some of this problem comes from the fact that says that you have to choose between structured or unstructured data:

model.pLike+ | model.publicationStmtPart+

which is a classic bit of TEI paternalism: "no, sorry, either you make up your mind completely, or you can't
have any of the nice semantic elements". These things are usually based (I claim) on the awful "you have
to be able to read/render the contents sequentially" paradigm. [...]

Re: encoding some summary like parts in texts (called sootitr)

Kevin Hawkins — Sun, 12 May 2013 13:18:23 -0400

Saeed emailed me his files directly and gave me permission to share. I
have put them here (though renamed them for ease of reference):

http://www.ultraslavonic.info/saeed/

Here's how I would handle each:

== bbc.jpg ==

If we lose reefs we lose an opportunity to create new
species by evolutionary processes
Wolfgang KiesslingHumboldt
University, Berlin

== formula.png ==

== textbook.png == [...]

Re: teiHeader and CIP

Linde B. — Sun, 12 May 2013 12:00:17 -0500

On Sun, May 12, 2013 at 11:45 AM, Kevin Hawkins <
kevin.s.hawkins@ultraslavonic.info> wrote:

> Cataloguing-in-publication data is actually highly structured data. It
> follows a national cataloging code, which is likely based on ISBD notation,
> and is a representation of how a national library will catalog the work
> once it is actually published and therefore how other libraries will do the
> same.
> [...]

Re: teiHeader and CIP

Kevin Hawkins — Sun, 12 May 2013 12:45:52 -0400

Cataloguing-in-publication data is actually highly structured data. It
follows a national cataloging code, which is likely based on ISBD
notation, and is a representation of how a national library will catalog
the work once it is actually published and therefore how other libraries
will do the same.

If you are encoding CIP data that appears in the source document, you
would want to include this within . But Matija's national
library is issuing CIP data for his digital editions, so he wants to
encode the CIP data for these digital editions in his TEI document. [...]

Re: encoding some summary like parts in texts (called sootitr)

Saeed Sarrafzadeh — Sun, 12 May 2013 08:40:26 -0400

On Thu, 9 May 2013 14:50:26 -0400, Paul F. Schaffner wrote:

>Perhaps something like these (clumsily scanned from some random
>textbooks):
>
>http://www-personal.umich.edu/~pfs/fun/pix/sidebars.pdf
>
>pfs
>

This sample seems that can be done using some div elements which have their own heading, as we can have a conclution section, section summary or a key points section at the end of each chapter in a book. What I mean is a type of summarization or key points which goes parallel to the text itself.

Re: teiHeader and CIP

Neven Jovanović — Sun, 12 May 2013 11:20:36 +0200

Hi, Matija,

could you put the CIP in another idno, just as you did for ISBN (@type="CIP")?

Pozdrav,

Neven

Neven Jovanovic, Zagreb
Hrvatska / Croatia

On 12 May 2013 01:26, Matija Ogrin wrote:
> Hello Laurent and Lou,
>
> Many thanks for your comments! We produce digital editions of manuscripts
> and early modern books, and so a CIP -- "cataloguing in publication" -- in
> our case applies to a newly produced digital edition. The idea of wrapping a
> CIP in a is attractive, but I have difficulties where exactly to
> place it.
>
[...]

Re: teiHeader and CIP

Matija Ogrin — Sun, 12 May 2013 01:26:53 +0200

Hello Laurent and Lou,

Many thanks for your comments! We produce digital editions of
manuscripts and early modern books, and so a CIP -- "cataloguing in
publication" -- in our case applies to a newly produced digital edition.
The idea of wrapping a CIP in a is attractive, but I have
difficulties where exactly to place it. [...]

Re: Quotation and SemanticWeb URI

Dave McAlpin — Sat, 11 May 2013 13:13:43 -0700

Great. Thanks Lou.

From: TEI (Text Encoding Initiative) public discussion list
[mailto:TEI-L@LISTSERV.BROWN.EDU] On Behalf Of Lou Burnard
Sent: Saturday, May 11, 2013 1:12 PM
To: TEI-L@LISTSERV.BROWN.EDU
Subject: Re: Quotation and SemanticWeb URI

Ah, I see the problem. does not have a @who attribute, since it is
primarily intended for things quoted from a written source. It does have
@source, which behaves in much the same way, though it is intended to point
to a bibliographic source, rather than a person. But that seems quite a
legitimate extension of its semantics. [...]

Re: Quotation and SemanticWeb URI

Lou Burnard — Sat, 11 May 2013 21:11:31 +0100

Ah, I see the problem. does not have a @who attribute, since it
is primarily intended for things quoted from a written source. It does
have @source, which behaves in much the same way, though it is intended
to point to a bibliographic source, rather than a person. But that seems
quite a legitimate extension of its semantics. [...]

Re: Quotation and SemanticWeb URI

Dave McAlpin — Sat, 11 May 2013 13:00:42 -0700

Thanks for the reply. To use the example from
http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-said.html, I think
my choices for quoted text that is either thought or spoken aloud are:

Celia thought privately, Dorothea quite
despises Sir James Chettam;

I believe she would not accept him. Celia felt that this was a
pity.

Celia thought privately, Dorothea quite
despises Sir James Chettam; [...]

Re: Quotation and SemanticWeb URI

Lou Burnard — Sat, 11 May 2013 20:48:16 +0100

Well, with @type for all of these things is fine by me, but the
reason that the new elements and were introduced was to
make it easier to distinguish direct/indirect speech or thought on the
one hand () from material quoted from elsewhere (), which
is what I am guessing you mean by "written in letters". [...]

Re: teiHeader and CIP

Lou Burnard — Sat, 11 May 2013 20:41:34 +0100

Hello Matija!

As I understand it the term "CIP" means "cataloguing in publication" --
but it's not clear whether you mean a CIP that already exists in the
source text you're encoding (in which case it belongs in the
sourceDesc), or a CIP that applies to the new digital edition you're
producing (in which case it belongs in the publication statement). In
either case though, I agree with Laurent that wrapping it in a
would probably be more useful than an [...]

Re: Quotation and SemanticWeb URI

Dave McAlpin — Sat, 11 May 2013 09:27:14 -0700

Sorry, I meant to say for quotes that are either thought or said
aloud, and for quotes that are written.

From: TEI (Text Encoding Initiative) public discussion list
[mailto:TEI-L@LISTSERV.BROWN.EDU] On Behalf Of Dave McAlpin
Sent: Saturday, May 11, 2013 9:09 AM
To: TEI-L@LISTSERV.BROWN.EDU
Subject: Re: Quotation and SemanticWeb URI

I'm working on a similar problem, and like Riccardo chose over .
It sounds like I may have made the wrong call. [...]

Re: Quotation and SemanticWeb URI

Dave McAlpin — Sat, 11 May 2013 09:08:37 -0700

I'm working on a similar problem, and like Riccardo chose over .
It sounds like I may have made the wrong call.

In my case I'm interested in communications that are either written in
letters, thought or spoken aloud. The tag didn't seem to apply to
written communication, so I used with @type throughout, mostly for
consistency. Would it be better to use with @who and @aloud for
spoken and written quotes, and with @who and @type for written
communications? [...]

Re: seeking help with segment of text crossing
and

Peter Boot — Sat, 11 May 2013 12:28:02 +0200

On 10-5-2013 17:16, Alexander, Mary wrote:
> Interp and interGroup works well for what she wants to accomplish.
> For one segment, the text crosses structure blocks. As a place
> holder, the 2nd part of the segment is marked the same as the 1st
> part. Is there a way to designate that the two parts are one
> segment and convey that it is same interpretation? [...]

Re: seeking help with segment of text crossing
and

Riccardo Tasso — Sat, 11 May 2013 08:43:36 +0200

Look for the span tag, which can be put anywhere inside or outside your
document, represents an annotation which covers a set of other elements, as
provided in the target attribute.

It seems to be your case.

Cheers,
Ricardo
Il giorno 10/mag/2013 17:26, "Alexander, Mary" ha
scritto:

> Hello, ****
>
> I am assisting with a manuscript project. I’m new to TEI and looking for
> help concerning a text segment that crosses a large block of text. ****
>
> The researcher’s source document is a 17th century diary written in
> Spanish with annotations from the [...]

Re: teiHeader and CIP

Laurent Romary — Sat, 11 May 2013 07:28:04 +0200

Hi Matija,
Isn't this a way to describe the source, in which case I would put this as an alternate bibliographical description (plain ) in the sourceDesc.
Laurent

Le 10 mai 2013 à 15:36, Matija Ogrin a écrit :

> Hello,
>
> I am required to insert a CIP record into the of our digital
> editions -- similarly as it appears in printed books. I wonder what is
> the recommended place in the to this scope.
>
> The CIP record is provided by the National library, prior to the
> publication of the edition, [...]

seeking help with segment of text crossing
and

Alexander, Mary — Fri, 10 May 2013 10:16:01 -0500

Hello,
I am assisting with a manuscript project. I’m new to TEI and looking for help concerning a text segment that crosses a large block of text.

The researcher’s source document is a 17th century diary written in Spanish with annotations from the same period. She will include her comments.

Interp and interGroup works well for what she wants to accomplish. For one segment, the text crosses structure blocks. As a place holder, the 2nd part of the segment is marked the same as the 1st part. Is there a way to designate that the two parts are one segment [...]

Re: Slightly OT: how to use with XSLT

Roberto Rosselli Del Turco — Fri, 10 May 2013 17:17:42 +0200

Thanks a lot Syd! I'll pass your suggestion to my student :)

I only hinted at my question being "slightly off topic" because it's
more about XSLT processing than TEI XML markup. That said, I sometimes
wish there were a sample XSLT snippet showing how the elements described
in the different sections of the TEI Guidelines might be transformed in
(X)HTML (nothing complex, just for didactic reasons). [...]

Re: Slightly OT: how to use with XSLT

Martin Holmes — Fri, 10 May 2013 08:00:39 -0700

There's a nice tutorial by Jeni Tennison on processing overlapping
hierarchies here:

Cheers,
Martin

On 13-05-10 02:03 AM, Roberto Rosselli Del Turco wrote:
> Dear all,
> I'm encoding a poetic text which presents several problems due to
> multiple hierarchies, which is why I was planning to use a couple of
> s and to re-create, in a virtual fashion, lines and word
> groups (having used to mark each single word in the text).
>
> The student who's collaborating to the project and helping me with style
> sheets, however, is not sure how [...]

Re: Quotation and SemanticWeb URI

Lou Burnard — Fri, 10 May 2013 15:37:34 +0100

On 10/05/13 15:07, Riccardo Tasso wrote:
>
> I'd like to annotate dialogues in my text, and from TEI reference I've
> seen the best tag should be the "quotation" .
> In particular I'm interested in the "who" attribute, used to declare
> the speaker. Inside the reference I read that each speaker should be
> declared inside a document as an item, with its own xml:id.
>
> I have an ontology (in owl/rdf) describing characters and their
> relations, so to me it would be great to declare, as value for the
> "who" attribute, the [...]

Quotation and SemanticWeb URI

Riccardo Tasso — Fri, 10 May 2013 16:07:32 +0200

Hi everybody,
I'm a TEI newbie and I'm trying to annotate a novel for a project about
digital humanities.

I'd like to annotate dialogues in my text, and from TEI reference I've seen
the best tag should be the "quotation" .
In particular I'm interested in the "who" attribute, used to declare the
speaker. Inside the reference I read that each speaker should be declared
inside a document as an item, with its own xml:id. [...]

Re: Slightly OT: how to use with XSLT

Syd Bauman — Fri, 10 May 2013 09:54:16 -0400

Doesn't seem off topic to me. I don't have anything lying around, but
you probably want something like the following. It's not particularly
robust, doesn't check the value of evaluate= or scope, etc. But it
shows you the idea of how this might be done. (There are probably
better ways to do this, too.) [...]

teiHeader and CIP

Matija Ogrin — Fri, 10 May 2013 15:36:28 +0200

Hello,

I am required to insert a CIP record into the of our digital
editions -- similarly as it appears in printed books. I wonder what is
the recommended place in the to this scope.

The CIP record is provided by the National library, prior to the
publication of the edition, as an unstructured paragraph(s) of text. So,
I basically need a simple , probably somewhere in the
? But non of the existing elements seems suitable for
CIP. [...]

Slightly OT: how to use with XSLT

Roberto Rosselli Del Turco — Fri, 10 May 2013 11:03:14 +0200

Dear all,
I'm encoding a poetic text which presents several problems due to
multiple hierarchies, which is why I was planning to use a couple of
s and to re-create, in a virtual fashion, lines and word
groups (having used to mark each single word in the text).

The student who's collaborating to the project and helping me with style
sheets, however, is not sure how to produce something like class="line"> in HTML on the basis of 's multiple targets. Could
anyone point me to an example of XML text and XSLT code doing this? or
explain [...]

Re: encoding some summary like parts in texts (called sootitr)

Paul F. Schaffner — Thu, 9 May 2013 14:50:26 -0400

Perhaps something like these (clumsily scanned from some random
textbooks):

http://www-personal.umich.edu/~pfs/fun/pix/sidebars.pdf

pfs

On Thu, 9 May 2013, Kevin Hawkins wrote:

> Sebastian asked for a picture of the original, and he later wrote ...
>
> On 2:59 PM, Sebastian Rahtz wrote:
>> On 8 May 2013, at 16:46, Lou Burnard wrote:
>>
>>> Yes, I agree with Paul that this sounds like what I know as a "pull
>>> quote": a bit of text usually but not always quoted from the story and
>>> splashed in the middle of the layout to attract readers to it. It's not a
[...]

DHQ: temporary moratorium on submissions

Julia Flanders — Thu, 9 May 2013 14:21:44 -0400

This summer, Digital Humanities Quarterly will be moving its editorial operations to Northeastern University. During the transition period, we will observe a temporary moratorium on new submissions, to enable us to focus on a few infrastructural improvements. The moratorium will last from May 15 through September 15, 2013.

The journal's production work on articles and special issues already submitted will not be affected by the moratorium. The journal will continue to publish as usual during this period. [...]

Re: encoding some summary like parts in texts (called sootitr)

Kevin Hawkins — Thu, 9 May 2013 12:13:54 -0400

Sebastian asked for a picture of the original, and he later wrote ...

On 2:59 PM, Sebastian Rahtz wrote:
> On 8 May 2013, at 16:46, Lou Burnard wrote:
>
>> Yes, I agree with Paul that this sounds like what I know as a "pull quote": a bit of text usually but not always quoted from the story and splashed in the middle of the layout to attract readers to it. It's not a proper heading, since it isn't tied to any particular location in the text, in fact it's not always clear what it is tied to.
>>
[...]

Re: encoding some summary like parts in texts (called sootitr)

Sebastian Rahtz — Thu, 9 May 2013 07:49:51 +0000

does this discussion suggest that we should just use the right semantic container (be it , , , , ), with
a @rend (or @rendition) as appropriate?

Re: encoding some summary like parts in texts (called sootitr)

Saeed Sarrafzadeh — Thu, 9 May 2013 01:29:14 -0400

Hi Stuart,
thanks for your participation.

On Thu, 9 May 2013 12:46:28 +1200, stuart yeates wrote:

>We use ... in
>documents such as:
>http://nzetc.victoria.ac.nz/tm/scholarly/tei-Gov1906Acts-t1-g1-g3-t1.html (TEI
>accessible via the link in right-hand menu). These are typical spatially
>coordinated with a facing-page bi-lingual parallel text, so location is
>very important.
>
>The generated HTML / CSS could be improved in this case.
>
>cheers
>stuart [...]

Re: encoding some summary like parts in texts (called sootitr)

Saeed Sarrafzadeh — Thu, 9 May 2013 01:16:31 -0400

Hi all
I don't know why my postings are not listed here, so I recompose it:
Hi all,
and thanks a lot for your participation in the discussion
I'd added a sample in my posting on yesterday and two other sample to a subsequent posting to show that that's not only the case for the newspapers but also it can be a good practice in university textbooks (unfortunately it seems that a problem causes them to not appear here). Students use this feature especially when they want to have a quick review of contents. I'd reviewed some elements which you [...]

Re: encoding some summary like parts in texts (called sootitr)

stuart yeates — Thu, 9 May 2013 12:46:28 +1200

We use ... in
documents such as:
http://nzetc.victoria.ac.nz/tm/scholarly/tei-Gov1906Acts-t1-g1-g3-t1.html (TEI
accessible via the link in right-hand menu). These are typical spatially
coordinated with a facing-page bi-lingual parallel text, so location is
very important.

The generated HTML / CSS could be improved in this case.

cheers
stuart

On 09/05/13 08:45, Paul F. Schaffner wrote:
> Dare I suggest that at least some floating summaries may bear some
> resemblance to the 'marginal running summaries' that I have raised
> in the past: common, e.g., in modern EETS editions, and very common
> in the 16th and 17th centuries. The chief [...]

Re: encoding some summary like parts in texts (called sootitr)

Paul F. Schaffner — Wed, 8 May 2013 16:45:27 -0400

Dare I suggest that at least some floating summaries may bear some
resemblance to the 'marginal running summaries' that I have raised
in the past: common, e.g., in modern EETS editions, and very common
in the 16th and 17th centuries. The chief distinction of marginal
summaries, of course, is that though in some sense external to the
main text, they also point into the text, and their placement is
significant, not that of a random floater. You will recall that I
ended up capturing most of these, rather unhappily, as a special @type of
(honoring their function of 'standing [...]

Re: encoding some summary like parts in texts (called sootitr)

Sebastian Rahtz — Wed, 8 May 2013 18:57:59 +0000

On 8 May 2013, at 18:40, Lou Burnard wrote:

> The trouble is that *sometimes* the thing in a "pull quote" (or "floating para" if you prefer) format is a quote from the text (and sometimes it isn't) possibly wrapped up like a cit, sometimes it behaves like a title or label, and sometimes it is indeed a brief summary of the text.
>
> So maybe what we want here is around whichever is the case?
>
so why isnt that ? [...]

Re: encoding some summary like parts in texts (called sootitr)

Lou Burnard — Wed, 8 May 2013 18:40:06 +0100

The trouble is that *sometimes* the thing in a "pull quote" (or
"floating para" if you prefer) format is a quote from the text (and
sometimes it isn't) possibly wrapped up like a cit, sometimes it
behaves like a title or label, and sometimes it is indeed a brief
summary of the text.

So maybe what we want here is around whichever is
the case? [...]

Re: encoding some summary like parts in texts (called sootitr)

Sebastian Rahtz — Wed, 8 May 2013 16:50:30 +0000

On 8 May 2013, at 16:46, Lou Burnard wrote:

> Yes, I agree with Paul that this sounds like what I know as a "pull quote": a bit of text usually but not always quoted from the story and splashed in the middle of the layout to attract readers to it. It's not a proper heading, since it isn't tied to any particular location in the text, in fact it's not always clear what it is tied to.
>
as the example shows, its a bit more than a heading, isn't it? it has some structure. this one has [...]

Re: encoding some summary like parts in texts (called sootitr)

Dr J. T. Young — Wed, 8 May 2013 17:27:33 +0100

That's what I thought too, though in the newspapers I read the 'pull
quote' is usually a *mis*quotation of the main text, which must be
infuriating for journalists. However, these things undoubtedly exist,
and I don't think ignoring them is really an option, however much you
dislike them. I've often wondered how you'd go about encoding them but
and seem plausible. I really don't see how you can
call them s because (as Lou says) they don't actually introduce
new sections, they just float around somewhere in the middle. The only
other thing I can think of is [...]

Duke Collaboratory for Classics Computing (DC3)

Hugh Cayless — Wed, 8 May 2013 12:23:59 -0400

Colleagues:

We are very pleased to announce the creation of the Duke Collaboratory for Classics Computing (DC3), a new Digital Classics R&D unit embedded in the Duke University Libraries, whose start-up has been generously funded by the Andrew W. Mellon Foundation and Duke University’s Dean of Arts & Sciences and Office of the Provost. [...]

Re: encoding some summary like parts in texts (called sootitr)

Marjorie Burghart — Wed, 8 May 2013 18:12:07 +0200

Hello Saeed!
Could it be "sous-titre", the French for "subheading"?
If these parts give an abstract / summary of the contents, maybe you could
check if would suit your needs?
Cheers, Marjorie

On 8 May 2013 14:36, Saeed Sarrafzadeh wrote:

> Hello all,
> sometimes we face with texts which has some parts displayed in a distinct
> way within main text which sometimes called (as I asked some people)
> sootitr (I don't know if they responded me exactly). That parts seems to be
> some summarization or collection of important points in the main text and
[...]

Re: encoding some summary like parts in texts (called sootitr)

Lou Burnard — Wed, 8 May 2013 16:46:11 +0100

Yes, I agree with Paul that this sounds like what I know as a "pull
quote": a bit of text usually but not always quoted from the story and
splashed in the middle of the layout to attract readers to it. It's not
a proper heading, since it isn't tied to any particular location in the
text, in fact it's not always clear what it is tied to. [...]

Re: encoding some summary like parts in texts (called sootitr)

Paul F. Schaffner — Wed, 8 May 2013 10:45:12 -0400

Sounds like any of the infinite variety of sidebars, pull quotes, etc.
that mar contemporary publishing style. "Points to remember in this
chapter" etc. Physically, may float anywhere. pfs

On Wed, 8 May 2013, Sebastian Rahtz wrote:

> On 8 May 2013, at 13:36, Saeed Sarrafzadeh
> wrote:
>
>>
>> sometimes we face with texts which has some parts displayed in a distinct way within main text which sometimes called (as I asked some people) sootitr (I don't know if they responded me exactly). That parts seems to be some summarization or collection of important points in the [...]

Re: encoding some summary like parts in texts (called sootitr)

Sebastian Rahtz — Wed, 8 May 2013 12:41:57 +0000

On 8 May 2013, at 13:36, Saeed Sarrafzadeh
wrote:

>
> sometimes we face with texts which has some parts displayed in a distinct way within main text which sometimes called (as I asked some people) sootitr (I don't know if they responded me exactly). That parts seems to be some summarization or collection of important points in the main text and may displayed everywhere near the related part (between lines or in margin or ...). This feature seems to be a common practice in newspapers and nowadays in some news sites and I saw that previously in some [...]

encoding some summary like parts in texts (called sootitr)

Saeed Sarrafzadeh — Wed, 8 May 2013 08:36:52 -0400

Hello all,
sometimes we face with texts which has some parts displayed in a distinct way within main text which sometimes called (as I asked some people) sootitr (I don't know if they responded me exactly). That parts seems to be some summarization or collection of important points in the main text and may displayed everywhere near the related part (between lines or in margin or ...). This feature seems to be a common practice in newspapers and nowadays in some news sites and I saw that previously in some text books. I wanna ask that how we can encode [...]

[ann] A series of 3 webinars on XSLT development with oXygen

George Cristian Bina — Tue, 7 May 2013 22:09:18 +0300

Hello,

I would like to invite you to attend our XSLT development with oXygen
webinars. We structured the XSLT development support in oXygen in 3 parts:

Part 1: Tomorrow, Wednesday, May 8th, between 11 AM and 12 PM EDT
Editing, Validation and Transformation
This covers the basics of XSLT support showing how to create a
stylesheet from scratch to get a HTML report from XML data, step by step
and outlining the oXygen functionality used during each step.
Details and registration link are available at
http://www.oxygenxml.com/events/2013/webinar_xslt_development_with_oXygen_Part1.html [...]

PhD students in Digital Humanities at Passau

Malte Rehbein — Tue, 7 May 2013 17:37:54 +0200

Dear list,

In addition to the recently advertised PostDoc, I am searching for two
PhD students to join the Digital Humanities team at Passau as research
and teaching fellows.

Find more details in the job description:
http://www.uni-passau.de/fileadmin/dokumente/beschaeftigte/Stellenangebote/2013_04_WM_Prof_Rehbein_Doktoranden_engl_1_1.pdf

International candidates are welcome to apply in English, and German is
not a requirement for your research and teaching.

If you have any questions, please do not hesitate to get in touch with
me. The deadline for applications is May 27th. [...]

NISO/DCMI Webinar: Semantic Mashups Across Large, Heterogeneous Institutions: Experiences from the VIVO Service

DCMI Announce — Tue, 7 May 2013 07:22:52 -0700

******************Please excuse the cross postings******************

Join NISO/DCMI for our joint May webinar

--Webinar: Semantic Mashups Across Large, Heterogeneous Institutions:
Experiences from the VIVO Service
--Date: May 22, 2013
--Time: 1:00 - 2:30 p.m. (Eastern Time - UTC 17:00:00) (World Clock:
http://bit.ly/157qF2S)
--Event webpage: http://www.niso.org/news/events/2013/dcmi/vivo/

DH-CASE 2013. Call for papers

Francesca Tomasi — Mon, 6 May 2013 18:02:22 +0200

Full message available at: DH-CASE 2013. Call for papers

Global Digital Humanities Essay Competition (Abstracts Due June 30, 2013)

Daniel O'Donnell — Sun, 5 May 2013 14:32:20 -0600

**** Please Cross Post ****

Hi all,

Global Outlook :: Digital Humanities, The University of Lethbridge, and
The Alliance of Digital Humanities Organisations is pleased to announce
the first Global Digital Humanities Essay Competition.
http://www.globaloutlookdh.org/global-outlookdigital-humanities-global-digital-humanities-essay-prize/

This is an open competition for research papers on the national,
regional, or international practice of the Digital Humanities--a broad
topic that has been designed to give authors the greatest possible
scope. Authors may write on individual projects or problems or broader
philosophical, geographical, sociological, political, or other aspects
of the practice of Digital Humanities in a global context. Papers
discussing the practice of DH [...]

CFP for JADH2013

Charles Muller — Mon, 6 May 2013 00:03:53 +0900

Dear Colleagues,

Please note that the Call for Papers for the 2013 meeting of the
Japanese Association for Digital Humanities is now open. Papers on any
aspect of TEI are warmly welcomed.

http://www.jadh.org/JADH2013

Regards,

Chuck

Re: and parallel encodings (in an authority file)

Lou Burnard — Sat, 4 May 2013 10:08:04 +0100

@corresp and are two ways of cracking the same egg, so I have
no opinion on which to recommend (actually that's not true: the standoff
method using scales up much better and creates less clutter.
But it's harder to process.)

However, if this translation/alignment is going on in a strickly
bibliographic context, you might also consider (" contains
or references some other bibliographic item which is related to the
present one in some specified manner, for example as a constituent or
alternative version of it") [...]

Re: and parallel encodings (in an authority file)

David Michelson — Fri, 3 May 2013 16:00:00 -0400

Thank you to all who sent their suggestions!

@corresp (as Syd suggested) or perhaps will better accommodate our needs.

Anyway, I'd love your thoughts on @corresp vs. for marking up parallelism in a different setting (this time a list of variant titles). To make the examples more easily intelligible, I've used the American and European titles for Harry Potter instead of Arabic. You can see that what we want to do is show multiple variants of a title and then show within those which ones are closer or more distant equivalents so that users of our data who [...]

PostDoc in Digital Humanities at Passau

Malte Rehbein — Fri, 3 May 2013 09:11:24 +0200

Dear list,

I am searching for a postdoctoral research and teaching fellow to join the newly established Digital Humanities team in the beautiful city of Passau (Bavaria, Germany). I am offering a three-years full-time contract (with possible renewal, six years max.) and the possibility to conduct your own research on fundamental methodology of DH. German is not a requirement for international candidates. You are welcome to apply and also to teach in English and contribute to Passau University's growing international programme. [...]

Ligatus Summer School 2013, Uppsala

Athanasios Velios — Thu, 2 May 2013 18:01:43 +0100

Apologies for cross-posting.

The History of European Bookbinding 1450-1830
and
Identifying and recording bookbinding structures of the Eastern
Mediterranean.
http://www.ligatus.org.uk/summerschool

26 – 30 August and 2 – 7 September 2013
University of Uppsala, Uppsala, Sweden

The 8th Ligatus Summer School, following the success of the courses in
Volos, Patmos, Thessaloniki, Wolfenbüttel, Venice, and Paris is to be
held this year at Uppsala University in Sweden, where we have access to
its magnificent library. The university was founded in 1477, and it is
the oldest university in Sweden, and still dominates the old centre of
the city, itself historically an important [...]

Re: and parallel encodings (in an authority file)

Martin Mueller — Thu, 2 May 2013 14:28:15 +0000

In Athenaeus' Deipnosophist there is a portrait of a learned pedant, whose
nickname is Keitoukeitos, because as an admirer of pure Attic he asks of
every word whether it occurs (keitai) or not (ou keitai) in the golden age
of Attic prose. Well, today the Macintosh spotlight makes it easy for each
us to be a Keitoukeitos. 'Pedantism' occurs in a dozen TCP Texts. Thus
Lady Craven in A Journey through the Crimea to Constantinople sees "in our
young men a strange mixture of pedantism and vice", and Harrington writes
in Oceana that "NOW began the native Spleen of Oceana [...]

Re: and parallel encodings (in an authority file)

Ondine LeBlanc — Thu, 2 May 2013 13:16:23 +0000

Pendatism may be a somewhat obsolete term, but it seems to be perfectly valid--as is pedanticism. (I'm validating against a 1976 Webster's unabridged.)

-----Original Message-----
From: TEI (Text Encoding Initiative) public discussion list [mailto:TEI-L@LISTSERV.BROWN.EDU] On Behalf Of Lou Burnard
Sent: Thursday, May 02, 2013 9:05 AM
To: TEI-L@LISTSERV.BROWN.EDU
Subject: Re: and parallel encodings (in an authority file) [...]

Re: and parallel encodings (in an authority file)

Lou Burnard — Thu, 2 May 2013 14:05:00 +0100

On 02/05/13 13:37, Kevin Hawkins wrote:
> While I'm raising the specter of pedantism, let me point out that
>

I think the word you want is "pedantry", Kevin. :-)

Re: and parallel encodings (in an authority file)

Kevin Hawkins — Thu, 2 May 2013 08:37:40 -0400

While I'm raising the specter of pedantism, let me point out that

Марк Твен

should in fact be

Марк Твен

because the value of @xml:lang must follow BCP 47, which says to use the
two-letter code for a language if it exists.

On the question being raised, I don't care for use of for the
same reason that Lou (and presumably Syd) doesn't. I would keep your
authority file outside of TEI: either use the MARC 21 Format for
Authority Data (which is the sort of thing you will need heavy library
technical support for), or jump [...]

Re: notes indicating future revisions

Kevin Hawkins — Thu, 2 May 2013 08:29:58 -0400

The option of using feels the most suitable to me. Your
use of is the simplest encoding, though a pedant
might argue that such a use of doesn't fit the definition of
this element. In that case, you could always give content of
like this:

Did all the encoding EXCEPT PLACE NAMES AND LINKS TO THE
GAZETTEER [...]

Re: and parallel encodings (in an authority file)

Lou Burnard — Thu, 2 May 2013 09:31:49 +0100

There's nothing strictly analogous to the EAC-CPF in
TEI P5 You could achieve the same effect though for example by adding a
new element ( anyone?) or by using the @type attribute to
distinguish say a "preferred" name from a "pseudonym" or a "translated
pseudo"

Like Syd I feel a bit unhappy about the extra tagging you would need to
bend to do the work here -- it shows us that is really
meant for choices of transcription. Suppose you had a name which had an
old and a new spelling form e.g. "Shakespyre" vs "Shakespeare" :
[...]

Re: and parallel encodings (in an authority file)

Syd Bauman — Wed, 1 May 2013 21:55:52 -0400

[Quick reply, am in middle of debugging some XSLT -- not sure how
these suggestions will mesh with ISAAR or EAC.]

What's wrong with just:

Mark Twain
[cyrillic]

Samuel Langhorne Clemens

(Answer: it's odd to ues as a grouping element for
multiple instances of itself like that, but I'd say it's better than
using persName/choice/seg/persName.) [...]

and parallel encodings (in an authority file)

Michelson, David Allen — Wed, 1 May 2013 23:38:32 +0000

Dear Colleagues,

I am writing to inquire about the use of to indicate when encodings are parallel. The guidelines mention briefly that it can be used to indicate non-exclusive parallels but I have not found extensive examples of this (one of my colleagues did get some response on a related but different query on the TEI-MS-SIG list: http://listserv.brown.edu/archives/cgi-bin/wa?A2=TEI-MS-SIG;7e519c21.1303 — thanks Lou!) [...]

notes indicating future revisions

Thomas A. Carlson — Wed, 1 May 2013 18:42:54 +0000

Dear all,

Thank you again to all who responded to my earlier question.

The editors of the project I am working on are realizing that not every desired feature of our TEI markup will be completed by the time we publish the first version. It would be nice to have a place to put notes of desired future revisions (e.g. "place names marked up, but need to add links from each name to the place in the gazetteer"), so that they don't fall off the map between versions and between editors. [...]