Jens Østergaard Petersen | 22 Sep 15:57 2014
Picon

<ab> within <ab>

That a paragraph cannot contain another paragraph is somehow evident, but why cannot an <ab> contain another <ab>?

<ab> belongs to the class of chunks which "includes the paragraph itself, and other elements which have similar structural properties, notably the <ab> (anonymous block) element described in 16.3. Blocks, Segments, and Anchors) which may be used as an alternative to the paragraph in some kinds of texts."

Are not most people using <ab> as an alternative to <div> (which of course recurses happily)?

I have always regarded <ab> as forming a pair up with the likewise "anonymous" <seg>, but <seg> can recurse.

Besides serving as hooks for linking, <ab> and <seg> are said to "also provide a convenient way of extending the semantics of the TEI markup scheme in a theory-neutral manner, by providing for two neutral or ‘anonymous’ elements to which the encoder can add any meaning not supplied by other TEI defined elements."

Since any meaning can be read into these, should they not be equally flexible?

The problem arises for me in connection with parallel alignment.

Jens


Susan Schreibman | 22 Sep 10:09 2014
Picon

PostDoc opportunity at Maynooth University

PostDoc in Irish History with Digital Humanities
An Foras Feasa
National University of Ireland, Maynooth

An Foras Feasa at Maynooth University is delighted to announce an opening for a PostDoc in Irish History
(ideally of the revolutionary period) with an expertise in Digital Humanities. The successful
candidate will join a dynamic interdisciplinary team creating the first crowdsourced digital
humanities project in Ireland, Letters of 1916. The
successful candidate will take a lead role as we prepare for the 2015 launch of the project, which has a
significant TEI component. This position is funded by the Digital Repository of Ireland

For further details about the position, please visit
http://humanresources.nuim.ie/vacancies.shtml

For further information or an informal conversation, please contact Susan Schreibman at the email
address below.

--

-- 
Susan Schreibman
Professor of Digital Humanities
Director of An Foras Feasa
Iontas Building
Maynooth University
Maynooth, Co. Kildare

email: susan.schreibman <at> nuim.ie
phone: +353 1 708 3451
fax:  +353 1 708 4797

Øyvind Eide | 21 Sep 19:51 2014
Picon
Picon

Call for Hosting Conferences: The LLOH Prize

Call for Hosting Conferences: The LLOH Prize (2015)

Deadline: October 10

Email address for proposal: oyvind.eide <at> uni-passau.de

The late EADH chair (2010-2012), Lisa Lena Opas-Hänninen, attended conferences not only in the digital
humanities but also in other disciplines. She was invariably interested in and encouraging of young
scholars in particular, and she also spent a great deal of time in informal conversation with a wide range
of colleagues. The Lisa Lena Opas-Hänninen Young Scholar Prize was established in 2013 to honour her
memory. The LLOH Prize is awarded to early-career scholars, that is, students, graduate students, or
postdoctoral researchers at different conferences each year. 

Any individual member of any of the ADHO constituent organizations may submit proposals to the Awards
Committee chair for conferences taking place in the following year. This call is specific to conferences
in 2015. Individual members are encouraged (but not required) to seek the endorsement of a constituent
organization. 

Proposals should clarify why the conference is likely to include contributions to digital humanities.
Eligible conferences may include sub-disciplines in which digital techniques have not been achieved
widespread acceptance. Special consideration should be given to proposals that encourage a diverse
pool of applicants, addressing matters of cultural, linguistic, ethnic, and gender diversity.
Proposals may ask for funding for one or two prizes and, additionally, a reception at which the prizes are
awarded. At the reception, the history and sponsorship of the prizes should be explained.

The proposal should identify the conferences (dates, venue, web site), the sort of contribution which is
to be recognized (paper, poster, etc.), how the winner or winners are to be selected, who will present the
award and explain its background, and the total budget. The budget may not exceed €1500 in total if two
prizes are to be awarded or €750 if one prize is to be awarded. The budget includes €500 for each winner
to defray the costs of travel, lodging and conference registration and up to € 250 (one prize) or € 500
(two prizes) for a reception. The awards committee selects the single best proposal for awarding the
prize(s) at a given conference. The committee will give preference to proposals from constituent
organizations that have not recently been awarded a LLOH Prize.

