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. 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 and creates pages in the category reserved for use by TEI Council.

Meetings

See the checklist for organizing a face-to-face meeting.

Meeting date and place	Agenda	Minutes	Action items
2015-07-28 Teleconference	Council Agenda 2015-07
2015-06-29 Teleconference	Council Agenda 2015-06	final minutes	(in minutes)
2015-05/27/28/29 Face to face in Ann Arbor, MI, USA	Council Agenda 2015-05	final minutes	(in minutes)
2015-04-24 Teleconference	Council Agenda 2015-04	final minutes	(in minutes)
2015-03-27 Teleconference	Council Agenda 2015-03	final minutes	(in minutes)
2015-02-27 Teleconference	Council agenda 2015-02	final minutes	(in minutes)
2015-01-30 Teleconference	Council agenda 2015-01	final minutes	(in minutes)
2014-12-05 Teleconference	Council agenda 2014-12	final minutes	(in minutes)
2014-11-17/18/19 Face to Face in Durham, NC, USA	Council agenda 2014-11	final minutes	(in minutes)
2014-10-03 Teleconference	Council agenda 2014-10	final minutes	(in minutes)
2014-08-01 Teleconference	Council agenda 2014-08	final minutes	(in minutes)
2014-06-30/07-02 Face to Face in Oxford	Council agenda 2014-06	final minutes	(in minutes)
2014-05-30 Teleconference	Council agenda 2014-05	final minutes	(in minutes)
2014-03-07 Teleconference	Council agenda 2014-03	final minutes	(in minutes)
2014-01-10 Teleconference	Council agenda 2014-01	final minutes
2013-11-11 to 2013-11-13 face-to-face Oxford	Council agenda 2013-11	final minutes	Oxford2013-Actions2
2013-10-21 Teleconference	Council agenda 2013-10	final minutes
2013-04-11 to 2013-04-13 face-to-face Providence	Council agenda 2013-04	final minutes	Council actions 2013-04
2012-12-13 teleconference	Council agenda 2012-12	final minutes
2012-09-19 to 2012-09-21 face-to-face meeting Oxford	Council agenda 2012-09	final minutes	Oxford2012-Actions
2012-08-09 teleconference	Council agenda 2012-08	final minutes
2012-04-15 to 2012-04-18 face-to-face meeting Ann Arbor	Council agenda 2012-04	final minutes	AnnArbor2012-Actions
2012-02-28 Teleconference	Council agenda 2012-02	final minutes
2011-11-07 to 2011-11-09 face-to-face meeting Paris	Council agenda 2011-11	final minutes
2011-08-17 teleconference		final minutes
2011-04-11 to 2011-04-13 face-to-face meeting Chicago	Council agenda 2011-04	Council notes 2011-04, final minutes
2010-10 feature request assignments	Council FR assignments
2010-04-28 to 2010-04-30 face-to-face meeting Dublin	Council agenda 2010-04	final minutes
2010-02-08 teleconference		final minutes
2009-12-07 teleconference		final minutes
2009-10-13 teleconference	Council agenda 2009-10	final minutes
2009-04-01 to 2009-04-03 face-to-face meeting Lyon	Council 2009-04	final minutes
2008-10-07 teleconference	Council agenda 2008-10	final minutes
For minutes of previous meetings, see minutes on TEI-C website

Workgroups

A full list is on the TEI-C website and the following wiki pages:

• Ad-hoc committee on encoding of bibliographic citations
• Text Directionality Workgroup

Old notes

Item for further consideration

• Stable URIs to discrete bits of the guidelines

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 (<author> 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 <event>: 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 <name> 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.