Council

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.

Wednesday 19 September 2012
Location: IT Services, 13 Banbury Road, Oxford, OX2 8NP - Kennet Room

09:30 - 10:30 Items to discuss
 * Review of Ann Arbor Actions and Teleconference Actions (JC)
 * Reports from SIGs (JC)
 * Deprecation policy: We need to figure out what we're doing. See Kevin's summary of current practice and stalled discussion
 * Private URI Schemes proposal (MH)

10:30 - 12:30 (tea break ~11:00)
 * Ticket Breakout Groups

12:30 - 13:30
 * Lunch

14:00 - 15:00 Items to discuss
 * Report on TEI ODD Workshop; ODD Proposals (JC/SR)
 * XPointer Proposal (GB)
 * Resolving Durand: c.f. http://foxglove.hypotheses.org/368 (LB)

15:00 - 16:30 (tea break ~16:00)
 * Ticket Breakout Groups

16:30 - 17:30
 * Discussion and supper plans

19:30 - 
 * Supper: http://www.al-shami.co.uk/ (Middle Eastern)

Thursday 20 September 2012
Location: Private Dining Room, Wolfson College, Linton Road, Oxford, OX2 6UD (Also use of 'coffee room' and 'florey room')

09:30 - 10:30 Items to discuss
 * Roma Templates and Example Customizations
 * Transcription of Speech and Video (LB)
 * Div.Liminal(lb)
 * LingSIG issues (PB)
 * Add yours here

10:30 - 12:30 (tea break ~11am)
 * Ticket Breakout Groups

12:30 - 13:30
 * Lunch

13:30 - 15:00 Items to discuss
 * Board Proposals for Council Consideration (EP)
 * We have very similar information on writing ODDs in the Guidelines and on the TEI-C website. I think these should be merged into one place.  Where should the merged documentation be?  Can someone review each document to make sure it's accurate before we ask someone to merge the two?
 * Add yours here
 * Add yours here

15:00 - 16:30 (tea break ~4pm)
 * Ticket Breakout Groups

16:30 - 17:30
 * Discussion and supper plans
 * Supper: If weather is nice, we thought about walking up the river from Wolfson to: http://www.victoriaarms.co.uk a nearby pub run by the Oxford Preservation Trust (British pub food). We may even take you here by punt. If weather is not so good we’ll go elsewhere in nearby Summertown.

Friday 21 September 2012
Location: Private Dining Room, Wolfson College, Linton Road, Oxford, OX2 6UD (Also use of 'coffee room' and 'florey room')

09:30 - 10:30 Items to discuss
 * Code Bounties: Decide Topics: (e.g. Roma ReWrite), poss specification brainstorming
 * Options for freezing and/or archiving Lite. Planning Lite reLaunch.
 * Add yours here

10:30 - 12:30 (tea break ~11am)
 * Ticket Breakout Groups

12:30 - 13:30
 * Lunch

