Pierazzo, Elena | 22 May 18:20 2015

Late Breaking call: Humanités numériques et Antiquité/ Digital Humanities and Antiquity DHANT

Dear all,

[English below]

Dans le cadre du colloque Humanités numériques et Antiquité/ Digital Humanities and Antiquity DHANT (http://dhant.sciencesconf.org), qui se tiendra à Grenoble du 2 au 4 septembre 2015, nous proposons un appel complémentaire pour quelques posters.  18 posters ont déjà été retenus mais, étant donné l’intérêt soulevé par ce colloque, nous pouvons accepter 5 ou 6 posters supplémentaires, qui ne passeront pas par la procédure de Peer-Review (Sur ces posters, figurera la precision “Late Call”).

Merci d’envoyer vos propositions avant le 10 juin à isabelle.cogitore <at> msh-alpes.fr et elena.pierazzo <at> u-grenoble3.fr


Given the large interest caused by our conference, we are now delighted to offer the possibility for submitting late proposals for posters only. The conference Humanités numériques et Antiquité/ Digital Humanities and Antiquity DHANT (http://dhant.sciencesconf.org) will take place in Grenoble from the 2nd to the 4th September. We already have 18 posters but we will be happy to include 5 to 6 more. Late proposal posters will not go through the normal peer-review process and will carry the label Late Call.

Please send your proposal before the 10 of June to the following addresses isabelle.cogitore <at> msh-alpes.fr and elena.pierazzo <at> u-grenoble3.fr

Elena Pierazzo
Visiting Senior Research Fellow
King's College London
Department of Digital Humanities
King's College London
26-29 Drury Lane

Professor of Italian Studies and Digital Humanities
Bureau F307
Université Grenoble Alpes - GERCI
BP 25 38040 Grenoble Cedex 9
Tel. +33 4 76828032

Hugh Cayless | 21 May 16:31 2015

Upcoming Council Meeting

Dear TEI-List members,

The Technical Council of the TEI will meet next week in Ann Arbor, starting on Thursday the 28th. If you have
issues you would like us to consider and haven’t yet opened a bug report or feature request at
http://tei.sourceforge.net, or if you have additional comments to make on any open tickets, please do so
before we meet. We rely on you to tell us how you want the TEI to evolve, so your input is vital!

All the best,

 *  Hugh A. Cayless, Ph.D
 *  Chair, TEI Technical Council
 *  hugh.cayless <at> duke.edu
 *  Duke Collaboratory for Classics Computing (DC3)
 *  http://blogs.library.duke.edu/dcthree/

Jeffrey Witt | 21 May 16:18 2015

declaring the type of transcription (critical or diplomatic) in the teiHeader

Hi all, 

I’m wondering if anyone has a suggestion about the place to identify in a TEI document whether a text is meant to be a “critical” or “diplomatic” transcription.

I was thinking may be somewhere in the encodingDescription like: <encodingDesc type=“diplomatic”> or <encodingDesc type=“critical”> 

Any concerns?

I anticipate that my schema is going to enforce different rules depending on whether the type is “diplomatic” or “critical”.

Thanks for your thoughts.

Dr. Jeffrey C. Witt
Philosophy Department
Loyola University Maryland
4501 N. Charles St.
Baltimore, MD 21210
Christian Grün | 21 May 15:56 2015

[ANN] BaseX 8.2: The Summer Edition

Dear all,

We invite you to check out Version 8.2, the Summer Edition, of BaseX,
our XML database system and XQuery 3.1 processor! You can expect the
following features:

 - much faster sequence modification via finger trees
 - improved compliance with XQuery 3.1

 - open, save and delete queries
 - better Tomcat support

 - updatable index structures: reduced disk space consumption

 - Standard Module: fn:json-to-xml, fn:xml-to-json
 - Web Module: web:encode-url, web:decode-url
 - File Module: file:is-absolute, file:resolve-path
 - Admin Module: admin:delete-logs
 - Database Module: db:output-cache

 - locking, full-text requests, stemming

 - event handling (will be replaced by database triggers)

The latest version is available at http://basex.org. As usual, various
minor bugs and inconsistencies have been fixed in the latest version;
check out our documentation (http://docs.basex.org) and the GitHub
commits (https://github.com/BaseXdb/basex) for more details!

We are looking forward to your feedback,
Your BaseX Team

George Bina | 21 May 13:40 2015

[ann] oXygen XML Editor 17

Hi all,

As some of you may already noticed, we released a new major version of 
oXygen XML Editor, bringing it to version 17.

The release notes are presented in detail at

Schematron Quick Fix support was already noticed by TEI users (see the 
message from Joel Kalvesmaki) - that is one of the highlights of version 
17 - along with the user friendly messages provided by Schematron 
validation, you can annotate the Schematron schema also with recovery 
actions that will be presented to the user in order to automatically fix 
a reported problem.
Next Wednesday we have a webinar that presents this functionality, both 
from the user perspective and from the Schematron developer perspective, 
so please join us then in case you want to find more about quick fixes 
and Schematron quick fixes in particular:

Another addition that you may find useful is the XML Refactoring support 
that can apply XML aware operations, defined as XQuery update scripts 
(for now, in 17.1 we plan to support also XSLT) to a set of files - but 
they are applied is a "safe" mode, preserving the DOCTYPE declarations, 
attributes order, etc.
Here it is a short video demonstration
and a webinar that explains this is scheduled for June 3:

The TEI framework was also updated to include the latest schemas (2.8.0) 
and stylesheets (7.34.0).

The SDK was updated to providing new extension points and the Web-based 
editor improves the integration API and provides an adaptive user 
interface that is both desktop and mobile-friendly.
You can quickly test this at following the "try it online" link at
If you place your own TEI files in Dropbox or Google Drive then you can 
use the test server to load them, as it includes these connectors.

I hope you find the above information useful!

Best Regards,
George Cristian Bina
<oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger

DCMI Announce | 21 May 00:57 2015

DCMI/ASIS&T Webinar: "Digital Preservation Metadata and Improvements to PREMIS in Version 3.0"

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

Digital Preservation Metadata and Improvements to PREMIS in Version 3.0

A DCMI/ASIST Joint Webinar

:: Presenter: Angela Dappert
:: Date: Wednesday, 27 May 2015
:: Time: 10:00am - 11:15am EDT (World Clock: 14:00 UTC http://bit.ly/Webinar-Dappert)


The PREMIS Data Dictionary for Preservation Metadata is the international standard for metadata to support the preservation of digital objects and ensure their long-term usability. Developed by an international team of experts, PREMIS is implemented in digital preservation projects around the world, and support for PREMIS is incorporated into a number of commercial and open-source digital preservation tools and systems. The PREMIS Editorial Committee coordinates revisions and implementation of the standard, which consists of the Data Dictionary, an XML schema, and supporting documentation.

The PREMIS Data Dictionary is currently in version 2.2. A new major release 3.0 is due out this summer. This webinar gives a brief overview of why digital preservation metadata is needed, shows examples of digital preservation metadata, shows how PREMIS can be used to capture this metadata, and illustrates some of the changes that will be available in version 3.0. 


Dr. Angela Dappert is Senior Research Fellow at the University of Portsmouth. She has widely researched and published on digital preservation. She has consulted for archives and libraries on digital life cycle management and policies, led and conducted research in the EU-co-funded Planets, Scape, TIMBUS, and E-ARK projects, and applied digital preservation practice at the British Library through work on digital repository implementation, digital metadata standards, digital asset registration, digital asset ingest, preservation risk assessment, planning and characterization, and data carrier stabilization. Angela holds a Ph.D. in Digital Preservation, an M.Sc. in Medical Informatics and an M.Sc. in Computer Sciences. She serves on the PREMIS Editorial Committee and the Digital Preservation Programme Board of National Records Scotland.

For more information and to register, visit the event webpage:
Burghart Marjorie | 20 May 23:57 2015

Re: Encoding divergent ending of a story (or: the <app> strikes back)

Thanks Fabio!
As for a deep revision of the apparatus module, we all agree. But I really think we must not postpone fixing
issues like this one and wait for a full revision of the module that will take a long time to come.
For the record, I've open a ticket on this topic:
Anyone who wishes to contribute to this ticket is welcome.

Best wishes,

----- Mail original -----
De: "Burghart Marjorie" <marjorie.burghart <at> ehess.fr>
À: "Fabio Ciotti" <fabio.ciotti <at> UNIROMA2.IT>
Envoyé: Mercredi 20 Mai 2015 23:56:26
Objet: Re: Encoding divergent ending of a story (or: the <app> strikes back)

Thanks Fabio! 
As for a deep revision of the apparatus module, we all agree. But I really think we must not postpone fixing
issues like this one and wait for a full revision of the module that will take a long time to come. 
For the record, I've open a ticket on this topic:
Anyone who wishes to contribute to this ticket is welcome. 

Best wishes, 

----- Mail original -----
De: "Fabio Ciotti" <fabio.ciotti <at> UNIROMA2.IT>
Envoyé: Mercredi 20 Mai 2015 10:10:05
Objet: Re: Encoding divergent ending of a story (or: the <app> strikes back)

I think Marjorie request is quite reasonable. Stand-off is fascinating, but
when you come to applying it to real cases it is also painful, hard to
apply and control, and you end up to hide a lot of the representation in
the "would be" processing tool (otherwise we would had abandoned XML in the
end... to recall a recent thread).

I agree that IFF you can do the easy way (inline markup) then do it. Of
course I am not taking into account the tech problems to implement it in a
content model, but I find really wrong to give up reasonable changes in the
schema if a way to express it in XML is available (although difficult).

On the other hand I really do no like extending the set of tags when there
is no real need (Ockam principle): the <app> element stand for apparatus,
and apparatus does not change its very nature if it represents variation at
phrase or block or even container level. So I think that Marjorie should
raise asking the more natural and obvious modification, then the tech
council will discuss and eventually find a technical way to do it. I would
add that this request strengthen the awareness that the whole apparatus
module should go under a deep revision.


2015-05-20 9:39 GMT+02:00 Jens Østergaard Petersen <oesterg <at> gmail.com>:

> I am all for standoff markup, but I think one argument for parallel
> segmentation is that it is humanely comprehensible. Having alternatives to
> choose from represented as children of the <app> element is simply easy to
> grok. This must be in the background of this debate, but it is seldom
> expressed, perhaps because standoff markup is technically more advanced –
> and no one wants to be seen as being challenged in that respect.
> However, we can only juggle around with so many anchors and xml:ids in our
> heads at one time, so there needs to be a way to convert between inline
> markup and standoff markup. I have experimented with this, round tripping
> inline TEI (with text-critical markup) to standoff markup, and it can be
> made to work (skewed overlaps result in multiple representations of the
> text with overlaps).
> The use case Marjorie has for a block level <app>, where a number of block
> level elements alternate on their presence, is the simplest one. The real
> challenge is to encode a number of block level elements with different
> order – and not duplicating a lot of contents in the process. There is also
> a standoff solution for this, involving flattening the XML hierarchy,
> reordering it and then combining it again – a real Humpty-Dumpty if you
> will.
> I have not had time to play with this for quite a while. Some of the code
> is in <https://github.com/jensopetersen/ShakespeareStandoff>, some in <
> https://github.com/jensopetersen/mopane>, and some in my head – needless
> to say, this work is far from completed. Ah, yes: I should admit that the
> standoff markup I use is not TEI-based …. See also <
> https://stackoverflow.com/questions/21527660/transforming-sequence-of-elements-to-tree>
> and <
> https://stackoverflow.com/questions/20729593/transforming-tree-to-sequence-of-elements>
> for the help I got in coding the block level problem.
> Jens
> On 19 May 2015 at 23:54:19, Burghart Marjorie (marjorie.burghart <at> ehess.fr)
> wrote:
> Sebastian, what you describe is actually what happens in real life. Of
> course, a whole chapter, present in some manuscripts, can be omitted in
> others, so <app> should indeed be allowed to contain <div>s.
> Just making <app> to be a sibling of <p> would already be an improvement.
> But what would be really useful would be to allow <app> to contain several
> <p>s, just like a <div>. I'm guessing that containing <div>s is not the
> most important thing, if it helps with the content model (and your quills).
> In the case of the present / omitted chapter mentioned above, for instance,
> instead of this:
> <app>
> <lem>
> <div type="chapter">
> <p>...</p>
> <p>...</p>
> <p>...</p>
> <p>...</p>
> </div>
> </lem>
> <rdg wit="#C #D"/>
> </app>
> we could have a structure like this one:
> <div type="chapter">
> <app>
> <lem>
> <p>...</p>
> <p>...</p>
> <p>...</p>
> <p>...</p>
> </lem>
> <rdg/>
> </app>
> </div>
> That would be satisfying enough.
> ----- Mail original -----
> De: "Sebastian Rahtz" <sebastian.rahtz <at> it.ox.ac.uk>
> À: "Burghart Marjorie" <marjorie.burghart <at> ehess.fr>
> Envoyé: Mardi 19 Mai 2015 23:23:35
> Objet: Re: Encoding divergent ending of a story (or: the <app> strikes
> back)
> > On 19 May 2015, at 22:06, Burghart Marjorie <marjorie.burghart <at> ehess.fr>
> wrote:
> >
> >
> > I would argue that the point is not to loosen the TEI model, but to
> correct it.
> > As it is, the TEI model is assuming that variants do not occur at div or
> paragraph levels. This is just plain wrong.
> Hang on, now. You started asking for <app> to be a child of <div>, to
> allow for an entire paragraph
> being a variant. Now you’re saying that an entire <div> can be a variant;
> and I would assume you also
> would say that a <front> or a <titlePage> can be a variant too?
> Nothing wrong with this, but it raises horrendous problems in actually
> constructing TEI
> content models which support what you describe. My hair is doing its
> "quills upon the fretful porpentine”
> thing at the thought. You’d have to make <app> a member of model.global,
> so it could appear
> _anywhere_, and then give it a content model not unlike <floatingText>.
> And then you’d have
> to learn how to process it.
> If you want to compromise by saying that you just want <app> to be
> blocklike, i.e. be a sibling of <p>,
> my quills relax.
> Sebastian Rahtz
> Chief Data Architect, IT Services


Fabio Ciotti
Dipartimento Studi Umanistici, Università di Roma Tor Vergata
Presidente Associazione Informatica Umanistica Cultura Digitale

Michelson, David Allen | 20 May 14:51 2015

Filiation vs. Provenance

Dear TEI list,

These questions are for those who work with the msDesc module.

I have a situation in which there are two manuscripts which share folia. Manuscript A was written first and at some point eight folia were removed or fell out of the manuscript. These eight folia were later inserted and bound into the front of Manuscript B. For my purposes, I will describe these eight itinerant folia as a separate msPart in my description of MS B (following a rule internal to my project which is to catalogue everything according to its current location). But I would like to also include a mention of their relationship to MS A (and I would like to include this mention in my descriptions of both MS A and MS B). 

The phrases I want to include are

In MS A’s description: “A lacuna of eight leaves between foll. 28 and 29 is filled exactly by MS B, foll. 1-8, leaves which originally belonged to this manuscript."

In MS B’s description: “These eight leaves belong to MS A where they exactly fill the lacuna between MS A, foll. 28 and 29."

What element(s) should I use? The two possibilities seem to be Filiation or History/Provenance? And would I use the same elements in my descriptions of both A and B or different elements.

On the one hand, I read the definition of the filiation element to be very close to what I am trying to do. On the other hand, my note is not really about the msContents but about the physDesc of the manuscript, thus provenance might be a better fit.

Thank you,
Michael Joyce | 19 May 23:45 2015

Encoding printed titles

My collection of documents contains newspaper articles. We're not
interested in the entire newspaper, or even a complete page - just
individual article.

They often have a title and subtitle printed in them. So far, we've
been using markup like this:

<div type='article'>
<head rend="text-transform:uppercase;" type="h1"> Oscar Wilde Arrested. </head>
                <head type="h2"> The Jury Finds Him Guilty of the
Charges by the Marquis of Queensbery. </head>
                <p>London, Apr. 3.—The case of Oscar Wilde against the
Marquis of Queensberry for
                    libel was brought to a close this morning in a
verdict in favor of the

The  <at> rend attribute contains CSS properties, and the  <at> type attribute
is meant to denote the level of the title. I initially decided to put
them in the document body's div because that's where they appear in
the printed page. But now I'm not sure, and I'm second guessing

Is it better to put the title and subtitle in the titleStmt element in
the header? Right now we're including the newspaper name and date
there (which might not be the best place for them).

Rosanna Cantavella | 19 May 19:17 2015

<div> or <seg>?

Dear all,

I'm marking up a series of medieval troubadour poetry handbooks, in 
order to localize and classify all different definitions and types of 
rhyme according to this cultural tradition. I am not transcribing 
directly from the manuscripts (often preserved in numerous witnesses), 
but from their modern editions; and not marking these works in their 
entirety, but only those parts in which definitions of rhyme are given 
in each text. 

I'm using <div> to enclose each fragment of text in which these 
definitions appear inside a given work. These fragments are in some 
cases as short as a paragraph, and in others as long as a chapter would 
be in a modern work. I usually have no more than two or three divs for 
each work: <div n= “1”>, <div n= “2”> etc.

Now my question: within each <div> I usually find definitions of several 
types of rhyme, which I'll duly mark up individually with  <at> ana 
attributes (thanks again, Lou!). But what element would you recommend 
for these arbitrary (that is, created by me and not by the author) 
chunks of text inside each <div>?

a) Again <div>? (But how should I differentiate the enclosing divs from 
these 'sub-divs'?)

b) Switch to <seg>? (But I've only seen very short <seg> examples. I 
have to enclose sometimes several paragraphs in one definition. Can 
<seg> enclose whole paragraphs? And would <seg ana= “#A1”>, <seg ana= 
“#C3”> etc. be a correct markup?)

Hypothetical example:

<div n= “1”> Bla bla bla … bla bla
<seg ana= “#C3”><p>DELS RIMS UTRISSONANS. Rim utrissonan son dig can la 
vocals muda lo significat de la dictio. mudan lo so plenissonan. en so. 
semissonan. o pel contrari. segon. quom pot ayssi vezer.
<l>Sias tempratz e gent apres. </l>
<l>En tas paraulas et apres. </l>
<l>Si fas de compas e de pes. </l>
<l>Sas obras remandran enpes.</l>
<p>Bla bla bla...</p></div>

As you can see, not every line of text inside every div refers to 
definitions, and therefore not every line or paragraph would be enclosed 
by <seg> or by these 'sub-divs'.

Thank you in advance,


Prof. Rosanna Cantavella
Universitat de València / Clare Hall, University of Cambridge 

Tamir Hassan (DocEng13 | 19 May 10:06 2015

ACM DocEng 2015 -- *Deadline extension* for short papers and application notes

Dear researcher,

We are pleased to inform you that we have now extended the deadline for 
short papers and application notes by one week - you now have until May 
28 (11:59pm AoE) to get your submissions in. So, if you have unpublished 
research work related to document engineering, now is a good time to 
consider submitting to DocEng 2015.

This year's DocEng will take place from September 8-11, 2015 at the 
Ecole Polytechnique Fédérale de Lausanne, Switzerland.

We will also have a doctoral consortium for PhD students, ProDoc <at> DocEng, 
to present their research in progress and obtain constructive feedback 
from more senior members of the audience. Submissions are also due on 
May 28. More information will follow shortly.

You can find the Call for Papers here:
=== http://www.doceng2015.org/call-papers ===

The ProDoc web page is at:
  === http://www.doceng2015.org/prodoc ===

All students presenting their work at DocEng 2015, including the 
Doctoral Consortium will be eligible to apply for an ACM SIGWEB Student 
Travel Award.

For more information, please visit the conference website at:
===  http://www.doceng2015.org  ===

Tamir Hassan
Research Scientist, HP Laboratories
Publicity Chair, ACM DocEng 2015