Re: TEI Next

Hi James,

Le 26/09/2016 à 14:05, James Cummings a écrit :
> On 26/09/16 13:41, Roberto Rosselli Del Turco wrote:
>
>>  * JSON is popular because it solves problems for tool developers: 
>> how about defining a tentative TEI to JSON "conversion 
>> recommendation" to help tool developers? we had to start from scratch 
>> with EVT 2.0, and surely our approach is faulty in some way, also it 
>> is different from everybody else's TEI > JSON conversion (hope I make 
>> sense here ;)
>
> I agree. We certainly could improve the nascent TEI to JSON 
> Stylesheets that already exist.  Do feel free to submit patches on 
> github!  But yes, it is hard since so many people might want very 
> different forms of JSON for their uses.
To prevent various JSONs to become TEI processing cul-de-sac, a solution 
might be to develop JSON > TEI in parallel with TEI > JSON (in the 
spirit of DOCX > TEI developped in parallel with TEI > DOCX).
>> - speaking of tools, I agree that a good, TEI-ready and free/open 
>> source XML editor is beyond the TEI responsibilities, but surely this 
>> is a need many people feel even if we all use Oxygen for professional 
>> work;
>
> I agree that this would be nice, and would happily beta test any such 
> editors people wish to create.  From the TEI Council perspective I 
> think it has enough on its place (e.g. with the passing of SPQR and 
> the departure from Council at the end of this year of Lou Burnard) 
> just keeping up with feature requests, bugs, and various bits of 
> software.
What is wrong with TextGrid XML Editor for this purpose? 
(https://wiki.de.dariah.eu/display/TextGrid/Source+View)

Best,
Serge

-- 
Dr. Serge Heiden, [email protected], http://textometrie.ens-lyon.fr
ENS de Lyon/CNRS - IHRIM UMR5317
15, parvis René Descartes 69342 Lyon BP7000 Cedex, tél. +33(0)622003883