The 2014 LLOH Prize was awarded at the Methods in Dialectology XV conference: http://methodsxv.webhosting.rug.nl

More information about the prize can be found at the webpage of the ADHO Awards Committee: http://adho.org/awards/lisa-lena-opas-hänninen-young-scholar-prize

Please feel free to write to the committee chair with any enquires: oyvind.eide <at> uni-passau.de

--

-- 

For The ADHO Awards Committee
Øyvind Eide
Arianna Ciula | 20 Sep 19:41 2014
Picon

Cultural Literacy In Europe: submission deadline extended

Dear all,

In case you missed it, the deadline for submission of paper or project proposals for the first international conference on "Cultural Literacy in Europe" is extended to the 6th of October: http://cleurope.eu/conference/call-for-papers/

An interesting set of keynotes are lined up to stimulate an interdisciplinary discussion around the themes of the conference: http://cleurope.eu/conference/programme/keynotes/

The call for bursary is also open until the 6th of October: http://cleurope.eu/conference/bursaries/

Contributions around the concepts of textuality, fictionality, rethoricity and historicity seen from a digital humanities perspective are welcome!

Best regards,
Arianna Ciula (On Behalf of the Cultural Literacy in Europe Steering Committee)

Department of Humanities
University of Roehampton | London | SW15 5PH
James Cummings | 18 Sep 11:21 2014
Picon
Picon

Re: COCOA, anyone?

On 18/09/14 10:37, Sebastian Rahtz wrote:
> I have added that cocoa-to-tei converter to the TEI Stylesheets family on Github,
> and will in due course add scripts and test file
>
> At least this preserves the work if that Oxford projects page goes AWOL.

Does this imply ongoing support of this conversion?  I'm of the 
opinion that although we have lots of conversions in the TEIC 
Stylesheets http://github.com/TEIC/Stylesheets this doesn't 
necessarily imply that the TEI Technical Council will fully 
maintain these. Presumably we should at least be reactive and if 
people submit bugs do our best to fix them. But, there are many 
ways that script could be improved I think, but doubt even you 
would do so without some concrete reason...though maybe *you* 
would.  The TEI community will mourn the loss of the level of 
support that Sebastian provides concerning the Stylesheets as an 
elected member of the TEI Technical Council when he rotates off 
the Council at the end of this year. (Though hopefully he will 
continue to contribute as a member of the community as we 
encourage anyone else to do as well.)

-James

--

-- 
Dr James Cummings, James.Cummings <at> it.ox.ac.uk
Academic IT Services, University of Oxford

Martin Mueller | 18 Sep 00:18 2014

TEI Conference update

Dear Colleague,

I spent some time yesterday and today completing and updating the TEI 2014 Conference site at http://tei.northwestern.edu, and it should have everything on it now, except for links to the full abstracts, which will be added in early October. I'm a great fan of collaborative curation: if you find things that are wrong, unclear, or not there, tell me, and I'll try to fix them. 

If you have not yet registered or made hotel reservations, remember that Sunday, September 21 is the cutoff date for early registration and room discounts. 

