Back in the day., when the tei "projects" page was first created, it was a web form which projects could use to update their own descriptions, the thinking being that they would be best placed to document their own activities, and that it wasn't the TEI's job to collect, still less to curate, their activities. So while I totally agree that that list of links to project manuals is a very useful resource, and that it would be desirable to see it maintained and expanded (I think I even suggested we should somehow try to make an ODD library somewhere) I remain cautious of making this into a new TEI job, except insofaras we are all "the TEI" of course.

May I alsoi say that I am rather unimpressed with the current state of the TEI Wiki?  It's full of dead links and unfulfilled promises, and there doesn't seem to be any mechanism for improving it.

From: TEI (Text Encoding Initiative) public discussion list [[log in to unmask]] on behalf of Elisa Beshero-Bondar [[log in to unmask]]
Sent: 02 November 2016 17:39
To: [log in to unmask]
Subject: Re: advantages of TEI

Hi Piotr,
That page badly needs to be updated, too, and by each of the project maintainers--I keep forgetting to update the links to my projects there!

We've been talking in Council and with Kevin Hawkins (who's working on a new incarnation of the TEI website) that we really should have a page that guides project designers with sample ODD documentations geared to specific kinds of material (e.g. CBML, an ODD developed for projects that digitally model comic books, and other ODD customizations that seem useful starting points ). Helping people to read and review project customizations would be the goal. Would a page featuring interesting and useful ODD customizations be an improvement?


On Wed, Nov 2, 2016 at 1:26 PM, Piotr Bański <[log in to unmask]<mailto:[log in to unmask]>> wrote:
We're talking about this page:

and the sub-thread began with a bunch of links to project-level guidelines. You're not going to find these links on any of the subpages of Projects/

So the quick thought was: someone has done the tough job of looking through those projects and finding their local guidelines. It might (maybe) make sense to keep the results somewhere in a dynamic setting, where it can either grow into an even more useful list or.. not grow, and in the latter case no one is going to cry about that. The Projects/ page, useful for PR purposes perhaps, is not very useful as a quick source of local guidelines. (And note that I abstract away from whether these local guidelines are good/useful/whathaveyou. That's another thing, but whether we end up classifying them as useful or not, and maybe even noticing valuable or unwanted tendencies in preparing local guidelines, it's rather good to _have_ those guidelines at a distance of a single click).

But I'm not sure where to put them at a minimal time investment on my part, to make them maximally useful to others. Hence my initial question.



On 02/11/16 17:34, Lou Burnard wrote:
You prefer a single page with 80 links you have to clicketty click to
check if they're any use to you? Chain son gout...

Sent from my Honor Mobile

-------- Original Message --------
Subject: Re: advantages of TEI
From: Piotr Bański
To: Lou Burnard ,[log in to unmask]<mailto:[log in to unmask]>

Hi Lou,

Of course I know the page, and of course I don't think it's very useful
for this kind of listing. Clickety-click through 80 sub-pages, not me... :-)



On 02/11/16 14:39, Lou Burnard wrote:
There is a tei projects page on the website which is where I would look
for this kind of information.

Sent from my Honor Mobile

-------- Original Message --------
Subject: Re: advantages of TEI
From: Piotr Bański
To: [log in to unmask]<mailto:[log in to unmask]>

A quick question to all: where in the TEI wiki structure would you
imagine this set of links?

@Paul: thanks for sharing! :-)



On 02/11/16 14:33, Magdalena Turska wrote:
Following on Paul's list, such project specific policies could be even
called 'cheatsheets' as in Marjorie


On 2 November 2016 at 13:18, Paul Broyles <[log in to unmask]<mailto:[log in to unmask]>
<mailto:[log in to unmask]<mailto:[log in to unmask]>>> wrote:


    Regarding the question of how flexibility and freedom complicate
    development, many projects develop internal encoding guidelines to
    provide consistency among their texts. Thus if you're developing a
    display system for the output of one particular project, you have a
    much more limited set of possibilities to aim for.

    These documents can also be useful to provide to encoders who are
    relative TEI novices, as they can help explain how TEI encoding
    works in a more beginner-friendly way than the official documentation.

    Here are a handful of examples I have handy and have found useful
    (the last is from a project I'm working on, though I had no hand in
    the guidelines):

    There are many more examples out there, though unfortunately they
    can be hard to search for as they go under varied names, from
    "Transcriptional Protocols" to "Encoding Guidelines" to "Technical


    On Wed, Nov 2, 2016 at 7:56 AM Eduard Drenth
    <[log in to unmask]<mailto:[log in to unmask]> <mailto:[log in to unmask]<mailto:[log in to unmask]>>> wrote:

        Dear all,

        At the moment we are converting some 8000 corpora (runes, old,
        mid and new frisian, dialects) at the fryske akademy to TEI.

        By adopting an international standard we hope to boost doing
        research on top of these data. *Related to this I am interested
        in experiences with:*

        1) doing research on TEI material

        2) disclosure and publication (i.g. web) of TEI material

        Experiments with oxGarage shows
        minimal, disappointing results.

        I did not yet try
        <>, perhaps this offers
        better results.

        *I wonder how much effort / development (i.a. xslt, xquery) the
        two aspects (publicaton and doing research) will take.*

        TEI offers flexibility and freedom (i.g. <span type="lemma"
        target="w1 w2"> instead of <lemma target="w1 w2">) that
        complicates tool development. How big of a problem is this?

        Eduard Drenth, Software Architekt

        [log in to unmask]<mailto:[log in to unmask]> <mailto:[log in to unmask]<mailto:[log in to unmask]>>

        Doelestrjitte 8

        8911 DX  Ljouwert

        +31 58 213 14 14<tel:%2B31%2058%20213%2014%2014>

        chat: [log in to unmask]<mailto:[log in to unmask]> <mailto:[log in to unmask]<mailto:[log in to unmask]>>

    Paul A. Broyles, Ph.D.
    CLIR Postdoctoral Fellow in Data Curation for Medieval Studies
    North Carolina State University
    [log in to unmask]<mailto:[log in to unmask]> <mailto:[log in to unmask]<mailto:[log in to unmask]>>

    All electronic mail messages in connection with State business which
    are sent to or received by this account are subject to the NC Public
    Records Law and may be disclosed to third parties.

Elisa Beshero-Bondar, PhD
Director, Center for the Digital Text | Associate Professor of English
University of Pittsburgh at Greensburg | Humanities Division
150 Finoli Drive
Greensburg, PA  15601  USA
E-mail: [log in to unmask]<mailto:[log in to unmask]>
Development site:<>