From TEIWiki

Revision as of 23:22, 15 February 2012 by Kshawkin (Talk | contribs)
Jump to: navigation, search

The TEI Technical Council, often referred to as 'TEI Council' or 'Council' is the elected body that is responsible for maintaining and implementing the TEI Guidelines. Also see the Council section of the TEI-C website for archived documents, and TEI-Council-FAQ for a Council FAQ. The TEI Council also uses this page to store some of its draft agendas while working them up before Face 2 Face meetings.


F2F meeting - Ann Arbor 15-18 April 2012



Sunday 15 April

Optional TEI HackFest for those arriving early (because of flights including a Saturday being cheaper) or local people who wish to attend.

Monday 16 April 09:00 - 17:00

  • TEI - Google Books
  • TEI Bugs and FR
  • TEI Release Process
  • TEI Exemplars
  • TEI Examples

Tuesday 17 April 09:00 - 17:00

  • More of same?

Wednesday 18 April 09:00 - 15:00

  • Finish off
  • (early end for those who need flights)

Teleconference - Tuesday 28 February 2012 at 18:00 GMT

  1. Brief Reports
    1. Bibliographic Citations (KH & MH)
    2. TEI Tite (KH)
    3. TEI and AdBlock (MH)
    4. Google Books (KH)
    5. Xpointer (GB)
    6. Attribute Datatypes (MH)
    7. Physical Bibliography (KH)
    8. TEI Release Process Document (MH)
  2. @ref/key/cRef & Private URI Schemes (MH)
  3. Best Practices for TEI in Libraries (KH)
  4. Practical Arrangements for April Face2Face (RW)
  5. Agenda for the April Face2Face (JC)
  6. AOB

F2F meeting - Paris 7-9 Nov. 2011

Location: Inria, 23 avenue d'Italie, Paris


Monday 7 - 10.00 - 17.00

  • organisational:
    • 9:30: breakfast
    • 12:30: lunch at Pizzeria Via Italia (Pizzeria Via Italia - 21, avenue d'Italie - 01 42 16 97 89)
    • 15:30: coffee break
  • topical
    • Review of FRs / Bugs
    • Genetic Work

Tuesday 9 - 9.00 - 17.00

  • organisational:
    • 10:00: coffee break
    • 12:30: lunch at restaurant de L'Avant-Goût (L'avant Goût - 26, rue Bobillot - 01 53 80 24 00)
    • 15:30: coffee break
  • topical
    • FRs / Bugs
    • EEBO stuff - with Brian L Pytlik Zillig
    • floating objects...

Wednesday 10 - 9.00 - 16.00

  • organisational:
    • 10:00: coffee break
    • 12:30: lunch at restaurant de L'Avant-Goût
    • 15:30: coffee break
  • topical
    • Wiki access restrictions
    • P4 survey
    • grp vs. list
    • Magic tokens
    • translations
    • P6 discussion and visions
    • community project
    • core too big
    • modifying attributes from a class
    • revamping Roma
    • Planning priorities for next year

Minutes/notes Paris 2011 Meeting

F2F meeting - Chicago 11-13 April 2010