13:30 - 15:00 Items to discuss
 * Experimental modules, lists of customizations, etc. (from discussion in early September on tei-council)
 * Sebastian should explain the purpose of providing downloadable customizations.
 * On http://www.tei-c.org/Guidelines/Customization/ and http://www.tei-c.org/Guidelines/Customization/odds.xml, are any modules labeled as experimental that should not be, or any modules not labeled but should be? (Note that currently the dictionaries module is documented differently on these two pages.)  Sebastian said that none are experimental any more.
 * Roma interface
 * Do we agree with Sebastian removing MS, dict, speech, drama, and corpus from the "Create Customization from template" drop-down menu at http://www.tei-c.org/Roma/ ? He said that Bare, Lite, and Tite make sense since they are coherent and have a purpose, and that SVG, MathML, XInclude, ITS, and ODD are also sensible since they involve non-obvious techniques which you can't recreate easily in Roma.  But the remaining five are are not meaningfully useful, documented, or follow any known recommendation.  James said they were supplied here as simple example customisations.  Martin suggested separating out such options as "advanced".
 * Should we provide template for community-created customisations in Roma that are reasonably mature and well-supported, such as EpiDoc? What would be our management process for this?
 * Should we begin generating HTML and PDF documentation for any modules besides Lite and Tite (and putting them in http://www.tei-c.org/release/doc/tei-p5-exemplars/ )?
 * For the two sections of customizations at http://www.tei-c.org/Guidelines/Customization/ :
 * Do we want to rename the first heading "Customizations provided by the TEI Consortium" to "Customizations maintained by the TEI Consortium" or "Customizations supported by the TEI Consortium"?
 * Can we clarify what "more restricted or experimental" means? These are not the same thing, and it isn't clear what either means.
 * Do we want to set up a procedure for deciding what can be added to the "TEI Community Customizations" or for periodically revisiting those listed there? Even if not, should we just go ahead and remove MEP from the list since the links are broken and it's not a P3 thing?
 * Do we find the heading "TEI Community Customizations" clear enough, or do we want to add a paragraph here explaining ?
 * Add yours here

15:00 - 16:30 (tea break ~4pm)
 * Ticket Breakout Groups

16:30 - 17:30
 * Discussion and supper plans

19:30 - 
 * Supper: http://www.mysichuan.co.uk/ (Chinese)

Agenda

 * Brief Reports
 * TEI Tite (KH)
 * SIG reports (JC)
 * Google Books (KH)
 * Physical Bibliography (KH)
 * ODD Meeting after DH2012 (JC)
 * XPointer scheme proposal (GB)
 * Face2Face Meeting: arrangements (JC)
 * Replacement for SY or not? (JC)
 * TEI Lite (LB)
 * Reminder to finish off Ann Arbor Actions (JC)
 * (more items TBD)

F2F meeting - Ann Arbor 15-18 April 2012
Turkish-American Friendship Room, Shapiro Science Library

Description : http://www.lib.umich.edu/node/22671/ Location : 42.275832 -83.737265

Here is a list of AnnArbor2012-Actions to be done.

Sunday 15 April 10:00-16:00 (optional)
Optional TEI HackFest for those arriving early (because of flights including a Saturday being cheaper) or local people who wish to attend.

Possible tasks for the day:


 * From Sebastian: "I think there is some problem of ODD processing in a pending ticket which I said was doable with some concentration - was it the idea of redeclaration of attributes (i.e. datatypes) in the P5 source itself?"
 * From Sebastian: "We need to reassess what is left over from EEBO/ECCO work which still needs resolving, to give a context for Monday"
 * James-C: Vault-related tidying perhaps; Also have some TEI -> MARC (for Google eBooks from TEI -> ePub) XSLT to complete.
 * Lou : I would like to work on accomodating some existing TEI-like schemas into proper TEI ODDs. Notably Vogeler's "Charters Encoding Initiative" dtd; other suggestions welcome. How about a proper effort to bring EAD back into the paths of righteousness? (Sebastian says: in a day?????)
 * Lou : I would also like to work on some Garage case studies, of the Word -> P5 variety

10:00 - 12:30'ish:
 * Hack on TEI-related development

12:30 - 14:30:
 * lunch

14:30 - 16:00:
 * More TEI-related hacking

19:00 -
 * Supper

Monday 16 April 09:00 - 17:30
(Tentative and flexible timetabled agenda)

09:00 - 10:00:
 * TEI - Google Books
 * TEI - EEBO / ECCO

10:00 - 12:30:
 * TEI Bugs and FR: (Green and hopefully some amber ones)

12:30 - 14:30 (shorter if possible):
 * Lunch

14:30 - 15:30:
 * TEI and Schematron Tests
 * TEI Exemplars (e.g. Tite)
 * Best Practices for TEI in Libraries

15:30 - 17:30:
 * TEI Bugs and FR: (Amber)

19:00- Supper (optional)

Tuesday 17 April 09:00 - 17:30
09:00-10:00:
 * TEI Namespaces and Conformance
 * Chapter/module fragmentation and consolidation (e.g. should things like 'dates' become a chapter of its own)
 * TEI Examples

10:00 - 12:30:
 * TEI Bugs and FR (Amber)

12:30 - 14:30:
 * 'Open Lunch' with people from University of Michigan community interested in meeting us

14:30 - 15:30:
 * TEI FR: Floating Div
 * TEI ODD Meeting

15:30 - 17:30:
 * TEI Bugs and FR (Amber)

19:00- Supper (optional)

Wednesday 18 April 09:00 - 16:00
09:00 - 10:00:
 * TEI and URIs
 * TEI Release Process
 * TEI Outreach and Education
 * Any Other Council Business

10:00 - 12:30:
 * Bugs and FR (Amber / Red)

12:30 - 14:30 (or shorter):
 * Lunch

14:30 - 16:00 (or longer?):
 * Bugs and FR: outstanding / summary
 * (early end for those who need flights)

Teleconference - Tuesday 28 February 2012 at 18:00 GMT

 * 1) Brief Reports
 * 2) Bibliographic Citations (KH & MH)
 * 3) TEI Tite (KH)
 * 4) TEI and AdBlock (MH)
 * 5) Google Books (KH)
 * 6) Xpointer (GB)
 * 7) Attribute Datatypes (MH)
 * 8) Physical Bibliography (KH)
 * 9) TEI Release Process Document (MH)
 * 10) Future of ODD meeting, DH2012 (JC)
 * 11) @ref/key/cRef & Private URI Schemes (MH)
 * 12) Best Practices for TEI in Libraries (KH)
 * 13) Practical Arrangements for April Face2Face (RW)
 * 14) Agenda for the April Face2Face (JC)
 * 15) 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

 * minutes in TEI
 * Paris 2011-11 minutes

