[tei-council] maintenance of Tite
daniel.odonnell at uleth.ca
Tue Aug 10 01:02:37 EDT 2010
I agree 100%. Let's get this under control.
Daniel Paul O'Donnell,
Professor of English
University of Lethbridge
>From my cell phone.
Subject: Re: [tei-council] maintenance of Tite
From: Laurent Romary <laurent.romary at inria.fr>
Date: 2010/08/09 22:54
In any case, we should tend towards a situation where:
- the council maintains the schema like any other official TEI
- we need to secure that when a change impacts on the AcessTEI program
Apex is in the loop to be informed
We should not designed an adhoc maintenance system to preserve the
simplicity of our processes.
Le 10 août 10 à 01:14, O'Donnell, Dan a écrit :
> I agree that it isn't at a satisfactory final state. We've benefited a
> lot from the development as a forerunner for exploring how we might
> develop customisations like this (and our discussions about the
> work is a result of that to a certain extent), but in the absence of
> established process we're of course having to feel our way forward.
> not quite sure the best way of getting this into the ideal
> with the council. I don't think it's been a lack of will.
> I have a call with Apex later this week, I'll ask them about the
> On 10-08-09 05:10 PM, Sebastian Rahtz wrote:
>> On 9 Aug 2010, at 21:29, "O'Donnell,
>> Dan"<daniel.odonnell at uleth.ca> wrote:
>>> Good question. The Tite experience has prompted a number of very
>>> issues and experiences including the need to have specifically
>>> releases and the issue about positively or negatively defining the
>>> inclusion and exclusion of elements.
>> Indeed. And so Tite needs to be revised to use these facilities.
>>> My understanding, cc'd to Perry here to check that I've got this
>>> is that Apex are using a specific schema generated from the
>>> current odd
>> I was surprised to see no mention of the schema at Accesstei. When
>> was this schema generated?
>>> and that the TEI can update and change the official ODD as we go
>>> on our regular update schedules.
>> By what criteria do we change it?
>>> Obviously we want to avoid breaking
>>> backwards compatibility, but Perry also did some custom examples and
>>> things, I think.
>> Which we don't have chez the TEIC alongside the Odd? This all seems
>> less than satisfactory.
> Daniel Paul O'Donnell
> Professor of English
> University of Lethbridge
> Chair and CEO, Text Encoding Initiative (http://www.tei-c.org/)
> Co-Chair, Digital Initiatives Advisory Board, Medieval Academy of
> President-elect (English), Society for Digital Humanities/Société
> pour l'étude des médias interactifs (http://sdh-semi.org/)
> Founding Director (2003-2009), Digital Medievalist Project (http://www.digitalmedievalist.org/
> Vox: +1 403 329-2377
> Fax: +1 403 382-7191 (non-confidential)
> Home Page: http://people.uleth.ca/~daniel.odonnell/
> tei-council mailing list
> tei-council at lists.village.Virginia.EDU
INRIA & HUB-IDSL
laurent.romary at inria.fr
More information about the tei-council