TEIWiki - User contributions [en]

Council

2011-11-09T13:45:34Z

Romary: /* Wednesday 10 - 9.00 - 16.00 */

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 [http://www.tei-c.org/Activities/Council/ Council section of the TEI-C website] for archived documents, and [[TEI-Council-FAQ]] for a Council FAQ

== F2F meeting - Paris 7-9 Nov. 2011 ==

Location: Inria, 23 avenue d'Italie, Paris

=== Agenda ===

==== 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 ==

[[Paris 2011-11 minutes]]

== F2F meeting - Chicago 11-13 April 2010 ==

=== 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.

=== Notes ===
==== 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: ( http://thread.gmane.org/gmane.comp.ai.gate.general/5257 )

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

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

=== Agenda ===
==== Thursday morning ====
* Welcome, overview of agenda
* Wrap-up from Symposium
* First SF session (see [http://www.tei-c.org/Activities/Council/Working/tcw17.html])
==== 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 ===

[http://www.tei-c.org/Activities/Council/Meetings/tcm45.xml 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

=== Agenda ===
* 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 ===
[https://listes.cru.fr/wiki/tei-res/public/tei_council_2009_a_lyon Meeting in Lyon]
Available abstracts under: [https://listes.cru.fr/wiki/tei-res/prive/reunioncouncilavril09]

=== Draft Agenda ===
[http://www.tei-c.org/Activities/Council/Meetings/tcm40.xml 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
[http://sourceforge.net/tracker2/?func=detail&aid=2411994&group_id=106328&atid=644065 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 [http://www.esf.org/activities/exploratory-workshops.html]
* SIGs
** TEI in library SIG - TEI Tite status
** New SIG: Scientific bibliographies [http://www.tei-c.org/Activities/Council/Working/tcw16.xml]
** Report: TEI Manuscript[http://www.tei-c.org/Activities/SIG/Manuscript/mssigr03.pdf]
* Misc.
** Necessary work on www.tei-c.org (further rationalization of structure,
etc.)
** In particular, status of TEI vault
http://www.tei-c.org.uk/Vault/Vault-GL.html (LB)

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

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

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--[[User:Romary|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)

== 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 [http://lists.village.virginia.edu/pipermail/tei-council/2008/010041.html Quoting a TEI Object] from September 2008. DS has created a new wiki page for discussing [[Council:stable references|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.

== Misc. ==
For general information concerning the council see [[TEI-Council-FAQ]] page and [[:Category: Council|category reserved for use by TEI Council]]...

[[Category:Council]]

Council

2011-11-09T11:23:45Z

Romary: /* Wednesday 10 - 9.00 - 16.00 */

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 [http://www.tei-c.org/Activities/Council/ Council section of the TEI-C website] for archived documents, and [[TEI-Council-FAQ]] for a Council FAQ

== F2F meeting - Paris 7-9 Nov. 2011 ==

Location: Inria, 23 avenue d'Italie, Paris

=== Agenda ===

==== 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
** grp vs. list
** community project
** Magic tokens
** P4 survey
** P6 discussion and visions
** core too big
** modifying attributes from a class
** revamping Roma
** translations
** Planning priorities for next year

== Minutes/notes Paris 2011 Meeting ==

[[Paris 2011-11 minutes]]

== F2F meeting - Chicago 11-13 April 2010 ==

=== 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.

=== Notes ===
==== 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: ( http://thread.gmane.org/gmane.comp.ai.gate.general/5257 )

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

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

=== Agenda ===
==== Thursday morning ====
* Welcome, overview of agenda
* Wrap-up from Symposium
* First SF session (see [http://www.tei-c.org/Activities/Council/Working/tcw17.html])
==== 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 ===

[http://www.tei-c.org/Activities/Council/Meetings/tcm45.xml 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

=== Agenda ===
* 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 ===
[https://listes.cru.fr/wiki/tei-res/public/tei_council_2009_a_lyon Meeting in Lyon]
Available abstracts under: [https://listes.cru.fr/wiki/tei-res/prive/reunioncouncilavril09]

=== Draft Agenda ===
[http://www.tei-c.org/Activities/Council/Meetings/tcm40.xml 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
[http://sourceforge.net/tracker2/?func=detail&aid=2411994&group_id=106328&atid=644065 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 [http://www.esf.org/activities/exploratory-workshops.html]
* SIGs
** TEI in library SIG - TEI Tite status
** New SIG: Scientific bibliographies [http://www.tei-c.org/Activities/Council/Working/tcw16.xml]
** Report: TEI Manuscript[http://www.tei-c.org/Activities/SIG/Manuscript/mssigr03.pdf]
* Misc.
** Necessary work on www.tei-c.org (further rationalization of structure,
etc.)
** In particular, status of TEI vault
http://www.tei-c.org.uk/Vault/Vault-GL.html (LB)

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

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

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--[[User:Romary|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)

== 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 [http://lists.village.virginia.edu/pipermail/tei-council/2008/010041.html Quoting a TEI Object] from September 2008. DS has created a new wiki page for discussing [[Council:stable references|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.

== Misc. ==
For general information concerning the council see [[TEI-Council-FAQ]] page and [[:Category: Council|category reserved for use by TEI Council]]...

[[Category:Council]]

Council

2011-11-09T11:23:22Z

Romary: /* Wednesday 10 - 9.00 - 16.00 */

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 [http://www.tei-c.org/Activities/Council/ Council section of the TEI-C website] for archived documents, and [[TEI-Council-FAQ]] for a Council FAQ

== F2F meeting - Paris 7-9 Nov. 2011 ==

Location: Inria, 23 avenue d'Italie, Paris

=== Agenda ===

==== 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
** grp vs. list
** community project
** Magic tokens
** P4 survey
** P6 discussion and visions
** core too big
** modifying attributes from a class
** P6
** revamping Roma
** translations
** Planning priorities for next year

== Minutes/notes Paris 2011 Meeting ==

[[Paris 2011-11 minutes]]

== F2F meeting - Chicago 11-13 April 2010 ==

=== 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.

=== Notes ===
==== 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: ( http://thread.gmane.org/gmane.comp.ai.gate.general/5257 )

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

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

=== Agenda ===
==== Thursday morning ====
* Welcome, overview of agenda
* Wrap-up from Symposium
* First SF session (see [http://www.tei-c.org/Activities/Council/Working/tcw17.html])
==== 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 ===

[http://www.tei-c.org/Activities/Council/Meetings/tcm45.xml 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

=== Agenda ===
* 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 ===
[https://listes.cru.fr/wiki/tei-res/public/tei_council_2009_a_lyon Meeting in Lyon]
Available abstracts under: [https://listes.cru.fr/wiki/tei-res/prive/reunioncouncilavril09]

=== Draft Agenda ===
[http://www.tei-c.org/Activities/Council/Meetings/tcm40.xml 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
[http://sourceforge.net/tracker2/?func=detail&aid=2411994&group_id=106328&atid=644065 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 [http://www.esf.org/activities/exploratory-workshops.html]
* SIGs
** TEI in library SIG - TEI Tite status
** New SIG: Scientific bibliographies [http://www.tei-c.org/Activities/Council/Working/tcw16.xml]
** Report: TEI Manuscript[http://www.tei-c.org/Activities/SIG/Manuscript/mssigr03.pdf]
* Misc.
** Necessary work on www.tei-c.org (further rationalization of structure,
etc.)
** In particular, status of TEI vault
http://www.tei-c.org.uk/Vault/Vault-GL.html (LB)

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

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

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--[[User:Romary|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)

== 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 [http://lists.village.virginia.edu/pipermail/tei-council/2008/010041.html Quoting a TEI Object] from September 2008. DS has created a new wiki page for discussing [[Council:stable references|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.

== Misc. ==
For general information concerning the council see [[TEI-Council-FAQ]] page and [[:Category: Council|category reserved for use by TEI Council]]...

[[Category:Council]]

Council

2011-11-09T11:19:33Z

Romary: /* Wednesday 10 - 9.00 - 16.00 */

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 [http://www.tei-c.org/Activities/Council/ Council section of the TEI-C website] for archived documents, and [[TEI-Council-FAQ]] for a Council FAQ

== F2F meeting - Paris 7-9 Nov. 2011 ==

Location: Inria, 23 avenue d'Italie, Paris

=== Agenda ===

==== 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
** grp vs. list
** community project
** Magic tokens
** P4 survey
** core too big
** modifying attributes from a class
** revamping Roma
** translations
** Planning priorities for next year

== Minutes/notes Paris 2011 Meeting ==

[[Paris 2011-11 minutes]]

== F2F meeting - Chicago 11-13 April 2010 ==

=== 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.

=== Notes ===
==== 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: ( http://thread.gmane.org/gmane.comp.ai.gate.general/5257 )

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

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

=== Agenda ===
==== Thursday morning ====
* Welcome, overview of agenda
* Wrap-up from Symposium
* First SF session (see [http://www.tei-c.org/Activities/Council/Working/tcw17.html])
==== 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 ===

[http://www.tei-c.org/Activities/Council/Meetings/tcm45.xml 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

=== Agenda ===
* 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 ===
[https://listes.cru.fr/wiki/tei-res/public/tei_council_2009_a_lyon Meeting in Lyon]
Available abstracts under: [https://listes.cru.fr/wiki/tei-res/prive/reunioncouncilavril09]

=== Draft Agenda ===
[http://www.tei-c.org/Activities/Council/Meetings/tcm40.xml 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
[http://sourceforge.net/tracker2/?func=detail&aid=2411994&group_id=106328&atid=644065 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 [http://www.esf.org/activities/exploratory-workshops.html]
* SIGs
** TEI in library SIG - TEI Tite status
** New SIG: Scientific bibliographies [http://www.tei-c.org/Activities/Council/Working/tcw16.xml]
** Report: TEI Manuscript[http://www.tei-c.org/Activities/SIG/Manuscript/mssigr03.pdf]
* Misc.
** Necessary work on www.tei-c.org (further rationalization of structure,
etc.)
** In particular, status of TEI vault
http://www.tei-c.org.uk/Vault/Vault-GL.html (LB)

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

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

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--[[User:Romary|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)

== 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 [http://lists.village.virginia.edu/pipermail/tei-council/2008/010041.html Quoting a TEI Object] from September 2008. DS has created a new wiki page for discussing [[Council:stable references|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.

== Misc. ==
For general information concerning the council see [[TEI-Council-FAQ]] page and [[:Category: Council|category reserved for use by TEI Council]]...

[[Category:Council]]

Council

2011-11-09T11:18:39Z

Romary: /* Wednesday 10 - 9.00 - 16.00 */

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 [http://www.tei-c.org/Activities/Council/ Council section of the TEI-C website] for archived documents, and [[TEI-Council-FAQ]] for a Council FAQ

== F2F meeting - Paris 7-9 Nov. 2011 ==

Location: Inria, 23 avenue d'Italie, Paris

=== Agenda ===

==== 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
** community project
** Magic tokens
** P4 survey
** core too big
** modifying attributes from a class
** grp vs. list
** revamping Roma
** translations
** Planning priorities for next year

== Minutes/notes Paris 2011 Meeting ==

[[Paris 2011-11 minutes]]

== F2F meeting - Chicago 11-13 April 2010 ==

=== 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.

=== Notes ===
==== 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: ( http://thread.gmane.org/gmane.comp.ai.gate.general/5257 )

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

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

=== Agenda ===
==== Thursday morning ====
* Welcome, overview of agenda
* Wrap-up from Symposium
* First SF session (see [http://www.tei-c.org/Activities/Council/Working/tcw17.html])
==== 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 ===

[http://www.tei-c.org/Activities/Council/Meetings/tcm45.xml 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

=== Agenda ===
* 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 ===
[https://listes.cru.fr/wiki/tei-res/public/tei_council_2009_a_lyon Meeting in Lyon]
Available abstracts under: [https://listes.cru.fr/wiki/tei-res/prive/reunioncouncilavril09]

=== Draft Agenda ===
[http://www.tei-c.org/Activities/Council/Meetings/tcm40.xml 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
[http://sourceforge.net/tracker2/?func=detail&aid=2411994&group_id=106328&atid=644065 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 [http://www.esf.org/activities/exploratory-workshops.html]
* SIGs
** TEI in library SIG - TEI Tite status
** New SIG: Scientific bibliographies [http://www.tei-c.org/Activities/Council/Working/tcw16.xml]
** Report: TEI Manuscript[http://www.tei-c.org/Activities/SIG/Manuscript/mssigr03.pdf]
* Misc.
** Necessary work on www.tei-c.org (further rationalization of structure,
etc.)
** In particular, status of TEI vault
http://www.tei-c.org.uk/Vault/Vault-GL.html (LB)

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

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

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--[[User:Romary|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)

== 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 [http://lists.village.virginia.edu/pipermail/tei-council/2008/010041.html Quoting a TEI Object] from September 2008. DS has created a new wiki page for discussing [[Council:stable references|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.

== Misc. ==
For general information concerning the council see [[TEI-Council-FAQ]] page and [[:Category: Council|category reserved for use by TEI Council]]...

[[Category:Council]]

Council

2011-11-09T11:12:37Z

Romary: /* Wednesday 10 - 9.00 - 16.00 */

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 [http://www.tei-c.org/Activities/Council/ Council section of the TEI-C website] for archived documents, and [[TEI-Council-FAQ]] for a Council FAQ

== F2F meeting - Paris 7-9 Nov. 2011 ==

Location: Inria, 23 avenue d'Italie, Paris

=== Agenda ===

==== 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
** Magic tokens
** P4 survey
** core too big
** modifying attributes from a class
** grp vs. list
** revamping Roma
** translations
** Planning priorities for next year

== Minutes/notes Paris 2011 Meeting ==

[[Paris 2011-11 minutes]]

== F2F meeting - Chicago 11-13 April 2010 ==

=== 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.

=== Notes ===
==== 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: ( http://thread.gmane.org/gmane.comp.ai.gate.general/5257 )

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

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

=== Agenda ===
==== Thursday morning ====
* Welcome, overview of agenda
* Wrap-up from Symposium
* First SF session (see [http://www.tei-c.org/Activities/Council/Working/tcw17.html])
==== 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 ===

[http://www.tei-c.org/Activities/Council/Meetings/tcm45.xml 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

=== Agenda ===
* 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 ===
[https://listes.cru.fr/wiki/tei-res/public/tei_council_2009_a_lyon Meeting in Lyon]
Available abstracts under: [https://listes.cru.fr/wiki/tei-res/prive/reunioncouncilavril09]

=== Draft Agenda ===
[http://www.tei-c.org/Activities/Council/Meetings/tcm40.xml 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
[http://sourceforge.net/tracker2/?func=detail&aid=2411994&group_id=106328&atid=644065 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 [http://www.esf.org/activities/exploratory-workshops.html]
* SIGs
** TEI in library SIG - TEI Tite status
** New SIG: Scientific bibliographies [http://www.tei-c.org/Activities/Council/Working/tcw16.xml]
** Report: TEI Manuscript[http://www.tei-c.org/Activities/SIG/Manuscript/mssigr03.pdf]
* Misc.
** Necessary work on www.tei-c.org (further rationalization of structure,
etc.)
** In particular, status of TEI vault
http://www.tei-c.org.uk/Vault/Vault-GL.html (LB)

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

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

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--[[User:Romary|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)

== 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 [http://lists.village.virginia.edu/pipermail/tei-council/2008/010041.html Quoting a TEI Object] from September 2008. DS has created a new wiki page for discussing [[Council:stable references|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.

== Misc. ==
For general information concerning the council see [[TEI-Council-FAQ]] page and [[:Category: Council|category reserved for use by TEI Council]]...

[[Category:Council]]

Council

2011-11-06T09:01:52Z

Romary: /* Tuesday 9 - 9.00 - 17.00 */

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 [http://www.tei-c.org/Activities/Council/ Council section of the TEI-C website] for archived documents, and [[TEI-Council-FAQ]] for a Council FAQ

== F2F meeting - Paris 7-9 Nov. 2011 ==

Location: Inria, 23 avenue d'Italie, Paris

=== Agenda ===

==== 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: coffe break
* topical
** Review of FRs / Bugs
** Genetic Work

==== Tuesday 9 - 9.00 - 17.00 ====
* organisational:
** 10:°0: coffe 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: coffe break
* topical
** FRs / Bugs
** EEBO stuff - with Brian L Pytlik Zillig
** floating objects...

==== Wednesday 10 - 9.00 - 16.00 ====
* organisational:
** 10:°0: coffe break
** 12:30: lunch at restaurant de L'Avant-Goût
** 15:30: coffe break
* topical
** Wiki access restrictions
** Magic tokens
** P4 survey
** Planning priorities for next year

== F2F meeting - Chicago 11-13 April 2010 ==

=== 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.

=== Notes ===
==== 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: ( http://thread.gmane.org/gmane.comp.ai.gate.general/5257 )

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

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

=== Agenda ===
==== Thursday morning ====
* Welcome, overview of agenda
* Wrap-up from Symposium
* First SF session (see [http://www.tei-c.org/Activities/Council/Working/tcw17.html])
==== 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 ===

[http://www.tei-c.org/Activities/Council/Meetings/tcm45.xml 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

=== Agenda ===
* 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 ===
[https://listes.cru.fr/wiki/tei-res/public/tei_council_2009_a_lyon Meeting in Lyon]
Available abstracts under: [https://listes.cru.fr/wiki/tei-res/prive/reunioncouncilavril09]

=== Draft Agenda ===
[http://www.tei-c.org/Activities/Council/Meetings/tcm40.xml 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
[http://sourceforge.net/tracker2/?func=detail&aid=2411994&group_id=106328&atid=644065 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 [http://www.esf.org/activities/exploratory-workshops.html]
* SIGs
** TEI in library SIG - TEI Tite status
** New SIG: Scientific bibliographies [http://www.tei-c.org/Activities/Council/Working/tcw16.xml]
** Report: TEI Manuscript[http://www.tei-c.org/Activities/SIG/Manuscript/mssigr03.pdf]
* Misc.
** Necessary work on www.tei-c.org (further rationalization of structure,
etc.)
** In particular, status of TEI vault
http://www.tei-c.org.uk/Vault/Vault-GL.html (LB)

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

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

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--[[User:Romary|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)

== 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 [http://lists.village.virginia.edu/pipermail/tei-council/2008/010041.html Quoting a TEI Object] from September 2008. DS has created a new wiki page for discussing [[Council:stable references|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.

== Misc. ==
For general information concerning the council see [[TEI-Council-FAQ]] page and [[:Category: Council|category reserved for use by TEI Council]]...

[[Category:Council]]

Council

2011-11-06T09:01:35Z

Romary: /* Monday 7 - 10.00 - 17.00 */

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 [http://www.tei-c.org/Activities/Council/ Council section of the TEI-C website] for archived documents, and [[TEI-Council-FAQ]] for a Council FAQ

== F2F meeting - Paris 7-9 Nov. 2011 ==

Location: Inria, 23 avenue d'Italie, Paris

=== Agenda ===

==== 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: coffe break
* topical
** Review of FRs / Bugs
** Genetic Work

==== Tuesday 9 - 9.00 - 17.00 ====
* organisational:
** 10:°0: coffe break
** 12:30: lunch at restaurant de L'Avant-Goût
** 15:30: coffe break
* topical
** FRs / Bugs
** EEBO stuff - with Brian L Pytlik Zillig
** floating objects...

==== Wednesday 10 - 9.00 - 16.00 ====
* organisational:
** 10:°0: coffe break
** 12:30: lunch at restaurant de L'Avant-Goût
** 15:30: coffe break
* topical
** Wiki access restrictions
** Magic tokens
** P4 survey
** Planning priorities for next year

== F2F meeting - Chicago 11-13 April 2010 ==

=== 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.

=== Notes ===
==== 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: ( http://thread.gmane.org/gmane.comp.ai.gate.general/5257 )

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

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

=== Agenda ===
==== Thursday morning ====
* Welcome, overview of agenda
* Wrap-up from Symposium
* First SF session (see [http://www.tei-c.org/Activities/Council/Working/tcw17.html])
==== 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 ===

[http://www.tei-c.org/Activities/Council/Meetings/tcm45.xml 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

=== Agenda ===
* 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 ===
[https://listes.cru.fr/wiki/tei-res/public/tei_council_2009_a_lyon Meeting in Lyon]
Available abstracts under: [https://listes.cru.fr/wiki/tei-res/prive/reunioncouncilavril09]

=== Draft Agenda ===
[http://www.tei-c.org/Activities/Council/Meetings/tcm40.xml 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
[http://sourceforge.net/tracker2/?func=detail&aid=2411994&group_id=106328&atid=644065 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 [http://www.esf.org/activities/exploratory-workshops.html]
* SIGs
** TEI in library SIG - TEI Tite status
** New SIG: Scientific bibliographies [http://www.tei-c.org/Activities/Council/Working/tcw16.xml]
** Report: TEI Manuscript[http://www.tei-c.org/Activities/SIG/Manuscript/mssigr03.pdf]
* Misc.
** Necessary work on www.tei-c.org (further rationalization of structure,
etc.)
** In particular, status of TEI vault
http://www.tei-c.org.uk/Vault/Vault-GL.html (LB)

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

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

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--[[User:Romary|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)

== 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 [http://lists.village.virginia.edu/pipermail/tei-council/2008/010041.html Quoting a TEI Object] from September 2008. DS has created a new wiki page for discussing [[Council:stable references|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.

== Misc. ==
For general information concerning the council see [[TEI-Council-FAQ]] page and [[:Category: Council|category reserved for use by TEI Council]]...

[[Category:Council]]

Council

2011-11-06T08:37:34Z

Romary: /* F2F meeting - Paris 7-9 Nov. 2011 */

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 [http://www.tei-c.org/Activities/Council/ Council section of the TEI-C website] for archived documents, and [[TEI-Council-FAQ]] for a Council FAQ

== F2F meeting - Paris 7-9 Nov. 2011 ==

Location: Inria, 23 avenue d'Italie, Paris

=== Agenda ===

==== Monday 7 - 10.00 - 17.00 ====
* organisational:
** 9:30: breakfast
** 12:30: lunch at Pizzeria Via Italia
** 15:30: coffe break
* topical
** Review of FRs / Bugs
** Genetic Work

==== Tuesday 9 - 9.00 - 17.00 ====
* organisational:
** 10:°0: coffe break
** 12:30: lunch at restaurant de L'Avant-Goût
** 15:30: coffe break
* topical
** FRs / Bugs
** EEBO stuff - with Brian L Pytlik Zillig
** floating objects...

==== Wednesday 10 - 9.00 - 16.00 ====
* organisational:
** 10:°0: coffe break
** 12:30: lunch at restaurant de L'Avant-Goût
** 15:30: coffe break
* topical
** Wiki access restrictions
** Magic tokens
** P4 survey
** Planning priorities for next year

== F2F meeting - Chicago 11-13 April 2010 ==

=== 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.

=== Notes ===
==== 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: ( http://thread.gmane.org/gmane.comp.ai.gate.general/5257 )

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

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

=== Agenda ===
==== Thursday morning ====
* Welcome, overview of agenda
* Wrap-up from Symposium
* First SF session (see [http://www.tei-c.org/Activities/Council/Working/tcw17.html])
==== 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 ===

[http://www.tei-c.org/Activities/Council/Meetings/tcm45.xml 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

=== Agenda ===
* 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 ===
[https://listes.cru.fr/wiki/tei-res/public/tei_council_2009_a_lyon Meeting in Lyon]
Available abstracts under: [https://listes.cru.fr/wiki/tei-res/prive/reunioncouncilavril09]

=== Draft Agenda ===
[http://www.tei-c.org/Activities/Council/Meetings/tcm40.xml 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
[http://sourceforge.net/tracker2/?func=detail&aid=2411994&group_id=106328&atid=644065 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 [http://www.esf.org/activities/exploratory-workshops.html]
* SIGs
** TEI in library SIG - TEI Tite status
** New SIG: Scientific bibliographies [http://www.tei-c.org/Activities/Council/Working/tcw16.xml]
** Report: TEI Manuscript[http://www.tei-c.org/Activities/SIG/Manuscript/mssigr03.pdf]
* Misc.
** Necessary work on www.tei-c.org (further rationalization of structure,
etc.)
** In particular, status of TEI vault
http://www.tei-c.org.uk/Vault/Vault-GL.html (LB)

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

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

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--[[User:Romary|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)

== 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 [http://lists.village.virginia.edu/pipermail/tei-council/2008/010041.html Quoting a TEI Object] from September 2008. DS has created a new wiki page for discussing [[Council:stable references|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.

== Misc. ==
For general information concerning the council see [[TEI-Council-FAQ]] page and [[:Category: Council|category reserved for use by TEI Council]]...

[[Category:Council]]

Council

2011-11-05T17:40:36Z

Romary: /* Tuesday 9 - 9.00 - 17.00 */

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 [http://www.tei-c.org/Activities/Council/ Council section of the TEI-C website] for archived documents, and [[TEI-Council-FAQ]] for a Council FAQ

== F2F meeting - Paris 7-9 Nov. 2011 ==

Location: Inria, 23 avenue d'Italie, Paris

=== Agenda ===

==== Monday 7 - 10.00 - 17.00 ====
* Review of FRs / Bugs
* Genetic Work

==== Tuesday 9 - 9.00 - 17.00 ====
* FRs / Bugs
* EEBO stuff - with Brian L Pytlik Zillig
* floating objects...

==== Wednesday 10 - 9.00 - 16.00 ====
* Wiki access restrictions
* Magic tokens
* P4 survey
* Planning priorities for next year

== F2F meeting - Chicago 11-13 April 2010 ==

=== 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.

=== Notes ===
==== 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: ( http://thread.gmane.org/gmane.comp.ai.gate.general/5257 )

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

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

=== Agenda ===
==== Thursday morning ====
* Welcome, overview of agenda
* Wrap-up from Symposium
* First SF session (see [http://www.tei-c.org/Activities/Council/Working/tcw17.html])
==== 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 ===

[http://www.tei-c.org/Activities/Council/Meetings/tcm45.xml 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

=== Agenda ===
* 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 ===
[https://listes.cru.fr/wiki/tei-res/public/tei_council_2009_a_lyon Meeting in Lyon]
Available abstracts under: [https://listes.cru.fr/wiki/tei-res/prive/reunioncouncilavril09]

=== Draft Agenda ===
[http://www.tei-c.org/Activities/Council/Meetings/tcm40.xml 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
[http://sourceforge.net/tracker2/?func=detail&aid=2411994&group_id=106328&atid=644065 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 [http://www.esf.org/activities/exploratory-workshops.html]
* SIGs
** TEI in library SIG - TEI Tite status
** New SIG: Scientific bibliographies [http://www.tei-c.org/Activities/Council/Working/tcw16.xml]
** Report: TEI Manuscript[http://www.tei-c.org/Activities/SIG/Manuscript/mssigr03.pdf]
* Misc.
** Necessary work on www.tei-c.org (further rationalization of structure,
etc.)
** In particular, status of TEI vault
http://www.tei-c.org.uk/Vault/Vault-GL.html (LB)

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

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

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--[[User:Romary|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)

== 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 [http://lists.village.virginia.edu/pipermail/tei-council/2008/010041.html Quoting a TEI Object] from September 2008. DS has created a new wiki page for discussing [[Council:stable references|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.

== Misc. ==
For general information concerning the council see [[TEI-Council-FAQ]] page and [[:Category: Council|category reserved for use by TEI Council]]...

[[Category:Council]]

Council

2011-11-05T17:40:19Z

Romary: /* Wednesday 10 - 9.00 - 16.00 */

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 [http://www.tei-c.org/Activities/Council/ Council section of the TEI-C website] for archived documents, and [[TEI-Council-FAQ]] for a Council FAQ

== F2F meeting - Paris 7-9 Nov. 2011 ==

Location: Inria, 23 avenue d'Italie, Paris

=== Agenda ===

==== Monday 7 - 10.00 - 17.00 ====
* Review of FRs / Bugs
* Genetic Work

==== Tuesday 9 - 9.00 - 17.00 ====
* FRs / Bugs
* EEBO stuff - with Brian L Pytlik Zillig

==== Wednesday 10 - 9.00 - 16.00 ====
* Wiki access restrictions
* Magic tokens
* P4 survey
* Planning priorities for next year

== F2F meeting - Chicago 11-13 April 2010 ==

=== 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.

=== Notes ===
==== 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: ( http://thread.gmane.org/gmane.comp.ai.gate.general/5257 )

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

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

=== Agenda ===
==== Thursday morning ====
* Welcome, overview of agenda
* Wrap-up from Symposium
* First SF session (see [http://www.tei-c.org/Activities/Council/Working/tcw17.html])
==== 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 ===

[http://www.tei-c.org/Activities/Council/Meetings/tcm45.xml 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

=== Agenda ===
* 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 ===
[https://listes.cru.fr/wiki/tei-res/public/tei_council_2009_a_lyon Meeting in Lyon]
Available abstracts under: [https://listes.cru.fr/wiki/tei-res/prive/reunioncouncilavril09]

=== Draft Agenda ===
[http://www.tei-c.org/Activities/Council/Meetings/tcm40.xml 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
[http://sourceforge.net/tracker2/?func=detail&aid=2411994&group_id=106328&atid=644065 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 [http://www.esf.org/activities/exploratory-workshops.html]
* SIGs
** TEI in library SIG - TEI Tite status
** New SIG: Scientific bibliographies [http://www.tei-c.org/Activities/Council/Working/tcw16.xml]
** Report: TEI Manuscript[http://www.tei-c.org/Activities/SIG/Manuscript/mssigr03.pdf]
* Misc.
** Necessary work on www.tei-c.org (further rationalization of structure,
etc.)
** In particular, status of TEI vault
http://www.tei-c.org.uk/Vault/Vault-GL.html (LB)

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

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

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--[[User:Romary|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)

== 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 [http://lists.village.virginia.edu/pipermail/tei-council/2008/010041.html Quoting a TEI Object] from September 2008. DS has created a new wiki page for discussing [[Council:stable references|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.

== Misc. ==
For general information concerning the council see [[TEI-Council-FAQ]] page and [[:Category: Council|category reserved for use by TEI Council]]...

[[Category:Council]]

Council

2011-11-05T17:32:54Z

Romary: /* Tuesday 9 - 9.00 - 17.00 */

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 [http://www.tei-c.org/Activities/Council/ Council section of the TEI-C website] for archived documents, and [[TEI-Council-FAQ]] for a Council FAQ

== F2F meeting - Paris 7-9 Nov. 2011 ==

Location: Inria, 23 avenue d'Italie, Paris

=== Agenda ===

==== Monday 7 - 10.00 - 17.00 ====
* Review of FRs / Bugs
* Genetic Work

==== Tuesday 9 - 9.00 - 17.00 ====
* FRs / Bugs
* EEBO stuff - with Brian L Pytlik Zillig

==== Wednesday 10 - 9.00 - 16.00 ====
* Wiki access restrictions
* Planning priorities for next year

== F2F meeting - Chicago 11-13 April 2010 ==

=== 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.

=== Notes ===
==== 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: ( http://thread.gmane.org/gmane.comp.ai.gate.general/5257 )

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

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

=== Agenda ===
==== Thursday morning ====
* Welcome, overview of agenda
* Wrap-up from Symposium
* First SF session (see [http://www.tei-c.org/Activities/Council/Working/tcw17.html])
==== 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 ===

[http://www.tei-c.org/Activities/Council/Meetings/tcm45.xml 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

=== Agenda ===
* 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 ===
[https://listes.cru.fr/wiki/tei-res/public/tei_council_2009_a_lyon Meeting in Lyon]
Available abstracts under: [https://listes.cru.fr/wiki/tei-res/prive/reunioncouncilavril09]

=== Draft Agenda ===
[http://www.tei-c.org/Activities/Council/Meetings/tcm40.xml 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
[http://sourceforge.net/tracker2/?func=detail&aid=2411994&group_id=106328&atid=644065 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 [http://www.esf.org/activities/exploratory-workshops.html]
* SIGs
** TEI in library SIG - TEI Tite status
** New SIG: Scientific bibliographies [http://www.tei-c.org/Activities/Council/Working/tcw16.xml]
** Report: TEI Manuscript[http://www.tei-c.org/Activities/SIG/Manuscript/mssigr03.pdf]
* Misc.
** Necessary work on www.tei-c.org (further rationalization of structure,
etc.)
** In particular, status of TEI vault
http://www.tei-c.org.uk/Vault/Vault-GL.html (LB)

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

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

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--[[User:Romary|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)

== 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 [http://lists.village.virginia.edu/pipermail/tei-council/2008/010041.html Quoting a TEI Object] from September 2008. DS has created a new wiki page for discussing [[Council:stable references|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.

== Misc. ==
For general information concerning the council see [[TEI-Council-FAQ]] page and [[:Category: Council|category reserved for use by TEI Council]]...

[[Category:Council]]

Council

2011-09-06T13:33:04Z

Romary: /* F2F meeting - Paris 7-9 Nov. 2011 */

Also see the [http://www.tei-c.org/Activities/Council/ Council section of the TEI-C website] for archived documents, and [[TEI-Council-FAQ]] for a Council FAQ

== F2F meeting - Paris 7-9 Nov. 2011 ==

Location: Inria, 23 avenue d'Italie, Paris

=== Agenda ===

==== Monday 7 - 10.00 - 17.00 ====

==== Monday 7 - 9.00 - 17.00 ====

==== Monday 7 - 9.00 - 16.00 ====

== F2F meeting - Chicago 11-13 April 2010 ==

=== 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.

=== Notes ===
==== 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: ( http://thread.gmane.org/gmane.comp.ai.gate.general/5257 )

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

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

=== Agenda ===
==== Thursday morning ====
* Welcome, overview of agenda
* Wrap-up from Symposium
* First SF session (see [http://www.tei-c.org/Activities/Council/Working/tcw17.html])
==== 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 ===

[http://www.tei-c.org/Activities/Council/Meetings/tcm45.xml 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

=== Agenda ===
* 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 ===
[https://listes.cru.fr/wiki/tei-res/public/tei_council_2009_a_lyon Meeting in Lyon]
Available abstracts under: [https://listes.cru.fr/wiki/tei-res/prive/reunioncouncilavril09]

=== Draft Agenda ===
[http://www.tei-c.org/Activities/Council/Meetings/tcm40.xml 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
[http://sourceforge.net/tracker2/?func=detail&aid=2411994&group_id=106328&atid=644065 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 [http://www.esf.org/activities/exploratory-workshops.html]
* SIGs
** TEI in library SIG - TEI Tite status
** New SIG: Scientific bibliographies [http://www.tei-c.org/Activities/Council/Working/tcw16.xml]
** Report: TEI Manuscript[http://www.tei-c.org/Activities/SIG/Manuscript/mssigr03.pdf]
* Misc.
** Necessary work on www.tei-c.org (further rationalization of structure,
etc.)
** In particular, status of TEI vault
http://www.tei-c.org.uk/Vault/Vault-GL.html (LB)

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

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

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--[[User:Romary|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)

== 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 [http://lists.village.virginia.edu/pipermail/tei-council/2008/010041.html Quoting a TEI Object] from September 2008. DS has created a new wiki page for discussing [[Council:stable references|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.

== Misc. ==
For general information concerning the council see [[TEI-Council-FAQ]] page and [[:Category: Council|category reserved for use by TEI Council]]...

[[Category:Council]]

Council

2011-09-06T13:29:42Z

Romary:

Also see the [http://www.tei-c.org/Activities/Council/ Council section of the TEI-C website] for archived documents, and [[TEI-Council-FAQ]] for a Council FAQ

== F2F meeting - Paris 7-9 Nov. 2011 ==

Location:
Inria
23 avenue d'Italie
75013 Paris

== F2F meeting - Chicago 11-13 April 2010 ==

=== 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.

=== Notes ===
==== 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: ( http://thread.gmane.org/gmane.comp.ai.gate.general/5257 )

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

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

=== Agenda ===
==== Thursday morning ====
* Welcome, overview of agenda
* Wrap-up from Symposium
* First SF session (see [http://www.tei-c.org/Activities/Council/Working/tcw17.html])
==== 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 ===

[http://www.tei-c.org/Activities/Council/Meetings/tcm45.xml 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

=== Agenda ===
* 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 ===
[https://listes.cru.fr/wiki/tei-res/public/tei_council_2009_a_lyon Meeting in Lyon]
Available abstracts under: [https://listes.cru.fr/wiki/tei-res/prive/reunioncouncilavril09]

=== Draft Agenda ===
[http://www.tei-c.org/Activities/Council/Meetings/tcm40.xml 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
[http://sourceforge.net/tracker2/?func=detail&aid=2411994&group_id=106328&atid=644065 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 [http://www.esf.org/activities/exploratory-workshops.html]
* SIGs
** TEI in library SIG - TEI Tite status
** New SIG: Scientific bibliographies [http://www.tei-c.org/Activities/Council/Working/tcw16.xml]
** Report: TEI Manuscript[http://www.tei-c.org/Activities/SIG/Manuscript/mssigr03.pdf]
* Misc.
** Necessary work on www.tei-c.org (further rationalization of structure,
etc.)
** In particular, status of TEI vault
http://www.tei-c.org.uk/Vault/Vault-GL.html (LB)

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

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

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--[[User:Romary|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)

== 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 [http://lists.village.virginia.edu/pipermail/tei-council/2008/010041.html Quoting a TEI Object] from September 2008. DS has created a new wiki page for discussing [[Council:stable references|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.

== Misc. ==
For general information concerning the council see [[TEI-Council-FAQ]] page and [[:Category: Council|category reserved for use by TEI Council]]...

[[Category:Council]]

BetweenPageBreaks

2011-08-05T06:13:38Z

Romary:

This stylesheet iteratively transforms the content between two page breaks in TEI to generate an HTML output that is put in a specific file (one output per page), with the purpose of creating a navigation allowing one to browse through pages.

The work has been done under my supervision by Solenne Coutagne, Master student at Ecole Naitonal des Chartes.

Laurent Romary

Input: a TEI document with all pages numbered (@n) and pointing to a scan (@facs).

Output: a series of HTML documents

Note: one of the outputs is a verbatim transform of the source, which is made by means of the xmlverbatimwrapper.xsl stylesheet, easy to find online.

<pre><nowiki>
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE xsl:stylesheet [<!ENTITY nbsp " ">]>
<xsl:stylesheet version="2.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns="http://www.w3.org/1999/xhtml" xmlns:tei="http://www.tei-c.org/ns/1.0"
exclude-result-prefixes="tei">


<xsl:import href="xmlverbatimwrapper.xsl"/>

<xsl:output indent="yes" method="html" encoding="UTF-8"
doctype-public="-//W3C//DTD XHTML 1.0 Strict//EN"
doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"/>


<xsl:template name="menu">

<div id="header">

<div id="bandeau">

<a href="../../accueil3.html">
<img id="image_bandeau" src="../../bandeau_petit.jpg" alt="bandeau"/>
</a>

<div id="links">
<a>Deutsch</a>
<a> English</a>

<a href="http://www.dfg.de/foerderung/faq/emmy_noether_faq/index.html">
<img src="../../emmy_noether.jpg" alt="Emmy Noether Program"/>
</a>
<a href="http://www.hu-berlin.de/">
<img src="../../humboldt.jpg" alt="Humboldt Universität zu Berlin"/>
</a>
</div>
</div>


<div id="projekte">
<ul class="menu">
<li>
<a class="unter_projekt"
href="../../franzosen_in_berlin/franzosen_in_berlin.html">FRANZOSEN IN
BERLIN</a>
</li>
<li>
<a class="unter_projekt"
href="../../wissenchaft_und_politik/wissenchaft_und_politik.html"
>WISSENCHAFT & POLITIK</a>
</li>
<li>
<a class="unter_projekt"
href="../../romantische_schluesseltexte/romantische_schluesseltexte.html"
>ROMANTISCHE SCHLÜSSELTEXTE</a>
</li>
<li>
<a class="unter_projekt"
href="../../freitag_gesellschaft/freitag_gesellschaft.html"
>FREITAG-GESELLSCHAFT</a>
</li>
<li>
<a class="unter_projekt" href="../../tieckiana/tieckiana.html">TIECKIANA</a>
</li>
</ul>
</div>

<div id="menu">
<ul class="menu">
<li>
<a class="item_menu" href="">Editorische Richtlinien</a>
</li>
<li>
<a class="item_menu" href="">Briefe</a>
<ul>
<li>
<a class="item_menu">nach Jahr</a>
</li>
<li>
<a class="item_menu">nach Ort</a>
</li>
<li>
<a class="item_menu">nach Besitzer</a>
</li>
<li>
<a class="item_menu">nach Absender</a>
</li>
<li>
<a class="item_menu">nach Adressat</a>
</li>
</ul>
</li>
<li>
<a class="item_menu" href="">Suche</a>
<ul>
<li>
<a href="" class="item_menu">Einfache Suche</a>
</li>
<li>
<a href="" class="item_menu">Erweiterte Suche</a>
</li>
</ul>
</li>
<li>
<a class="item_menu" href="">Kontakt</a>
</li>
<li>
<a class="item_menu" href="">Aktuell</a>
</li>
</ul>
</div>
</div>

<div id="titel">
<a href="javascript:DivStatus( 'mondiv', '1' )">
<xsl:value-of select="normalize-space(//tei:titleStmt/tei:title)"/>
</a>
</div>

<div name="mondiv1" id="mondiv1" class="cachediv">
<div id="divcache">
<xsl:for-each select="//tei:respStmt">
<xsl:value-of select="concat(tei:resp, ': ', tei:persName | tei:orgName)"/>
<br/>
</xsl:for-each>

<xsl:if test="//tei:msIdentifier/tei:institution">
<xsl:choose>
<xsl:when test="//tei:institution/following-sibling::node()">
<xsl:value-of select="concat(//tei:msIdentifier/tei:institution, ',')"/>
</xsl:when>
<xsl:otherwise>
<xsl:value-of select="concat(//tei:msIdentifier/tei:institution, '.')"/>
</xsl:otherwise>
</xsl:choose>
</xsl:if>
<xsl:if test="//tei:msIdentifier/tei:repository">
<xsl:choose>
<xsl:when test="//tei:repository/following-sibling::node()">
<xsl:value-of select="concat(//tei:msIdentifier/tei:repository, ',')"/>
</xsl:when>
<xsl:otherwise>
<xsl:value-of select="concat(//tei:msIdentifier/tei:repository, '.')"/>
</xsl:otherwise>
</xsl:choose>
</xsl:if>
<xsl:if test="//tei:msIdentifier/tei:collection">
<xsl:choose>
<xsl:when test="//tei:collection/following-sibling::node()">
<xsl:value-of select="concat(//tei:msIdentifier/tei:collection, ',')"/>
</xsl:when>
<xsl:otherwise>
<xsl:value-of select="concat(//tei:msIdentifier/tei:collection, '.')"/>
</xsl:otherwise>
</xsl:choose>
</xsl:if>
<xsl:if test="//tei:msIdentifier/tei:idno">
<xsl:value-of select="concat(//tei:msIdentifier/tei:idno, '.')"/>
</xsl:if>
</div>
</div>
</xsl:template>


<xsl:template name="structure">

<xsl:param name="output"/>

<html>
<head>
<title>
<xsl:value-of select="normalize-space(//tei:titleStmt/tei:title)"/>
</title>
<link rel="stylesheet" type="text/css" href="../../test.css"/>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
<script type="text/javascript" src="../../mojozoom.js"/>
<script src="FancyZoom 1.1/js-global/FancyZoom.js" type="text/javascript"/>
<script src="FancyZoom 1.1/js-global/FancyZoomHTML.js" type="text/javascript"/>
<script src="../../cachediv.js" type="text/javascript"/>
</head>
<body onload="initialize()">

<xsl:call-template name="menu"/>

<div id="facs">
<xsl:element name="a">
<xsl:attribute name="href">
<xsl:value-of select="@facs"/>
</xsl:attribute>
<xsl:element name="img">
<xsl:attribute name="src">

<xsl:value-of
select="concat(substring-before(@facs, '.jpg'), 'k', '.jpg')"/>
</xsl:attribute>

<xsl:attribute name="data-zoomsrc">
<xsl:value-of select="@facs"/>
</xsl:attribute>
<xsl:attribute name="alt">
<xsl:value-of select="bild"/>
</xsl:attribute>
</xsl:element>
</xsl:element>
</div>
<div id="transkription">

<div id="inhaltsverzeichnis">
<p class="type_transcription">

<a href="xml.html" class="item_menu">XML-Datei </a>
</p>
<p class="type_transcription">
<a href="page_{@n}_korrigiert.html" class="item_menu"> Kritisch</a>
</p>
<p class="type_transcription">
<a href="page_{@n}_urtext.html" class="item_menu">Diplomatisch</a>
</p>
</div>
<br/>
<br/>
<div id="text">


<xsl:variable name="letzte_seite" select="preceding::tei:pb[1]"/>
<xsl:if test="$letzte_seite">

<xsl:choose>
<xsl:when test="$output='urtext'">
<a href="page_{$letzte_seite/@n}_urtext.html">[Seite
<xsl:value-of select="$letzte_seite/@n"/>] </a>
<br/>
</xsl:when>

<xsl:when test="$output='korrigiert'">
<a href="page_{$letzte_seite/@n}_korrigiert.html">[Seite
<xsl:value-of select="$letzte_seite/@n"/>] </a>
<br/>
</xsl:when>
</xsl:choose>
</xsl:if>

<xsl:apply-templates select="//tei:body">
<xsl:with-param name="anfang" select="."/>
<xsl:with-param name="ende" select="following::tei:pb[1]"/>
<xsl:with-param name="output" select="$output"/>
</xsl:apply-templates>
<br/><br/><br/><br/><br/>

<xsl:variable name="naechste_seite" select="following::tei:pb[1]"/>
<xsl:if test="$naechste_seite">
<xsl:choose>
<xsl:when test="$output='urtext'">
<a href="page_{$naechste_seite/@n}_urtext.html">[Seite
<xsl:value-of select="$naechste_seite/@n"/>] </a>
<br/>
<br/>
</xsl:when>
<xsl:when test="$output='korrigiert'">
<a href="page_{$naechste_seite/@n}_korrigiert.html">[Seite
<xsl:value-of select="$naechste_seite/@n"/>] </a>
<br/>
<br/>
</xsl:when>
</xsl:choose>
</xsl:if>
</div>
</div>
</body>
</html>
</xsl:template>


<xsl:template match="/">
<xsl:for-each select="//tei:pb">
<xsl:result-document method="html" href="page_{@n}_urtext.html">
<xsl:call-template name="structure">
<xsl:with-param name="output" select="'urtext'"/>
</xsl:call-template>
</xsl:result-document>
</xsl:for-each>
<xsl:for-each select="//tei:pb">
<xsl:result-document method="html" href="page_{@n}_korrigiert.html">
<xsl:call-template name="structure">
<xsl:with-param name="output" select="'korrigiert'"/>
</xsl:call-template>
</xsl:result-document>
</xsl:for-each>
<xsl:result-document method="html" href="xml.html">
<html>
<head>
<title>
<xsl:value-of select="normalize-space(//tei:titleStmt/tei:title)"/>
</title>
<link rel="stylesheet" type="text/css" href="../../test.css"/>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
</head>
<body>
<xsl:call-template name="menu"/>
<div id="facs">
<xsl:for-each select="//tei:pb">
<img>
<xsl:attribute name="src">
<xsl:value-of
select="concat(substring-before(@facs, '.jpg'), 'k', '.jpg')"
/>
</xsl:attribute>
</img>
</xsl:for-each>
</div>
<div id="transkription">

<div id="inhaltsverzeichnis">
<p class="type_transcription">
<a href="xml.html">XML-Datei</a>
</p>
<p class="type_transcription">
<xsl:element name="a">
<xsl:attribute name="href">
<xsl:value-of
select="concat('page_', //tei:div[@type='transkription']/*[1]/@n, '_korrigiert.html')"
/>
</xsl:attribute>
<xsl:text>Kritisch</xsl:text>
</xsl:element>
</p>
<p class="type_transcription">
<xsl:element name="a">
<xsl:attribute name="href">
<xsl:value-of
select="concat('page_', //tei:div[@type='transkription']/*[1]/@n, '_urtext.html')"
/>
</xsl:attribute>
<xsl:text>Diplomatisch</xsl:text>
</xsl:element>
</p>
</div>
<div id="text">
<xsl:apply-templates select="." mode="xmlverb"/>
</div>
</div>
</body>
</html>
</xsl:result-document>
</xsl:template>



<xsl:template match="text()">
<xsl:param name="anfang"/>
<xsl:param name="ende"/>
<xsl:param name="output"/>
<xsl:if test="not(following::tei:pb[@n=$anfang/@n]) and not(preceding::tei:pb[@n=$ende/@n])">
<xsl:value-of select="."/>
</xsl:if>
</xsl:template>



<xsl:template match="tei:p">
<xsl:param name="anfang"/>
<xsl:param name="ende"/>
<xsl:param name="output"/>
<xsl:if test="not(following::tei:pb[@n=$anfang/@n]) and not(preceding::tei:pb[@n=$ende/@n])">
<p>
<xsl:apply-templates>
<xsl:with-param name="anfang" select="$anfang"/>
<xsl:with-param name="ende" select="$ende"/>
<xsl:with-param name="output" select="$output"/>
</xsl:apply-templates>
</p>
</xsl:if>
</xsl:template>


<xsl:template match="tei:lb">
<xsl:param name="anfang"/>
<xsl:param name="ende"/>
<xsl:param name="output"/>
<xsl:if test="not(following::tei:pb[@n=$anfang/@n]) and not(preceding::tei:pb[@n=$ende/@n])">
<br/>
</xsl:if>
</xsl:template>


<xsl:template name="rendition">
<xsl:param name="rend"/>
<xsl:if test="$rend != ''">
<xsl:attribute name="class">
<xsl:for-each select="tokenize($rend, '\s')">

<xsl:value-of select="concat(substring-after(., '#'), ' ')"/>
<xsl:if test="position() != last()"/>
</xsl:for-each>
</xsl:attribute>
</xsl:if>
</xsl:template>


<xsl:template match="//tei:add[not(ancestor::tei:subst)]">
<xsl:param name="anfang"/>
<xsl:param name="ende"/>
<xsl:param name="output"/>
<xsl:if test="not(following::tei:pb[@n=$anfang/@n]) and not(preceding::tei:pb[@n=$ende/@n])">
<xsl:choose><xsl:when test="$output='urtext'">
<p>
<xsl:call-template name="rendition">
<xsl:with-param name="rend" select="@rendition"/>
</xsl:call-template>
<xsl:apply-templates>
<xsl:with-param name="anfang" select="$anfang"/>
<xsl:with-param name="ende" select="$ende"/>
<xsl:with-param name="output" select="$output"/>
</xsl:apply-templates>
</p></xsl:when>
<xsl:otherwise>
<p>
<xsl:apply-templates>
<xsl:with-param name="anfang" select="$anfang"/>
<xsl:with-param name="ende" select="$ende"/>
<xsl:with-param name="output" select="$output"/>
</xsl:apply-templates>
</p>
</xsl:otherwise>
</xsl:choose>
</xsl:if>
</xsl:template>

<xsl:template match="tei:subst/tei:add">
<xsl:param name="anfang"/>
<xsl:param name="ende"/>
<xsl:param name="output"/>
<xsl:if test="not(following::tei:pb[@n=$anfang/@n]) and not(preceding::tei:pb[@n=$ende/@n])">
<xsl:if test="$output='urtext'">
<xsl:choose>
<xsl:when test="@place='above'">
<sup>
<xsl:apply-templates>
<xsl:with-param name="anfang" select="$anfang"/>
<xsl:with-param name="ende" select="$ende"/>
</xsl:apply-templates>
</sup>
</xsl:when>
<xsl:when test="@place='below'">
<sub>
<xsl:apply-templates>
<xsl:with-param name="anfang" select="$anfang"/>
<xsl:with-param name="ende" select="$ende"/>
</xsl:apply-templates>
</sub>
</xsl:when>
<xsl:otherwise>
<xsl:apply-templates>
<xsl:with-param name="anfang" select="$anfang"/>
<xsl:with-param name="ende" select="$ende"/>
</xsl:apply-templates>
</xsl:otherwise>
</xsl:choose>
</xsl:if>
<xsl:if test="$output='korrigiert'">
<xsl:apply-templates>
<xsl:with-param name="anfang" select="$anfang"/>
<xsl:with-param name="ende" select="$ende"/>
</xsl:apply-templates>
</xsl:if>
</xsl:if>
</xsl:template>


<xsl:template match="tei:del">
<xsl:param name="anfang"/>
<xsl:param name="ende"/>
<xsl:param name="output"/>
<xsl:if test="not(following::tei:pb[@n=$anfang/@n]) and not(preceding::tei:pb[@n=$ende/@n])">
<xsl:if test="$output='urtext'">
<del>
<xsl:apply-templates>
<xsl:with-param name="anfang" select="$anfang"/>
<xsl:with-param name="ende" select="$ende"/>
</xsl:apply-templates>
</del>
</xsl:if>
</xsl:if>
</xsl:template>


<xsl:template match="//tei:hi[@rend='underline']">
<xsl:param name="anfang"/>
<xsl:param name="ende"/>
<xsl:param name="output"/>
<xsl:if test="not(following::tei:pb[@n=$anfang/@n]) and not(preceding::tei:pb[@n=$ende/@n])">
<xsl:choose>
<xsl:when test="$output='urtext'">
<u>
<xsl:apply-templates>
<xsl:with-param name="anfang" select="$anfang"/>
<xsl:with-param name="ende" select="$ende"/>
<xsl:with-param name="output" select="$output"/>
</xsl:apply-templates>
</u>
</xsl:when>
<xsl:otherwise>
<xsl:apply-templates>
<xsl:with-param name="anfang" select="$anfang"/>
<xsl:with-param name="ende" select="$ende"/>
<xsl:with-param name="output" select="korrigiert"/>
</xsl:apply-templates>
</xsl:otherwise>
</xsl:choose>
</xsl:if>
</xsl:template>
<xsl:template match="tei:hi[@rend='italic']">
<xsl:param name="anfang"/>
<xsl:param name="ende"/>
<xsl:param name="output"/>
<xsl:if test="not(following::tei:pb[@n=$anfang/@n]) and not(preceding::tei:pb[@n=$ende/@n])">
<i>
<xsl:apply-templates>
<xsl:with-param name="anfang" select="$anfang"/>
<xsl:with-param name="ende" select="$ende"/>
<xsl:with-param name="output" select="$output"/>
</xsl:apply-templates>
</i>
</xsl:if>
</xsl:template>


<xsl:template match="tei:dateline">
<xsl:param name="output"/>
<xsl:param name="anfang"/>
<xsl:param name="ende"/>
<xsl:if test="not(following::tei:pb[@n=$anfang/@n]) and not(preceding::tei:pb[@n=$ende/@n])">
<xsl:choose>
<xsl:when test="//tei:dateline[@rendition] and $output='urtext'">
<p>
<xsl:call-template name="rendition">
<xsl:with-param name="rend" select="@rendition"/>
</xsl:call-template>
<xsl:apply-templates select="tei:settlement">
<xsl:with-param name="anfang" select="$anfang"/>
<xsl:with-param name="ende" select="$ende"/>
<xsl:with-param name="output" select="$output"/>
</xsl:apply-templates>   <xsl:apply-templates select="tei:date">
<xsl:with-param name="anfang" select="$anfang"/>
<xsl:with-param name="ende" select="$ende"/>
<xsl:with-param name="output" select="$output"/>
</xsl:apply-templates></p>
</xsl:when>

<xsl:otherwise>
<p>
<xsl:apply-templates select="tei:settlement">
<xsl:with-param name="anfang" select="$anfang"/>
<xsl:with-param name="ende" select="$ende"/>
<xsl:with-param name="output" select="$output"/>
</xsl:apply-templates>   <xsl:apply-templates select="tei:date">
<xsl:with-param name="anfang" select="$anfang"/>
<xsl:with-param name="ende" select="$ende"/>
<xsl:with-param name="output" select="$output"/>
</xsl:apply-templates></p>
</xsl:otherwise>
</xsl:choose>
</xsl:if>
</xsl:template>


<xsl:template match="tei:salute | tei:signed">
<xsl:param name="anfang"/>
<xsl:param name="ende"/>
<xsl:param name="output"/>
<xsl:if test="not(following::tei:pb[@n=$anfang/@n]) and not(preceding::tei:pb[@n=$ende/@n])">
<xsl:choose>
<xsl:when test="//tei:dateline[@rendition] and $output='urtext'">
<p>
<xsl:call-template name="rendition">
<xsl:with-param name="rend" select="@rendition"/>
</xsl:call-template>
<xsl:apply-templates>
<xsl:with-param name="anfang" select="$anfang"/>
<xsl:with-param name="ende" select="$ende"/>
<xsl:with-param name="output" select="$output"/>
</xsl:apply-templates>
</p>
</xsl:when>
<xsl:otherwise>
<p>
<xsl:apply-templates>
<xsl:with-param name="anfang" select="$anfang"/>
<xsl:with-param name="ende" select="$ende"/>
<xsl:with-param name="output" select="$output"/>
</xsl:apply-templates>
</p>
</xsl:otherwise>
</xsl:choose>
</xsl:if>
</xsl:template>


<xsl:template match="tei:gap">
<xsl:param name="anfang"/>
<xsl:param name="ende"/>
<xsl:param name="output"/>
<xsl:if test="not(following::tei:pb[@n=$anfang/@n]) and not(preceding::tei:pb[@n=$ende/@n])">
<xsl:text>[...]</xsl:text>
</xsl:if>
</xsl:template>
<xsl:template match="tei:unclear">
<xsl:param name="output"/>
<xsl:param name="anfang"/>
<xsl:param name="ende"/>
<xsl:if test="not(following::tei:pb[@n=$anfang/@n]) and not(preceding::tei:pb[@n=$ende/@n])">
<xsl:value-of select="concat('[', normalize-space(.), ']')"/>
</xsl:if>
</xsl:template>


<xsl:template match="//tei:expan | //tei:reg | //tei:corr">
<xsl:param name="output"/>
<xsl:param name="anfang"/>
<xsl:param name="ende"/>
<xsl:if test="not(following::tei:pb[@n=$anfang/@n]) and not(preceding::tei:pb[@n=$ende/@n])">
<xsl:if test="$output='korrigiert'">
<xsl:apply-templates>
<xsl:with-param name="anfang" select="$anfang"/>
<xsl:with-param name="ende" select="$ende"/>
</xsl:apply-templates>
</xsl:if>
</xsl:if>
</xsl:template>

<xsl:template match="//tei:abbr | //tei:orig | //tei:sic">
<xsl:param name="output"/>
<xsl:param name="anfang"/>
<xsl:param name="ende"/>
<xsl:if test="not(following::tei:pb[@n=$anfang/@n]) and not(preceding::tei:pb[@n=$ende/@n])">
<xsl:if test="$output='urtext'">
<xsl:apply-templates>
<xsl:with-param name="anfang" select="$anfang"/>
<xsl:with-param name="ende" select="$ende"/>
</xsl:apply-templates>
</xsl:if>
</xsl:if>
</xsl:template>


<xsl:template match="tei:note[not(@resp)]">
<xsl:param name="anfang"/>
<xsl:param name="ende"/>
<xsl:param name="output"/>
<xsl:if test="not(following::tei:pb[@n=$anfang/@n]) and not(preceding::tei:pb[@n=$ende/@n])">
<p>
<xsl:apply-templates>
<xsl:with-param name="anfang" select="$anfang"/>
<xsl:with-param name="ende" select="$ende"/>
<xsl:with-param name="output" select="$output"/>
</xsl:apply-templates>
</p>
</xsl:if>
</xsl:template>



<xsl:template match="tei:note[@resp]">
<xsl:param name="output"/>
<xsl:param name="anfang"/>
<xsl:param name="ende"/>
<xsl:if test="not(following::tei:pb[@n=$anfang/@n]) and not(preceding::tei:pb[@n=$ende/@n])">
<a class="info_anmerkung" href="#">
<sup>
<xsl:value-of select="count(preceding::tei:note) + 1"/>
</sup>
<span>
<xsl:value-of select=".[@xml:id]"/>
</span>
</a>

</xsl:if>
</xsl:template>

</xsl:stylesheet>

</nowiki></pre>

[[Category:XSLT]]

BetweenPageBreaks

2011-08-05T06:08:02Z

Romary:

This stylesheet iteratively transforms the content between two page breaks in TEI to generate an HTML output that is put in a specific file (one output per page), with the purpose of creating a navigation allowing one to browse through pages.

The work has been done under my supervision by Solenne Coutagne, Master student at Ecole Naitonal des Chartes.

Laurent Romary

<pre><nowiki>
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE xsl:stylesheet [<!ENTITY nbsp " ">]>
<xsl:stylesheet version="2.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns="http://www.w3.org/1999/xhtml" xmlns:tei="http://www.tei-c.org/ns/1.0"
exclude-result-prefixes="tei">


<xsl:import href="xmlverbatimwrapper.xsl"/>

<xsl:output indent="yes" method="html" encoding="UTF-8"
doctype-public="-//W3C//DTD XHTML 1.0 Strict//EN"
doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"/>


<xsl:template name="menu">

<div id="header">

<div id="bandeau">

<a href="../../accueil3.html">
<img id="image_bandeau" src="../../bandeau_petit.jpg" alt="bandeau"/>
</a>

<div id="links">
<a>Deutsch</a>
<a> English</a>

<a href="http://www.dfg.de/foerderung/faq/emmy_noether_faq/index.html">
<img src="../../emmy_noether.jpg" alt="Emmy Noether Program"/>
</a>
<a href="http://www.hu-berlin.de/">
<img src="../../humboldt.jpg" alt="Humboldt Universität zu Berlin"/>
</a>
</div>
</div>


<div id="projekte">
<ul class="menu">
<li>
<a class="unter_projekt"
href="../../franzosen_in_berlin/franzosen_in_berlin.html">FRANZOSEN IN
BERLIN</a>
</li>
<li>
<a class="unter_projekt"
href="../../wissenchaft_und_politik/wissenchaft_und_politik.html"
>WISSENCHAFT & POLITIK</a>
</li>
<li>
<a class="unter_projekt"
href="../../romantische_schluesseltexte/romantische_schluesseltexte.html"
>ROMANTISCHE SCHLÜSSELTEXTE</a>
</li>
<li>
<a class="unter_projekt"
href="../../freitag_gesellschaft/freitag_gesellschaft.html"
>FREITAG-GESELLSCHAFT</a>
</li>
<li>
<a class="unter_projekt" href="../../tieckiana/tieckiana.html">TIECKIANA</a>
</li>
</ul>
</div>

<div id="menu">
<ul class="menu">
<li>
<a class="item_menu" href="">Editorische Richtlinien</a>
</li>
<li>
<a class="item_menu" href="">Briefe</a>
<ul>
<li>
<a class="item_menu">nach Jahr</a>
</li>
<li>
<a class="item_menu">nach Ort</a>
</li>
<li>
<a class="item_menu">nach Besitzer</a>
</li>
<li>
<a class="item_menu">nach Absender</a>
</li>
<li>
<a class="item_menu">nach Adressat</a>
</li>
</ul>
</li>
<li>
<a class="item_menu" href="">Suche</a>
<ul>
<li>
<a href="" class="item_menu">Einfache Suche</a>
</li>
<li>
<a href="" class="item_menu">Erweiterte Suche</a>
</li>
</ul>
</li>
<li>
<a class="item_menu" href="">Kontakt</a>
</li>
<li>
<a class="item_menu" href="">Aktuell</a>
</li>
</ul>
</div>
</div>

<div id="titel">
<a href="javascript:DivStatus( 'mondiv', '1' )">
<xsl:value-of select="normalize-space(//tei:titleStmt/tei:title)"/>
</a>
</div>

<div name="mondiv1" id="mondiv1" class="cachediv">
<div id="divcache">
<xsl:for-each select="//tei:respStmt">
<xsl:value-of select="concat(tei:resp, ': ', tei:persName | tei:orgName)"/>
<br/>
</xsl:for-each>

<xsl:if test="//tei:msIdentifier/tei:institution">
<xsl:choose>
<xsl:when test="//tei:institution/following-sibling::node()">
<xsl:value-of select="concat(//tei:msIdentifier/tei:institution, ',')"/>
</xsl:when>
<xsl:otherwise>
<xsl:value-of select="concat(//tei:msIdentifier/tei:institution, '.')"/>
</xsl:otherwise>
</xsl:choose>
</xsl:if>
<xsl:if test="//tei:msIdentifier/tei:repository">
<xsl:choose>
<xsl:when test="//tei:repository/following-sibling::node()">
<xsl:value-of select="concat(//tei:msIdentifier/tei:repository, ',')"/>
</xsl:when>
<xsl:otherwise>
<xsl:value-of select="concat(//tei:msIdentifier/tei:repository, '.')"/>
</xsl:otherwise>
</xsl:choose>
</xsl:if>
<xsl:if test="//tei:msIdentifier/tei:collection">
<xsl:choose>
<xsl:when test="//tei:collection/following-sibling::node()">
<xsl:value-of select="concat(//tei:msIdentifier/tei:collection, ',')"/>
</xsl:when>
<xsl:otherwise>
<xsl:value-of select="concat(//tei:msIdentifier/tei:collection, '.')"/>
</xsl:otherwise>
</xsl:choose>
</xsl:if>
<xsl:if test="//tei:msIdentifier/tei:idno">
<xsl:value-of select="concat(//tei:msIdentifier/tei:idno, '.')"/>
</xsl:if>
</div>
</div>
</xsl:template>


<xsl:template name="structure">

<xsl:param name="output"/>

<html>
<head>
<title>
<xsl:value-of select="normalize-space(//tei:titleStmt/tei:title)"/>
</title>
<link rel="stylesheet" type="text/css" href="../../test.css"/>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
<script type="text/javascript" src="../../mojozoom.js"/>
<script src="FancyZoom 1.1/js-global/FancyZoom.js" type="text/javascript"/>
<script src="FancyZoom 1.1/js-global/FancyZoomHTML.js" type="text/javascript"/>
<script src="../../cachediv.js" type="text/javascript"/>
</head>
<body onload="initialize()">

<xsl:call-template name="menu"/>

<div id="facs">
<xsl:element name="a">
<xsl:attribute name="href">
<xsl:value-of select="@facs"/>
</xsl:attribute>
<xsl:element name="img">
<xsl:attribute name="src">

<xsl:value-of
select="concat(substring-before(@facs, '.jpg'), 'k', '.jpg')"/>
</xsl:attribute>

<xsl:attribute name="data-zoomsrc">
<xsl:value-of select="@facs"/>
</xsl:attribute>
<xsl:attribute name="alt">
<xsl:value-of select="bild"/>
</xsl:attribute>
</xsl:element>
</xsl:element>
</div>
<div id="transkription">

<div id="inhaltsverzeichnis">
<p class="type_transcription">

<a href="xml.html" class="item_menu">XML-Datei </a>
</p>
<p class="type_transcription">
<a href="page_{@n}_korrigiert.html" class="item_menu"> Kritisch</a>
</p>
<p class="type_transcription">
<a href="page_{@n}_urtext.html" class="item_menu">Diplomatisch</a>
</p>
</div>
<br/>
<br/>
<div id="text">


<xsl:variable name="letzte_seite" select="preceding::tei:pb[1]"/>
<xsl:if test="$letzte_seite">

<xsl:choose>
<xsl:when test="$output='urtext'">
<a href="page_{$letzte_seite/@n}_urtext.html">[Seite
<xsl:value-of select="$letzte_seite/@n"/>] </a>
<br/>
</xsl:when>

<xsl:when test="$output='korrigiert'">
<a href="page_{$letzte_seite/@n}_korrigiert.html">[Seite
<xsl:value-of select="$letzte_seite/@n"/>] </a>
<br/>
</xsl:when>
</xsl:choose>
</xsl:if>

<xsl:apply-templates select="//tei:body">
<xsl:with-param name="anfang" select="."/>
<xsl:with-param name="ende" select="following::tei:pb[1]"/>
<xsl:with-param name="output" select="$output"/>
</xsl:apply-templates>
<br/><br/><br/><br/><br/>

<xsl:variable name="naechste_seite" select="following::tei:pb[1]"/>
<xsl:if test="$naechste_seite">
<xsl:choose>
<xsl:when test="$output='urtext'">
<a href="page_{$naechste_seite/@n}_urtext.html">[Seite
<xsl:value-of select="$naechste_seite/@n"/>] </a>
<br/>
<br/>
</xsl:when>
<xsl:when test="$output='korrigiert'">
<a href="page_{$naechste_seite/@n}_korrigiert.html">[Seite
<xsl:value-of select="$naechste_seite/@n"/>] </a>
<br/>
<br/>
</xsl:when>
</xsl:choose>
</xsl:if>
</div>
</div>
</body>
</html>
</xsl:template>


<xsl:template match="/">
<xsl:for-each select="//tei:pb">
<xsl:result-document method="html" href="page_{@n}_urtext.html">
<xsl:call-template name="structure">
<xsl:with-param name="output" select="'urtext'"/>
</xsl:call-template>
</xsl:result-document>
</xsl:for-each>
<xsl:for-each select="//tei:pb">
<xsl:result-document method="html" href="page_{@n}_korrigiert.html">
<xsl:call-template name="structure">
<xsl:with-param name="output" select="'korrigiert'"/>
</xsl:call-template>
</xsl:result-document>
</xsl:for-each>
<xsl:result-document method="html" href="xml.html">
<html>
<head>
<title>
<xsl:value-of select="normalize-space(//tei:titleStmt/tei:title)"/>
</title>
<link rel="stylesheet" type="text/css" href="../../test.css"/>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
</head>
<body>
<xsl:call-template name="menu"/>
<div id="facs">
<xsl:for-each select="//tei:pb">
<img>
<xsl:attribute name="src">
<xsl:value-of
select="concat(substring-before(@facs, '.jpg'), 'k', '.jpg')"
/>
</xsl:attribute>
</img>
</xsl:for-each>
</div>
<div id="transkription">

<div id="inhaltsverzeichnis">
<p class="type_transcription">
<a href="xml.html">XML-Datei</a>
</p>
<p class="type_transcription">
<xsl:element name="a">
<xsl:attribute name="href">
<xsl:value-of
select="concat('page_', //tei:div[@type='transkription']/*[1]/@n, '_korrigiert.html')"
/>
</xsl:attribute>
<xsl:text>Kritisch</xsl:text>
</xsl:element>
</p>
<p class="type_transcription">
<xsl:element name="a">
<xsl:attribute name="href">
<xsl:value-of
select="concat('page_', //tei:div[@type='transkription']/*[1]/@n, '_urtext.html')"
/>
</xsl:attribute>
<xsl:text>Diplomatisch</xsl:text>
</xsl:element>
</p>
</div>
<div id="text">
<xsl:apply-templates select="." mode="xmlverb"/>
</div>
</div>
</body>
</html>
</xsl:result-document>
</xsl:template>



<xsl:template match="text()">
<xsl:param name="anfang"/>
<xsl:param name="ende"/>
<xsl:param name="output"/>
<xsl:if test="not(following::tei:pb[@n=$anfang/@n]) and not(preceding::tei:pb[@n=$ende/@n])">
<xsl:value-of select="."/>
</xsl:if>
</xsl:template>



<xsl:template match="tei:p">
<xsl:param name="anfang"/>
<xsl:param name="ende"/>
<xsl:param name="output"/>
<xsl:if test="not(following::tei:pb[@n=$anfang/@n]) and not(preceding::tei:pb[@n=$ende/@n])">
<p>
<xsl:apply-templates>
<xsl:with-param name="anfang" select="$anfang"/>
<xsl:with-param name="ende" select="$ende"/>
<xsl:with-param name="output" select="$output"/>
</xsl:apply-templates>
</p>
</xsl:if>
</xsl:template>


<xsl:template match="tei:lb">
<xsl:param name="anfang"/>
<xsl:param name="ende"/>
<xsl:param name="output"/>
<xsl:if test="not(following::tei:pb[@n=$anfang/@n]) and not(preceding::tei:pb[@n=$ende/@n])">
<br/>
</xsl:if>
</xsl:template>


<xsl:template name="rendition">
<xsl:param name="rend"/>
<xsl:if test="$rend != ''">
<xsl:attribute name="class">
<xsl:for-each select="tokenize($rend, '\s')">

<xsl:value-of select="concat(substring-after(., '#'), ' ')"/>
<xsl:if test="position() != last()"/>
</xsl:for-each>
</xsl:attribute>
</xsl:if>
</xsl:template>


<xsl:template match="//tei:add[not(ancestor::tei:subst)]">
<xsl:param name="anfang"/>
<xsl:param name="ende"/>
<xsl:param name="output"/>
<xsl:if test="not(following::tei:pb[@n=$anfang/@n]) and not(preceding::tei:pb[@n=$ende/@n])">
<xsl:choose><xsl:when test="$output='urtext'">
<p>
<xsl:call-template name="rendition">
<xsl:with-param name="rend" select="@rendition"/>
</xsl:call-template>
<xsl:apply-templates>
<xsl:with-param name="anfang" select="$anfang"/>
<xsl:with-param name="ende" select="$ende"/>
<xsl:with-param name="output" select="$output"/>
</xsl:apply-templates>
</p></xsl:when>
<xsl:otherwise>
<p>
<xsl:apply-templates>
<xsl:with-param name="anfang" select="$anfang"/>
<xsl:with-param name="ende" select="$ende"/>
<xsl:with-param name="output" select="$output"/>
</xsl:apply-templates>
</p>
</xsl:otherwise>
</xsl:choose>
</xsl:if>
</xsl:template>

<xsl:template match="tei:subst/tei:add">
<xsl:param name="anfang"/>
<xsl:param name="ende"/>
<xsl:param name="output"/>
<xsl:if test="not(following::tei:pb[@n=$anfang/@n]) and not(preceding::tei:pb[@n=$ende/@n])">
<xsl:if test="$output='urtext'">
<xsl:choose>
<xsl:when test="@place='above'">
<sup>
<xsl:apply-templates>
<xsl:with-param name="anfang" select="$anfang"/>
<xsl:with-param name="ende" select="$ende"/>
</xsl:apply-templates>
</sup>
</xsl:when>
<xsl:when test="@place='below'">
<sub>
<xsl:apply-templates>
<xsl:with-param name="anfang" select="$anfang"/>
<xsl:with-param name="ende" select="$ende"/>
</xsl:apply-templates>
</sub>
</xsl:when>
<xsl:otherwise>
<xsl:apply-templates>
<xsl:with-param name="anfang" select="$anfang"/>
<xsl:with-param name="ende" select="$ende"/>
</xsl:apply-templates>
</xsl:otherwise>
</xsl:choose>
</xsl:if>
<xsl:if test="$output='korrigiert'">
<xsl:apply-templates>
<xsl:with-param name="anfang" select="$anfang"/>
<xsl:with-param name="ende" select="$ende"/>
</xsl:apply-templates>
</xsl:if>
</xsl:if>
</xsl:template>


<xsl:template match="tei:del">
<xsl:param name="anfang"/>
<xsl:param name="ende"/>
<xsl:param name="output"/>
<xsl:if test="not(following::tei:pb[@n=$anfang/@n]) and not(preceding::tei:pb[@n=$ende/@n])">
<xsl:if test="$output='urtext'">
<del>
<xsl:apply-templates>
<xsl:with-param name="anfang" select="$anfang"/>
<xsl:with-param name="ende" select="$ende"/>
</xsl:apply-templates>
</del>
</xsl:if>
</xsl:if>
</xsl:template>


<xsl:template match="//tei:hi[@rend='underline']">
<xsl:param name="anfang"/>
<xsl:param name="ende"/>
<xsl:param name="output"/>
<xsl:if test="not(following::tei:pb[@n=$anfang/@n]) and not(preceding::tei:pb[@n=$ende/@n])">
<xsl:choose>
<xsl:when test="$output='urtext'">
<u>
<xsl:apply-templates>
<xsl:with-param name="anfang" select="$anfang"/>
<xsl:with-param name="ende" select="$ende"/>
<xsl:with-param name="output" select="$output"/>
</xsl:apply-templates>
</u>
</xsl:when>
<xsl:otherwise>
<xsl:apply-templates>
<xsl:with-param name="anfang" select="$anfang"/>
<xsl:with-param name="ende" select="$ende"/>
<xsl:with-param name="output" select="korrigiert"/>
</xsl:apply-templates>
</xsl:otherwise>
</xsl:choose>
</xsl:if>
</xsl:template>
<xsl:template match="tei:hi[@rend='italic']">
<xsl:param name="anfang"/>
<xsl:param name="ende"/>
<xsl:param name="output"/>
<xsl:if test="not(following::tei:pb[@n=$anfang/@n]) and not(preceding::tei:pb[@n=$ende/@n])">
<i>
<xsl:apply-templates>
<xsl:with-param name="anfang" select="$anfang"/>
<xsl:with-param name="ende" select="$ende"/>
<xsl:with-param name="output" select="$output"/>
</xsl:apply-templates>
</i>
</xsl:if>
</xsl:template>


<xsl:template match="tei:dateline">
<xsl:param name="output"/>
<xsl:param name="anfang"/>
<xsl:param name="ende"/>
<xsl:if test="not(following::tei:pb[@n=$anfang/@n]) and not(preceding::tei:pb[@n=$ende/@n])">
<xsl:choose>
<xsl:when test="//tei:dateline[@rendition] and $output='urtext'">
<p>
<xsl:call-template name="rendition">
<xsl:with-param name="rend" select="@rendition"/>
</xsl:call-template>
<xsl:apply-templates select="tei:settlement">
<xsl:with-param name="anfang" select="$anfang"/>
<xsl:with-param name="ende" select="$ende"/>
<xsl:with-param name="output" select="$output"/>
</xsl:apply-templates>   <xsl:apply-templates select="tei:date">
<xsl:with-param name="anfang" select="$anfang"/>
<xsl:with-param name="ende" select="$ende"/>
<xsl:with-param name="output" select="$output"/>
</xsl:apply-templates></p>
</xsl:when>

<xsl:otherwise>
<p>
<xsl:apply-templates select="tei:settlement">
<xsl:with-param name="anfang" select="$anfang"/>
<xsl:with-param name="ende" select="$ende"/>
<xsl:with-param name="output" select="$output"/>
</xsl:apply-templates>   <xsl:apply-templates select="tei:date">
<xsl:with-param name="anfang" select="$anfang"/>
<xsl:with-param name="ende" select="$ende"/>
<xsl:with-param name="output" select="$output"/>
</xsl:apply-templates></p>
</xsl:otherwise>
</xsl:choose>
</xsl:if>
</xsl:template>


<xsl:template match="tei:salute | tei:signed">
<xsl:param name="anfang"/>
<xsl:param name="ende"/>
<xsl:param name="output"/>
<xsl:if test="not(following::tei:pb[@n=$anfang/@n]) and not(preceding::tei:pb[@n=$ende/@n])">
<xsl:choose>
<xsl:when test="//tei:dateline[@rendition] and $output='urtext'">
<p>
<xsl:call-template name="rendition">
<xsl:with-param name="rend" select="@rendition"/>
</xsl:call-template>
<xsl:apply-templates>
<xsl:with-param name="anfang" select="$anfang"/>
<xsl:with-param name="ende" select="$ende"/>
<xsl:with-param name="output" select="$output"/>
</xsl:apply-templates>
</p>
</xsl:when>
<xsl:otherwise>
<p>
<xsl:apply-templates>
<xsl:with-param name="anfang" select="$anfang"/>
<xsl:with-param name="ende" select="$ende"/>
<xsl:with-param name="output" select="$output"/>
</xsl:apply-templates>
</p>
</xsl:otherwise>
</xsl:choose>
</xsl:if>
</xsl:template>


<xsl:template match="tei:gap">
<xsl:param name="anfang"/>
<xsl:param name="ende"/>
<xsl:param name="output"/>
<xsl:if test="not(following::tei:pb[@n=$anfang/@n]) and not(preceding::tei:pb[@n=$ende/@n])">
<xsl:text>[...]</xsl:text>
</xsl:if>
</xsl:template>
<xsl:template match="tei:unclear">
<xsl:param name="output"/>
<xsl:param name="anfang"/>
<xsl:param name="ende"/>
<xsl:if test="not(following::tei:pb[@n=$anfang/@n]) and not(preceding::tei:pb[@n=$ende/@n])">
<xsl:value-of select="concat('[', normalize-space(.), ']')"/>
</xsl:if>
</xsl:template>


<xsl:template match="//tei:expan | //tei:reg | //tei:corr">
<xsl:param name="output"/>
<xsl:param name="anfang"/>
<xsl:param name="ende"/>
<xsl:if test="not(following::tei:pb[@n=$anfang/@n]) and not(preceding::tei:pb[@n=$ende/@n])">
<xsl:if test="$output='korrigiert'">
<xsl:apply-templates>
<xsl:with-param name="anfang" select="$anfang"/>
<xsl:with-param name="ende" select="$ende"/>
</xsl:apply-templates>
</xsl:if>
</xsl:if>
</xsl:template>

<xsl:template match="//tei:abbr | //tei:orig | //tei:sic">
<xsl:param name="output"/>
<xsl:param name="anfang"/>
<xsl:param name="ende"/>
<xsl:if test="not(following::tei:pb[@n=$anfang/@n]) and not(preceding::tei:pb[@n=$ende/@n])">
<xsl:if test="$output='urtext'">
<xsl:apply-templates>
<xsl:with-param name="anfang" select="$anfang"/>
<xsl:with-param name="ende" select="$ende"/>
</xsl:apply-templates>
</xsl:if>
</xsl:if>
</xsl:template>


<xsl:template match="tei:note[not(@resp)]">
<xsl:param name="anfang"/>
<xsl:param name="ende"/>
<xsl:param name="output"/>
<xsl:if test="not(following::tei:pb[@n=$anfang/@n]) and not(preceding::tei:pb[@n=$ende/@n])">
<p>
<xsl:apply-templates>
<xsl:with-param name="anfang" select="$anfang"/>
<xsl:with-param name="ende" select="$ende"/>
<xsl:with-param name="output" select="$output"/>
</xsl:apply-templates>
</p>
</xsl:if>
</xsl:template>



<xsl:template match="tei:note[@resp]">
<xsl:param name="output"/>
<xsl:param name="anfang"/>
<xsl:param name="ende"/>
<xsl:if test="not(following::tei:pb[@n=$anfang/@n]) and not(preceding::tei:pb[@n=$ende/@n])">
<a class="info_anmerkung" href="#">
<sup>
<xsl:value-of select="count(preceding::tei:note) + 1"/>
</sup>
<span>
<xsl:value-of select=".[@xml:id]"/>
</span>
</a>

</xsl:if>
</xsl:template>

</xsl:stylesheet>

</nowiki></pre>

[[Category:XSLT]]

BetweenPageBreaks

2011-08-05T06:07:33Z

Romary: New page: This stylesheet iteratively transforms the content between two page breaks in TEI to generate an HTML output that is put in a specific file (one output per page), with the purpose of creat...

This stylesheet iteratively transforms the content between two page breaks in TEI to generate an HTML output that is put in a specific file (one output per page), with the purpose of creating a navigation allowing one to browse through pages.

The work has been done under my supervision by Solenne Coutagne, Master student at Ecole Naitonal des Chartes.

Laurent Romary

<pre><nowiki>
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE xsl:stylesheet [<!ENTITY nbsp " ">]>
<xsl:stylesheet version="2.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns="http://www.w3.org/1999/xhtml" xmlns:tei="http://www.tei-c.org/ns/1.0"
exclude-result-prefixes="tei">


<xsl:import href="xmlverbatimwrapper.xsl"/>

<xsl:output indent="yes" method="html" encoding="UTF-8"
doctype-public="-//W3C//DTD XHTML 1.0 Strict//EN"
doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"/>


<xsl:template name="menu">

<div id="header">

<div id="bandeau">

<a href="../../accueil3.html">
<img id="image_bandeau" src="../../bandeau_petit.jpg" alt="bandeau"/>
</a>

<div id="links">
<a>Deutsch</a>
<a> English</a>

<a href="http://www.dfg.de/foerderung/faq/emmy_noether_faq/index.html">
<img src="../../emmy_noether.jpg" alt="Emmy Noether Program"/>
</a>
<a href="http://www.hu-berlin.de/">
<img src="../../humboldt.jpg" alt="Humboldt Universität zu Berlin"/>
</a>
</div>
</div>


<div id="projekte">
<ul class="menu">
<li>
<a class="unter_projekt"
href="../../franzosen_in_berlin/franzosen_in_berlin.html">FRANZOSEN IN
BERLIN</a>
</li>
<li>
<a class="unter_projekt"
href="../../wissenchaft_und_politik/wissenchaft_und_politik.html"
>WISSENCHAFT & POLITIK</a>
</li>
<li>
<a class="unter_projekt"
href="../../romantische_schluesseltexte/romantische_schluesseltexte.html"
>ROMANTISCHE SCHLÜSSELTEXTE</a>
</li>
<li>
<a class="unter_projekt"
href="../../freitag_gesellschaft/freitag_gesellschaft.html"
>FREITAG-GESELLSCHAFT</a>
</li>
<li>
<a class="unter_projekt" href="../../tieckiana/tieckiana.html">TIECKIANA</a>
</li>
</ul>
</div>

<div id="menu">
<ul class="menu">
<li>
<a class="item_menu" href="">Editorische Richtlinien</a>
</li>
<li>
<a class="item_menu" href="">Briefe</a>
<ul>
<li>
<a class="item_menu">nach Jahr</a>
</li>
<li>
<a class="item_menu">nach Ort</a>
</li>
<li>
<a class="item_menu">nach Besitzer</a>
</li>
<li>
<a class="item_menu">nach Absender</a>
</li>
<li>
<a class="item_menu">nach Adressat</a>
</li>
</ul>
</li>
<li>
<a class="item_menu" href="">Suche</a>
<ul>
<li>
<a href="" class="item_menu">Einfache Suche</a>
</li>
<li>
<a href="" class="item_menu">Erweiterte Suche</a>
</li>
</ul>
</li>
<li>
<a class="item_menu" href="">Kontakt</a>
</li>
<li>
<a class="item_menu" href="">Aktuell</a>
</li>
</ul>
</div>
</div>

<div id="titel">
<a href="javascript:DivStatus( 'mondiv', '1' )">
<xsl:value-of select="normalize-space(//tei:titleStmt/tei:title)"/>
</a>
</div>

<div name="mondiv1" id="mondiv1" class="cachediv">
<div id="divcache">
<xsl:for-each select="//tei:respStmt">
<xsl:value-of select="concat(tei:resp, ': ', tei:persName | tei:orgName)"/>
<br/>
</xsl:for-each>

<xsl:if test="//tei:msIdentifier/tei:institution">
<xsl:choose>
<xsl:when test="//tei:institution/following-sibling::node()">
<xsl:value-of select="concat(//tei:msIdentifier/tei:institution, ',')"/>
</xsl:when>
<xsl:otherwise>
<xsl:value-of select="concat(//tei:msIdentifier/tei:institution, '.')"/>
</xsl:otherwise>
</xsl:choose>
</xsl:if>
<xsl:if test="//tei:msIdentifier/tei:repository">
<xsl:choose>
<xsl:when test="//tei:repository/following-sibling::node()">
<xsl:value-of select="concat(//tei:msIdentifier/tei:repository, ',')"/>
</xsl:when>
<xsl:otherwise>
<xsl:value-of select="concat(//tei:msIdentifier/tei:repository, '.')"/>
</xsl:otherwise>
</xsl:choose>
</xsl:if>
<xsl:if test="//tei:msIdentifier/tei:collection">
<xsl:choose>
<xsl:when test="//tei:collection/following-sibling::node()">
<xsl:value-of select="concat(//tei:msIdentifier/tei:collection, ',')"/>
</xsl:when>
<xsl:otherwise>
<xsl:value-of select="concat(//tei:msIdentifier/tei:collection, '.')"/>
</xsl:otherwise>
</xsl:choose>
</xsl:if>
<xsl:if test="//tei:msIdentifier/tei:idno">
<xsl:value-of select="concat(//tei:msIdentifier/tei:idno, '.')"/>
</xsl:if>
</div>
</div>
</xsl:template>


<xsl:template name="structure">

<xsl:param name="output"/>

<html>
<head>
<title>
<xsl:value-of select="normalize-space(//tei:titleStmt/tei:title)"/>
</title>
<link rel="stylesheet" type="text/css" href="../../test.css"/>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
<script type="text/javascript" src="../../mojozoom.js"/>
<script src="FancyZoom 1.1/js-global/FancyZoom.js" type="text/javascript"/>
<script src="FancyZoom 1.1/js-global/FancyZoomHTML.js" type="text/javascript"/>
<script src="../../cachediv.js" type="text/javascript"/>
</head>
<body onload="initialize()">

<xsl:call-template name="menu"/>

<div id="facs">
<xsl:element name="a">
<xsl:attribute name="href">
<xsl:value-of select="@facs"/>
</xsl:attribute>
<xsl:element name="img">
<xsl:attribute name="src">

<xsl:value-of
select="concat(substring-before(@facs, '.jpg'), 'k', '.jpg')"/>
</xsl:attribute>

<xsl:attribute name="data-zoomsrc">
<xsl:value-of select="@facs"/>
</xsl:attribute>
<xsl:attribute name="alt">
<xsl:value-of select="bild"/>
</xsl:attribute>
</xsl:element>
</xsl:element>
</div>
<div id="transkription">

<div id="inhaltsverzeichnis">
<p class="type_transcription">

<a href="xml.html" class="item_menu">XML-Datei </a>
</p>
<p class="type_transcription">
<a href="page_{@n}_korrigiert.html" class="item_menu"> Kritisch</a>
</p>
<p class="type_transcription">
<a href="page_{@n}_urtext.html" class="item_menu">Diplomatisch</a>
</p>
</div>
<br/>
<br/>
<div id="text">


<xsl:variable name="letzte_seite" select="preceding::tei:pb[1]"/>
<xsl:if test="$letzte_seite">

<xsl:choose>
<xsl:when test="$output='urtext'">
<a href="page_{$letzte_seite/@n}_urtext.html">[Seite
<xsl:value-of select="$letzte_seite/@n"/>] </a>
<br/>
</xsl:when>

<xsl:when test="$output='korrigiert'">
<a href="page_{$letzte_seite/@n}_korrigiert.html">[Seite
<xsl:value-of select="$letzte_seite/@n"/>] </a>
<br/>
</xsl:when>
</xsl:choose>
</xsl:if>

<xsl:apply-templates select="//tei:body">
<xsl:with-param name="anfang" select="."/>
<xsl:with-param name="ende" select="following::tei:pb[1]"/>
<xsl:with-param name="output" select="$output"/>
</xsl:apply-templates>
<br/><br/><br/><br/><br/>

<xsl:variable name="naechste_seite" select="following::tei:pb[1]"/>
<xsl:if test="$naechste_seite">
<xsl:choose>
<xsl:when test="$output='urtext'">
<a href="page_{$naechste_seite/@n}_urtext.html">[Seite
<xsl:value-of select="$naechste_seite/@n"/>] </a>
<br/>
<br/>
</xsl:when>
<xsl:when test="$output='korrigiert'">
<a href="page_{$naechste_seite/@n}_korrigiert.html">[Seite
<xsl:value-of select="$naechste_seite/@n"/>] </a>
<br/>
<br/>
</xsl:when>
</xsl:choose>
</xsl:if>
</div>
</div>
</body>
</html>
</xsl:template>


<xsl:template match="/">
<xsl:for-each select="//tei:pb">
<xsl:result-document method="html" href="page_{@n}_urtext.html">
<xsl:call-template name="structure">
<xsl:with-param name="output" select="'urtext'"/>
</xsl:call-template>
</xsl:result-document>
</xsl:for-each>
<xsl:for-each select="//tei:pb">
<xsl:result-document method="html" href="page_{@n}_korrigiert.html">
<xsl:call-template name="structure">
<xsl:with-param name="output" select="'korrigiert'"/>
</xsl:call-template>
</xsl:result-document>
</xsl:for-each>
<xsl:result-document method="html" href="xml.html">
<html>
<head>
<title>
<xsl:value-of select="normalize-space(//tei:titleStmt/tei:title)"/>
</title>
<link rel="stylesheet" type="text/css" href="../../test.css"/>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
</head>
<body>
<xsl:call-template name="menu"/>
<div id="facs">
<xsl:for-each select="//tei:pb">
<img>
<xsl:attribute name="src">
<xsl:value-of
select="concat(substring-before(@facs, '.jpg'), 'k', '.jpg')"
/>
</xsl:attribute>
</img>
</xsl:for-each>
</div>
<div id="transkription">

<div id="inhaltsverzeichnis">
<p class="type_transcription">
<a href="xml.html">XML-Datei</a>
</p>
<p class="type_transcription">
<xsl:element name="a">
<xsl:attribute name="href">
<xsl:value-of
select="concat('page_', //tei:div[@type='transkription']/*[1]/@n, '_korrigiert.html')"
/>
</xsl:attribute>
<xsl:text>Kritisch</xsl:text>
</xsl:element>
</p>
<p class="type_transcription">
<xsl:element name="a">
<xsl:attribute name="href">
<xsl:value-of
select="concat('page_', //tei:div[@type='transkription']/*[1]/@n, '_urtext.html')"
/>
</xsl:attribute>
<xsl:text>Diplomatisch</xsl:text>
</xsl:element>
</p>
</div>
<div id="text">
<xsl:apply-templates select="." mode="xmlverb"/>
</div>
</div>
</body>
</html>
</xsl:result-document>
</xsl:template>



<xsl:template match="text()">
<xsl:param name="anfang"/>
<xsl:param name="ende"/>
<xsl:param name="output"/>
<xsl:if test="not(following::tei:pb[@n=$anfang/@n]) and not(preceding::tei:pb[@n=$ende/@n])">
<xsl:value-of select="."/>
</xsl:if>
</xsl:template>



<xsl:template match="tei:p">
<xsl:param name="anfang"/>
<xsl:param name="ende"/>
<xsl:param name="output"/>
<xsl:if test="not(following::tei:pb[@n=$anfang/@n]) and not(preceding::tei:pb[@n=$ende/@n])">
<p>
<xsl:apply-templates>
<xsl:with-param name="anfang" select="$anfang"/>
<xsl:with-param name="ende" select="$ende"/>
<xsl:with-param name="output" select="$output"/>
</xsl:apply-templates>
</p>
</xsl:if>
</xsl:template>


<xsl:template match="tei:lb">
<xsl:param name="anfang"/>
<xsl:param name="ende"/>
<xsl:param name="output"/>
<xsl:if test="not(following::tei:pb[@n=$anfang/@n]) and not(preceding::tei:pb[@n=$ende/@n])">
<br/>
</xsl:if>
</xsl:template>


<xsl:template name="rendition">
<xsl:param name="rend"/>
<xsl:if test="$rend != ''">
<xsl:attribute name="class">
<xsl:for-each select="tokenize($rend, '\s')">

<xsl:value-of select="concat(substring-after(., '#'), ' ')"/>
<xsl:if test="position() != last()"/>
</xsl:for-each>
</xsl:attribute>
</xsl:if>
</xsl:template>


<xsl:template match="//tei:add[not(ancestor::tei:subst)]">
<xsl:param name="anfang"/>
<xsl:param name="ende"/>
<xsl:param name="output"/>
<xsl:if test="not(following::tei:pb[@n=$anfang/@n]) and not(preceding::tei:pb[@n=$ende/@n])">
<xsl:choose><xsl:when test="$output='urtext'">
<p>
<xsl:call-template name="rendition">
<xsl:with-param name="rend" select="@rendition"/>
</xsl:call-template>
<xsl:apply-templates>
<xsl:with-param name="anfang" select="$anfang"/>
<xsl:with-param name="ende" select="$ende"/>
<xsl:with-param name="output" select="$output"/>
</xsl:apply-templates>
</p></xsl:when>
<xsl:otherwise>
<p>
<xsl:apply-templates>
<xsl:with-param name="anfang" select="$anfang"/>
<xsl:with-param name="ende" select="$ende"/>
<xsl:with-param name="output" select="$output"/>
</xsl:apply-templates>
</p>
</xsl:otherwise>
</xsl:choose>
</xsl:if>
</xsl:template>

<xsl:template match="tei:subst/tei:add">
<xsl:param name="anfang"/>
<xsl:param name="ende"/>
<xsl:param name="output"/>
<xsl:if test="not(following::tei:pb[@n=$anfang/@n]) and not(preceding::tei:pb[@n=$ende/@n])">
<xsl:if test="$output='urtext'">
<xsl:choose>
<xsl:when test="@place='above'">
<sup>
<xsl:apply-templates>
<xsl:with-param name="anfang" select="$anfang"/>
<xsl:with-param name="ende" select="$ende"/>
</xsl:apply-templates>
</sup>
</xsl:when>
<xsl:when test="@place='below'">
<sub>
<xsl:apply-templates>
<xsl:with-param name="anfang" select="$anfang"/>
<xsl:with-param name="ende" select="$ende"/>
</xsl:apply-templates>
</sub>
</xsl:when>
<xsl:otherwise>
<xsl:apply-templates>
<xsl:with-param name="anfang" select="$anfang"/>
<xsl:with-param name="ende" select="$ende"/>
</xsl:apply-templates>
</xsl:otherwise>
</xsl:choose>
</xsl:if>
<xsl:if test="$output='korrigiert'">
<xsl:apply-templates>
<xsl:with-param name="anfang" select="$anfang"/>
<xsl:with-param name="ende" select="$ende"/>
</xsl:apply-templates>
</xsl:if>
</xsl:if>
</xsl:template>


<xsl:template match="tei:del">
<xsl:param name="anfang"/>
<xsl:param name="ende"/>
<xsl:param name="output"/>
<xsl:if test="not(following::tei:pb[@n=$anfang/@n]) and not(preceding::tei:pb[@n=$ende/@n])">
<xsl:if test="$output='urtext'">
<del>
<xsl:apply-templates>
<xsl:with-param name="anfang" select="$anfang"/>
<xsl:with-param name="ende" select="$ende"/>
</xsl:apply-templates>
</del>
</xsl:if>
</xsl:if>
</xsl:template>


<xsl:template match="//tei:hi[@rend='underline']">
<xsl:param name="anfang"/>
<xsl:param name="ende"/>
<xsl:param name="output"/>
<xsl:if test="not(following::tei:pb[@n=$anfang/@n]) and not(preceding::tei:pb[@n=$ende/@n])">
<xsl:choose>
<xsl:when test="$output='urtext'">
<u>
<xsl:apply-templates>
<xsl:with-param name="anfang" select="$anfang"/>
<xsl:with-param name="ende" select="$ende"/>
<xsl:with-param name="output" select="$output"/>
</xsl:apply-templates>
</u>
</xsl:when>
<xsl:otherwise>
<xsl:apply-templates>
<xsl:with-param name="anfang" select="$anfang"/>
<xsl:with-param name="ende" select="$ende"/>
<xsl:with-param name="output" select="korrigiert"/>
</xsl:apply-templates>
</xsl:otherwise>
</xsl:choose>
</xsl:if>
</xsl:template>
<xsl:template match="tei:hi[@rend='italic']">
<xsl:param name="anfang"/>
<xsl:param name="ende"/>
<xsl:param name="output"/>
<xsl:if test="not(following::tei:pb[@n=$anfang/@n]) and not(preceding::tei:pb[@n=$ende/@n])">
<i>
<xsl:apply-templates>
<xsl:with-param name="anfang" select="$anfang"/>
<xsl:with-param name="ende" select="$ende"/>
<xsl:with-param name="output" select="$output"/>
</xsl:apply-templates>
</i>
</xsl:if>
</xsl:template>


<xsl:template match="tei:dateline">
<xsl:param name="output"/>
<xsl:param name="anfang"/>
<xsl:param name="ende"/>
<xsl:if test="not(following::tei:pb[@n=$anfang/@n]) and not(preceding::tei:pb[@n=$ende/@n])">
<xsl:choose>
<xsl:when test="//tei:dateline[@rendition] and $output='urtext'">
<p>
<xsl:call-template name="rendition">
<xsl:with-param name="rend" select="@rendition"/>
</xsl:call-template>
<xsl:apply-templates select="tei:settlement">
<xsl:with-param name="anfang" select="$anfang"/>
<xsl:with-param name="ende" select="$ende"/>
<xsl:with-param name="output" select="$output"/>
</xsl:apply-templates>   <xsl:apply-templates select="tei:date">
<xsl:with-param name="anfang" select="$anfang"/>
<xsl:with-param name="ende" select="$ende"/>
<xsl:with-param name="output" select="$output"/>
</xsl:apply-templates></p>
</xsl:when>

<xsl:otherwise>
<p>
<xsl:apply-templates select="tei:settlement">
<xsl:with-param name="anfang" select="$anfang"/>
<xsl:with-param name="ende" select="$ende"/>
<xsl:with-param name="output" select="$output"/>
</xsl:apply-templates>   <xsl:apply-templates select="tei:date">
<xsl:with-param name="anfang" select="$anfang"/>
<xsl:with-param name="ende" select="$ende"/>
<xsl:with-param name="output" select="$output"/>
</xsl:apply-templates></p>
</xsl:otherwise>
</xsl:choose>
</xsl:if>
</xsl:template>


<xsl:template match="tei:salute | tei:signed">
<xsl:param name="anfang"/>
<xsl:param name="ende"/>
<xsl:param name="output"/>
<xsl:if test="not(following::tei:pb[@n=$anfang/@n]) and not(preceding::tei:pb[@n=$ende/@n])">
<xsl:choose>
<xsl:when test="//tei:dateline[@rendition] and $output='urtext'">
<p>
<xsl:call-template name="rendition">
<xsl:with-param name="rend" select="@rendition"/>
</xsl:call-template>
<xsl:apply-templates>
<xsl:with-param name="anfang" select="$anfang"/>
<xsl:with-param name="ende" select="$ende"/>
<xsl:with-param name="output" select="$output"/>
</xsl:apply-templates>
</p>
</xsl:when>
<xsl:otherwise>
<p>
<xsl:apply-templates>
<xsl:with-param name="anfang" select="$anfang"/>
<xsl:with-param name="ende" select="$ende"/>
<xsl:with-param name="output" select="$output"/>
</xsl:apply-templates>
</p>
</xsl:otherwise>
</xsl:choose>
</xsl:if>
</xsl:template>


<xsl:template match="tei:gap">
<xsl:param name="anfang"/>
<xsl:param name="ende"/>
<xsl:param name="output"/>
<xsl:if test="not(following::tei:pb[@n=$anfang/@n]) and not(preceding::tei:pb[@n=$ende/@n])">
<xsl:text>[...]</xsl:text>
</xsl:if>
</xsl:template>
<xsl:template match="tei:unclear">
<xsl:param name="output"/>
<xsl:param name="anfang"/>
<xsl:param name="ende"/>
<xsl:if test="not(following::tei:pb[@n=$anfang/@n]) and not(preceding::tei:pb[@n=$ende/@n])">
<xsl:value-of select="concat('[', normalize-space(.), ']')"/>
</xsl:if>
</xsl:template>


<xsl:template match="//tei:expan | //tei:reg | //tei:corr">
<xsl:param name="output"/>
<xsl:param name="anfang"/>
<xsl:param name="ende"/>
<xsl:if test="not(following::tei:pb[@n=$anfang/@n]) and not(preceding::tei:pb[@n=$ende/@n])">
<xsl:if test="$output='korrigiert'">
<xsl:apply-templates>
<xsl:with-param name="anfang" select="$anfang"/>
<xsl:with-param name="ende" select="$ende"/>
</xsl:apply-templates>
</xsl:if>
</xsl:if>
</xsl:template>

<xsl:template match="//tei:abbr | //tei:orig | //tei:sic">
<xsl:param name="output"/>
<xsl:param name="anfang"/>
<xsl:param name="ende"/>
<xsl:if test="not(following::tei:pb[@n=$anfang/@n]) and not(preceding::tei:pb[@n=$ende/@n])">
<xsl:if test="$output='urtext'">
<xsl:apply-templates>
<xsl:with-param name="anfang" select="$anfang"/>
<xsl:with-param name="ende" select="$ende"/>
</xsl:apply-templates>
</xsl:if>
</xsl:if>
</xsl:template>


<xsl:template match="tei:note[not(@resp)]">
<xsl:param name="anfang"/>
<xsl:param name="ende"/>
<xsl:param name="output"/>
<xsl:if test="not(following::tei:pb[@n=$anfang/@n]) and not(preceding::tei:pb[@n=$ende/@n])">
<p>
<xsl:apply-templates>
<xsl:with-param name="anfang" select="$anfang"/>
<xsl:with-param name="ende" select="$ende"/>
<xsl:with-param name="output" select="$output"/>
</xsl:apply-templates>
</p>
</xsl:if>
</xsl:template>



<xsl:template match="tei:note[@resp]">
<xsl:param name="output"/>
<xsl:param name="anfang"/>
<xsl:param name="ende"/>
<xsl:if test="not(following::tei:pb[@n=$anfang/@n]) and not(preceding::tei:pb[@n=$ende/@n])">
<a class="info_anmerkung" href="#">
<sup>
<xsl:value-of select="count(preceding::tei:note) + 1"/>
</sup>
<span>
<xsl:value-of select=".[@xml:id]"/>
</span>
</a>

</xsl:if>
</xsl:template>

</xsl:stylesheet>

</nowiki></pre>

ODD

2011-04-13T13:18:57Z

Romary: /* Uses besides the TEI Guidelines and various customizations */

'''ODD''' stands for "One Document Does it all". It is a TEI XML-conformant specification format that allows one to customize TEI P5 in a [[Wikipedia:literate programming|literate programming]] fashion. It uses elements from the new [http://www.tei-c.org/P5/Guidelines/TD.html Tag Documentation] module.

== Description ==
The TEI Guidelines, its DTD, and its schema fragments, are all produced from a single XML resource containing:

# Descriptive prose (lots of it)
# Examples of usage (plenty)
# Formal declarations for components of the TEI Abstract Model:
## elements and attributes
## modules
## classes and macros

We call this resource an ODD (One Document Does it all), although the master source is instantiated as a gazillion XML mini-documents.

A system of XSLT stylesheets called [[Roma]] has been created for the purpose of easy manipulation of ODD files.

== Example ==
The TEI scheme can only be used by customizing it. Customizations are also expressed in the ODD language. For example:

<pre>
<schemaSpec ident="myTEIlite">
<desc>This is TEI Lite with simplified heads</desc>
<moduleRef name="teistructure"/>
<moduleRef name="linking"/>
<moduleRef name="core"/>
<moduleRef name="teiheader"/>
<elementSpec ident="head" mode="change">
<content><rng:text/></content>
</elementSpec>
</schemaSpec>
</pre>

produces the schema for TEI Lite, with a slight change.

== Uses besides the TEI Guidelines and various customizations ==

* [http://www.w3.org/TR/its/ Internationalization Tag Set (ITS)]
* various standards proposal designed within ISO committee TC 37 have been totally or partially written in TEI/ODD: MLIF, MAF, ISO 16642 rev., ISOTimeML

== Future plans ==

Over the years ODD has evolved progressively to reflect more and more needs of the TEI community, both as the core specification language for the TEI guidelines, but also as generic customization language for any TEI users. Still ODD remains a hybrid environment combining its own vacabulary with RelaxNG fragments and at times, validation vocabularies from external languages (e.g. Schematron). The TEI council contemplates putting on its work program a revision of the ODD infrastructure, considering either to drop it altogether in favor of one existing schema language, or extend its capabilities to make it a self contained and generic specification language.

== See also ==
*[http://en.wikipedia.org/wiki/ODD_%28Text_Encoding_Initiative%29 ODD (Text Encoding Initiative)] in Wikipedia
*[http://www.tei-c.org/Guidelines/Customization/odds.xml Getting Started with P5 ODDs]
*[http://tei.oucs.ox.ac.uk/Oxford/2007-02-13-oucs/talk-odds.xml A talk about the ODD system], given on 13 Feb 2007 by Lou Burnard and Sebastian Rahtz at the OUCS ''Encoding Digital Texts'' workshop
*[http://tei.oucs.ox.ac.uk/Oxford/2006-09-methNet/Talks/RomaJourney.ppt A PowerPoint presentation on TEI/ODD] by Laurent Romary; OUCS, September 2006
*[http://www.w3.org/TR/xml-i18n-bp/#tei-modularization A fragment of W3C's Best Practices for XML Internationalization concerning ODD customization for the Internationalization Tag Set (ITS).]
* [http://conferences.idealliance.org/extreme/html/2004/Bauman01/EML2004Bauman01.html Odd Customizations], by Syd Bauman and Julia Flanders.
* [http://conferences.idealliance.org/extreme/html/2004/Burnard01/EML2004Burnard01.html RelaxNG with Son of ODD], by Lou Burnard and Sebastian Rahtz.
* [http://www.balisage.net/Proceedings/vol1/html/Bauman01/BalisageVol1-Bauman01.html Freedom to Constrain] by Syd Bauman

[[Category:Customization|!]]

ODD

2011-04-13T13:02:27Z

Romary: /* Future plans */

'''ODD''' stands for "One Document Does it all". It is a TEI XML-conformant specification format that allows one to customize TEI P5 in a [[Wikipedia:literate programming|literate programming]] fashion. It uses elements from the new [http://www.tei-c.org/P5/Guidelines/TD.html Tag Documentation] module.

== Description ==
The TEI Guidelines, its DTD, and its schema fragments, are all produced from a single XML resource containing:

# Descriptive prose (lots of it)
# Examples of usage (plenty)
# Formal declarations for components of the TEI Abstract Model:
## elements and attributes
## modules
## classes and macros

We call this resource an ODD (One Document Does it all), although the master source is instantiated as a gazillion XML mini-documents.

A system of XSLT stylesheets called [[Roma]] has been created for the purpose of easy manipulation of ODD files.

== Example ==
The TEI scheme can only be used by customizing it. Customizations are also expressed in the ODD language. For example:

<pre>
<schemaSpec ident="myTEIlite">
<desc>This is TEI Lite with simplified heads</desc>
<moduleRef name="teistructure"/>
<moduleRef name="linking"/>
<moduleRef name="core"/>
<moduleRef name="teiheader"/>
<elementSpec ident="head" mode="change">
<content><rng:text/></content>
</elementSpec>
</schemaSpec>
</pre>

produces the schema for TEI Lite, with a slight change.

== Uses besides the TEI Guidelines and various customizations ==

* [http://www.w3.org/TR/its/ Internationalization Tag Set (ITS)]

== Future plans ==

Over the years ODD has evolved progressively to reflect more and more needs of the TEI community, both as the core specification language for the TEI guidelines, but also as generic customization language for any TEI users. Still ODD remains a hybrid environment combining its own vacabulary with RelaxNG fragments and at times, validation vocabularies from external languages (e.g. Schematron). The TEI council contemplates putting on its work program a revision of the ODD infrastructure, considering either to drop it altogether in favor of one existing schema language, or extend its capabilities to make it a self contained and generic specification language.

== See also ==
*[http://en.wikipedia.org/wiki/ODD_%28Text_Encoding_Initiative%29 ODD (Text Encoding Initiative)] in Wikipedia
*[http://www.tei-c.org/Guidelines/Customization/odds.xml Getting Started with P5 ODDs]
*[http://tei.oucs.ox.ac.uk/Oxford/2007-02-13-oucs/talk-odds.xml A talk about the ODD system], given on 13 Feb 2007 by Lou Burnard and Sebastian Rahtz at the OUCS ''Encoding Digital Texts'' workshop
*[http://tei.oucs.ox.ac.uk/Oxford/2006-09-methNet/Talks/RomaJourney.ppt A PowerPoint presentation on TEI/ODD] by Laurent Romary; OUCS, September 2006
*[http://www.w3.org/TR/xml-i18n-bp/#tei-modularization A fragment of W3C's Best Practices for XML Internationalization concerning ODD customization for the Internationalization Tag Set (ITS).]
* [http://conferences.idealliance.org/extreme/html/2004/Bauman01/EML2004Bauman01.html Odd Customizations], by Syd Bauman and Julia Flanders.
* [http://conferences.idealliance.org/extreme/html/2004/Burnard01/EML2004Burnard01.html RelaxNG with Son of ODD], by Lou Burnard and Sebastian Rahtz.
* [http://www.balisage.net/Proceedings/vol1/html/Bauman01/BalisageVol1-Bauman01.html Freedom to Constrain] by Syd Bauman

[[Category:Customization|!]]

Council

2011-04-13T09:27:02Z

Romary: /* Agenda */

Also see the [http://www.tei-c.org/Activities/Council/ Council section of the TEI-C website] for archived documents.

== F2F meeting - Chicago 11-13 April 2010 ==

=== 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.

=== Notes ===
==== 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: ( http://thread.gmane.org/gmane.comp.ai.gate.general/5257 )

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

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

=== Agenda ===
==== Thursday morning ====
* Welcome, overview of agenda
* Wrap-up from Symposium
* First SF session (see [http://www.tei-c.org/Activities/Council/Working/tcw17.html])
==== 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 ===

[[Draft minutes of 2010-04 Council meeting|Draft minutes]]

== 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

=== Agenda ===
* 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 ===
[https://listes.cru.fr/wiki/tei-res/public/tei_council_2009_a_lyon Meeting in Lyon]
Available abstracts under: [https://listes.cru.fr/wiki/tei-res/prive/reunioncouncilavril09]

=== Draft Agenda ===
[http://www.tei-c.org/Activities/Council/Meetings/tcm40.xml 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
[http://sourceforge.net/tracker2/?func=detail&aid=2411994&group_id=106328&atid=644065 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 [http://www.esf.org/activities/exploratory-workshops.html]
* SIGs
** TEI in library SIG - TEI Tite status
** New SIG: Scientific bibliographies [http://www.tei-c.org/Activities/Council/Working/tcw16.xml]
** Report: TEI Manuscript[http://www.tei-c.org/Activities/SIG/Manuscript/mssigr03.pdf]
* Misc.
** Necessary work on www.tei-c.org (further rationalization of structure,
etc.)
** In particular, status of TEI vault
http://www.tei-c.org.uk/Vault/Vault-GL.html (LB)

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

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

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--[[User:Romary|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)

== 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 [http://lists.village.virginia.edu/pipermail/tei-council/2008/010041.html Quoting a TEI Object] from September 2008. DS has created a new wiki page for discussing [[Council:stable references|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.

== Misc. ==
For general information concerning the council see [[TEI-Council-FAQ]] page and [[:Category: Council|category reserved for use by TEI Council]]...

[[Category:Council]]

Council

2011-04-12T18:04:50Z

Romary: /* Agenda */

Also see the [http://www.tei-c.org/Activities/Council/ Council section of the TEI-C website] for archived documents.

== F2F meeting - Chicago 11-13 April 2010 ==

=== 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.

From the ongoing discussion, we may also want to discuss the following issues:
* usage of floatingText within other constructs: sp, quote, etc.

=== Notes ===
==== 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: ( http://thread.gmane.org/gmane.comp.ai.gate.general/5257 )

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

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

=== Agenda ===
==== Thursday morning ====
* Welcome, overview of agenda
* Wrap-up from Symposium
* First SF session (see [http://www.tei-c.org/Activities/Council/Working/tcw17.html])
==== 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 ===

[[Draft minutes of 2010-04 Council meeting|Draft minutes]]

== 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

=== Agenda ===
* 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 ===
[https://listes.cru.fr/wiki/tei-res/public/tei_council_2009_a_lyon Meeting in Lyon]
Available abstracts under: [https://listes.cru.fr/wiki/tei-res/prive/reunioncouncilavril09]

=== Draft Agenda ===
[http://www.tei-c.org/Activities/Council/Meetings/tcm40.xml 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
[http://sourceforge.net/tracker2/?func=detail&aid=2411994&group_id=106328&atid=644065 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 [http://www.esf.org/activities/exploratory-workshops.html]
* SIGs
** TEI in library SIG - TEI Tite status
** New SIG: Scientific bibliographies [http://www.tei-c.org/Activities/Council/Working/tcw16.xml]
** Report: TEI Manuscript[http://www.tei-c.org/Activities/SIG/Manuscript/mssigr03.pdf]
* Misc.
** Necessary work on www.tei-c.org (further rationalization of structure,
etc.)
** In particular, status of TEI vault
http://www.tei-c.org.uk/Vault/Vault-GL.html (LB)

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

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

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--[[User:Romary|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)

== 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 [http://lists.village.virginia.edu/pipermail/tei-council/2008/010041.html Quoting a TEI Object] from September 2008. DS has created a new wiki page for discussing [[Council:stable references|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.

== Misc. ==
For general information concerning the council see [[TEI-Council-FAQ]] page and [[:Category: Council|category reserved for use by TEI Council]]...

[[Category:Council]]

Council

2011-03-24T07:52:18Z

Romary: /* Agenda */

== F2F meeting - Chicago 11-13 April 2010 ==

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

* Automating guidelines production (Presentation by Sebastian, Tuesday morning)
* Presentation on Guideline edition (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?)

From the ongoing discussion, we may also want to discuss the following issues:
* usage of floatingText within other constructs: sp, quote, etc.

=== Notes ===
==== 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 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 annotable text look like?" is an important question.

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

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

== Item for further consideration ==
* Stable URIs to whatever 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)

=== Agenda ===
==== Thursday morning ====
* Welcome, overview of agenda
* Wrap-up from Symposium
* First SF session (see [http://www.tei-c.org/Activities/Council/Working/tcw17.html])
==== 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 ===

[[Draft minutes of 2010-04 Council meeting|Draft minutes]]

== 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

=== Agenda ===
* 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 ===
[https://listes.cru.fr/wiki/tei-res/public/tei_council_2009_a_lyon Meeting in Lyon]
Available abstracts under: [https://listes.cru.fr/wiki/tei-res/prive/reunioncouncilavril09]

=== Draft Agenda ===
[http://www.tei-c.org/Activities/Council/Meetings/tcm40.xml 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
[http://sourceforge.net/tracker2/?func=detail&aid=2411994&group_id=106328&atid=644065 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 [http://www.esf.org/activities/exploratory-workshops.html]
* SIGs
** TEI in library SIG - TEI Tite status
** New SIG: Scientific bibliographies [http://www.tei-c.org/Activities/Council/Working/tcw16.xml]
** Report: TEI Manuscript[http://www.tei-c.org/Activities/SIG/Manuscript/mssigr03.pdf]
* Misc.
** Necessary work on www.tei-c.org (further rationalization of structure,
etc.)
** In particular, status of TEI vault
http://www.tei-c.org.uk/Vault/Vault-GL.html (LB)

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

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

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--[[User:Romary|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)

== 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 [http://lists.village.virginia.edu/pipermail/tei-council/2008/010041.html Quoting a TEI Object] from September 2008. DS has created a new wiki page for discussing [[Council:stable references|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.

== Misc. ==
For general information concerning the council see [[TEI-Council-FAQ]] page and [[:Category: Council|category reserved for use by TEI Council]]...

[[Category:Council]]

Council

2011-03-24T06:01:43Z

Romary: /* F2F meeting - Chicago 11-13 April 2010 */

== F2F meeting - Chicago 11-13 April 2010 ==

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

* Automating guidelines production (Presentation by Sebastian, Tuesday morning)
* Presentation on Guideline edition (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?)

=== Notes ===
==== 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 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 annotable text look like?" is an important question.

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

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

== Item for further consideration ==
* Stable URIs to whatever 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)

=== Agenda ===
==== Thursday morning ====
* Welcome, overview of agenda
* Wrap-up from Symposium
* First SF session (see [http://www.tei-c.org/Activities/Council/Working/tcw17.html])
==== 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 ===

[[Draft minutes of 2010-04 Council meeting|Draft minutes]]

== 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

=== Agenda ===
* 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 ===
[https://listes.cru.fr/wiki/tei-res/public/tei_council_2009_a_lyon Meeting in Lyon]
Available abstracts under: [https://listes.cru.fr/wiki/tei-res/prive/reunioncouncilavril09]

=== Draft Agenda ===
[http://www.tei-c.org/Activities/Council/Meetings/tcm40.xml 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
[http://sourceforge.net/tracker2/?func=detail&aid=2411994&group_id=106328&atid=644065 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 [http://www.esf.org/activities/exploratory-workshops.html]
* SIGs
** TEI in library SIG - TEI Tite status
** New SIG: Scientific bibliographies [http://www.tei-c.org/Activities/Council/Working/tcw16.xml]
** Report: TEI Manuscript[http://www.tei-c.org/Activities/SIG/Manuscript/mssigr03.pdf]
* Misc.
** Necessary work on www.tei-c.org (further rationalization of structure,
etc.)
** In particular, status of TEI vault
http://www.tei-c.org.uk/Vault/Vault-GL.html (LB)

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

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

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--[[User:Romary|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)

== 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 [http://lists.village.virginia.edu/pipermail/tei-council/2008/010041.html Quoting a TEI Object] from September 2008. DS has created a new wiki page for discussing [[Council:stable references|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.

== Misc. ==
For general information concerning the council see [[TEI-Council-FAQ]] page and [[:Category: Council|category reserved for use by TEI Council]]...

[[Category:Council]]

Council

2011-03-23T15:44:38Z

Romary: /* Agenda */

== F2F meeting - Chicago 11-13 April 2010 ==

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

* Automating guidelines production (Presentation by Sebastian, Tuesday morning)
* TEI and Google: report from Martin M. and strategy
* TEI for publishing - next steps (reports from Lou (revues.org+PUC), Kewin for TEI PUB SIG?)

=== Notes ===
==== 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 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 annotable text look like?" is an important question.

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

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

== Item for further consideration ==
* Stable URIs to whatever 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)

=== Agenda ===
==== Thursday morning ====
* Welcome, overview of agenda
* Wrap-up from Symposium
* First SF session (see [http://www.tei-c.org/Activities/Council/Working/tcw17.html])
==== 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 ===

[[Draft minutes of 2010-04 Council meeting|Draft minutes]]

== 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

=== Agenda ===
* 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 ===
[https://listes.cru.fr/wiki/tei-res/public/tei_council_2009_a_lyon Meeting in Lyon]
Available abstracts under: [https://listes.cru.fr/wiki/tei-res/prive/reunioncouncilavril09]

=== Draft Agenda ===
[http://www.tei-c.org/Activities/Council/Meetings/tcm40.xml 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
[http://sourceforge.net/tracker2/?func=detail&aid=2411994&group_id=106328&atid=644065 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 [http://www.esf.org/activities/exploratory-workshops.html]
* SIGs
** TEI in library SIG - TEI Tite status
** New SIG: Scientific bibliographies [http://www.tei-c.org/Activities/Council/Working/tcw16.xml]
** Report: TEI Manuscript[http://www.tei-c.org/Activities/SIG/Manuscript/mssigr03.pdf]
* Misc.
** Necessary work on www.tei-c.org (further rationalization of structure,
etc.)
** In particular, status of TEI vault
http://www.tei-c.org.uk/Vault/Vault-GL.html (LB)

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

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

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--[[User:Romary|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)

== 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 [http://lists.village.virginia.edu/pipermail/tei-council/2008/010041.html Quoting a TEI Object] from September 2008. DS has created a new wiki page for discussing [[Council:stable references|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.

== Misc. ==
For general information concerning the council see [[TEI-Council-FAQ]] page and [[:Category: Council|category reserved for use by TEI Council]]...

[[Category:Council]]

Council

2011-03-23T13:36:46Z

Romary: /* TEI and Google */

== F2F meeting - Chicago 11-13 April 2010 ==

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

* Automating guidelines production (Presentation by Sebastian, Tuesday morning)
* TEI and Google: report from Martin and strategy
* TEI for publishing - next steps (reports from Lou (revues.org+PUC), Kewin for TEI PUB SIG?)

=== Notes ===
==== 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 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 annotable text look like?" is an important question.

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

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

== Item for further consideration ==
* Stable URIs to whatever 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)

=== Agenda ===
==== Thursday morning ====
* Welcome, overview of agenda
* Wrap-up from Symposium
* First SF session (see [http://www.tei-c.org/Activities/Council/Working/tcw17.html])
==== 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 ===

[[Draft minutes of 2010-04 Council meeting|Draft minutes]]

== 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

=== Agenda ===
* 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 ===
[https://listes.cru.fr/wiki/tei-res/public/tei_council_2009_a_lyon Meeting in Lyon]
Available abstracts under: [https://listes.cru.fr/wiki/tei-res/prive/reunioncouncilavril09]

=== Draft Agenda ===
[http://www.tei-c.org/Activities/Council/Meetings/tcm40.xml 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
[http://sourceforge.net/tracker2/?func=detail&aid=2411994&group_id=106328&atid=644065 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 [http://www.esf.org/activities/exploratory-workshops.html]
* SIGs
** TEI in library SIG - TEI Tite status
** New SIG: Scientific bibliographies [http://www.tei-c.org/Activities/Council/Working/tcw16.xml]
** Report: TEI Manuscript[http://www.tei-c.org/Activities/SIG/Manuscript/mssigr03.pdf]
* Misc.
** Necessary work on www.tei-c.org (further rationalization of structure,
etc.)
** In particular, status of TEI vault
http://www.tei-c.org.uk/Vault/Vault-GL.html (LB)

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

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

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--[[User:Romary|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)

== 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 [http://lists.village.virginia.edu/pipermail/tei-council/2008/010041.html Quoting a TEI Object] from September 2008. DS has created a new wiki page for discussing [[Council:stable references|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.

== Misc. ==
For general information concerning the council see [[TEI-Council-FAQ]] page and [[:Category: Council|category reserved for use by TEI Council]]...

[[Category:Council]]

Council

2011-03-23T12:59:36Z

Romary: /* Agenda */

== F2F meeting - Chicago 11-13 April 2010 ==

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

* Automating guidelines production (Presentation by Sebastian, Tuesday morning)
* TEI and Google: report from Martin and strategy
* TEI for publishing - next steps (reports from Lou (revues.org+PUC), Kewin for TEI PUB SIG?)

=== Notes ===
==== 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 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 annotable text look like?" is an important question.

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

== Item for further consideration ==
* Stable URIs to whatever 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)

=== Agenda ===
==== Thursday morning ====
* Welcome, overview of agenda
* Wrap-up from Symposium
* First SF session (see [http://www.tei-c.org/Activities/Council/Working/tcw17.html])
==== 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 ===

[[Draft minutes of 2010-04 Council meeting|Draft minutes]]

== 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

=== Agenda ===
* 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 ===
[https://listes.cru.fr/wiki/tei-res/public/tei_council_2009_a_lyon Meeting in Lyon]
Available abstracts under: [https://listes.cru.fr/wiki/tei-res/prive/reunioncouncilavril09]

=== Draft Agenda ===
[http://www.tei-c.org/Activities/Council/Meetings/tcm40.xml 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
[http://sourceforge.net/tracker2/?func=detail&aid=2411994&group_id=106328&atid=644065 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 [http://www.esf.org/activities/exploratory-workshops.html]
* SIGs
** TEI in library SIG - TEI Tite status
** New SIG: Scientific bibliographies [http://www.tei-c.org/Activities/Council/Working/tcw16.xml]
** Report: TEI Manuscript[http://www.tei-c.org/Activities/SIG/Manuscript/mssigr03.pdf]
* Misc.
** Necessary work on www.tei-c.org (further rationalization of structure,
etc.)
** In particular, status of TEI vault
http://www.tei-c.org.uk/Vault/Vault-GL.html (LB)

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

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

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--[[User:Romary|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)

== 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 [http://lists.village.virginia.edu/pipermail/tei-council/2008/010041.html Quoting a TEI Object] from September 2008. DS has created a new wiki page for discussing [[Council:stable references|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.

== Misc. ==
For general information concerning the council see [[TEI-Council-FAQ]] page and [[:Category: Council|category reserved for use by TEI Council]]...

[[Category:Council]]

Council

2011-03-23T12:47:38Z

Romary:

== F2F meeting - Chicago 11-13 April 2010 ==

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

* Automating guidelines production (Presentation by Sebastian, Tuesday morning)
* TEI and Google: report from Martin and strategy
* TEI for publishing - next steps (reports from Lou (revues.org+PUC), Kewin for TEI PUB SIG?)

== Item for further consideration ==
* Stable URIs to whatever 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)

=== Agenda ===
==== Thursday morning ====
* Welcome, overview of agenda
* Wrap-up from Symposium
* First SF session (see [http://www.tei-c.org/Activities/Council/Working/tcw17.html])
==== 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 ===

[[Draft minutes of 2010-04 Council meeting|Draft minutes]]

== 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

=== Agenda ===
* 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 ===
[https://listes.cru.fr/wiki/tei-res/public/tei_council_2009_a_lyon Meeting in Lyon]
Available abstracts under: [https://listes.cru.fr/wiki/tei-res/prive/reunioncouncilavril09]

=== Draft Agenda ===
[http://www.tei-c.org/Activities/Council/Meetings/tcm40.xml 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
[http://sourceforge.net/tracker2/?func=detail&aid=2411994&group_id=106328&atid=644065 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 [http://www.esf.org/activities/exploratory-workshops.html]
* SIGs
** TEI in library SIG - TEI Tite status
** New SIG: Scientific bibliographies [http://www.tei-c.org/Activities/Council/Working/tcw16.xml]
** Report: TEI Manuscript[http://www.tei-c.org/Activities/SIG/Manuscript/mssigr03.pdf]
* Misc.
** Necessary work on www.tei-c.org (further rationalization of structure,
etc.)
** In particular, status of TEI vault
http://www.tei-c.org.uk/Vault/Vault-GL.html (LB)

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

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

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--[[User:Romary|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)

== 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 [http://lists.village.virginia.edu/pipermail/tei-council/2008/010041.html Quoting a TEI Object] from September 2008. DS has created a new wiki page for discussing [[Council:stable references|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.

== Misc. ==
For general information concerning the council see [[TEI-Council-FAQ]] page and [[:Category: Council|category reserved for use by TEI Council]]...

[[Category:Council]]

SIG:TEI for Linguists

2010-08-11T09:54:43Z

Romary: /* The most relevant chapters of the Guidelines */

[[Category:Community]]
This is an informal meeting point for those interested in linguistics, in the TEI, and in putting the two together.

Mailing list:

=== Links ===
==== History ====
* Here's [http://listserv.brown.edu/archives/cgi-bin/wa?A2=ind1007&L=TEI-L&T=0&F=&S=&P=1668 how it began]
* TEI Guidelines have their apocrypha as well, here's one on [http://www.tei-c.org/Activities/Workgroups/SO/sow05.xml corpus annotation]. Note that it is absolutely non-normative, included here to give credit to the original Working Group and to provide a platform to either elaborate on or to diverge from.
==== The most relevant chapters of the Guidelines ====
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/TS.html 8. Transcriptions of Speech]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DI.html 9. Dictionaries]: we need to have a plan so that the NLP community does consider this as a default vocabulary for representing NLP lexica (e.g. full form lexica)
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CC.html 15. Language Corpora]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/AI.html 17. Simple Analytic Mechanisms]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/FS.html 18. Feature Structures]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/NH.html 20. Non-hierarchical Structures]

==== Related SIGs ====
* [[SIG:Ontologies|Ontologies]]
* [[SIG:Tools|Tools]]
* [[SIG:Overlap|Overlap]]
==== Papers/presentations? ====
On using the TEI dictionary chapter as a default implementation of ISO 24613 (Lexical Markup Framework), let me quote http://hal.archives-ouvertes.fr/hal-00436328/fr/ ("Standardization of the formal representation of lexical information for NLP").

==== Projects ====
TEI projects with a linguistic focus
* FreeDict http://freedict.org/en/

==== Tools - reports of non-TEI linguistic tools working / not working with TEI ====
* [http://gate.ac.uk/ GATE] doesn't do XML see [http://thread.gmane.org/gmane.comp.ai.gate.general/5257/focus=5301 XML parsing issue: consecutive empty elements mishandled]
* See also the TEI-influenced or TEI-based tools: [[Xaira]], [[Textometrie]], [[Poliqarp]] and [[Anotatornia]]

=== LLiZ (Linguistic Lunch in Zadar) ===
The idea is to meet at an informal lunch during the [http://ling.unizd.hr/~tei2010/index.en.html TEI-MM in Zadar] to see what common goals we may have and what we want to do about them.

'''Date''': (let's decide around October)

'''Place''': (let's decide in November)

'''List of participants''' (add your name):
* Elena Pierazzo (who lit the spark, inspired by Piotr and Adam's talk -- or so they want to think)
* Piotr Bański (who dropped the last drop and suggested the meeting)
* Espen Ore
* Eleonora Litta Modignani Picozzi (who has currently still on leave and is ready to take on some administrative chores)
* Sabine Bartsch
* Andreas Witt
* Laurent Romary
* ...

SIG:TEI for Linguists

2010-08-11T09:53:33Z

Romary: /* Papers/presentations? */

[[Category:Community]]
This is an informal meeting point for those interested in linguistics, in the TEI, and in putting the two together.

Mailing list:

=== Links ===
==== History ====
* Here's [http://listserv.brown.edu/archives/cgi-bin/wa?A2=ind1007&L=TEI-L&T=0&F=&S=&P=1668 how it began]
* TEI Guidelines have their apocrypha as well, here's one on [http://www.tei-c.org/Activities/Workgroups/SO/sow05.xml corpus annotation]. Note that it is absolutely non-normative, included here to give credit to the original Working Group and to provide a platform to either elaborate on or to diverge from.
==== The most relevant chapters of the Guidelines ====
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/TS.html 8. Transcriptions of Speech]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DI.html 9. Dictionaries]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CC.html 15. Language Corpora]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/AI.html 17. Simple Analytic Mechanisms]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/FS.html 18. Feature Structures]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/NH.html 20. Non-hierarchical Structures]
==== Related SIGs ====
* [[SIG:Ontologies|Ontologies]]
* [[SIG:Tools|Tools]]
* [[SIG:Overlap|Overlap]]
==== Papers/presentations? ====
On using the TEI dictionary chapter as a default implementation of ISO 24613 (Lexical Markup Framework), let me quote http://hal.archives-ouvertes.fr/hal-00436328/fr/ ("Standardization of the formal representation of lexical information for NLP").

==== Projects ====
TEI projects with a linguistic focus
* FreeDict http://freedict.org/en/

==== Tools - reports of non-TEI linguistic tools working / not working with TEI ====
* [http://gate.ac.uk/ GATE] doesn't do XML see [http://thread.gmane.org/gmane.comp.ai.gate.general/5257/focus=5301 XML parsing issue: consecutive empty elements mishandled]
* See also the TEI-influenced or TEI-based tools: [[Xaira]], [[Textometrie]], [[Poliqarp]] and [[Anotatornia]]

=== LLiZ (Linguistic Lunch in Zadar) ===
The idea is to meet at an informal lunch during the [http://ling.unizd.hr/~tei2010/index.en.html TEI-MM in Zadar] to see what common goals we may have and what we want to do about them.

'''Date''': (let's decide around October)

'''Place''': (let's decide in November)

'''List of participants''' (add your name):
* Elena Pierazzo (who lit the spark, inspired by Piotr and Adam's talk -- or so they want to think)
* Piotr Bański (who dropped the last drop and suggested the meeting)
* Espen Ore
* Eleonora Litta Modignani Picozzi (who has currently still on leave and is ready to take on some administrative chores)
* Sabine Bartsch
* Andreas Witt
* Laurent Romary
* ...

SIG:TEI for Linguists

2010-08-11T09:50:16Z

Romary: /* LLiZ (Linguistic Lunch in Zadar) */

[[Category:Community]]
This is an informal meeting point for those interested in linguistics, in the TEI, and in putting the two together.

Mailing list:

=== Links ===
==== History ====
* Here's [http://listserv.brown.edu/archives/cgi-bin/wa?A2=ind1007&L=TEI-L&T=0&F=&S=&P=1668 how it began]
* TEI Guidelines have their apocrypha as well, here's one on [http://www.tei-c.org/Activities/Workgroups/SO/sow05.xml corpus annotation]. Note that it is absolutely non-normative, included here to give credit to the original Working Group and to provide a platform to either elaborate on or to diverge from.
==== The most relevant chapters of the Guidelines ====
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/TS.html 8. Transcriptions of Speech]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DI.html 9. Dictionaries]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CC.html 15. Language Corpora]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/AI.html 17. Simple Analytic Mechanisms]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/FS.html 18. Feature Structures]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/NH.html 20. Non-hierarchical Structures]
==== Related SIGs ====
* [[SIG:Ontologies|Ontologies]]
* [[SIG:Tools|Tools]]
* [[SIG:Overlap|Overlap]]
==== Papers/presentations? ====
==== Projects ====
TEI projects with a linguistic focus
* FreeDict http://freedict.org/en/

==== Tools - reports of non-TEI linguistic tools working / not working with TEI ====
* [http://gate.ac.uk/ GATE] doesn't do XML see [http://thread.gmane.org/gmane.comp.ai.gate.general/5257/focus=5301 XML parsing issue: consecutive empty elements mishandled]
* See also the TEI-influenced or TEI-based tools: [[Xaira]], [[Textometrie]], [[Poliqarp]] and [[Anotatornia]]

=== LLiZ (Linguistic Lunch in Zadar) ===
The idea is to meet at an informal lunch during the [http://ling.unizd.hr/~tei2010/index.en.html TEI-MM in Zadar] to see what common goals we may have and what we want to do about them.

'''Date''': (let's decide around October)

'''Place''': (let's decide in November)

'''List of participants''' (add your name):
* Elena Pierazzo (who lit the spark, inspired by Piotr and Adam's talk -- or so they want to think)
* Piotr Bański (who dropped the last drop and suggested the meeting)
* Espen Ore
* Eleonora Litta Modignani Picozzi (who has currently still on leave and is ready to take on some administrative chores)
* Sabine Bartsch
* Andreas Witt
* Laurent Romary
* ...

Council

2010-04-30T14:41:36Z

Romary: /* F2F meeting - Dublin 28-30 April 2010 */

== Item for further consideration ==
* Stable URIs to whatever bits of the guidelines

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

=== Agenda ===
==== Thursday morning ====
* Welcome, overview of agenda
* Wrap-up from Symposium
* First SF session (see [http://www.tei-c.org/Activities/Council/Working/tcw17.html])
==== 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)

== 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

=== Agenda ===
* 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 ===
[https://listes.cru.fr/wiki/tei-res/public/tei_council_2009_a_lyon Meeting in Lyon]
Available abstracts under: [https://listes.cru.fr/wiki/tei-res/prive/reunioncouncilavril09]

=== Draft Agenda ===
[http://www.tei-c.org/Activities/Council/Meetings/tcm40.xml 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
[http://sourceforge.net/tracker2/?func=detail&aid=2411994&group_id=106328&atid=644065 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 [http://www.esf.org/activities/exploratory-workshops.html]
* SIGs
** TEI in library SIG - TEI Tite status
** New SIG: Scientific bibliographies [http://www.tei-c.org/Activities/Council/Working/tcw16.xml]
** Report: TEI Manuscript[http://www.tei-c.org/Activities/SIG/Manuscript/mssigr03.pdf]
* Misc.
** Necessary work on www.tei-c.org (further rationalization of structure,
etc.)
** In particular, status of TEI vault
http://www.tei-c.org.uk/Vault/Vault-GL.html (LB)

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

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

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--[[User:Romary|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)

== 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 [http://lists.village.virginia.edu/pipermail/tei-council/2008/010041.html Quoting a TEI Object] from September 2008. DS has created a new wiki page for discussing [[Council:stable references|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.

== Misc. ==
For general information concerning the council see [[TEI-Council-FAQ]] page and [[:Category: Council|category reserved for use by TEI Council]]...

[[Category:Council]]

Council

2010-04-14T08:58:47Z

Romary:

== F2F meeting - Dublin 28-30 April 2010 ==
=== Agenda ===
==== Thursday morning ====
* Welcome, overview of agenda
* Wrap-up from Symposium
* First SF session (see [http://www.tei-c.org/Activities/Council/Working/tcw17.html])
==== Thursday afternoon ====
* bilStruct
* Manuscript
* Second SF session
==== 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)

== 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

=== Agenda ===
* 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 ===
[https://listes.cru.fr/wiki/tei-res/public/tei_council_2009_a_lyon Meeting in Lyon]
Available abstracts under: [https://listes.cru.fr/wiki/tei-res/prive/reunioncouncilavril09]

=== Draft Agenda ===
[http://www.tei-c.org/Activities/Council/Meetings/tcm40.xml 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
[http://sourceforge.net/tracker2/?func=detail&aid=2411994&group_id=106328&atid=644065 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 [http://www.esf.org/activities/exploratory-workshops.html]
* SIGs
** TEI in library SIG - TEI Tite status
** New SIG: Scientific bibliographies [http://www.tei-c.org/Activities/Council/Working/tcw16.xml]
** Report: TEI Manuscript[http://www.tei-c.org/Activities/SIG/Manuscript/mssigr03.pdf]
* Misc.
** Necessary work on www.tei-c.org (further rationalization of structure,
etc.)
** In particular, status of TEI vault
http://www.tei-c.org.uk/Vault/Vault-GL.html (LB)

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

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

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--[[User:Romary|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)

== 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 [http://lists.village.virginia.edu/pipermail/tei-council/2008/010041.html Quoting a TEI Object] from September 2008. DS has created a new wiki page for discussing [[Council:stable references|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.

== Misc. ==
For general information concerning the council see [[TEI-Council-FAQ]] page and [[:Category: Council|category reserved for use by TEI Council]]...

[[Category:Council]]

Council

2010-04-14T08:58:24Z

Romary:

== F2F meeting - Dublin 28-30 April 2010 ==
=== Agenda ===
== Thursday morning ==
* Welcome, overview of agenda
* Wrap-up from Symposium
* First SF session (see [http://www.tei-c.org/Activities/Council/Working/tcw17.html])
==== Thursday afternoon ====
* bilStruct
* Manuscript
* Second SF session
==== 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)

== 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

=== Agenda ===
* 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 ===
[https://listes.cru.fr/wiki/tei-res/public/tei_council_2009_a_lyon Meeting in Lyon]
Available abstracts under: [https://listes.cru.fr/wiki/tei-res/prive/reunioncouncilavril09]

=== Draft Agenda ===
[http://www.tei-c.org/Activities/Council/Meetings/tcm40.xml 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
[http://sourceforge.net/tracker2/?func=detail&aid=2411994&group_id=106328&atid=644065 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 [http://www.esf.org/activities/exploratory-workshops.html]
* SIGs
** TEI in library SIG - TEI Tite status
** New SIG: Scientific bibliographies [http://www.tei-c.org/Activities/Council/Working/tcw16.xml]
** Report: TEI Manuscript[http://www.tei-c.org/Activities/SIG/Manuscript/mssigr03.pdf]
* Misc.
** Necessary work on www.tei-c.org (further rationalization of structure,
etc.)
** In particular, status of TEI vault
http://www.tei-c.org.uk/Vault/Vault-GL.html (LB)

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

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

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--[[User:Romary|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)

== 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 [http://lists.village.virginia.edu/pipermail/tei-council/2008/010041.html Quoting a TEI Object] from September 2008. DS has created a new wiki page for discussing [[Council:stable references|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.

== Misc. ==
For general information concerning the council see [[TEI-Council-FAQ]] page and [[:Category: Council|category reserved for use by TEI Council]]...

[[Category:Council]]

Council

2010-04-14T08:57:16Z

Romary: /* F2F meeting - Dublin 28-30 April 2010 */

== F2F meeting - Dublin 28-30 April 2010 ==
=== Agenda ===
== Thursday morning ==
* Welcome, overview of agenda
* Wrap-up from Symposium
* First SF session (see [http://www.tei-c.org/Activities/Council/Working/tcw17.html])
== Thursday afternoon ==
* bilStruct
* Manuscript
* Second SF session
== 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)

== 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

=== Agenda ===
* 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 ===
[https://listes.cru.fr/wiki/tei-res/public/tei_council_2009_a_lyon Meeting in Lyon]
Available abstracts under: [https://listes.cru.fr/wiki/tei-res/prive/reunioncouncilavril09]

=== Draft Agenda ===
[http://www.tei-c.org/Activities/Council/Meetings/tcm40.xml 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
[http://sourceforge.net/tracker2/?func=detail&aid=2411994&group_id=106328&atid=644065 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 [http://www.esf.org/activities/exploratory-workshops.html]
* SIGs
** TEI in library SIG - TEI Tite status
** New SIG: Scientific bibliographies [http://www.tei-c.org/Activities/Council/Working/tcw16.xml]
** Report: TEI Manuscript[http://www.tei-c.org/Activities/SIG/Manuscript/mssigr03.pdf]
* Misc.
** Necessary work on www.tei-c.org (further rationalization of structure,
etc.)
** In particular, status of TEI vault
http://www.tei-c.org.uk/Vault/Vault-GL.html (LB)

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

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

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--[[User:Romary|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)

== 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 [http://lists.village.virginia.edu/pipermail/tei-council/2008/010041.html Quoting a TEI Object] from September 2008. DS has created a new wiki page for discussing [[Council:stable references|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.

== Misc. ==
For general information concerning the council see [[TEI-Council-FAQ]] page and [[:Category: Council|category reserved for use by TEI Council]]...

[[Category:Council]]

Council

2010-02-09T16:44:45Z

Romary: /* Topics for discussion */

== F2F meeting - Dublin 28-30 April 2010 ==
=== Topics for discussion ===
* Deprecating mechanisms
* Pointing and keying - can one absorb the other? (key?, target/targets)

== 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

=== Agenda ===
* 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 ===
[https://listes.cru.fr/wiki/tei-res/public/tei_council_2009_a_lyon Meeting in Lyon]
Available abstracts under: [https://listes.cru.fr/wiki/tei-res/prive/reunioncouncilavril09]

=== Draft Agenda ===
[http://www.tei-c.org/Activities/Council/Meetings/tcm40.xml 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
[http://sourceforge.net/tracker2/?func=detail&aid=2411994&group_id=106328&atid=644065 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 [http://www.esf.org/activities/exploratory-workshops.html]
* SIGs
** TEI in library SIG - TEI Tite status
** New SIG: Scientific bibliographies [http://www.tei-c.org/Activities/Council/Working/tcw16.xml]
** Report: TEI Manuscript[http://www.tei-c.org/Activities/SIG/Manuscript/mssigr03.pdf]
* Misc.
** Necessary work on www.tei-c.org (further rationalization of structure,
etc.)
** In particular, status of TEI vault
http://www.tei-c.org.uk/Vault/Vault-GL.html (LB)

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

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

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--[[User:Romary|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)

== 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 [http://lists.village.virginia.edu/pipermail/tei-council/2008/010041.html Quoting a TEI Object] from September 2008. DS has created a new wiki page for discussing [[Council:stable references|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.

== Misc. ==
For general information concerning the council see [[TEI-Council-FAQ]] page and [[:Category: Council|category reserved for use by TEI Council]]...

[[Category:Council]]

Council

2010-02-09T16:43:01Z

Romary: /* Topics for discussion */

== F2F meeting - Dublin 28-30 April 2010 ==
=== Topics for discussion ===
* Deprecating mechanisms
* Pointing and keying - can one absorb the other?

== 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

=== Agenda ===
* 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 ===
[https://listes.cru.fr/wiki/tei-res/public/tei_council_2009_a_lyon Meeting in Lyon]
Available abstracts under: [https://listes.cru.fr/wiki/tei-res/prive/reunioncouncilavril09]

=== Draft Agenda ===
[http://www.tei-c.org/Activities/Council/Meetings/tcm40.xml 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
[http://sourceforge.net/tracker2/?func=detail&aid=2411994&group_id=106328&atid=644065 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 [http://www.esf.org/activities/exploratory-workshops.html]
* SIGs
** TEI in library SIG - TEI Tite status
** New SIG: Scientific bibliographies [http://www.tei-c.org/Activities/Council/Working/tcw16.xml]
** Report: TEI Manuscript[http://www.tei-c.org/Activities/SIG/Manuscript/mssigr03.pdf]
* Misc.
** Necessary work on www.tei-c.org (further rationalization of structure,
etc.)
** In particular, status of TEI vault
http://www.tei-c.org.uk/Vault/Vault-GL.html (LB)

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

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

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--[[User:Romary|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)

== 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 [http://lists.village.virginia.edu/pipermail/tei-council/2008/010041.html Quoting a TEI Object] from September 2008. DS has created a new wiki page for discussing [[Council:stable references|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.

== Misc. ==
For general information concerning the council see [[TEI-Council-FAQ]] page and [[:Category: Council|category reserved for use by TEI Council]]...

[[Category:Council]]

Council

2010-02-09T16:42:47Z

Romary: /* Telko October 2009 */

Council

2009-10-13T13:45:41Z

Romary: /* Agenda */

== 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

=== Agenda ===
* 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 ===
[https://listes.cru.fr/wiki/tei-res/public/tei_council_2009_a_lyon Meeting in Lyon]
Available abstracts under: [https://listes.cru.fr/wiki/tei-res/prive/reunioncouncilavril09]

=== Draft Agenda ===
[http://www.tei-c.org/Activities/Council/Meetings/tcm40.xml 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
[http://sourceforge.net/tracker2/?func=detail&aid=2411994&group_id=106328&atid=644065 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 [http://www.esf.org/activities/exploratory-workshops.html]
* SIGs
** TEI in library SIG - TEI Tite status
** New SIG: Scientific bibliographies [http://www.tei-c.org/Activities/Council/Working/tcw16.xml]
** Report: TEI Manuscript[http://www.tei-c.org/Activities/SIG/Manuscript/mssigr03.pdf]
* Misc.
** Necessary work on www.tei-c.org (further rationalization of structure,
etc.)
** In particular, status of TEI vault
http://www.tei-c.org.uk/Vault/Vault-GL.html (LB)

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

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

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--[[User:Romary|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)

== 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 [http://lists.village.virginia.edu/pipermail/tei-council/2008/010041.html Quoting a TEI Object] from September 2008. DS has created a new wiki page for discussing [[Council:stable references|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.

== Misc. ==
For general information concerning the council see [[TEI-Council-FAQ]] page and [[:Category: Council|category reserved for use by TEI Council]]...

[[Category:Council]]

Council

2009-10-13T13:45:06Z

Romary: /* Agenda */

== 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

=== Agenda ===
* SF
* reworking the generic TEI-to-HTML stylesheets
* HTML5
* valList and content

== Face to face meeting - Lyon 1-3 April 2009 ==
=== Local organisation - programm of the seminar ===
[https://listes.cru.fr/wiki/tei-res/public/tei_council_2009_a_lyon Meeting in Lyon]
Available abstracts under: [https://listes.cru.fr/wiki/tei-res/prive/reunioncouncilavril09]

=== Draft Agenda ===
[http://www.tei-c.org/Activities/Council/Meetings/tcm40.xml 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
[http://sourceforge.net/tracker2/?func=detail&aid=2411994&group_id=106328&atid=644065 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 [http://www.esf.org/activities/exploratory-workshops.html]
* SIGs
** TEI in library SIG - TEI Tite status
** New SIG: Scientific bibliographies [http://www.tei-c.org/Activities/Council/Working/tcw16.xml]
** Report: TEI Manuscript[http://www.tei-c.org/Activities/SIG/Manuscript/mssigr03.pdf]
* Misc.
** Necessary work on www.tei-c.org (further rationalization of structure,
etc.)
** In particular, status of TEI vault
http://www.tei-c.org.uk/Vault/Vault-GL.html (LB)

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

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

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--[[User:Romary|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)

== 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 [http://lists.village.virginia.edu/pipermail/tei-council/2008/010041.html Quoting a TEI Object] from September 2008. DS has created a new wiki page for discussing [[Council:stable references|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.

== Misc. ==
For general information concerning the council see [[TEI-Council-FAQ]] page and [[:Category: Council|category reserved for use by TEI Council]]...

[[Category:Council]]

Council

2009-10-13T13:44:33Z

Romary: /* Connexion details */

== 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

=== Agenda ===
* FS
* reworking the generic TEI-to-HTML stylesheets
* HTML5
* valList and content

== Face to face meeting - Lyon 1-3 April 2009 ==
=== Local organisation - programm of the seminar ===
[https://listes.cru.fr/wiki/tei-res/public/tei_council_2009_a_lyon Meeting in Lyon]
Available abstracts under: [https://listes.cru.fr/wiki/tei-res/prive/reunioncouncilavril09]

=== Draft Agenda ===
[http://www.tei-c.org/Activities/Council/Meetings/tcm40.xml 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
[http://sourceforge.net/tracker2/?func=detail&aid=2411994&group_id=106328&atid=644065 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 [http://www.esf.org/activities/exploratory-workshops.html]
* SIGs
** TEI in library SIG - TEI Tite status
** New SIG: Scientific bibliographies [http://www.tei-c.org/Activities/Council/Working/tcw16.xml]
** Report: TEI Manuscript[http://www.tei-c.org/Activities/SIG/Manuscript/mssigr03.pdf]
* Misc.
** Necessary work on www.tei-c.org (further rationalization of structure,
etc.)
** In particular, status of TEI vault
http://www.tei-c.org.uk/Vault/Vault-GL.html (LB)

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

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

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--[[User:Romary|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)

== 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 [http://lists.village.virginia.edu/pipermail/tei-council/2008/010041.html Quoting a TEI Object] from September 2008. DS has created a new wiki page for discussing [[Council:stable references|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.

== Misc. ==
For general information concerning the council see [[TEI-Council-FAQ]] page and [[:Category: Council|category reserved for use by TEI Council]]...

[[Category:Council]]

FS2Latex.xsl

2009-09-18T10:28:13Z

Romary: New page: Test

Test

Council

2009-09-15T08:37:50Z

Romary: /* Agenda */

== Telko October 2009 ==
=== Connexion details ===
=== Agenda ===
* FS
* reworking the generic TEI-to-HTML stylesheets
* HTML5
* valList and content

== Face to face meeting - Lyon 1-3 April 2009 ==
=== Local organisation - programm of the seminar ===
[https://listes.cru.fr/wiki/tei-res/public/tei_council_2009_a_lyon Meeting in Lyon]
Available abstracts under: [https://listes.cru.fr/wiki/tei-res/prive/reunioncouncilavril09]

=== Draft Agenda ===
[http://www.tei-c.org/Activities/Council/Meetings/tcm40.xml 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
[http://sourceforge.net/tracker2/?func=detail&aid=2411994&group_id=106328&atid=644065 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 [http://www.esf.org/activities/exploratory-workshops.html]
* SIGs
** TEI in library SIG - TEI Tite status
** New SIG: Scientific bibliographies [http://www.tei-c.org/Activities/Council/Working/tcw16.xml]
** Report: TEI Manuscript[http://www.tei-c.org/Activities/SIG/Manuscript/mssigr03.pdf]
* Misc.
** Necessary work on www.tei-c.org (further rationalization of structure,
etc.)
** In particular, status of TEI vault
http://www.tei-c.org.uk/Vault/Vault-GL.html (LB)

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

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

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--[[User:Romary|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)

== 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 [http://lists.village.virginia.edu/pipermail/tei-council/2008/010041.html Quoting a TEI Object] from September 2008. DS has created a new wiki page for discussing [[Council:stable references|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.

== Misc. ==
For general information concerning the council see [[TEI-Council-FAQ]] page and [[:Category: Council|category reserved for use by TEI Council]]...

[[Category:Council]]

Council

2009-09-15T08:11:56Z

Romary: /* Agenda */

== Telko October 2009 ==
=== Connexion details ===
=== Agenda ===
* FS
* reworking the generic TEI-to-HTML stylesheets
* HTML5

== Face to face meeting - Lyon 1-3 April 2009 ==
=== Local organisation - programm of the seminar ===
[https://listes.cru.fr/wiki/tei-res/public/tei_council_2009_a_lyon Meeting in Lyon]
Available abstracts under: [https://listes.cru.fr/wiki/tei-res/prive/reunioncouncilavril09]

=== Draft Agenda ===
[http://www.tei-c.org/Activities/Council/Meetings/tcm40.xml 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
[http://sourceforge.net/tracker2/?func=detail&aid=2411994&group_id=106328&atid=644065 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 [http://www.esf.org/activities/exploratory-workshops.html]
* SIGs
** TEI in library SIG - TEI Tite status
** New SIG: Scientific bibliographies [http://www.tei-c.org/Activities/Council/Working/tcw16.xml]
** Report: TEI Manuscript[http://www.tei-c.org/Activities/SIG/Manuscript/mssigr03.pdf]
* Misc.
** Necessary work on www.tei-c.org (further rationalization of structure,
etc.)
** In particular, status of TEI vault
http://www.tei-c.org.uk/Vault/Vault-GL.html (LB)

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

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

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--[[User:Romary|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)

== 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 [http://lists.village.virginia.edu/pipermail/tei-council/2008/010041.html Quoting a TEI Object] from September 2008. DS has created a new wiki page for discussing [[Council:stable references|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.

== Misc. ==
For general information concerning the council see [[TEI-Council-FAQ]] page and [[:Category: Council|category reserved for use by TEI Council]]...

[[Category:Council]]

Council

2009-09-15T08:09:35Z

Romary: /* Face to face meeting - Lyon 1-3 April 2009 */

== Telko October 2009 ==
=== Connexion details ===
=== Agenda ===
* reworking the generic TEI-to-HTML stylesheets
== Face to face meeting - Lyon 1-3 April 2009 ==
=== Local organisation - programm of the seminar ===
[https://listes.cru.fr/wiki/tei-res/public/tei_council_2009_a_lyon Meeting in Lyon]
Available abstracts under: [https://listes.cru.fr/wiki/tei-res/prive/reunioncouncilavril09]

=== Draft Agenda ===
[http://www.tei-c.org/Activities/Council/Meetings/tcm40.xml 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
[http://sourceforge.net/tracker2/?func=detail&aid=2411994&group_id=106328&atid=644065 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 [http://www.esf.org/activities/exploratory-workshops.html]
* SIGs
** TEI in library SIG - TEI Tite status
** New SIG: Scientific bibliographies [http://www.tei-c.org/Activities/Council/Working/tcw16.xml]
** Report: TEI Manuscript[http://www.tei-c.org/Activities/SIG/Manuscript/mssigr03.pdf]
* Misc.
** Necessary work on www.tei-c.org (further rationalization of structure,
etc.)
** In particular, status of TEI vault
http://www.tei-c.org.uk/Vault/Vault-GL.html (LB)

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

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

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--[[User:Romary|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)

== 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 [http://lists.village.virginia.edu/pipermail/tei-council/2008/010041.html Quoting a TEI Object] from September 2008. DS has created a new wiki page for discussing [[Council:stable references|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.

== Misc. ==
For general information concerning the council see [[TEI-Council-FAQ]] page and [[:Category: Council|category reserved for use by TEI Council]]...

[[Category:Council]]

TEI for ISO

2009-06-02T13:49:56Z

Romary: /* Linking to ISO cat */

= Using the TEI for Editing ISO documents =

== Basic principles ==
Most of the necessary documentation for using the giudelines in specific contexts can be found under: [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/USE.html].

Looking between the lines at [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/USE.html#STPE], one can also get advice as to how to integrate a TEI component within a third party DTD or schema.

=== Terms and definition ===

The term and difinition section should be represented as a list of items:

<div n="3" type="termsAndDefinitions">
<head>Terms and definitions</head>
<list type="termlist">
<item/>
</list>
</div>

Each item should have the following structure:
<item xml:id="stateOfTheArt" n="3.13">
<term>state of the art</term>
<gloss>developed stage of technical capability at a given time as regards
products, processes and services, based on the relevant consolidated
findings of science, technology and experience</gloss>
<ref>ISO/IEC Guide 2:2004, definition 1.4</ref>
</item>

Abbreviation should be represented by means of an <abbr> following the corresponding <term>
Additional terms for the same concepts should be represented as <term>'s following the main entry.

== Using TEI modules in ISO specification (and others...) ==

=== Feature structures ===

The relaxNg schema for representing feature structures is available under [http://www.tei-c.org/release/xml/tei/schema/relaxng/iso-fs.rng].

This can be generated directly by means of the following ODD declaration:
<schemaSpec ident="testjustfs" start="">
<moduleRef key="tei"/>
<moduleRef key="iso-fs"/>
</schemaSpec>

== Using Vesta to compile ISO document ==

=== Bugs and feature requests ===

* figures in docx outputs do not appear
* xml tags within egXML do not appear in the HTML output
* generating anchors

== Linking to ISO cat ==

List of references to data categories as [http://www.isocat.org/ ISOCat] entries at the end of an ISO standards are represented along a pattern close to that of terminological entries:

<item xml:id="DCn" dcr:datcat="http://www.isocat.org/datcat/ISO-DC-n">
<term>abbreviation</term>
<gloss>Designation formed by omitting words or letters from a longer form
and refering to the same concept.</gloss>
</item>

The dcr prefix should be associated with the name space: http://www.isocat.org/ns/dcr

Work is ongoing to provide a TEI export to ISOCat that would allow one to embed a DCS (Data Category Selection) expressed as a list of items automatically.

http://www.isocat.org/12620/schemas/DCIF.html

http://www.isocat.org/rest/help.html#dcs

TEI for ISO

2009-06-02T13:38:19Z

Romary: /* Terms and definition */

TEI for ISO

2009-06-02T13:37:52Z

Romary: /* Basic principles */

= Using the TEI for Editing ISO documents =

== Basic principles ==
Most of the necessary documentation for using the giudelines in specific contexts can be found under: [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/USE.html].

Looking between the lines at [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/USE.html#STPE], one can also get advice as to how to integrate a TEI component within a third party DTD or schema.

=== Terms and definition ===

The term and difinition section should be represented as a list of items:

<div n="3" type="termsAndDefinitions">
<head>Terms and definitions</head>
<list type="termlist">
<item/>
</list>
</div>

Each item should have the following structure:
<item xml:id="stateOfTheArt" n="3.13">
<term>state of the art</term>
<gloss>developed stage of technical capability
at a given time as regards
products, processes and services, based on the relevant consolidated
findings of science, technology and experience</gloss>
<ref>ISO/IEC Guide 2:2004, definition 1.4</ref>
</item>

Abbreviation should be represented by means of an <abbr> following the corresponding <term>
Additional terms for the same concepts should be represented as <term>'s following the main entry.

== Using TEI modules in ISO specification (and others...) ==

=== Feature structures ===

The relaxNg schema for representing feature structures is available under [http://www.tei-c.org/release/xml/tei/schema/relaxng/iso-fs.rng].

This can be generated directly by means of the following ODD declaration:
<schemaSpec ident="testjustfs" start="">
<moduleRef key="tei"/>
<moduleRef key="iso-fs"/>
</schemaSpec>

== Using Vesta to compile ISO document ==

=== Bugs and feature requests ===

* figures in docx outputs do not appear
* xml tags within egXML do not appear in the HTML output
* generating anchors

== Linking to ISO cat ==

TEI for ISO

2009-06-02T13:32:56Z

Romary: /* Using Vesta to compile ISO document */

TEI for ISO

2009-06-02T13:30:43Z

Romary: /* Using the TEI for Editing ISO documents */

TEI for ISO

2009-06-02T13:19:37Z

Romary: /* Basic principles */