Agenda
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. http://www.tei-c.org/Activities/Council/Working/tcw20.xml)
 * TEI and Google: report from Martin M. and strategy
 * TEI for publishing - next steps (reports from Lou (revues.org+PUC), 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 ()

SY Gate is a really good flexible framework that includes tokenisation, but only pretends to do XML: ( http://thread.gmane.org/gmane.comp.ai.gate.general/5257 )

KH: cf. http://purl.oclc.org/NET/teiinlibraries

Minutes
Minutes of the Chicago meeting for reference

Item for further consideration

 * Stable URIs to discrete bits of the guidelines
 * Council FR assignments

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 )

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
Minutes of the Dublin meeting for reference

Ad-hoc committee on encoding of bibliographic citations
Ad-hoc committee on encoding of bibliographic citations

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

Agenda

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

Local organisation - programm of the seminar
Meeting in Lyon Available abstracts under:

Draft Agenda
Minutes of the October meeting for reference (SourceForge item 2411994) and related issue of permanent URLs for TEI documentation - David Sewell SF ID: 2411994
 * 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
 * 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?

etc.) http://www.tei-c.org.uk/Vault/Vault-GL.html (LB)
 * 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
 * SIGs
 * TEI in library SIG - TEI Tite status
 * New SIG: Scientific bibliographies
 * Report: TEI Manuscript
 * Misc.
 * Necessary work on www.tei-c.org (further rationalization of structure,
 * In particular, status of TEI vault

http://quod.lib.umich.edu/t/tei/ (Chris Powell)

Chris Ruotolo: For now, you can find older versions of the Guidelines at http://www.tei-c.org.uk/Vault/Vault-GL.html, We are in the process of moving these archival files to the current website.

Syd: They used to be at http://www.tei-c.org/Vault/GL/P1/  [source only] http://www.tei-c.org/Vault/GL/P2/ [source only] http://www.tei-c.org/Vault/GL/P3/index.htm [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: http://quod.lib.umich.edu/t/tei/ http://etext.virginia.edu/standards/tei/teip3/

Council Telco - 21 August 2008
Minutes of the last meeting: http://www.tei-c.org/Activities/Council/Meetings/tcm39.xml

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 (http://lists.village.virginia.edu/pipermail/tei-council/2008/009971.html) 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

http://lists.village.virginia.edu/pipermail/tei-council/2008/010033.html
 * placement of Schematron rules in ODD

Note to be produced by SR


 * update on '"getting started"', see https://USER@tei.svn.sourceforge.net/svnroot/tei/trunk/Documents/GettingStarted (replacing 'USER' with your SourceForge username) and Getting Started

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)

Namespaces


 * 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)

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 ( in http://www.tei-c.org/ns/1.0), 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. http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-tree.html

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 : http://tei.svn.sourceforge.net/viewvc/tei/trunk/P5/Source/Specs/event.xml?revision=231&view=markup

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: http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-event.html but on the generated reference pages like this contain a link to the appropriate place in the SVN repository? i.e. http://tei.svn.sourceforge.net/viewvc/tei/trunk/P5/Source/Specs/event.xml?view=log 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: http://www.tei-c.org/Guidelines/access.xml

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 in the Guidelines

http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-name.html

we would use something like

doi:10.1111/tei-p5-doc:en:ref-name

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.

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