Do have a look at the program of the Chicago DHCS colloqium (http://dhcs.northwestern.edu). There is also a joint summary schedule of the two events. I am not sure whether the links survive on the TEI-list, but here is the URL:


There are also several links to it from pages on the conference site. 

I look forward to meeting many of you in late October.

With best wishes


Martin Mueller
Professor emeritus of English and Classics
Northwestern University
Martin Holmes | 17 Sep 23:45 2014
Picon
Picon

Journal of the Text Encoding Initiative: Authoring package

Hi all,

You will all have seen the recent announcement that John Walsh has taken 
over as Editor-in-Chief of the Journal, and the publication of the Call 
for Papers for Issue 9, 'TEI and Materiality'[1].

We would also like to announce the availability of a new Oxygen-based 
authoring package for anyone who would like to submit their article in 
TEI XML. Since the beginning of JTEI, article submissions have been 
accepted in TEI P5 XML. However, since everyone's notion of how journal 
articles should be encoded in TEI is completely different, and the TEI 
Guidelines provide many different ways of encoding similar textual 
features, no two submissions have ever really resembled each other much, 
and every XML submission has needed substantial initial work to turn it 
into something our reviewers and copyeditors can work with. Now we are 
providing a set of schemas, along with helpful rendering tools, which 
should make the process of submission easier for authors using XML, and 
the processes of reviewing and copyediting much easier for us.

Details of the package, and a download, are available on the TEI wiki:

<http://wiki.tei-c.org/index.php/TEI_Journal_Encoding_Package>

The package has been created by Ron Van den Branden, our Technical 
Editor, with some help from me. We view this as a "beta release"; we 
have been using the tools internally for some months, but this is the 
first time authors are being asked to use them, so please report any 
issues or confusion to myself or to Ron.

Best,
Martin Holmes
(Managing Editor, JTEI)

1. 
<http://textencodinginitiative.wordpress.com/2014/09/13/new-editor-of-jtei-and-cfp-issue-9/>

Piotr Bański | 17 Sep 18:16 2014
Picon

COCOA, anyone?

"The Text Encoding Initiative community maintains legacy support for 
COCOA."[1]

Do we? ;-) The relevant link is deathly cold.[2],[3]

Thanks and best,

   Piotr

-----
[1] https://en.wikipedia.org/wiki/COCOA_%28digital_humanities%29

[2] Deathly-cold links feature the kind of hyphenation that the 
Guidelines cannot resist! :-)

[3] http://tei.oucs.ox.ac.uk/Projects/nuOTA/cocoa-to-tei.xsl

James Cummings | 17 Sep 00:04 2014
Picon
Picon

TEI P5 Guidelines version 2.7.0 is released!

Today, Tuesday 16 September 2014, the TEI Consortium has released 
TEI P5 Guidelines version 2.7.0 (Codename: NinianTheEnlightener). 
This release introduces some additional recommendations (for 
example on text directionality) significant corrections to bugs, 
many publicly submitted feature requests, and especially 
inconsistencies of all sorts.