Most of the three days will be dedicated to expediting SF tickets. In between we have the following items to consider for discussion.

  • Automating guidelines production (Presentation by Sebastian, Tuesday morning)
  • Presentation on editing the Guidelines (Lou cf.
  • TEI and Google: report from Martin M. and strategy
  • TEI for publishing - next steps (reports from Lou (, Kevin for TEI PUB SIG?)
  • deprecation, beta, etc.
  • automatic generation of feeds/twitts from SF tickets (new ones; solved ones)

From the ongoing discussion, we may also want to discuss the following issues:

  • usage of floatingText within other constructs: sp, quote, etc.


TEI and Google

very bare TEI with adequate but sparse functionalities for structural and linguistic annotation

MM: When we worked on the MONK project and prepared the various TEI P4 versions for linguistic annotation, it became immediately apparent that nobody had ever given any thought to the problems of tokenization that arose for the sqirrely ways of recording or not recording words that break at lines or pages. But the question "What should an annotatable text look like?" is an important question.

LR: cf. Kernkodierung in TextGrid - minimal token annotation (<w>)

SY Gate is a really good flexible framework that includes tokenisation, but only pretends to do XML: ( )

KH: cf.

Minutes =

Minutes of the Chicago meeting for reference

Item for further consideration

F2F meeting - Dublin 28-30 April 2010

Thursday: 9:30 - 17:00; Friday: 9:30 - 15:00 (catered lunches 12:30-13:30, coffee breaks mid-morning and mid-afternoon)


Thursday morning

  • Welcome, overview of agenda
  • Wrap-up from Symposium
  • First SF session (see [1])

Thursday afternoon

  • Manuscript (genetic editions)
  • Second SF session
  • 4 p.m.: biblStruct

Friday morning

  • hyphenation
  • ODD - (r)evolutions
  • Third SF session

Friday afternoon

  • remaining issues
  • prospective

Topics for discussion

  • Deprecating mechanisms
  • Pointing and keying - can one absorb the other? (key?, target/targets)


Minutes of the Dublin meeting for reference

Ad-hoc committee on encoding of bibliographic citations

Ad-hoc committee on encoding of bibliographic citations

Telko October 2009

Connexion details

Call information:

Conference Room: 1349998

Skype (free): +9900827041349998

Telephone numbers:

  • Domestic*

USA USA 1-201-793-9022 Canada Canada 1-201-793-9022 Long distance costs apply

  • International*

Austria Austria 0820 401 15470 Belgium Belgium 0703 57 134 France France 0826 109 071 Germany Germany 01805 00 9527 Ireland Ireland 0818 270 968 Italy Italy 848 390 177 Spain Spain 902 885 791 Switzerland Switzerland 0848 560 397 United Kingdom United Kingdom 0870 0990 931


  • SF
  • reworking the generic TEI-to-HTML stylesheets
  • HTML5
  • valList and content
  • report to TEI MM

Face to face meeting - Lyon 1-3 April 2009

Local organisation - programm of the seminar

Meeting in Lyon Available abstracts under: [2]

Draft Agenda

Minutes of the October meeting for reference

  • Bug and features - SF
  • Focussed technical discussions
    • Placement of schematron constraints in ODD - Sebastian Rahtz
    • Discussion of "canonical way of referencing TEI element definitions"
    • Wider debate: the future of ODD

(SourceForge item 2411994) and related issue of permanent URLs for TEI documentation - David Sewell SF ID: 2411994

    • Reporting on stylesheets (SR, DOD)
      • Evolution towards XSL 2.0
        • main advantages (features) provided by a switch to 2.0
        • consequences on the TEI infrastructure; maintenance of one or two sets of stylesheets?
        • how much of this should be known by the TEI community?
  • Getting started (PB)
  • Projects
    • TEI - ISO
  • Perspective workshop on TEI for the next decade
    • communities
      • role of TEI in research infrastructures (AC)
    • event
      • Dagstuhl
      • ESF [3]
  • SIGs
    • TEI in library SIG - TEI Tite status
    • New SIG: Scientific bibliographies [4]
    • Report: TEI Manuscript[5]
  • Misc.
    • Necessary work on (further rationalization of structure,


    • In particular, status of TEI vault (LB) (Chris Powell)

Chris Ruotolo: For now, you can find older versions of the Guidelines at, We are in the process of moving these archival files to the current website.

Syd: They used to be at  [source only]  [source only]  [source in P3X/]

But I don't know where old stuff went when we moved to the new website. In any case, there are copies of P3 at:

Council Telco - 21 August 2008

Minutes of the last meeting:

Issues for next Telco - Oct 2008

  • update on SF bugs and features (Oxford)
  • report to TEI MM
  • naming releases/versions (tei vs. P5)

Peter Boot: tei.full - tei.components

This refers to my (PB's) question on the council list ( about identification of releases and the following discussions. The difference between the two packages (tei.full - tei.components ) on SF has been clarified. Sebastian has added version numbers to generated schema’s.

Issues that remain

- do we use the SF news mechanism (a project where the latest news item dates from a year ago doesn't seem very dynamic)

- Roma shows a version number of the software, not of the TEI release that is being used

  • update on SIGs + responsabilities
  • placement of Schematron rules in ODD

Note to be produced by SR

Looking for candidates:

    • 6. Choosing and installing an editor
    • 9. Getting this to work on sample of own text
    • 11. Where to go from here

Issues for next F2F

  • Discussion on ODD and its evolution--Romary 02:34, 9 September 2008 (EDT)

cf. @usage in elementSpec

ODD modifing an ODD (ODD architecture)


  • Evolution of Roma

Proposal (SR): rewriting Roma almost entirely in Javascript, interacting with web services to deliver TEI and to generate outputs. The Javascript would grab a copy of TEI (cut down) from a chosen server, and load it into memory. Then it would use that to help you build your ODD. when you were done, it would send the ODD document to a web service whose job is to return a schema or documentation back to the browsers. So Roma would be a Javascript ODD editor, not needing server support beyond a simple Apache, but closely coupled to a pair of generic web services. The generator web service would be identical code to the Vesta desktop

Additional functionalities needed (PB):

- adding copy element functionality,

- supporting the creation/manipulation of content models (instead of the user having to write the models),

- support/help in creating schematron constraints?

- TEI schema validation service (cf. also ISO project)

  • should the TEI-C we produce a general purpose online service which can validate and process documents (cf. ISO work)

Highlights to be brought to the TEI MM 2008

Topics (could be moved up to one F2F or Telco meeting

  • Stable reference to TEI objects

(For original source of these comments, see tei-council thread Quoting a TEI Object from September 2008. DS has created a new wiki page for discussing stable references.)

[LR] In many cases, one has to map schemas and describe the mappings by reference to actual objects in the respective encoding schemes. In this context do (should) we have a mechanism to refer uniquely to TEI objects, beyond the reference to the TEI namespace (<author> in, sort of TEI unique identifiers?

[JC] I'd think the proper way to cite an element, class, or datatype generally is to point to its reference page.

However, we might want to re-examine that... while the hierarchy should remain the same, deprecated elements (etc.) disappear. I have no way easy way to point to something at a particular date in time...unless maybe I point to it at a particular revision in the SVN source tree?

Pointing to a location in the SVN source tree isn't necessarily very pretty but does work and is accurate:

See for example an earlier version of <event>:

As a cognate example, I can point to any revision of a page in the TEI wiki at any point in its history. We should be able to do this, somehow, in the official way we are meant to cite TEI sources as changing objects in time.

However, maybe an easier solution is to cite: but on the generated reference pages like this contain a link to the appropriate place in the SVN repository? i.e. which lists all the revisions.

[AC] The only place on the website where I am ware there are some recommendations with URLs is the citation page:

This could certainly be enriched with notes on how to point to an element on the line James suggests, but in that case would the version number be enough to point to particular revisions?

[DS] As an alternative to using a TEI-specific convention for citing URLs, we might want to consider adopting one or another of the standard systems for permanent identifiers, for example DOI (Digital Object Identifier).

In the case of DOI, there would be some fairly minimal costs involved to register the DOIs with one of the national registries, but some more extensive costs in human time to set up a good system for mapping from our existing nomenclature to a set of DOI identifiers. (Publishers typically use DOIs to identify individual books or journal articles, but they can be more granular: every reference page in the Guidelines could have its own DOI, for example.)

The advantage of doing this would be that anyone accustomed to using DOIs for citations could simply cite a DOI. So instead of the reference for <name> in the Guidelines

we would use something like


which would be resolved to the actual Web address by a DOI resolver. (Many journal DOIs are mostly numeric but the syntax allows more human-readable names).

If we seriously want to consider an option like this, we should put out a call to the librarians/metadata gurus in our community for assistance with implementation.


For general information concerning the council see TEI-Council-FAQ page and category reserved for use by TEI Council...

Personal tools