Re: advantages of TEI

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 ,[email protected]
CC:

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... :-)

Cheers,

   P.

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: [email protected]
> CC:
>
> A quick question to all: where in the TEI wiki structure would you
> imagine this set of links?
>
> @Paul: thanks for sharing! :-)
>
> Best,
>
>    Piotr
>
> 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
>> Burkhart's http://marjorie.burghart.online.fr/?q=en/content/tei-critical-apparatus-cheatsheet
>>
>> Magdalena
>>
>> On 2 November 2016 at 13:18, Paul Broyles <[email protected]
>> <mailto:[email protected]>> wrote:
>>
>>     Eduard,
>>
>>     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):
>>     http://www.newtonproject.sussex.ac.uk/resources/pdfs/techspec.pdf
>>     <http://www.newtonproject.sussex.ac.uk/resources/pdfs/techspec.pdf>
>>     http://www.cdlib.org/groups/stwg/docs/MS_BPG.pdf
>>     <http://www.cdlib.org/groups/stwg/docs/MS_BPG.pdf>
>>     http://www.whitmanarchive.org/mediawiki/index.php/Whitman_Encoding_Guidelines
>>     <http://www.whitmanarchive.org/mediawiki/index.php/Whitman_Encoding_Guidelines>
>>     http://piers.iath.virginia.edu/resources/transcriptionalProtocols.html
>>     <http://piers.iath.virginia.edu/resources/transcriptionalProtocols.html>
>>
>>     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
>>     Introduction."
>>
>>     Paul
>>
>>     On Wed, Nov 2, 2016 at 7:56 AM Eduard Drenth
>>     <[email protected] <mailto:[email protected]>> 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 http://www.tei-c.org/oxgarage/ shows
>>         minimal, disappointing results.
>>
>>
>>         I did not yet try https://github.com/TEIC/Stylesheets
>>         <https://github.com/TEIC/Stylesheets>, 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
>>
>>
>>         [email protected] <mailto:[email protected]>
>>
>>
>>         Doelestrjitte 8
>>
>>         8911 DX  Ljouwert
>>
>>         +31 58 213 14 14
>>
>>         chat: [email protected] <mailto:[email protected]>
>>
>>     --
>>     Paul A. Broyles, Ph.D.
>>     CLIR Postdoctoral Fellow in Data Curation for Medieval Studies
>>     North Carolina State University
>>     [email protected] <mailto:[email protected]>
>>
>>     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.
>>
>>