This release was done jointly by two release technicians: Elli 
Mylonas (Brown University) and Syd Bauman (Northeastern 
University). Although our release procedure documentation is very 
detailed (see 
http://www.tei-c.org/Activities/Council/Working/tcw22.xml), this 
release raised yet more possible clarifications which will be fed 
into this documentation for future release technicians. The minor 
problems were encountered during the release were overcome easily 
with the fortitude and perseverance we expect in our the release 
technicians and with the dedicated help of other members of your 
fully-elected TEI Technical Council, especially with the help of 
Martin Holmes, Hugh Cayless, and Peter Stadler.

As always, please do report bugs and make feature requests for 
changes to the Guidelines (via theSourceForge site 
<http://tei.sf.net/>) since this is how the TEI Guidelines 
continue to improve. The software of the TEI Consortium such as 
the Stylesheets and Roma are managed on GitHub at 
https://github.com/TEIC/Stylesheets and any issues with those 
should be reported there. The updated version of the TEI 
Guidelines are available from all the usual places (such as the 
TEI website 
http://www.tei-c.org/release/doc/tei-p5-doc/en/html/index.html 
and theSourceForge site <http://tei.sf.net/>). The oxygen-tei 
package and TEI debian packages will be updated in due course 
separately. The TEI P5 version 2.7.0 release notes are below, but 
also available at 
http://www.tei-c.org/release/doc/tei-p5-doc/readme-2.7.0.html.

James Cummings
Chair, TEI Technical Council

  TEI P5 version 2.7.0 release notes

This version of the TEI Guidelines introduces new features and 
resolves a number of issues raised by the TEI community. As 
always, the majority of these changes and corrections are a 
consequence of feature requests or bugs reported by the TEI 
community using the SourceForge tracking system. If you find 
something you think needs to change in the TEI Guidelines, 
schemas, tools, or website, please submit a feature request or 
bug ticket athttp://tei.sf.net/for consideration. Lists ofclosed 
bugs

<http://sourceforge.net/p/tei/bugs/search/?q=status%3Aclosed-wont-fix+or+status%3Aclosed-rejected+or+status%3Aclosed-out-of-date+or+status%3Aclosed-accepted+or+status%3Aclosed-works-for-me+or+status%3Aclosed+or+status%3Aclosed-duplicate+or+status%3Aclosed-invalid+or+status%3Aclosed-fixed>andclosed 
feature requests

<http://sourceforge.net/p/tei/feature-requests/search/?q=status%3Aclosed-wont-fix+or+status%3Aclosed-later+or+status%3Aclosed-rejected+or+status%3Aclosed-out-of-date+or+status%3Aclosed-accepted+or+status%3Aclosed-remind+or+status%3Aclosed+or+status%3Aclosed-duplicate+or+status%3Aclosed-invalid+or+status%3Aclosed-fixed>are 
available on the site.

Some of the more noticeable changes inthis release 
<http://www.tei-c.org/release/doc/tei-p5-doc/en/html/index.html>include:

  * Chapter 5 has been expanded to include new recommendations
    and suggestions for handling text directionality and writing
    modes, including vertical text.
  * Bibliography links in the Guidelines now appear in a pop-up
    box on the same page instead of jumping to the Bibliography
    page (if you have Javascript enabled in your browser).
  * The<resp>element now claims membership
    inatt.datableperhttps://sourceforge.net/p/tei/feature-requests/513/.
  * The use of<altIdentifier>as a direct child of<msPart>is now
    deprecated
    perhttps://sourceforge.net/p/tei/feature-requests/294/: to be
    removed 2016-09-09.
  * Dozens of links to external resources that have moved or
    disappeared have been fixed or replaced.
  * Global elements were added to the content model
    of<personGrp>so that it matches more closely the permitted
    content of<person>, perhttps://sourceforge.net/p/tei/bugs/648/.
  * ‘e-mail’is now consistently
    spelled‘email’perhttps://sourceforge.net/p/tei/bugs/664/.
  * Several bibliographic entries for examples were added.
  * The deprecated <at> formattribute of the<quotation>element was
    removed.
  * A more detailed explanation the difference
    between <at> datingMethodand <at> calendarwas added
    perhttps://sourceforge.net/p/tei/bugs/668/.
  * The<constraintSpec>element is now allowed
    inside<specGrp>perhttps://sourceforge.net/p/tei/feature-requests/508/.
  * The discussion of stand-off markup, in particular of the TEI
    XPointer schemes, has been expanded and improved.
  * <msDesc>now claims membership inatt.declaring(and thus gets
    the <at> declsattribute).
  * Vestiges of the‘mandatory when applicable’and‘recommended
    when applicable’attribute usage statuses were removed
    perhttps://sourceforge.net/p/tei/bugs/676/.
  * Schematron validation now confirms that multiple pointers
    appear in the <at> targetattribute on either<join>or<link>, and
    that only a single pointer appears in
    the <at> fromand <at> toattributes
    of<span>perhttps://sourceforge.net/p/tei/bugs/671/.
  * The escape to indicate a dollar sign in the value
    of <at> replacementPatternwas changed
    from|%24|to|$$|perhttps://sourceforge.net/p/tei/bugs/629/.
  * The content model of<summary>was changed
    frommacro.phraseSeqtomacro.paraContent, thus allowing
    children
    like<cit>and<quote>perhttps://sourceforge.net/p/tei/bugs/616/.
  * <availability>has been added tomodel.biblPartand directly to
    the content models of<series>,<analytic>, and<monogr>as
    perhttps://sourceforge.net/p/tei/feature-requests/484/.
  * The descriptions of<biblScope>,<citedRange>and<locus>now
    explain how to cite single pages or ranges that only specify
    an initial location
    perhttps://sourceforge.net/p/tei/feature-requests/389/.
  * The Guidelines no longer assert on the title page that they
    are published in Charlottesville, Virginia.
  * <rs>is now a member ofatt.responsibility, thus giving it
    the <at> certand <at> respattributes
    perhttps://sourceforge.net/p/tei/feature-requests/509/.
  * The <at> mediumattribute ofatt.handFeatures(and thus of
    the<handNote>,<handShift>,<scriptNote>,
    and<typeNote>elements) now permits multiple values from its
    enumerated list of values.
  * The prose of the Guidelines and the element specification
    for<list>have been changed to differentiate between
    the <at> typeattribute, which should be used to identify the
    category of list, and the rendering attributes ( <at> rend, <at> style,
    and <at> rendition) which should be used to indicate how the list
    is rendered. Perhttps://sourceforge.net/p/tei/bugs/460/.
  * The element specification for<education>was enhanced to show
    an example using the <at> fromand <at> toattributes as well as
    the <at> notBeforeand <at> notAfterattributes, to suggest more precise
    ways of indicating dates, if appropriate.
    Perhttps://sourceforge.net/p/tei/bugs/654/.
  * The <at> newattribute is now mandatory on the<shift>element as
    perhttps://sourceforge.net/p/tei/bugs/512/.
  * The content model of<geogFeat>and<offset>is
    nowmacro.phraseSeq, making them parallel
    to<geogName>perhttps://sourceforge.net/p/tei/feature-requests/460/.
  * The<listRelation>element and members ofmodel.headLikeare now
    permitted as children
    of<listRelation>perhttps://sourceforge.net/p/tei/bugs/658/.
  * A new metadata element,<punctuation>, has been added
    tomodel.editorialDeclPartfor describing editorial practice
    with respect to punctuation marks.
  * The<surfaceGrp>element was removed fromatt.coordinated, thus
    losing the <at> start, <at> ulx, <at> uly, <at> lrx, <at> lry, and <at> pointsattributes,
    perhttps://sourceforge.net/p/tei/bugs/679/.
  * The discussion of the content of<publicationStmt>was altered
    to match the schema perhttps://sourceforge.net/p/tei/bugs/685/.
  * And, of course, dozens of typos were corrected.

In addition, improvements have been made to the XSL stylesheets 
(which provide processing of TEI ODD files for Roma and OxGarage 
as well as other TEI conversions). The Stylesheets are maintained 
separately from the Guidelines and are 
athttps://github.com/TEIC/Stylesheets.

--

-- 
Dr James Cummings,James.Cummings <at> it.ox.ac.uk
Academic IT Services, University of Oxford

Piotr Bański | 16 Sep 22:17 2014
Picon

formally-defined. repeatedly-used

Hi Council,

Given the flurry of commits in my mailbox, I hope I'm still in time 
asking the following question. I have just been casually skimming 
Chapter 1[1], and noticed some fancy hyphenations, as in:

"formally-defined style definition language such as CSS"

"used to hold repeatedly-used format descriptions"

Question: are these hyphens advocated by the Style Guide, and if not, 
aren't they spurious?

I'm not saying they are "bad", but they feel like forced attempts at 
freezing combinations that are still free and compositional. So I 
thought I'd ask.

Thanks and good luck with the upcoming release,

   Piotr

[1]: http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ST.html

Birnbaum, David J | 16 Sep 16:06 2014
Picon

common_core.xsl in <oXygen/>

Dear TEI-L,

When I try to transform a TEI document that has <at> place attributes on <note> elements (validates as TEI all in the latest version of <oXygen/>) using the built-in transformation scenario (click the red triangle, choose the first option), the transformation fails with the following error:

System ID: /Users/djb/Downloads/oxygen-3/frameworks/tei/xml/tei/stylesheet/common/common_core.xsl
Scenario: TEI P5 XHTML
XML file: /Users/djb/Dropbox/2014-09_varna_el-manuscript/workshop/Azbukovnik.xml
XSL file: /Users/djb/Downloads/oxygen-3/frameworks/tei/xml/tei/stylesheet/html/html.xsl
Document type: TEI P5
Engine name: Saxon-PE 9.5.1.5
Severity: error
Description: Processing terminated by xsl:message at line 1023 in common_core.xsl
Start location: 1023:1

When I open common_core.xsl, it's invalid (105 errors). Is this a TEI problem, an <oXygen/> problem, or - worst of all - user error?

Thanks,

David


Gmane