https://wiki.tei-c.org/api.php?action=feedcontributions&feedformat=atom&user=ElenapTEIWiki - User contributions [en]2026-04-19T07:52:21ZUser contributionsMediaWiki 1.32.0https://wiki.tei-c.org/index.php?title=GeneticEditionsWorkshopParis&diff=6421GeneticEditionsWorkshopParis2009-05-13T10:35:31Z<p>Elenap: /* Thursday 14 May 2009 */</p>
<hr />
<div>[[Category:Genetic Editions]]<br />
=Workshop Genetic Editions in a Digital Framework=<br />
==Agenda==<br />
<br />
===Thursday 14 May 2009===<br />
<br />
Venue: Salle des résistants (45, rue d'Ulm)<br />
<br />
14:00 Welcome<br />
<br />
14:10 Introduction<br />
<br />
14:30 "Case Studies I" (presentations and discussion)<br />
<br />
Chair: Jean-Louis Lebrave<br />
<br />
* Ken Price and Brett Barney, The Making, Remaking, and Unmaking of Walt Whitman's "The Sleepers"<br />
* Daniel Ferrer, Complex genetic relationships<br />
* Anne Bohnenkamp, Goethe's 'Faust'. Towards reconstruction and presentation of the drama's genesis<br />
* Wolfgang Lukas, Problèmes de genèse et de leur représentation dans l'édition historique et critique de la correspondance de C. F. Meyer<br />
<br />
16:00 Coffee Break<br />
<br />
16:30 "Case Studies II" (presentations and discussion)<br />
<br />
Chair: Daniel Ferrer<br />
<br />
* Jean-Louis Lebrave, Three emblematic cases for a digital edition of genetic data<br />
* John Bryant, Coding the Revision Sequence<br />
* Dirk Van Hulle, Segment shifts in modern manuscripts: That Time, in Beckett’s hand<br />
* Kathryn Sutherland, Is there a case for a Genetic Edition of Jane Austen’s Manuscripts?<br />
18:00 Summary<br />
<br />
===Friday 15 May 2009===<br />
<br />
Venue: Amphithéâtre Jules-Ferry (29, rue d'Ulm)<br />
<br />
09:00 "Concepts" (presentations and discussion)<br />
<br />
Chair: Laurent Romary<br />
<br />
* Jean-Daniel Fekete and Aurèle Crasson, From Corpus to Regions: Multiscale Representation of Draft Manuscripts<br />
* Axel Gellhaus, Die Entstehung von literarischen Konzepten und die Probleme ihrer editorischen Darstellung: Stadien der Verräumlichung und Stadien der Linearisierung<br />
* Hans Walter Gabler, TEXT GENETICS – GENETIC EDITING – GENETIC EDITIONS<br />
* Claus Huitfeldt, Grammar, Space and Time<br />
<br />
10:30 The TEI task force "Genetic Editions" (presentation)<br />
<br />
11:15 Coffee Break<br />
<br />
11:30 Modelling the Encoding (working groups)<br />
<br />
13:15 Lunch Break<br />
<br />
14:00 Modelling the Encoding (presentations and discussion)<br />
<br />
15:00 Wrap-Up, Summary, Outlook<br />
<br />
15:30 Closure<br />
<br />
==Organisation==<br />
* Elena Pierazzo<br />
* Fotis Jannidis<br />
* Paolo D'Iorio<br />
* [[User:Malte|Malte Rehbein]]<br />
<br />
==Sponsors==<br />
<br />
ALLC - Association for Literary and Linguistic Computing<br />
<br />
ACH - Association for Computing in the Humanities<br />
<br />
Moore Institute - University of Galway <br />
<br />
TEI - Text Encoding Initiative<br />
<br />
Fotis Jannidis - University of Würzburg<br />
<br />
==Venue==<br />
<br />
Institut des Textes & Manuscript Modernes (ITEM)<br />
<br />
45 Rue D'Ulm resp. 29 Rue D'Ulm<br />
<br />
Paris<br />
<br />
==Accomodation==<br />
<br />
Please make your own arrangements. We suggest to choose one of the following hotels:<br />
<br />
<br />
<br />
Hotel France quartier latin<br />
<br />
108 rue Monge<br />
<br />
01 47 07 19 04<br />
<br />
http://www.hotelfrancequartierlatin.com/<br />
<br />
info@parishoteldefrance.com<br />
<br />
<br />
<br />
Hôtel des 3 Collèges,<br />
<br />
16, rue Cujas<br />
<br />
75005 Paris<br />
<br />
http://www.3colleges.com/<br />
<br />
<br />
<br />
Hôtel du Bresil<br />
<br />
10 Rue Le Goff<br />
<br />
75005 Paris<br />
<br />
Tél : 33(0)1 43 54 76 11<br />
<br />
Fax : 33(0)1 46 33 45 78<br />
<br />
http://www.bresil-paris-hotel.com/<br />
<br />
<br />
<br />
Hotel de la Sorbonne<br />
<br />
6 rue Victor Cousin<br />
<br />
01 43 54 58 08<br />
<br />
http://www.hotelsorbonne.com/<br />
<br />
<br />
<br />
Hotel royal cardinal<br />
<br />
1 rue des écoles<br />
<br />
01 43 26 83 64<br />
<br />
http://www.paris-hotel-royal-cardinal.com<br />
<br />
<br />
<br />
Hotel Excelsior Latin<br />
<br />
20 rue Cujas - 75005 Paris<br />
<br />
Tél : +33(0)1 46 34 79 50<br />
<br />
Fax : +33(0)1 43 54 87 10<br />
<br />
E.mail : excelsior5@orange.fr<br />
<br />
<br />
<br />
Hotel Minerve<br />
<br />
13, rue des Ecoles<br />
<br />
75006 Paris, France<br />
<br />
0033 1 43 26 26 04<br />
<br />
http://www.hotel-paris-minerve.com<br />
<br />
<br />
<br />
Hôtel de Sully Saint Germain<br />
<br />
29 r Ecoles 75005 PARIS<br />
<br />
29 r Ecoles 75005 PARIS<br />
<br />
01 43 26 56 02<br />
<br />
<br />
<br />
Comfort hotel André latin<br />
<br />
50-52 rue Gay lussac<br />
<br />
01 43 54 56 19<br />
<br />
http://www.andre-latin-paris-hotel.com/</div>Elenaphttps://wiki.tei-c.org/index.php?title=Genetic_Editions&diff=6414Genetic Editions2009-05-11T13:16:13Z<p>Elenap: /* Documents */</p>
<hr />
<div>[[category:Genetic Editions]]<br />
At the Members Meeting in London in November, a panel focussing on the problem of genetic editions is planned.<br />
<br />
<br />
#[[Introduction to Genetic Editions | Introduction]]<br />
#[[Textual alterations]]<br />
#[[Time]]<br />
#[[Grouping changes]]<br />
#[[A coordinate system for relation of different witnesses]]<br />
#[[Justification and discussion of editorial decisions]]<br />
#[[Uncertainty]]<br />
#[[Examples]]<br />
<br />
<br />
== Documents ==<br />
<br />
* [http://staff.cch.kcl.ac.uk/~epierazzo/GeneticEditionDraft1.pdf Draft 1: 11-05-2009]<br />
** [[GeneticEditionDraf1Comments | Comments]]<br />
<br />
== Meetings ==<br />
<br />
Workshop "Genetic Editions in a Digital Framework", Paris, 14/15 May 2009 -> [[GeneticEditionsWorkshopParis|Programme]]<br />
<br />
Workshop during the TEI-meeting 2008 in London -> [[minutes London 2008]]<br />
<br />
Task Force meeting at Kings College London on 12./13. March 2009 -> [[minutes London 03-2009]]<br />
<br />
== Useful Resources ==<br />
* HyperNietsche<br />
** [http://www.hypernietzsche.org/doc/HNML/ HyperNietzsche Markup Language HNML], in [http://www.hypernietzsche.org/doc/HNML/HNML-engl.pdf English], and in [http://www.hypernietzsche.org/doc/HNML/HNML-de.pdf German]<br />
** Article on [http://computerphilologie.uni-muenchen.de/jg03/saller.html HNML]<br />
** Matteo D’Alfonso, Harald Saller: [http://www.germanistik.ch/publikation.php?id=Kodierung_und_Darstellung Kodierung und Darstellung von Schreibschichten in der elektronischen Edition des Druckmanuskripts zu Der Wanderer und sein Schatten]. In: Literatur und Literaturwissenschaften auf dem Weg zu den digitalen Medien - Eine Standortbestimmung, hg. v. Michael Stolz. Online veröffentlicht bei Gisi + Loop.<br />
* Genetic Markup Language (In French) [http://staff.cch.kcl.ac.uk/~epierazzo/GML-fr.pdf download it from here]<br />
* Multi-Version Document Format. See the related [http://multiversiondocs.blogspot.com/ blog] and the post [http://multiversiondocs.blogspot.com/2008/03/whats-multi-version-document.html What's a Multi-Version Document?].<br />
<br />
== Literature on genetic editions ==<br />
* Gabler, Hans Walter<br />
** "Das wissenschaftliche Edieren als Funktion der Dokumente." Published at: [http://computerphilologie.tu-darmstadt.de/jg06/gabler.html http://computerphilologie.tu-darmstadt.de/jg06/gabler.html]; and in: Jahrbuch für Computerphilologie 8 (2007), 55-62.<br />
** "The Primacy of the Document in Editing." Ecdotica 4 (2007), 197-207. [http://staff.cch.kcl.ac.uk/~epierazzo/Gabler%20Ecdotica%204.pdf download it from here]<br />
** "La prééminence du document dans l’édition." In: Françoise Leriche et Cécile Maynard (eds.), De l'hypertexte au manuscrit. L'apport et les limites du numérique pour l'édition et la valorisation de manuscrits littéraires modernes. (Recherches & Travaux, no. 72.) Grenoble: ELLUG, 2008, pp. 39-51.[http://staff.cch.kcl.ac.uk/~epierazzo/GABLER%20definitif.pdf download it from here]</div>Elenaphttps://wiki.tei-c.org/index.php?title=Genetic_Editions&diff=6413Genetic Editions2009-05-11T13:07:19Z<p>Elenap: </p>
<hr />
<div>[[category:Genetic Editions]]<br />
At the Members Meeting in London in November, a panel focussing on the problem of genetic editions is planned.<br />
<br />
<br />
#[[Introduction to Genetic Editions | Introduction]]<br />
#[[Textual alterations]]<br />
#[[Time]]<br />
#[[Grouping changes]]<br />
#[[A coordinate system for relation of different witnesses]]<br />
#[[Justification and discussion of editorial decisions]]<br />
#[[Uncertainty]]<br />
#[[Examples]]<br />
<br />
<br />
== Documents ==<br />
<br />
* [http://staff.cch.kcl.ac.uk/~epierazzo/GeneticEditionDraft1.pdf Draft 1: 11-05-2009]<br />
<br />
== Meetings ==<br />
<br />
Workshop "Genetic Editions in a Digital Framework", Paris, 14/15 May 2009 -> [[GeneticEditionsWorkshopParis|Programme]]<br />
<br />
Workshop during the TEI-meeting 2008 in London -> [[minutes London 2008]]<br />
<br />
Task Force meeting at Kings College London on 12./13. March 2009 -> [[minutes London 03-2009]]<br />
<br />
== Useful Resources ==<br />
* HyperNietsche<br />
** [http://www.hypernietzsche.org/doc/HNML/ HyperNietzsche Markup Language HNML], in [http://www.hypernietzsche.org/doc/HNML/HNML-engl.pdf English], and in [http://www.hypernietzsche.org/doc/HNML/HNML-de.pdf German]<br />
** Article on [http://computerphilologie.uni-muenchen.de/jg03/saller.html HNML]<br />
** Matteo D’Alfonso, Harald Saller: [http://www.germanistik.ch/publikation.php?id=Kodierung_und_Darstellung Kodierung und Darstellung von Schreibschichten in der elektronischen Edition des Druckmanuskripts zu Der Wanderer und sein Schatten]. In: Literatur und Literaturwissenschaften auf dem Weg zu den digitalen Medien - Eine Standortbestimmung, hg. v. Michael Stolz. Online veröffentlicht bei Gisi + Loop.<br />
* Genetic Markup Language (In French) [http://staff.cch.kcl.ac.uk/~epierazzo/GML-fr.pdf download it from here]<br />
* Multi-Version Document Format. See the related [http://multiversiondocs.blogspot.com/ blog] and the post [http://multiversiondocs.blogspot.com/2008/03/whats-multi-version-document.html What's a Multi-Version Document?].<br />
<br />
== Literature on genetic editions ==<br />
* Gabler, Hans Walter<br />
** "Das wissenschaftliche Edieren als Funktion der Dokumente." Published at: [http://computerphilologie.tu-darmstadt.de/jg06/gabler.html http://computerphilologie.tu-darmstadt.de/jg06/gabler.html]; and in: Jahrbuch für Computerphilologie 8 (2007), 55-62.<br />
** "The Primacy of the Document in Editing." Ecdotica 4 (2007), 197-207. [http://staff.cch.kcl.ac.uk/~epierazzo/Gabler%20Ecdotica%204.pdf download it from here]<br />
** "La prééminence du document dans l’édition." In: Françoise Leriche et Cécile Maynard (eds.), De l'hypertexte au manuscrit. L'apport et les limites du numérique pour l'édition et la valorisation de manuscrits littéraires modernes. (Recherches & Travaux, no. 72.) Grenoble: ELLUG, 2008, pp. 39-51.[http://staff.cch.kcl.ac.uk/~epierazzo/GABLER%20definitif.pdf download it from here]</div>Elenaphttps://wiki.tei-c.org/index.php?title=GeneticEditionsWorkshopParis&diff=6380GeneticEditionsWorkshopParis2009-05-08T16:48:34Z<p>Elenap: /* Sponsors */</p>
<hr />
<div>[[Category:Genetic Editions]]<br />
=Workshop Genetic Editions in a Digital Framework=<br />
==Agenda==<br />
<br />
===Thursday 14 May 2009===<br />
<br />
Venue: Salle des résistants (29, rue d'Ulm)<br />
<br />
14:00 Welcome<br />
<br />
14:10 Introduction<br />
<br />
14:30 "Case Studies I" (presentations and discussion)<br />
<br />
Chair: Jean-Louis Lebrave<br />
<br />
* Ken Price and Brett Barney, The Making, Remaking, and Unmaking of Walt Whitman's "The Sleepers"<br />
* Daniel Ferrer, Complex genetic relationships<br />
* Anne Bohnenkamp, Goethe's 'Faust'. Towards reconstruction and presentation of the drama's genesis<br />
* Wolfgang Lukas, Problèmes de genèse et de leur représentation dans l'édition historique et critique de la correspondance de C. F. Meyer<br />
<br />
16:00 Coffee Break<br />
<br />
16:30 "Case Studies II" (presentations and discussion)<br />
<br />
Chair: Daniel Ferrer<br />
<br />
* Jean-Louis Lebrave, Three emblematic cases for a digital edition of genetic data<br />
* John Bryant, Coding the Revision Sequence<br />
* Dirk Van Hulle, Segment shifts in modern manuscripts: That Time, in Beckett’s hand<br />
* Kathryn Sutherland, Is there a case for a Genetic Edition of Jane Austen’s Manuscripts?<br />
18:00 Summary<br />
<br />
===Friday 15 May 2009===<br />
<br />
Venue: Amphithéâtre Jules-Ferry (29, rue d'Ulm)<br />
<br />
09:00 "Concepts" (presentations and discussion)<br />
<br />
Chair: Laurent Romary<br />
<br />
* Jean-Daniel Fekete and Aurèle Crasson, From Corpus to Regions: Multiscale Representation of Draft Manuscripts<br />
* Axel Gellhaus, Die Entstehung von literarischen Konzepten und die Probleme ihrer editorischen Darstellung: Stadien der Verräumlichung und Stadien der Linearisierung<br />
* Hans Walter Gabler, TEXT GENETICS – GENETIC EDITING – GENETIC EDITIONS<br />
* Claus Huitfeldt, Grammar, Space and Time<br />
<br />
10:30 The TEI task force "Genetic Editions" (presentation)<br />
<br />
11:15 Coffee Break<br />
<br />
11:30 Modelling the Encoding (working groups)<br />
<br />
13:15 Lunch Break<br />
<br />
14:00 Modelling the Encoding (presentations and discussion)<br />
<br />
15:00 Wrap-Up, Summary, Outlook<br />
<br />
15:30 Closure<br />
<br />
==Organisation==<br />
* Elena Pierazzo<br />
* Fotis Jannidis<br />
* Paolo D'Iorio<br />
* [[User:Malte|Malte Rehbein]]<br />
<br />
==Sponsors==<br />
<br />
ALLC - Association for Literary and Linguistic Computing<br />
<br />
ACH - Association for Computing in the Humanities<br />
<br />
Moore Institute - University of Galway <br />
<br />
TEI - Text Encoding Initiative<br />
<br />
Fotis Jannidis - University of Würzburg<br />
<br />
==Venue==<br />
<br />
Institut des Textes & Manuscript Modernes (ITEM)<br />
<br />
45 Rue D'Ulm resp. 29 Rue D'Ulm<br />
<br />
Paris<br />
<br />
==Accomodation==<br />
<br />
Please make your own arrangements. We suggest to choose one of the following hotels:<br />
<br />
<br />
<br />
Hotel France quartier latin<br />
<br />
108 rue Monge<br />
<br />
01 47 07 19 04<br />
<br />
http://www.hotelfrancequartierlatin.com/<br />
<br />
info@parishoteldefrance.com<br />
<br />
<br />
<br />
Hôtel des 3 Collèges,<br />
<br />
16, rue Cujas<br />
<br />
75005 Paris<br />
<br />
http://www.3colleges.com/<br />
<br />
<br />
<br />
Hôtel du Bresil<br />
<br />
10 Rue Le Goff<br />
<br />
75005 Paris<br />
<br />
Tél : 33(0)1 43 54 76 11<br />
<br />
Fax : 33(0)1 46 33 45 78<br />
<br />
http://www.bresil-paris-hotel.com/<br />
<br />
<br />
<br />
Hotel de la Sorbonne<br />
<br />
6 rue Victor Cousin<br />
<br />
01 43 54 58 08<br />
<br />
http://www.hotelsorbonne.com/<br />
<br />
<br />
<br />
Hotel royal cardinal<br />
<br />
1 rue des écoles<br />
<br />
01 43 26 83 64<br />
<br />
http://www.paris-hotel-royal-cardinal.com<br />
<br />
<br />
<br />
Hotel Excelsior Latin<br />
<br />
20 rue Cujas - 75005 Paris<br />
<br />
Tél : +33(0)1 46 34 79 50<br />
<br />
Fax : +33(0)1 43 54 87 10<br />
<br />
E.mail : excelsior5@orange.fr<br />
<br />
<br />
<br />
Hotel Minerve<br />
<br />
13, rue des Ecoles<br />
<br />
75006 Paris, France<br />
<br />
0033 1 43 26 26 04<br />
<br />
http://www.hotel-paris-minerve.com<br />
<br />
<br />
<br />
Hôtel de Sully Saint Germain<br />
<br />
29 r Ecoles 75005 PARIS<br />
<br />
29 r Ecoles 75005 PARIS<br />
<br />
01 43 26 56 02<br />
<br />
<br />
<br />
Comfort hotel André latin<br />
<br />
50-52 rue Gay lussac<br />
<br />
01 43 54 56 19<br />
<br />
http://www.andre-latin-paris-hotel.com/</div>Elenaphttps://wiki.tei-c.org/index.php?title=GeneticEditionsWorkshopParis&diff=6379GeneticEditionsWorkshopParis2009-05-08T16:48:12Z<p>Elenap: </p>
<hr />
<div>[[Category:Genetic Editions]]<br />
=Workshop Genetic Editions in a Digital Framework=<br />
==Agenda==<br />
<br />
===Thursday 14 May 2009===<br />
<br />
Venue: Salle des résistants (29, rue d'Ulm)<br />
<br />
14:00 Welcome<br />
<br />
14:10 Introduction<br />
<br />
14:30 "Case Studies I" (presentations and discussion)<br />
<br />
Chair: Jean-Louis Lebrave<br />
<br />
* Ken Price and Brett Barney, The Making, Remaking, and Unmaking of Walt Whitman's "The Sleepers"<br />
* Daniel Ferrer, Complex genetic relationships<br />
* Anne Bohnenkamp, Goethe's 'Faust'. Towards reconstruction and presentation of the drama's genesis<br />
* Wolfgang Lukas, Problèmes de genèse et de leur représentation dans l'édition historique et critique de la correspondance de C. F. Meyer<br />
<br />
16:00 Coffee Break<br />
<br />
16:30 "Case Studies II" (presentations and discussion)<br />
<br />
Chair: Daniel Ferrer<br />
<br />
* Jean-Louis Lebrave, Three emblematic cases for a digital edition of genetic data<br />
* John Bryant, Coding the Revision Sequence<br />
* Dirk Van Hulle, Segment shifts in modern manuscripts: That Time, in Beckett’s hand<br />
* Kathryn Sutherland, Is there a case for a Genetic Edition of Jane Austen’s Manuscripts?<br />
18:00 Summary<br />
<br />
===Friday 15 May 2009===<br />
<br />
Venue: Amphithéâtre Jules-Ferry (29, rue d'Ulm)<br />
<br />
09:00 "Concepts" (presentations and discussion)<br />
<br />
Chair: Laurent Romary<br />
<br />
* Jean-Daniel Fekete and Aurèle Crasson, From Corpus to Regions: Multiscale Representation of Draft Manuscripts<br />
* Axel Gellhaus, Die Entstehung von literarischen Konzepten und die Probleme ihrer editorischen Darstellung: Stadien der Verräumlichung und Stadien der Linearisierung<br />
* Hans Walter Gabler, TEXT GENETICS – GENETIC EDITING – GENETIC EDITIONS<br />
* Claus Huitfeldt, Grammar, Space and Time<br />
<br />
10:30 The TEI task force "Genetic Editions" (presentation)<br />
<br />
11:15 Coffee Break<br />
<br />
11:30 Modelling the Encoding (working groups)<br />
<br />
13:15 Lunch Break<br />
<br />
14:00 Modelling the Encoding (presentations and discussion)<br />
<br />
15:00 Wrap-Up, Summary, Outlook<br />
<br />
15:30 Closure<br />
<br />
==Organisation==<br />
* Elena Pierazzo<br />
* Fotis Jannidis<br />
* Paolo D'Iorio<br />
* [[User:Malte|Malte Rehbein]]<br />
<br />
==Sponsors==<br />
<br />
ALLC - Association for Literary and Linguistic Computing<br />
ACH - Association for Computing in the Humanities<br />
Moore Institute - University of Galway <br />
TEI - Text Encoding Initiative<br />
Fotis Jannidis - University of Würzburg<br />
<br />
==Venue==<br />
<br />
Institut des Textes & Manuscript Modernes (ITEM)<br />
<br />
45 Rue D'Ulm resp. 29 Rue D'Ulm<br />
<br />
Paris<br />
<br />
==Accomodation==<br />
<br />
Please make your own arrangements. We suggest to choose one of the following hotels:<br />
<br />
<br />
<br />
Hotel France quartier latin<br />
<br />
108 rue Monge<br />
<br />
01 47 07 19 04<br />
<br />
http://www.hotelfrancequartierlatin.com/<br />
<br />
info@parishoteldefrance.com<br />
<br />
<br />
<br />
Hôtel des 3 Collèges,<br />
<br />
16, rue Cujas<br />
<br />
75005 Paris<br />
<br />
http://www.3colleges.com/<br />
<br />
<br />
<br />
Hôtel du Bresil<br />
<br />
10 Rue Le Goff<br />
<br />
75005 Paris<br />
<br />
Tél : 33(0)1 43 54 76 11<br />
<br />
Fax : 33(0)1 46 33 45 78<br />
<br />
http://www.bresil-paris-hotel.com/<br />
<br />
<br />
<br />
Hotel de la Sorbonne<br />
<br />
6 rue Victor Cousin<br />
<br />
01 43 54 58 08<br />
<br />
http://www.hotelsorbonne.com/<br />
<br />
<br />
<br />
Hotel royal cardinal<br />
<br />
1 rue des écoles<br />
<br />
01 43 26 83 64<br />
<br />
http://www.paris-hotel-royal-cardinal.com<br />
<br />
<br />
<br />
Hotel Excelsior Latin<br />
<br />
20 rue Cujas - 75005 Paris<br />
<br />
Tél : +33(0)1 46 34 79 50<br />
<br />
Fax : +33(0)1 43 54 87 10<br />
<br />
E.mail : excelsior5@orange.fr<br />
<br />
<br />
<br />
Hotel Minerve<br />
<br />
13, rue des Ecoles<br />
<br />
75006 Paris, France<br />
<br />
0033 1 43 26 26 04<br />
<br />
http://www.hotel-paris-minerve.com<br />
<br />
<br />
<br />
Hôtel de Sully Saint Germain<br />
<br />
29 r Ecoles 75005 PARIS<br />
<br />
29 r Ecoles 75005 PARIS<br />
<br />
01 43 26 56 02<br />
<br />
<br />
<br />
Comfort hotel André latin<br />
<br />
50-52 rue Gay lussac<br />
<br />
01 43 54 56 19<br />
<br />
http://www.andre-latin-paris-hotel.com/</div>Elenaphttps://wiki.tei-c.org/index.php?title=Alternatives&diff=5578Alternatives2009-03-19T15:48:12Z<p>Elenap: /* Alternatives */</p>
<hr />
<div>== Alternatives ==<br />
<br />
* Authors often record different alternatives for the same passage<br />
* the scope of the alternatives ranges from single word (or part) to blocks (see Vetter & McDonald 2003)<br />
* we need a mechanism able to cope with different dimensions of alternation, similar (if not the same) to http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-alt.html<br />
* respect the <alt/> element, we need also a system to declare the evidence of editorial/authorial choices. For instance in some cases we can say which alternative was preferred by the author because the text is underlined or has other functional marks (see again Vetter & McDonald 2003), or because in later draft we have evidence that one reading has been preferred <br />
* The proposal is therefore to create a new element or to add an attribute to <alt/> in order to link to a functional mark or an editorial discussion about a specific point.</div>Elenaphttps://wiki.tei-c.org/index.php?title=Alternatives&diff=5577Alternatives2009-03-19T15:47:22Z<p>Elenap: /* Alternatives */</p>
<hr />
<div>== Alternatives ==<br />
<br />
* Authors often record different alternatives for the same passage<br />
* the dimension of the alternatives ranges from the single word (or part) to blocks (see Vetter & McDonald 2003)<br />
* we need a mechanism able to cope with different level of alternation, similar (if not the same) to http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-alt.html<br />
* respect the <alt/> element, we need also a system to declare the evidence of editorial/authorial choices. For instance in some cases we can say which alternative was preferred by the author because the text is underlined or has other functional marks (see again Vetter & McDonald 2003), or because in later draft we have evidence that one reading has been preferred <br />
* The proposal is therefore to create a new element or to add an attribute to <alt/> in order to link to a functional mark or an editorial discussion about a specific point.</div>Elenaphttps://wiki.tei-c.org/index.php?title=Alternatives&diff=5576Alternatives2009-03-19T15:46:38Z<p>Elenap: /* Alternatives */</p>
<hr />
<div>== Alternatives ==<br />
<br />
* Authors often record different alternatives for the same passage<br />
* the dimension of the alternatives ranges from the single word (or part) to blocks (see Vetter & McDonald 2003)<br />
* we need a mechanism able to cope with different level of alternation, similar (if not the same) to http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-alt.html<br />
* respect the <alt/> element, we need also a system to declare the evidence of editorial/authorial choices. For instance in some cases we can say which alternative was preferred by the author because the text is underlined or has other functional marks (see again Vetter & McDonald 2003), or because in later draft we have evidence that one reading has been preferred <br />
* The proposal is therefore to create a new element or to add an attribute to <alt/> in order to link to a functional mark or an editorial discussion about a specific point.</div>Elenaphttps://wiki.tei-c.org/index.php?title=Alternatives&diff=5575Alternatives2009-03-19T15:41:24Z<p>Elenap: New page: == Alternatives == * Authors often record different alternatives for the same passage * the dimension of the alternatives ranges from the single word (or part) to blocks (see Vetter & McD...</p>
<hr />
<div>== Alternatives ==<br />
<br />
* Authors often record different alternatives for the same passage<br />
* the dimension of the alternatives ranges from the single word (or part) to blocks (see Vetter & McDonald 2003)<br />
*</div>Elenaphttps://wiki.tei-c.org/index.php?title=Minutes_London_03-2009&diff=5574Minutes London 03-20092009-03-19T15:34:46Z<p>Elenap: /* Specification tasks */</p>
<hr />
<div>''Present: Katrin Dennerlein, Paolo D'Iorio, Fotis Jannidis, Gregor Middell, Elena Pierazzo, Malte Rehbein, Moritz Wissenbach.''<br />
<br />
''Discussion led by Elena Pierazzo, minutes by Gregor Middell.''<br />
<br />
==Organization==<br />
<br />
===Technical infrastructure/ Workflow===<br />
<br />
* coordination takes place in this wiki<br />
* project has to be announced on the news bar at http://tei-c.org/<br />
* wiki will be reorganzied in 2 distinct parts: a public one (with announcements, draft specs …) and an internal one with information, that is less interesting to the general public<br />
* list of sponsors has to go on the wiki as well<br />
* ''Google Docs'' used for the (internal) specification process<br />
* draft versions of the specification are checked out as a PDF document and put on the wiki every week, so we can gather feedback<br />
<br />
===Conference in Paris===<br />
<br />
* ITEM provides up to 3 rooms for the conference; definitely 1 on both days, possibly 3 on the second<br />
* Paolo D'Iorio coordinates the room allocation with ITEM<br />
* we want to offer lunch at the conference (attendants shall ''confirm'' their participation upon registration)<br />
* SIG will invite speakers and organizers to a dinner as well<br />
* Paolo D'Iorio organizes hotel, dinner bookings, internet access, beamer<br />
* Malte Rehbein manages registration<br />
* registration deadline is 17.04. (first come, first serve)<br />
* conference program will be split up into 2 sections:<br />
** a common program with presentations and public discussions<br />
** a workgroup-oriented program with talks, which are oriented toward certain aspects of the specification<br />
<br />
====Spending institution====<br />
<br />
* TU Darmstadt/ Universität Würzburg (chair of Fotis Jannidis) will be spending institution<br />
* in case of any restrictions NUI Galway can serve as a workaround<br />
* funding will be provided by ALLC, ACH, TEI and Galway<br />
* Fotis Jannidis contacts sponsors as soon as the ultimate recipient of reimbursements is determined<br />
<br />
====Program: 1. day====<br />
<br />
* start at 02:00pm<br />
* one coffee break<br />
* 2 sessions, 4 talks each, 15 min/talk + 5 min/discussion<br />
* (edition) project presentations<br />
<br />
====Program: 2. day====<br />
<br />
* start at 09:00am<br />
* present the SIG work: 45 min<br />
* 10:00am: discussion<br />
* 11:00am: coffee<br />
* 11:30am: discussion<br />
* 01:00pm: lunch<br />
* 02:00pm:discussion, wrap up, roadmap, outlook<br />
* finish at 03:30pm<br />
<br />
====Technical support====<br />
<br />
* we want to offer an optional web publication service, so attendants can refer online to all the examples during discussion<br />
<br />
==Specification==<br />
<br />
===Deliverables===<br />
<br />
# a presentation of the draft specification at the conference<br />
# the XML schema<br />
# a contribution to the TEI guidelines<br />
<br />
===Theoretical framework===<br />
<br />
* the specification shall be independent of presuppositions made by a particular theoretical framework<br />
* therefore a couple of typical dichotomies in editorial theory have to be recognized<br />
* first there is the notion of ''fact (or representation) vs. interpretation''<br />
* maybe we should think of differing ''levels of interpretation'' instead<br />
* reason: we might not be able to cleary differentiate between „what's there“ (document/fact) and „how does it relate“ (text/interpretation)<br />
* this leads to the second opposition, that is central to editorial theory: ''document vs. text''<br />
* Paolo D'Iorio explains the HyperNietzsche approach to handle this opposition<br />
* HyperNietzsche bases its functionality on a thorough manuscript description, that happens on the documentary level<br />
* the interpretative acts (constituting a text) build upon the manuscript description<br />
* to summarize the HyperNietzsche experience while trying to adopt TEI guidelines: the '''Text''' Encoding Initiative does not handle "the document level" very well thus far<br />
* for genetic editions though, this level is crucial<br />
<br />
===Methodology===<br />
<br />
* we want to propose a standard, we do not want (even better: we cannot) prescribe one, given the complex landscape of editorial practices<br />
* in the beginning we will work on a pseudo-encoding, which is tightly bound to our own terminology<br />
* in a second step, we will try to map this pseudo-encoding to the actual TEI encoding framework, probably in cooperation with someone from the TEI Council<br />
* the same step-by-step approach shall be taken for the standardization process<br />
* first we develop an application profile aka. TEI customization<br />
* when that proves to be of general interest, we rework it into a separate chapter for the TEI guidelines<br />
<br />
==Aspects of Genetic Editions==<br />
<br />
===Topological description on the document level===<br />
<br />
* the description functions hierarchically on 3 levels:<br />
* highest level: the ''page''<br />
* pages contain ''zones''<br />
* zones are are nestable, groupable, can overlap and have a depth level (aka. belong to a layer)<br />
* zones are arbitrary in as much as they can be defined by layout and/or semantic aspects<br />
* on a third level, zones normally contain (among other entities) ''lines''<br />
<br />
===Dating===<br />
<br />
* on the one hand the dating of a witness may not be directly related to its encoded content, it therefore has to go into the header<br />
* on the other hand, dates added by the original author as metadata to the text on the witness should be encoded without necessarily going into the header [can be embedded within a Functional Mark]<br />
* dating can be justified by prose and/or by reference to a characteristic of a manuscript (e.g. hand)<br />
<br />
<teiHeader><br />
<datingDesc><br />
<dating ....><br />
<div1>...</div1><br />
</dating><br />
</datingDesc><br />
</teiHeader><br />
<br />
===Time/ Chronology===<br />
<br />
* we want to express time as absolute and relative measures<br />
* express absolute time by adapting the existing date element/attributes; see http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ND.html#NDATTSda<br />
* express relative time as predecessor/successor-relationships<br />
** might be a direct relationship: next, previous<br />
** might be a „sorting“ relationship: before, after<br />
** relationships may also be expressed via a numbering scheme<br />
** relationships may have 1:n cardinality, e.g. one witness is dated before a set of others<br />
<br />
===Grouping changes (“changesets”)===<br />
<br />
* forming changesets is necessary to group text passages, which all form one revision<br />
* implemented either via a wrapping element (e.g. <revision/>) or via a stand-off mechanism for spatially disparate changes<br />
<br />
===Alterations===<br />
<br />
* alterations are practically related to the ''collation'' of texts<br />
* we need to deal with collation as a separate aspect of genetic editions<br />
* for example we need an expression for ''ommissions'' as a textual feature, that results from relating texts via collation<br />
* another set of alterations to be expressed is the one, that results from authors ''fixating'' a text passage by overwriting it (e.g. a penciled passage fixated with ink)<br />
* marginal notes have to be differentiated from ''functional marks'' commanding an alteration (e.g. „move this passage over there”)<br />
<br />
===Deletions===<br />
<br />
====“marked as used”====<br />
<br />
* passages happen to be striked through, which marks the passage to be used at another location<br />
* two-step markup<br />
* first: markup the block on the document level<br />
* secondly: describe the function (“mark as used”)<br />
<br />
====Overwriting====<br />
<br />
* overwriting is a special case of a deletion<br />
<br />
===Undoing alterations===<br />
<br />
* how to express on the document level, that an alteration has been taken back, e.g. a striked through passage being reinstantiated via a dotted underlining<br />
* <restore/> already exists for undoing an deletion, but we might need a more general approach<br />
* possible solutions via an element or via an attribute “undo”<br />
* proposal: add a generic element <undo/> with an attribute referring to the action being undone<br />
* can be further differentiated by a type attribute, e.g. immediate correction vs. revising<br />
* this is preliminary: we have to open up this solution to discussion<br />
<br />
===Transpositions===<br />
<br />
* current approach: express transpositions as pairs of additions and deletions<br />
* we also want to express transpositions as an atomic operation, because it might be expressed as such on the document as well<br />
* first: make the segment to be transposed adressable<br />
* either via an identifiable wrapping element or via a “cross-cutting” <seg/><br />
* secondly: markup “functional mark”, which might be in the text (e.g. a superlinear “add ‘is’ here”), with an element like <fm/><br />
* relate the functional mark to the identified passages<br />
<br />
<add><fm type="addition">add</fm> ‘is’ here</add><br />
<br />
* either refer to the passage added via attributes<br />
* or it might be implicit, which passage is transposed, because the <fm/> is contained in an <add/> or <delete/><br />
* maybe we can generalize the idea of a ''functional mark'' (<fm/>)<br />
* we markup passages on the representational level, but also on the semantic level, on which they command alterations<br />
<br />
===Clarification===<br />
<br />
* think of clarification as a ''repetition'' of a text<br />
* this idea can also offer a solution for encoding fixations<br />
<br />
<repetition type="clarification|fixation|..." position="superlinear" hand=""/><br />
<br />
===Correction===<br />
<br />
* supply an additional attribute to <add/> and <delete/> that typifies the alteration (e. g. “instant correction”)<br />
<br />
===“Coordinate system”===<br />
<br />
* how to express genetic relationships on an inter- and intra-document level<br />
* we need a scheme for addressing the linked passages and a means for describing such relationships/ links<br />
* adopt the HyperNietzsche concept: relational description via ''paths''<br />
* paths are typed, depending on the relation expressed (e.g. a timeline, a conceptual link …)<br />
* paths: define complete paths via a set of vertices (''steps'')<br />
* <linkGrp/> is a candidate for grouping a set of steps forming a path<br />
* steps of a path can be ordered or unordered, but that might belong to the aspect of uncertainty)<br />
* the steps of a path should be describable, so the expressed relationships can be justified or further characterized<br />
* we should import concepts from the critical apparatus here: http://www.tei-c.org/release/doc/tei-p5-doc/en/html/TC.html<br />
* relationships might be ''transitive'' in nature, should we express that as well<br />
* then: is there a potential scope conflict between the TEI and other graph-oriented markup languages like RDF/XML<br />
* maybe we can differentiate between the description of the relationships itself and their characterization/justification<br />
* the relationships might be described as an RDF graph, which is argumented with TEI-based prose<br />
<br />
==Roadmap==<br />
<br />
===Organizational tasks===<br />
<br />
* conference announcement: Malte Rehbein<br />
* call for more examples on the TEI list: Elena Pierazzo<br />
* apply for a panel on the next TEI Member’s meeting<br />
<br />
===Specification tasks===<br />
<br />
* as we were not able to deal with all aspects, the further work on the remaining ones is distributed among the SIG members<br />
<br />
{| class="wikitable" border="1" cellpadding="2"<br />
|-<br />
! Aspect !! responsible<br />
|-<br />
| [[Alternatives]] || Elena Pierazzo<br />
|-<br />
| Substitution || Malte Rehbein<br />
|-<br />
| Gaps || Fotis Jannidis<br />
|-<br />
| Editorial Decisions || Paolo D'Iorio<br />
|-<br />
| Uncertainty || Malte Rehbein<br />
|-<br />
| Critical Apparatus || Fotis Jannidis<br />
|-<br />
|Textual Constitution || Paolo D'Iorio<br />
|}<br />
<br />
===Upcoming events===<br />
<br />
{| class="wikitable" border="1" cellpadding="2"<br />
|- class="hintergrundfarbe5"<br />
! Date/Time !! Event<br />
|-<br />
| 21.04. 09:30am CET || conference talk: content-related issues<br />
|-<br />
| 05.05. 09:30am CET || conference talk: organization-related issues<br />
|-<br />
| 11.05. || deadline for publication of draft specification to the conf. participants<br />
|-<br />
| 14./15.05. || Conference in Paris<br />
|-<br />
| 16.05. || post-conference meeting<br />
|-<br />
| 16.06. 09:30 CET || conference talk: specification<br />
|-<br />
| 07.08. 09:30 CET || conference talk: specification<br />
|-<br />
| 16./17.09. || Wuerzburg: finalize specification (place might change; depends on funding)<br />
|}</div>Elenaphttps://wiki.tei-c.org/index.php?title=Minutes_London_03-2009&diff=5573Minutes London 03-20092009-03-19T15:33:49Z<p>Elenap: /* Specification tasks */</p>
<hr />
<div>''Present: Katrin Dennerlein, Paolo D'Iorio, Fotis Jannidis, Gregor Middell, Elena Pierazzo, Malte Rehbein, Moritz Wissenbach.''<br />
<br />
''Discussion led by Elena Pierazzo, minutes by Gregor Middell.''<br />
<br />
==Organization==<br />
<br />
===Technical infrastructure/ Workflow===<br />
<br />
* coordination takes place in this wiki<br />
* project has to be announced on the news bar at http://tei-c.org/<br />
* wiki will be reorganzied in 2 distinct parts: a public one (with announcements, draft specs …) and an internal one with information, that is less interesting to the general public<br />
* list of sponsors has to go on the wiki as well<br />
* ''Google Docs'' used for the (internal) specification process<br />
* draft versions of the specification are checked out as a PDF document and put on the wiki every week, so we can gather feedback<br />
<br />
===Conference in Paris===<br />
<br />
* ITEM provides up to 3 rooms for the conference; definitely 1 on both days, possibly 3 on the second<br />
* Paolo D'Iorio coordinates the room allocation with ITEM<br />
* we want to offer lunch at the conference (attendants shall ''confirm'' their participation upon registration)<br />
* SIG will invite speakers and organizers to a dinner as well<br />
* Paolo D'Iorio organizes hotel, dinner bookings, internet access, beamer<br />
* Malte Rehbein manages registration<br />
* registration deadline is 17.04. (first come, first serve)<br />
* conference program will be split up into 2 sections:<br />
** a common program with presentations and public discussions<br />
** a workgroup-oriented program with talks, which are oriented toward certain aspects of the specification<br />
<br />
====Spending institution====<br />
<br />
* TU Darmstadt/ Universität Würzburg (chair of Fotis Jannidis) will be spending institution<br />
* in case of any restrictions NUI Galway can serve as a workaround<br />
* funding will be provided by ALLC, ACH, TEI and Galway<br />
* Fotis Jannidis contacts sponsors as soon as the ultimate recipient of reimbursements is determined<br />
<br />
====Program: 1. day====<br />
<br />
* start at 02:00pm<br />
* one coffee break<br />
* 2 sessions, 4 talks each, 15 min/talk + 5 min/discussion<br />
* (edition) project presentations<br />
<br />
====Program: 2. day====<br />
<br />
* start at 09:00am<br />
* present the SIG work: 45 min<br />
* 10:00am: discussion<br />
* 11:00am: coffee<br />
* 11:30am: discussion<br />
* 01:00pm: lunch<br />
* 02:00pm:discussion, wrap up, roadmap, outlook<br />
* finish at 03:30pm<br />
<br />
====Technical support====<br />
<br />
* we want to offer an optional web publication service, so attendants can refer online to all the examples during discussion<br />
<br />
==Specification==<br />
<br />
===Deliverables===<br />
<br />
# a presentation of the draft specification at the conference<br />
# the XML schema<br />
# a contribution to the TEI guidelines<br />
<br />
===Theoretical framework===<br />
<br />
* the specification shall be independent of presuppositions made by a particular theoretical framework<br />
* therefore a couple of typical dichotomies in editorial theory have to be recognized<br />
* first there is the notion of ''fact (or representation) vs. interpretation''<br />
* maybe we should think of differing ''levels of interpretation'' instead<br />
* reason: we might not be able to cleary differentiate between „what's there“ (document/fact) and „how does it relate“ (text/interpretation)<br />
* this leads to the second opposition, that is central to editorial theory: ''document vs. text''<br />
* Paolo D'Iorio explains the HyperNietzsche approach to handle this opposition<br />
* HyperNietzsche bases its functionality on a thorough manuscript description, that happens on the documentary level<br />
* the interpretative acts (constituting a text) build upon the manuscript description<br />
* to summarize the HyperNietzsche experience while trying to adopt TEI guidelines: the '''Text''' Encoding Initiative does not handle "the document level" very well thus far<br />
* for genetic editions though, this level is crucial<br />
<br />
===Methodology===<br />
<br />
* we want to propose a standard, we do not want (even better: we cannot) prescribe one, given the complex landscape of editorial practices<br />
* in the beginning we will work on a pseudo-encoding, which is tightly bound to our own terminology<br />
* in a second step, we will try to map this pseudo-encoding to the actual TEI encoding framework, probably in cooperation with someone from the TEI Council<br />
* the same step-by-step approach shall be taken for the standardization process<br />
* first we develop an application profile aka. TEI customization<br />
* when that proves to be of general interest, we rework it into a separate chapter for the TEI guidelines<br />
<br />
==Aspects of Genetic Editions==<br />
<br />
===Topological description on the document level===<br />
<br />
* the description functions hierarchically on 3 levels:<br />
* highest level: the ''page''<br />
* pages contain ''zones''<br />
* zones are are nestable, groupable, can overlap and have a depth level (aka. belong to a layer)<br />
* zones are arbitrary in as much as they can be defined by layout and/or semantic aspects<br />
* on a third level, zones normally contain (among other entities) ''lines''<br />
<br />
===Dating===<br />
<br />
* on the one hand the dating of a witness may not be directly related to its encoded content, it therefore has to go into the header<br />
* on the other hand, dates added by the original author as metadata to the text on the witness should be encoded without necessarily going into the header [can be embedded within a Functional Mark]<br />
* dating can be justified by prose and/or by reference to a characteristic of a manuscript (e.g. hand)<br />
<br />
<teiHeader><br />
<datingDesc><br />
<dating ....><br />
<div1>...</div1><br />
</dating><br />
</datingDesc><br />
</teiHeader><br />
<br />
===Time/ Chronology===<br />
<br />
* we want to express time as absolute and relative measures<br />
* express absolute time by adapting the existing date element/attributes; see http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ND.html#NDATTSda<br />
* express relative time as predecessor/successor-relationships<br />
** might be a direct relationship: next, previous<br />
** might be a „sorting“ relationship: before, after<br />
** relationships may also be expressed via a numbering scheme<br />
** relationships may have 1:n cardinality, e.g. one witness is dated before a set of others<br />
<br />
===Grouping changes (“changesets”)===<br />
<br />
* forming changesets is necessary to group text passages, which all form one revision<br />
* implemented either via a wrapping element (e.g. <revision/>) or via a stand-off mechanism for spatially disparate changes<br />
<br />
===Alterations===<br />
<br />
* alterations are practically related to the ''collation'' of texts<br />
* we need to deal with collation as a separate aspect of genetic editions<br />
* for example we need an expression for ''ommissions'' as a textual feature, that results from relating texts via collation<br />
* another set of alterations to be expressed is the one, that results from authors ''fixating'' a text passage by overwriting it (e.g. a penciled passage fixated with ink)<br />
* marginal notes have to be differentiated from ''functional marks'' commanding an alteration (e.g. „move this passage over there”)<br />
<br />
===Deletions===<br />
<br />
====“marked as used”====<br />
<br />
* passages happen to be striked through, which marks the passage to be used at another location<br />
* two-step markup<br />
* first: markup the block on the document level<br />
* secondly: describe the function (“mark as used”)<br />
<br />
====Overwriting====<br />
<br />
* overwriting is a special case of a deletion<br />
<br />
===Undoing alterations===<br />
<br />
* how to express on the document level, that an alteration has been taken back, e.g. a striked through passage being reinstantiated via a dotted underlining<br />
* <restore/> already exists for undoing an deletion, but we might need a more general approach<br />
* possible solutions via an element or via an attribute “undo”<br />
* proposal: add a generic element <undo/> with an attribute referring to the action being undone<br />
* can be further differentiated by a type attribute, e.g. immediate correction vs. revising<br />
* this is preliminary: we have to open up this solution to discussion<br />
<br />
===Transpositions===<br />
<br />
* current approach: express transpositions as pairs of additions and deletions<br />
* we also want to express transpositions as an atomic operation, because it might be expressed as such on the document as well<br />
* first: make the segment to be transposed adressable<br />
* either via an identifiable wrapping element or via a “cross-cutting” <seg/><br />
* secondly: markup “functional mark”, which might be in the text (e.g. a superlinear “add ‘is’ here”), with an element like <fm/><br />
* relate the functional mark to the identified passages<br />
<br />
<add><fm type="addition">add</fm> ‘is’ here</add><br />
<br />
* either refer to the passage added via attributes<br />
* or it might be implicit, which passage is transposed, because the <fm/> is contained in an <add/> or <delete/><br />
* maybe we can generalize the idea of a ''functional mark'' (<fm/>)<br />
* we markup passages on the representational level, but also on the semantic level, on which they command alterations<br />
<br />
===Clarification===<br />
<br />
* think of clarification as a ''repetition'' of a text<br />
* this idea can also offer a solution for encoding fixations<br />
<br />
<repetition type="clarification|fixation|..." position="superlinear" hand=""/><br />
<br />
===Correction===<br />
<br />
* supply an additional attribute to <add/> and <delete/> that typifies the alteration (e. g. “instant correction”)<br />
<br />
===“Coordinate system”===<br />
<br />
* how to express genetic relationships on an inter- and intra-document level<br />
* we need a scheme for addressing the linked passages and a means for describing such relationships/ links<br />
* adopt the HyperNietzsche concept: relational description via ''paths''<br />
* paths are typed, depending on the relation expressed (e.g. a timeline, a conceptual link …)<br />
* paths: define complete paths via a set of vertices (''steps'')<br />
* <linkGrp/> is a candidate for grouping a set of steps forming a path<br />
* steps of a path can be ordered or unordered, but that might belong to the aspect of uncertainty)<br />
* the steps of a path should be describable, so the expressed relationships can be justified or further characterized<br />
* we should import concepts from the critical apparatus here: http://www.tei-c.org/release/doc/tei-p5-doc/en/html/TC.html<br />
* relationships might be ''transitive'' in nature, should we express that as well<br />
* then: is there a potential scope conflict between the TEI and other graph-oriented markup languages like RDF/XML<br />
* maybe we can differentiate between the description of the relationships itself and their characterization/justification<br />
* the relationships might be described as an RDF graph, which is argumented with TEI-based prose<br />
<br />
==Roadmap==<br />
<br />
===Organizational tasks===<br />
<br />
* conference announcement: Malte Rehbein<br />
* call for more examples on the TEI list: Elena Pierazzo<br />
* apply for a panel on the next TEI Member’s meeting<br />
<br />
===Specification tasks===<br />
<br />
* as we were not able to deal with all aspects, the further work on the remaining ones is distributed among the SIG members<br />
<br />
{| class="wikitable" border="1" cellpadding="2"<br />
|-<br />
! Aspect !! responsible<br />
|-<br />
| Alternatives || Elena Pierazzo<br />
|-<br />
| Substitution || Malte Rehbein<br />
|-<br />
| Gaps || Fotis Jannidis<br />
|-<br />
| Editorial Decisions || Paolo D'Iorio<br />
|-<br />
| Uncertainty || Malte Rehbein<br />
|-<br />
| Critical Apparatus || Fotis Jannidis<br />
|-<br />
|Textual Constitution || Paolo D'Iorio<br />
|}<br />
<br />
===Upcoming events===<br />
<br />
{| class="wikitable" border="1" cellpadding="2"<br />
|- class="hintergrundfarbe5"<br />
! Date/Time !! Event<br />
|-<br />
| 21.04. 09:30am CET || conference talk: content-related issues<br />
|-<br />
| 05.05. 09:30am CET || conference talk: organization-related issues<br />
|-<br />
| 11.05. || deadline for publication of draft specification to the conf. participants<br />
|-<br />
| 14./15.05. || Conference in Paris<br />
|-<br />
| 16.05. || post-conference meeting<br />
|-<br />
| 16.06. 09:30 CET || conference talk: specification<br />
|-<br />
| 07.08. 09:30 CET || conference talk: specification<br />
|-<br />
| 16./17.09. || Wuerzburg: finalize specification (place might change; depends on funding)<br />
|}</div>Elenaphttps://wiki.tei-c.org/index.php?title=Genetic_Editions&diff=5572Genetic Editions2009-03-19T13:55:16Z<p>Elenap: /* Meetings */</p>
<hr />
<div>[[category:Genetic Editions]]<br />
At the Members Meeting in London in November, a panel focussing on the problem of genetic editions is planned.<br />
<br />
<br />
#[[Introduction to Genetic Editions | Introduction]]<br />
#[[Textual alterations]]<br />
#[[Time]]<br />
#[[Grouping changes]]<br />
#[[A coordinate system for relation of different witnesses]]<br />
#[[Justification and discussion of editorial decisions]]<br />
#[[Uncertainty]]<br />
#[[Examples]]<br />
<br />
<br />
<br />
== Meetings ==<br />
Workshop during the TEI-meeting 2008 in London -> [[minutes London 2008]]<br />
<br />
Task Force meeting at Kings College London on 12./13. March 2009 -> [[minutes London 03-2009]]<br />
<br />
== Useful Resources ==<br />
* HyperNietsche<br />
** [http://www.hypernietzsche.org/doc/HNML/ HyperNietzsche Markup Language HNML], in [http://www.hypernietzsche.org/doc/HNML/HNML-engl.pdf English], and in [http://www.hypernietzsche.org/doc/HNML/HNML-de.pdf German]<br />
** Article on [http://computerphilologie.uni-muenchen.de/jg03/saller.html HNML]<br />
** Matteo D’Alfonso, Harald Saller: [http://www.germanistik.ch/publikation.php?id=Kodierung_und_Darstellung Kodierung und Darstellung von Schreibschichten in der elektronischen Edition des Druckmanuskripts zu Der Wanderer und sein Schatten]. In: Literatur und Literaturwissenschaften auf dem Weg zu den digitalen Medien - Eine Standortbestimmung, hg. v. Michael Stolz. Online veröffentlicht bei Gisi + Loop.<br />
* Genetic Markup Language (In French) [http://staff.cch.kcl.ac.uk/~epierazzo/GML-fr.pdf download it from here]<br />
* Multi-Version Document Format. See the related [http://multiversiondocs.blogspot.com/ blog] and the post [http://multiversiondocs.blogspot.com/2008/03/whats-multi-version-document.html What's a Multi-Version Document?].<br />
<br />
== Literature on genetic editions ==<br />
* Gabler, Hans Walter<br />
** "Das wissenschaftliche Edieren als Funktion der Dokumente." Published at: [http://computerphilologie.tu-darmstadt.de/jg06/gabler.html http://computerphilologie.tu-darmstadt.de/jg06/gabler.html]; and in: Jahrbuch für Computerphilologie 8 (2007), 55-62.<br />
** "The Primacy of the Document in Editing." Ecdotica 4 (2007), 197-207. [http://staff.cch.kcl.ac.uk/~epierazzo/Gabler%20Ecdotica%204.pdf download it from here]<br />
** "La prééminence du document dans l’édition." In: Françoise Leriche et Cécile Maynard (eds.), De l'hypertexte au manuscrit. L'apport et les limites du numérique pour l'édition et la valorisation de manuscrits littéraires modernes. (Recherches & Travaux, no. 72.) Grenoble: ELLUG, 2008, pp. 39-51.[http://staff.cch.kcl.ac.uk/~epierazzo/GABLER%20definitif.pdf download it from here]</div>Elenaphttps://wiki.tei-c.org/index.php?title=Minutes_London_03-2009&diff=5571Minutes London 03-20092009-03-19T13:50:35Z<p>Elenap: /* “Coordinate system” */</p>
<hr />
<div>''Present: Katrin Dennerlein, Paolo D'Iorio, Fotis Jannidis, Gregor Middell, Elena Pierazzo, Malte Rehbein, Moritz Wissenbach.''<br />
<br />
''Discussion led by Elena Pierazzo, minutes by Gregor Middell.''<br />
<br />
==Organization==<br />
<br />
===Technical infrastructure/ Workflow===<br />
<br />
* coordination takes place in this wiki<br />
* project has to be announced on the news bar at http://tei-c.org/<br />
* wiki will be reorganzied in 2 distinct parts: a public one (with announcements, draft specs …) and an internal one with information, that is less interesting to the general public<br />
* list of sponsors has to go on the wiki as well<br />
* ''Google Docs'' used for the (internal) specification process<br />
* draft versions of the specification are checked out as a PDF document and put on the wiki every week, so we can gather feedback<br />
<br />
===Conference in Paris===<br />
<br />
* ITEM provides up to 3 rooms for the conference; definitely 1 on both days, possibly 3 on the second<br />
* Paolo D'Iorio coordinates the room allocation with ITEM<br />
* we want to offer lunch at the conference (attendants shall ''confirm'' their participation upon registration)<br />
* SIG will invite speakers and organizers to a dinner as well<br />
* Paolo D'Iorio organizes hotel, dinner bookings, internet access, beamer<br />
* Malte Rehbein manages registration<br />
* registration deadline is 17.04. (first come, first serve)<br />
* conference program will be split up into 2 sections:<br />
** a common program with presentations and public discussions<br />
** a workgroup-oriented program with talks, which are oriented toward certain aspects of the specification<br />
<br />
====Spending institution====<br />
<br />
* TU Darmstadt/ Universität Würzburg (chair of Fotis Jannidis) will be spending institution<br />
* in case of any restrictions NUI Galway can serve as a workaround<br />
* funding will be provided by ALLC, ACH, TEI and Galway<br />
* Fotis Jannidis contacts sponsors as soon as the ultimate recipient of reimbursements is determined<br />
<br />
====Program: 1. day====<br />
<br />
* start at 02:00pm<br />
* one coffee break<br />
* 2 sessions, 4 talks each, 15 min/talk + 5 min/discussion<br />
* (edition) project presentations<br />
<br />
====Program: 2. day====<br />
<br />
* start at 09:00am<br />
* present the SIG work: 45 min<br />
* 10:00am: discussion<br />
* 11:00am: coffee<br />
* 11:30am: discussion<br />
* 01:00pm: lunch<br />
* 02:00pm:discussion, wrap up, roadmap, outlook<br />
* finish at 03:30pm<br />
<br />
====Technical support====<br />
<br />
* we want to offer an optional web publication service, so attendants can refer online to all the examples during discussion<br />
<br />
==Specification==<br />
<br />
===Deliverables===<br />
<br />
# a presentation of the draft specification at the conference<br />
# the XML schema<br />
# a contribution to the TEI guidelines<br />
<br />
===Theoretical framework===<br />
<br />
* the specification shall be independent of presuppositions made by a particular theoretical framework<br />
* therefore a couple of typical dichotomies in editorial theory have to be recognized<br />
* first there is the notion of ''fact (or representation) vs. interpretation''<br />
* maybe we should think of differing ''levels of interpretation'' instead<br />
* reason: we might not be able to cleary differentiate between „what's there“ (document/fact) and „how does it relate“ (text/interpretation)<br />
* this leads to the second opposition, that is central to editorial theory: ''document vs. text''<br />
* Paolo D'Iorio explains the HyperNietzsche approach to handle this opposition<br />
* HyperNietzsche bases its functionality on a thorough manuscript description, that happens on the documentary level<br />
* the interpretative acts (constituting a text) build upon the manuscript description<br />
* to summarize the HyperNietzsche experience while trying to adopt TEI guidelines: the '''Text''' Encoding Initiative does not handle "the document level" very well thus far<br />
* for genetic editions though, this level is crucial<br />
<br />
===Methodology===<br />
<br />
* we want to propose a standard, we do not want (even better: we cannot) prescribe one, given the complex landscape of editorial practices<br />
* in the beginning we will work on a pseudo-encoding, which is tightly bound to our own terminology<br />
* in a second step, we will try to map this pseudo-encoding to the actual TEI encoding framework, probably in cooperation with someone from the TEI Council<br />
* the same step-by-step approach shall be taken for the standardization process<br />
* first we develop an application profile aka. TEI customization<br />
* when that proves to be of general interest, we rework it into a separate chapter for the TEI guidelines<br />
<br />
==Aspects of Genetic Editions==<br />
<br />
===Topological description on the document level===<br />
<br />
* the description functions hierarchically on 3 levels:<br />
* highest level: the ''page''<br />
* pages contain ''zones''<br />
* zones are are nestable, groupable, can overlap and have a depth level (aka. belong to a layer)<br />
* zones are arbitrary in as much as they can be defined by layout and/or semantic aspects<br />
* on a third level, zones normally contain (among other entities) ''lines''<br />
<br />
===Dating===<br />
<br />
* on the one hand the dating of a witness may not be directly related to its encoded content, it therefore has to go into the header<br />
* on the other hand, dates added by the original author as metadata to the text on the witness should be encoded without necessarily going into the header [can be embedded within a Functional Mark]<br />
* dating can be justified by prose and/or by reference to a characteristic of a manuscript (e.g. hand)<br />
<br />
<teiHeader><br />
<datingDesc><br />
<dating ....><br />
<div1>...</div1><br />
</dating><br />
</datingDesc><br />
</teiHeader><br />
<br />
===Time/ Chronology===<br />
<br />
* we want to express time as absolute and relative measures<br />
* express absolute time by adapting the existing date element/attributes; see http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ND.html#NDATTSda<br />
* express relative time as predecessor/successor-relationships<br />
** might be a direct relationship: next, previous<br />
** might be a „sorting“ relationship: before, after<br />
** relationships may also be expressed via a numbering scheme<br />
** relationships may have 1:n cardinality, e.g. one witness is dated before a set of others<br />
<br />
===Grouping changes (“changesets”)===<br />
<br />
* forming changesets is necessary to group text passages, which all form one revision<br />
* implemented either via a wrapping element (e.g. <revision/>) or via a stand-off mechanism for spatially disparate changes<br />
<br />
===Alterations===<br />
<br />
* alterations are practically related to the ''collation'' of texts<br />
* we need to deal with collation as a separate aspect of genetic editions<br />
* for example we need an expression for ''ommissions'' as a textual feature, that results from relating texts via collation<br />
* another set of alterations to be expressed is the one, that results from authors ''fixating'' a text passage by overwriting it (e.g. a penciled passage fixated with ink)<br />
* marginal notes have to be differentiated from ''functional marks'' commanding an alteration (e.g. „move this passage over there”)<br />
<br />
===Deletions===<br />
<br />
====“marked as used”====<br />
<br />
* passages happen to be striked through, which marks the passage to be used at another location<br />
* two-step markup<br />
* first: markup the block on the document level<br />
* secondly: describe the function (“mark as used”)<br />
<br />
====Overwriting====<br />
<br />
* overwriting is a special case of a deletion<br />
<br />
===Undoing alterations===<br />
<br />
* how to express on the document level, that an alteration has been taken back, e.g. a striked through passage being reinstantiated via a dotted underlining<br />
* <restore/> already exists for undoing an deletion, but we might need a more general approach<br />
* possible solutions via an element or via an attribute “undo”<br />
* proposal: add a generic element <undo/> with an attribute referring to the action being undone<br />
* can be further differentiated by a type attribute, e.g. immediate correction vs. revising<br />
* this is preliminary: we have to open up this solution to discussion<br />
<br />
===Transpositions===<br />
<br />
* current approach: express transpositions as pairs of additions and deletions<br />
* we also want to express transpositions as an atomic operation, because it might be expressed as such on the document as well<br />
* first: make the segment to be transposed adressable<br />
* either via an identifiable wrapping element or via a “cross-cutting” <seg/><br />
* secondly: markup “functional mark”, which might be in the text (e.g. a superlinear “add ‘is’ here”), with an element like <fm/><br />
* relate the functional mark to the identified passages<br />
<br />
<add><fm type="addition">add</fm> ‘is’ here</add><br />
<br />
* either refer to the passage added via attributes<br />
* or it might be implicit, which passage is transposed, because the <fm/> is contained in an <add/> or <delete/><br />
* maybe we can generalize the idea of a ''functional mark'' (<fm/>)<br />
* we markup passages on the representational level, but also on the semantic level, on which they command alterations<br />
<br />
===Clarification===<br />
<br />
* think of clarification as a ''repetition'' of a text<br />
* this idea can also offer a solution for encoding fixations<br />
<br />
<repetition type="clarification|fixation|..." position="superlinear" hand=""/><br />
<br />
===Correction===<br />
<br />
* supply an additional attribute to <add/> and <delete/> that typifies the alteration (e. g. “instant correction”)<br />
<br />
===“Coordinate system”===<br />
<br />
* how to express genetic relationships on an inter- and intra-document level<br />
* we need a scheme for addressing the linked passages and a means for describing such relationships/ links<br />
* adopt the HyperNietzsche concept: relational description via ''paths''<br />
* paths are typed, depending on the relation expressed (e.g. a timeline, a conceptual link …)<br />
* paths: define complete paths via a set of vertices (''steps'')<br />
* <linkGrp/> is a candidate for grouping a set of steps forming a path<br />
* steps of a path can be ordered or unordered, but that might belong to the aspect of uncertainty)<br />
* the steps of a path should be describable, so the expressed relationships can be justified or further characterized<br />
* we should import concepts from the critical apparatus here: http://www.tei-c.org/release/doc/tei-p5-doc/en/html/TC.html<br />
* relationships might be ''transitive'' in nature, should we express that as well<br />
* then: is there a potential scope conflict between the TEI and other graph-oriented markup languages like RDF/XML<br />
* maybe we can differentiate between the description of the relationships itself and their characterization/justification<br />
* the relationships might be described as an RDF graph, which is argumented with TEI-based prose<br />
<br />
==Roadmap==<br />
<br />
===Organizational tasks===<br />
<br />
* conference announcement: Malte Rehbein<br />
* call for more examples on the TEI list: Elena Pierazzo<br />
* apply for a panel on the next TEI Member’s meeting<br />
<br />
===Specification tasks===<br />
<br />
* as we were not able to deal with all aspects, the further work on the remaining ones is distributed among the SIG members<br />
<br />
{| class="wikitable" border="1" cellpadding="2"<br />
|-<br />
! Aspect !! responsible<br />
|-<br />
| Alternatives || Elena Pierazzo<br />
|-<br />
| Substitution || Malte Rehbein<br />
|-<br />
| Gaps || Fotis Jannidis<br />
|-<br />
| Editorial Decisions || Paolo D'Iorio<br />
|-<br />
| Uncertainty || Malte Rehbein<br />
|-<br />
| Critical Apparatus || Fotis Jannidis<br />
|-<br />
|Textual Constitution || Elena Pierazzo, Paolo D'Iorio<br />
|}<br />
<br />
===Upcoming events===<br />
<br />
{| class="wikitable" border="1" cellpadding="2"<br />
|- class="hintergrundfarbe5"<br />
! Date/Time !! Event<br />
|-<br />
| 21.04. 09:30am CET || conference talk: content-related issues<br />
|-<br />
| 05.05. 09:30am CET || conference talk: organization-related issues<br />
|-<br />
| 11.05. || deadline for publication of draft specification to the conf. participants<br />
|-<br />
| 14./15.05. || Conference in Paris<br />
|-<br />
| 16.05. || post-conference meeting<br />
|-<br />
| 16.06. 09:30 CET || conference talk: specification<br />
|-<br />
| 07.08. 09:30 CET || conference talk: specification<br />
|-<br />
| 16./17.09. || Wuerzburg: finalize specification (place might change; depends on funding)<br />
|}</div>Elenaphttps://wiki.tei-c.org/index.php?title=Minutes_London_03-2009&diff=5570Minutes London 03-20092009-03-19T13:46:12Z<p>Elenap: /* Dating */</p>
<hr />
<div>''Present: Katrin Dennerlein, Paolo D'Iorio, Fotis Jannidis, Gregor Middell, Elena Pierazzo, Malte Rehbein, Moritz Wissenbach.''<br />
<br />
''Discussion led by Elena Pierazzo, minutes by Gregor Middell.''<br />
<br />
==Organization==<br />
<br />
===Technical infrastructure/ Workflow===<br />
<br />
* coordination takes place in this wiki<br />
* project has to be announced on the news bar at http://tei-c.org/<br />
* wiki will be reorganzied in 2 distinct parts: a public one (with announcements, draft specs …) and an internal one with information, that is less interesting to the general public<br />
* list of sponsors has to go on the wiki as well<br />
* ''Google Docs'' used for the (internal) specification process<br />
* draft versions of the specification are checked out as a PDF document and put on the wiki every week, so we can gather feedback<br />
<br />
===Conference in Paris===<br />
<br />
* ITEM provides up to 3 rooms for the conference; definitely 1 on both days, possibly 3 on the second<br />
* Paolo D'Iorio coordinates the room allocation with ITEM<br />
* we want to offer lunch at the conference (attendants shall ''confirm'' their participation upon registration)<br />
* SIG will invite speakers and organizers to a dinner as well<br />
* Paolo D'Iorio organizes hotel, dinner bookings, internet access, beamer<br />
* Malte Rehbein manages registration<br />
* registration deadline is 17.04. (first come, first serve)<br />
* conference program will be split up into 2 sections:<br />
** a common program with presentations and public discussions<br />
** a workgroup-oriented program with talks, which are oriented toward certain aspects of the specification<br />
<br />
====Spending institution====<br />
<br />
* TU Darmstadt/ Universität Würzburg (chair of Fotis Jannidis) will be spending institution<br />
* in case of any restrictions NUI Galway can serve as a workaround<br />
* funding will be provided by ALLC, ACH, TEI and Galway<br />
* Fotis Jannidis contacts sponsors as soon as the ultimate recipient of reimbursements is determined<br />
<br />
====Program: 1. day====<br />
<br />
* start at 02:00pm<br />
* one coffee break<br />
* 2 sessions, 4 talks each, 15 min/talk + 5 min/discussion<br />
* (edition) project presentations<br />
<br />
====Program: 2. day====<br />
<br />
* start at 09:00am<br />
* present the SIG work: 45 min<br />
* 10:00am: discussion<br />
* 11:00am: coffee<br />
* 11:30am: discussion<br />
* 01:00pm: lunch<br />
* 02:00pm:discussion, wrap up, roadmap, outlook<br />
* finish at 03:30pm<br />
<br />
====Technical support====<br />
<br />
* we want to offer an optional web publication service, so attendants can refer online to all the examples during discussion<br />
<br />
==Specification==<br />
<br />
===Deliverables===<br />
<br />
# a presentation of the draft specification at the conference<br />
# the XML schema<br />
# a contribution to the TEI guidelines<br />
<br />
===Theoretical framework===<br />
<br />
* the specification shall be independent of presuppositions made by a particular theoretical framework<br />
* therefore a couple of typical dichotomies in editorial theory have to be recognized<br />
* first there is the notion of ''fact (or representation) vs. interpretation''<br />
* maybe we should think of differing ''levels of interpretation'' instead<br />
* reason: we might not be able to cleary differentiate between „what's there“ (document/fact) and „how does it relate“ (text/interpretation)<br />
* this leads to the second opposition, that is central to editorial theory: ''document vs. text''<br />
* Paolo D'Iorio explains the HyperNietzsche approach to handle this opposition<br />
* HyperNietzsche bases its functionality on a thorough manuscript description, that happens on the documentary level<br />
* the interpretative acts (constituting a text) build upon the manuscript description<br />
* to summarize the HyperNietzsche experience while trying to adopt TEI guidelines: the '''Text''' Encoding Initiative does not handle "the document level" very well thus far<br />
* for genetic editions though, this level is crucial<br />
<br />
===Methodology===<br />
<br />
* we want to propose a standard, we do not want (even better: we cannot) prescribe one, given the complex landscape of editorial practices<br />
* in the beginning we will work on a pseudo-encoding, which is tightly bound to our own terminology<br />
* in a second step, we will try to map this pseudo-encoding to the actual TEI encoding framework, probably in cooperation with someone from the TEI Council<br />
* the same step-by-step approach shall be taken for the standardization process<br />
* first we develop an application profile aka. TEI customization<br />
* when that proves to be of general interest, we rework it into a separate chapter for the TEI guidelines<br />
<br />
==Aspects of Genetic Editions==<br />
<br />
===Topological description on the document level===<br />
<br />
* the description functions hierarchically on 3 levels:<br />
* highest level: the ''page''<br />
* pages contain ''zones''<br />
* zones are are nestable, groupable, can overlap and have a depth level (aka. belong to a layer)<br />
* zones are arbitrary in as much as they can be defined by layout and/or semantic aspects<br />
* on a third level, zones normally contain (among other entities) ''lines''<br />
<br />
===Dating===<br />
<br />
* on the one hand the dating of a witness may not be directly related to its encoded content, it therefore has to go into the header<br />
* on the other hand, dates added by the original author as metadata to the text on the witness should be encoded without necessarily going into the header [can be embedded within a Functional Mark]<br />
* dating can be justified by prose and/or by reference to a characteristic of a manuscript (e.g. hand)<br />
<br />
<teiHeader><br />
<datingDesc><br />
<dating ....><br />
<div1>...</div1><br />
</dating><br />
</datingDesc><br />
</teiHeader><br />
<br />
===Time/ Chronology===<br />
<br />
* we want to express time as absolute and relative measures<br />
* express absolute time by adapting the existing date element/attributes; see http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ND.html#NDATTSda<br />
* express relative time as predecessor/successor-relationships<br />
** might be a direct relationship: next, previous<br />
** might be a „sorting“ relationship: before, after<br />
** relationships may also be expressed via a numbering scheme<br />
** relationships may have 1:n cardinality, e.g. one witness is dated before a set of others<br />
<br />
===Grouping changes (“changesets”)===<br />
<br />
* forming changesets is necessary to group text passages, which all form one revision<br />
* implemented either via a wrapping element (e.g. <revision/>) or via a stand-off mechanism for spatially disparate changes<br />
<br />
===Alterations===<br />
<br />
* alterations are practically related to the ''collation'' of texts<br />
* we need to deal with collation as a separate aspect of genetic editions<br />
* for example we need an expression for ''ommissions'' as a textual feature, that results from relating texts via collation<br />
* another set of alterations to be expressed is the one, that results from authors ''fixating'' a text passage by overwriting it (e.g. a penciled passage fixated with ink)<br />
* marginal notes have to be differentiated from ''functional marks'' commanding an alteration (e.g. „move this passage over there”)<br />
<br />
===Deletions===<br />
<br />
====“marked as used”====<br />
<br />
* passages happen to be striked through, which marks the passage to be used at another location<br />
* two-step markup<br />
* first: markup the block on the document level<br />
* secondly: describe the function (“mark as used”)<br />
<br />
====Overwriting====<br />
<br />
* overwriting is a special case of a deletion<br />
<br />
===Undoing alterations===<br />
<br />
* how to express on the document level, that an alteration has been taken back, e.g. a striked through passage being reinstantiated via a dotted underlining<br />
* <restore/> already exists for undoing an deletion, but we might need a more general approach<br />
* possible solutions via an element or via an attribute “undo”<br />
* proposal: add a generic element <undo/> with an attribute referring to the action being undone<br />
* can be further differentiated by a type attribute, e.g. immediate correction vs. revising<br />
* this is preliminary: we have to open up this solution to discussion<br />
<br />
===Transpositions===<br />
<br />
* current approach: express transpositions as pairs of additions and deletions<br />
* we also want to express transpositions as an atomic operation, because it might be expressed as such on the document as well<br />
* first: make the segment to be transposed adressable<br />
* either via an identifiable wrapping element or via a “cross-cutting” <seg/><br />
* secondly: markup “functional mark”, which might be in the text (e.g. a superlinear “add ‘is’ here”), with an element like <fm/><br />
* relate the functional mark to the identified passages<br />
<br />
<add><fm type="addition">add</fm> ‘is’ here</add><br />
<br />
* either refer to the passage added via attributes<br />
* or it might be implicit, which passage is transposed, because the <fm/> is contained in an <add/> or <delete/><br />
* maybe we can generalize the idea of a ''functional mark'' (<fm/>)<br />
* we markup passages on the representational level, but also on the semantic level, on which they command alterations<br />
<br />
===Clarification===<br />
<br />
* think of clarification as a ''repetition'' of a text<br />
* this idea can also offer a solution for encoding fixations<br />
<br />
<repetition type="clarification|fixation|..." position="superlinear" hand=""/><br />
<br />
===Correction===<br />
<br />
* supply an additional attribute to <add/> and <delete/> that typifies the alteration (e. g. “instant correction”)<br />
<br />
===“Coordinate system”===<br />
<br />
* how to express genetic relationships on an inter- and intra-document level<br />
* we need a scheme for addressing the linked passages and a means for describing such relationships/ links<br />
* adopt the HyperNietzsche concept: relational description via ''paths''<br />
* paths are typed, depending on the relation expressed (e.g. a timeline, a conceptual link …)<br />
* paths: define complete paths via a set of vertices (''steps'')<br />
* <linkGrp/> is a candidate for grouping a set of steps forming a path<br />
* steps of a path can be ordered or unordered, but that might belon to the aspect of uncertainty)<br />
* the steps of a path should be describable, so the expressed relationships can be justified or further characterized<br />
* we should import concepts from the critical apparatus here: http://www.tei-c.org/release/doc/tei-p5-doc/en/html/TC.html<br />
* relationships might be ''transitive'' in nature, should we express that as well<br />
* then: is there a potential scope conflict between the TEI and other graph-oriented markup languages like RDF/XML<br />
* maybe we can differentiate between the description of the relationships itself and their characterization/justification<br />
* the relationships might be described as an RDF graph, which is augmented with TEI-based prose<br />
<br />
==Roadmap==<br />
<br />
===Organizational tasks===<br />
<br />
* conference announcement: Malte Rehbein<br />
* call for more examples on the TEI list: Elena Pierazzo<br />
* apply for a panel on the next TEI Member’s meeting<br />
<br />
===Specification tasks===<br />
<br />
* as we were not able to deal with all aspects, the further work on the remaining ones is distributed among the SIG members<br />
<br />
{| class="wikitable" border="1" cellpadding="2"<br />
|-<br />
! Aspect !! responsible<br />
|-<br />
| Alternatives || Elena Pierazzo<br />
|-<br />
| Substitution || Malte Rehbein<br />
|-<br />
| Gaps || Fotis Jannidis<br />
|-<br />
| Editorial Decisions || Paolo D'Iorio<br />
|-<br />
| Uncertainty || Malte Rehbein<br />
|-<br />
| Critical Apparatus || Fotis Jannidis<br />
|-<br />
|Textual Constitution || Elena Pierazzo, Paolo D'Iorio<br />
|}<br />
<br />
===Upcoming events===<br />
<br />
{| class="wikitable" border="1" cellpadding="2"<br />
|- class="hintergrundfarbe5"<br />
! Date/Time !! Event<br />
|-<br />
| 21.04. 09:30am CET || conference talk: content-related issues<br />
|-<br />
| 05.05. 09:30am CET || conference talk: organization-related issues<br />
|-<br />
| 11.05. || deadline for publication of draft specification to the conf. participants<br />
|-<br />
| 14./15.05. || Conference in Paris<br />
|-<br />
| 16.05. || post-conference meeting<br />
|-<br />
| 16.06. 09:30 CET || conference talk: specification<br />
|-<br />
| 07.08. 09:30 CET || conference talk: specification<br />
|-<br />
| 16./17.09. || Wuerzburg: finalize specification (place might change; depends on funding)<br />
|}</div>Elenaphttps://wiki.tei-c.org/index.php?title=Minutes_London_03-2009&diff=5569Minutes London 03-20092009-03-19T13:45:12Z<p>Elenap: /* Theoretical framework */</p>
<hr />
<div>''Present: Katrin Dennerlein, Paolo D'Iorio, Fotis Jannidis, Gregor Middell, Elena Pierazzo, Malte Rehbein, Moritz Wissenbach.''<br />
<br />
''Discussion led by Elena Pierazzo, minutes by Gregor Middell.''<br />
<br />
==Organization==<br />
<br />
===Technical infrastructure/ Workflow===<br />
<br />
* coordination takes place in this wiki<br />
* project has to be announced on the news bar at http://tei-c.org/<br />
* wiki will be reorganzied in 2 distinct parts: a public one (with announcements, draft specs …) and an internal one with information, that is less interesting to the general public<br />
* list of sponsors has to go on the wiki as well<br />
* ''Google Docs'' used for the (internal) specification process<br />
* draft versions of the specification are checked out as a PDF document and put on the wiki every week, so we can gather feedback<br />
<br />
===Conference in Paris===<br />
<br />
* ITEM provides up to 3 rooms for the conference; definitely 1 on both days, possibly 3 on the second<br />
* Paolo D'Iorio coordinates the room allocation with ITEM<br />
* we want to offer lunch at the conference (attendants shall ''confirm'' their participation upon registration)<br />
* SIG will invite speakers and organizers to a dinner as well<br />
* Paolo D'Iorio organizes hotel, dinner bookings, internet access, beamer<br />
* Malte Rehbein manages registration<br />
* registration deadline is 17.04. (first come, first serve)<br />
* conference program will be split up into 2 sections:<br />
** a common program with presentations and public discussions<br />
** a workgroup-oriented program with talks, which are oriented toward certain aspects of the specification<br />
<br />
====Spending institution====<br />
<br />
* TU Darmstadt/ Universität Würzburg (chair of Fotis Jannidis) will be spending institution<br />
* in case of any restrictions NUI Galway can serve as a workaround<br />
* funding will be provided by ALLC, ACH, TEI and Galway<br />
* Fotis Jannidis contacts sponsors as soon as the ultimate recipient of reimbursements is determined<br />
<br />
====Program: 1. day====<br />
<br />
* start at 02:00pm<br />
* one coffee break<br />
* 2 sessions, 4 talks each, 15 min/talk + 5 min/discussion<br />
* (edition) project presentations<br />
<br />
====Program: 2. day====<br />
<br />
* start at 09:00am<br />
* present the SIG work: 45 min<br />
* 10:00am: discussion<br />
* 11:00am: coffee<br />
* 11:30am: discussion<br />
* 01:00pm: lunch<br />
* 02:00pm:discussion, wrap up, roadmap, outlook<br />
* finish at 03:30pm<br />
<br />
====Technical support====<br />
<br />
* we want to offer an optional web publication service, so attendants can refer online to all the examples during discussion<br />
<br />
==Specification==<br />
<br />
===Deliverables===<br />
<br />
# a presentation of the draft specification at the conference<br />
# the XML schema<br />
# a contribution to the TEI guidelines<br />
<br />
===Theoretical framework===<br />
<br />
* the specification shall be independent of presuppositions made by a particular theoretical framework<br />
* therefore a couple of typical dichotomies in editorial theory have to be recognized<br />
* first there is the notion of ''fact (or representation) vs. interpretation''<br />
* maybe we should think of differing ''levels of interpretation'' instead<br />
* reason: we might not be able to cleary differentiate between „what's there“ (document/fact) and „how does it relate“ (text/interpretation)<br />
* this leads to the second opposition, that is central to editorial theory: ''document vs. text''<br />
* Paolo D'Iorio explains the HyperNietzsche approach to handle this opposition<br />
* HyperNietzsche bases its functionality on a thorough manuscript description, that happens on the documentary level<br />
* the interpretative acts (constituting a text) build upon the manuscript description<br />
* to summarize the HyperNietzsche experience while trying to adopt TEI guidelines: the '''Text''' Encoding Initiative does not handle "the document level" very well thus far<br />
* for genetic editions though, this level is crucial<br />
<br />
===Methodology===<br />
<br />
* we want to propose a standard, we do not want (even better: we cannot) prescribe one, given the complex landscape of editorial practices<br />
* in the beginning we will work on a pseudo-encoding, which is tightly bound to our own terminology<br />
* in a second step, we will try to map this pseudo-encoding to the actual TEI encoding framework, probably in cooperation with someone from the TEI Council<br />
* the same step-by-step approach shall be taken for the standardization process<br />
* first we develop an application profile aka. TEI customization<br />
* when that proves to be of general interest, we rework it into a separate chapter for the TEI guidelines<br />
<br />
==Aspects of Genetic Editions==<br />
<br />
===Topological description on the document level===<br />
<br />
* the description functions hierarchically on 3 levels:<br />
* highest level: the ''page''<br />
* pages contain ''zones''<br />
* zones are are nestable, groupable, can overlap and have a depth level (aka. belong to a layer)<br />
* zones are arbitrary in as much as they can be defined by layout and/or semantic aspects<br />
* on a third level, zones normally contain (among other entities) ''lines''<br />
<br />
===Dating===<br />
<br />
* on the one handthe dating of a witness may not be directly related to its encoded content, it therefore has to go into the header<br />
* on the other hand, dates added by the original author as metadata to the text on the witness should be encoded without necessarily going into the header<br />
* dating can be justified by prose and/or by reference to a characteristic of a manuscript (e.g. hand)<br />
<br />
<teiHeader><br />
<datingDesc><br />
<dating ....><br />
<div1>...</div1><br />
</dating><br />
</datingDesc><br />
</teiHeader><br />
<br />
===Time/ Chronology===<br />
<br />
* we want to express time as absolute and relative measures<br />
* express absolute time by adapting the existing date element/attributes; see http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ND.html#NDATTSda<br />
* express relative time as predecessor/successor-relationships<br />
** might be a direct relationship: next, previous<br />
** might be a „sorting“ relationship: before, after<br />
** relationships may also be expressed via a numbering scheme<br />
** relationships may have 1:n cardinality, e.g. one witness is dated before a set of others<br />
<br />
===Grouping changes (“changesets”)===<br />
<br />
* forming changesets is necessary to group text passages, which all form one revision<br />
* implemented either via a wrapping element (e.g. <revision/>) or via a stand-off mechanism for spatially disparate changes<br />
<br />
===Alterations===<br />
<br />
* alterations are practically related to the ''collation'' of texts<br />
* we need to deal with collation as a separate aspect of genetic editions<br />
* for example we need an expression for ''ommissions'' as a textual feature, that results from relating texts via collation<br />
* another set of alterations to be expressed is the one, that results from authors ''fixating'' a text passage by overwriting it (e.g. a penciled passage fixated with ink)<br />
* marginal notes have to be differentiated from ''functional marks'' commanding an alteration (e.g. „move this passage over there”)<br />
<br />
===Deletions===<br />
<br />
====“marked as used”====<br />
<br />
* passages happen to be striked through, which marks the passage to be used at another location<br />
* two-step markup<br />
* first: markup the block on the document level<br />
* secondly: describe the function (“mark as used”)<br />
<br />
====Overwriting====<br />
<br />
* overwriting is a special case of a deletion<br />
<br />
===Undoing alterations===<br />
<br />
* how to express on the document level, that an alteration has been taken back, e.g. a striked through passage being reinstantiated via a dotted underlining<br />
* <restore/> already exists for undoing an deletion, but we might need a more general approach<br />
* possible solutions via an element or via an attribute “undo”<br />
* proposal: add a generic element <undo/> with an attribute referring to the action being undone<br />
* can be further differentiated by a type attribute, e.g. immediate correction vs. revising<br />
* this is preliminary: we have to open up this solution to discussion<br />
<br />
===Transpositions===<br />
<br />
* current approach: express transpositions as pairs of additions and deletions<br />
* we also want to express transpositions as an atomic operation, because it might be expressed as such on the document as well<br />
* first: make the segment to be transposed adressable<br />
* either via an identifiable wrapping element or via a “cross-cutting” <seg/><br />
* secondly: markup “functional mark”, which might be in the text (e.g. a superlinear “add ‘is’ here”), with an element like <fm/><br />
* relate the functional mark to the identified passages<br />
<br />
<add><fm type="addition">add</fm> ‘is’ here</add><br />
<br />
* either refer to the passage added via attributes<br />
* or it might be implicit, which passage is transposed, because the <fm/> is contained in an <add/> or <delete/><br />
* maybe we can generalize the idea of a ''functional mark'' (<fm/>)<br />
* we markup passages on the representational level, but also on the semantic level, on which they command alterations<br />
<br />
===Clarification===<br />
<br />
* think of clarification as a ''repetition'' of a text<br />
* this idea can also offer a solution for encoding fixations<br />
<br />
<repetition type="clarification|fixation|..." position="superlinear" hand=""/><br />
<br />
===Correction===<br />
<br />
* supply an additional attribute to <add/> and <delete/> that typifies the alteration (e. g. “instant correction”)<br />
<br />
===“Coordinate system”===<br />
<br />
* how to express genetic relationships on an inter- and intra-document level<br />
* we need a scheme for addressing the linked passages and a means for describing such relationships/ links<br />
* adopt the HyperNietzsche concept: relational description via ''paths''<br />
* paths are typed, depending on the relation expressed (e.g. a timeline, a conceptual link …)<br />
* paths: define complete paths via a set of vertices (''steps'')<br />
* <linkGrp/> is a candidate for grouping a set of steps forming a path<br />
* steps of a path can be ordered or unordered, but that might belon to the aspect of uncertainty)<br />
* the steps of a path should be describable, so the expressed relationships can be justified or further characterized<br />
* we should import concepts from the critical apparatus here: http://www.tei-c.org/release/doc/tei-p5-doc/en/html/TC.html<br />
* relationships might be ''transitive'' in nature, should we express that as well<br />
* then: is there a potential scope conflict between the TEI and other graph-oriented markup languages like RDF/XML<br />
* maybe we can differentiate between the description of the relationships itself and their characterization/justification<br />
* the relationships might be described as an RDF graph, which is augmented with TEI-based prose<br />
<br />
==Roadmap==<br />
<br />
===Organizational tasks===<br />
<br />
* conference announcement: Malte Rehbein<br />
* call for more examples on the TEI list: Elena Pierazzo<br />
* apply for a panel on the next TEI Member’s meeting<br />
<br />
===Specification tasks===<br />
<br />
* as we were not able to deal with all aspects, the further work on the remaining ones is distributed among the SIG members<br />
<br />
{| class="wikitable" border="1" cellpadding="2"<br />
|-<br />
! Aspect !! responsible<br />
|-<br />
| Alternatives || Elena Pierazzo<br />
|-<br />
| Substitution || Malte Rehbein<br />
|-<br />
| Gaps || Fotis Jannidis<br />
|-<br />
| Editorial Decisions || Paolo D'Iorio<br />
|-<br />
| Uncertainty || Malte Rehbein<br />
|-<br />
| Critical Apparatus || Fotis Jannidis<br />
|-<br />
|Textual Constitution || Elena Pierazzo, Paolo D'Iorio<br />
|}<br />
<br />
===Upcoming events===<br />
<br />
{| class="wikitable" border="1" cellpadding="2"<br />
|- class="hintergrundfarbe5"<br />
! Date/Time !! Event<br />
|-<br />
| 21.04. 09:30am CET || conference talk: content-related issues<br />
|-<br />
| 05.05. 09:30am CET || conference talk: organization-related issues<br />
|-<br />
| 11.05. || deadline for publication of draft specification to the conf. participants<br />
|-<br />
| 14./15.05. || Conference in Paris<br />
|-<br />
| 16.05. || post-conference meeting<br />
|-<br />
| 16.06. 09:30 CET || conference talk: specification<br />
|-<br />
| 07.08. 09:30 CET || conference talk: specification<br />
|-<br />
| 16./17.09. || Wuerzburg: finalize specification (place might change; depends on funding)<br />
|}</div>Elenaphttps://wiki.tei-c.org/index.php?title=Textual_alterations&diff=5502Textual alterations2009-03-13T10:55:44Z<p>Elenap: /* Textual alterations */</p>
<hr />
<div>[[Category:Genetic Editions]]<br />
todo: Add examples for all forms. Especially difficult ones<br />
<br />
== Textual alterations ==<br />
<br />
* Addition, <br />
* deletion, <br />
* transposition, <br />
* clarification, <br />
* substitution (should allow for cases like stylisitic rewriting and total rewriting, looser way), <br />
* restoration, <br />
* overwriting, <br />
* immediate/instant correction, <br />
* functional mark (marked as used, printer marks, later scribe marks), <br />
* gap for a planned insertion (which has been filled or not)<br />
* alternatives<br />
* fixation<br />
<br />
Here are Hilde Bøe's slides with examples from Henrik Ibsen's manuscripts: http://www.emunch.no/tei-mm-2008/index_ms.html<br />
<br />
These categories appear to refer to the graphical form of the text. A distinction should be drawn, however, between the logical editing operations that change the flow of the text, which only include insertion, deletion, substitution and transposition, and their graphical form in manuscripts. For example:<br />
<br />
* Clarification is a purely graphical rewriting of the same text. It is really a kind of substitution<br />
* Restoration is the deletion of a crossing-out. This is a case of variation in the markup itself<br />
* Overwriting - another case of substitution, but with a different graphical detail<br />
* Transposition cannot be represented adequately via markup. Since entire blocks of text, or single words, can be transposed across the boundaries of tags, how can this be done without breaking the schema of the XML document? In theory anything, even markup itself, can be transposed e.g. movement of a line-break: word&lt;/l&gt;&lt;l&gt; into &lt;/l&gt;&lt;l&gt;word. A mechanism for representing transposition is needed, in addition to some way of recording its visual appearance. See D. Smith Textual Variation and Version Control in the TEI, Computers and the Humanities, 33.1-2 (1999) 103-112, who argues that we need to go 'one level above' the markup to represent transposition or variation in markup.<br />
* Deletion in markup seems simple but is also problematic: how does one represent, for example, the deletion of a paragraph boundary? &lt;del&gt;&lt;/p&gt;&lt;p&gt;&lt;/del&gt;??? or deletion of underlining on its own without also enclosing the underlined word in a &lt;del&gt; element?<br />
* immediate/instant correction is really a partial version which disturbs the flow: 'I think &lt;del&gt;the...&lt;/del&gt; a reason is ...' There is really one original version here that has no continuation in the sentence.<br />
In principle textual variation is ''outside'' the text, even if the text contains markup. Any other representation leads to serious shortcomings.</div>Elenaphttps://wiki.tei-c.org/index.php?title=Textual_alterations&diff=5501Textual alterations2009-03-12T17:49:20Z<p>Elenap: /* Textual alterations */</p>
<hr />
<div>[[Category:Genetic Editions]]<br />
todo: Add examples for all forms. Especially difficult ones<br />
<br />
== Textual alterations ==<br />
<br />
* Addition, <br />
* deletion, <br />
* transposition, <br />
* clarification, <br />
* substitution (should allow for cases like stylisitic rewriting and total rewriting, looser way), <br />
* restoration, <br />
* overwriting, <br />
* immediate/instant correction, <br />
* functional mark (marked as used, printer marks, later scribe marks), <br />
* gap for a planned insertion (which has been filled or not)<br />
* alternatives<br />
* fusion<br />
<br />
Here are Hilde Bøe's slides with examples from Henrik Ibsen's manuscripts: http://www.emunch.no/tei-mm-2008/index_ms.html<br />
<br />
These categories appear to refer to the graphical form of the text. A distinction should be drawn, however, between the logical editing operations that change the flow of the text, which only include insertion, deletion, substitution and transposition, and their graphical form in manuscripts. For example:<br />
<br />
* Clarification is a purely graphical rewriting of the same text. It is really a kind of substitution<br />
* Restoration is the deletion of a crossing-out. This is a case of variation in the markup itself<br />
* Overwriting - another case of substitution, but with a different graphical detail<br />
* Transposition cannot be represented adequately via markup. Since entire blocks of text, or single words, can be transposed across the boundaries of tags, how can this be done without breaking the schema of the XML document? In theory anything, even markup itself, can be transposed e.g. movement of a line-break: word&lt;/l&gt;&lt;l&gt; into &lt;/l&gt;&lt;l&gt;word. A mechanism for representing transposition is needed, in addition to some way of recording its visual appearance. See D. Smith Textual Variation and Version Control in the TEI, Computers and the Humanities, 33.1-2 (1999) 103-112, who argues that we need to go 'one level above' the markup to represent transposition or variation in markup.<br />
* Deletion in markup seems simple but is also problematic: how does one represent, for example, the deletion of a paragraph boundary? &lt;del&gt;&lt;/p&gt;&lt;p&gt;&lt;/del&gt;??? or deletion of underlining on its own without also enclosing the underlined word in a &lt;del&gt; element?<br />
* immediate/instant correction is really a partial version which disturbs the flow: 'I think &lt;del&gt;the...&lt;/del&gt; a reason is ...' There is really one original version here that has no continuation in the sentence.<br />
In principle textual variation is ''outside'' the text, even if the text contains markup. Any other representation leads to serious shortcomings.</div>Elenaphttps://wiki.tei-c.org/index.php?title=Genetic_Editions&diff=4787Genetic Editions2008-11-17T14:43:06Z<p>Elenap: /* Useful Resources */</p>
<hr />
<div>At the Members Meeting in London in November, a panel focussing on the problem of genetic editions is planned.<br />
<br />
== Meetings ==<br />
Workshop during the TEI-meeting 2008 in London -> [[minutes London 2008]]<br />
<br />
== Useful Resources ==<br />
* HyperNietsche<br />
** [http://www.hypernietzsche.org/doc/HNML/ HMNL], in [http://www.hypernietzsche.org/doc/HNML/HNML-engl.pdf English], and in [http://www.hypernietzsche.org/doc/HNML/HNML-de.pdf German]<br />
** Article on [http://computerphilologie.uni-muenchen.de/jg03/saller.html HMNL]<br />
** Matteo D’Alfonso, Harald Saller: [http://www.germanistik.ch/publikation.php?id=Kodierung_und_Darstellung Kodierung und Darstellung von Schreibschichten in der elektronischen Edition des Druckmanuskripts zu Der Wanderer und sein Schatten]. In: Literatur und Literaturwissenschaften auf dem Weg zu den digitalen Medien - Eine Standortbestimmung, hg. v. Michael Stolz. Online veröffentlicht bei Gisi + Loop.<br />
* Genetic Markup Language (In French) [http://staff.cch.kcl.ac.uk/~epierazzo/GML-fr.pdf download it from here]<br />
* Gabler, Hans Walter<br />
** "Das wissenschaftliche Edieren als Funktion der Dokumente." Published at: [http://computerphilologie.tu-darmstadt.de/jg06/gabler.html http://computerphilologie.tu-darmstadt.de/jg06/gabler.html]; and in: Jahrbuch für Computerphilologie 8 (2007), 55-62.<br />
** "The Primacy of the Document in Editing." Ecdotica 4 (2007), 197-207. [http://staff.cch.kcl.ac.uk/~epierazzo/Gabler%20Ecdotica%204.pdf download it from here]<br />
** "La prééminence du document dans l’édition." In: Françoise Leriche et Cécile Maynard (eds.), De l'hypertexte au manuscrit. L'apport et les limites du numérique pour l'édition et la valorisation de manuscrits littéraires modernes. (Recherches & Travaux, no. 72.) Grenoble: ELLUG, 2008, pp. 39-51.[http://staff.cch.kcl.ac.uk/~epierazzo/GABLER%20definitif.pdf download it from here]</div>Elenaphttps://wiki.tei-c.org/index.php?title=Genetic_Editions&diff=4735Genetic Editions2008-10-31T15:09:58Z<p>Elenap: /* Useful Resources */</p>
<hr />
<div>At the Members Meeting in London in November, a panel focussing on the problem of genetic editions is planned.<br />
<br />
== Useful Resources ==<br />
* HyperNietsche<br />
** [http://www.hypernietzsche.org/doc/HNML/ HMNL], in [http://www.hypernietzsche.org/doc/HNML/HNML-engl.pdf English], and in [http://www.hypernietzsche.org/doc/HNML/HNML-de.pdf German]<br />
** Article on [http://computerphilologie.uni-muenchen.de/jg03/saller.html HMNL]<br />
* Gabler, Hans Walter<br />
** "Das wissenschaftliche Edieren als Funktion der Dokumente." Published at: [http://computerphilologie.tu-darmstadt.de/jg06/gabler.html http://computerphilologie.tu-darmstadt.de/jg06/gabler.html]; and in: Jahrbuch für Computerphilologie 8 (2007), 55-62.<br />
** "The Primacy of the Document in Editing." Ecdotica 4 (2007), 197-207. [http://staff.cch.kcl.ac.uk/~epierazzo/Gabler%20Ecdotica%204.pdf download it from here]<br />
** "La prééminence du document dans l’édition." In: Françoise Leriche et Cécile Maynard (eds.), De l'hypertexte au manuscrit. L'apport et les limites du numérique pour l'édition et la valorisation de manuscrits littéraires modernes. (Recherches & Travaux, no. 72.) Grenoble: ELLUG, 2008, pp. 39-51.[http://staff.cch.kcl.ac.uk/~epierazzo/GABLER%20definitif.pdf download it from here]</div>Elenaphttps://wiki.tei-c.org/index.php?title=Genetic_Editions&diff=4730Genetic Editions2008-10-28T19:39:42Z<p>Elenap: </p>
<hr />
<div>At the Members Meeting in London in November, a panel focussing on the problem of genetic editions is planned.<br />
<br />
== Useful Resources ==<br />
* HyperNietsche<br />
** [http://www.hypernietzsche.org/doc/HNML/ HMNL], in [http://www.hypernietzsche.org/doc/HNML/HNML-engl.pdf English], and in [http://www.hypernietzsche.org/doc/HNML/HNML-de.pdf German]<br />
** Article on [http://computerphilologie.uni-muenchen.de/jg03/saller.html HMNL]</div>Elenaphttps://wiki.tei-c.org/index.php?title=SIG:MSS&diff=4729SIG:MSS2008-10-28T19:27:23Z<p>Elenap: /* News */</p>
<hr />
<div>== TEI Special Interest Group on Manuscripts (TEI MS SIG) ==<br />
<br />
=== News ===<br />
<br />
'''Agenda for the SIG meeting: London 8th of November 2008.'''<br />
<br />
* 9:30-11:00 <br />
** Working papers panel: presentations and discussion<br />
* 11:30-13:00 <br />
** End of discussion (if necessary)<br />
** Working Groups:<br />
*** Manuscript description Enhancement (chair: Torsten Schassan); the WG Wiki page can be found [[msDesc enhancement|here]]<br />
*** Genetic editions (chair: Fotis Iannidis); the WG Wiki page can be found [[Genetic Editions |here]]<br />
* 14:00-15:30<br />
** Working Groups: continuation<br />
* 16:00-17:30<br />
** Working Group: report and discussion<br />
** Approval of possible actions (features requests; bug reports, etc.)<br />
** Drawing of an agenda for the SIG on going work<br />
<br />
=== Introduction ===<br />
<br />
The goal of the TEI Special Interest Group on Manuscripts is to bring together users of the TEI who wish to improve the encoding strategies for marking up transcriptions and editions of manuscript materials.<br />
<br />
This SIG will explore a range of issues common to editing manuscripts, including: <br />
# how to handle time based encoding<br />
# how to record place based encoding<br />
# how to encode fragments<br />
# how to record codicology (the substance of the medium, ink stints, etc); Robinson noted that the TEI already has mechanisms to record this, but it needs to be better documented<br />
# issues of substitutions<br />
# issues of variation<br />
# to clarify the role of using the critical apparatus tagset in manuscript transcription (which is dependent on whether one is encoding an edition or encoding a manuscript transcription)<br />
<br />
It will do this by: <br />
* running a mailing list on this topic<br />
* assess the TEI and suggest improvements/alterations to the TEI-Council<br />
<br />
The SIG is setup by: <br />
* Elena Pierazzo of the University of Pisa (Italy)<br />
* Susan Schreibman of the Maryland Institute for Technology in the Humanities (US), who is also a member of the TEI Council.<br />
* Edward Vanhoutte of the Centre for [http://www.kantl.be/ctb/ Scholarly Editing and Document Studies] of the Royal Academy of Dutch Language and Literature (Belgium), who is also a member of the TEI Council.<br />
<br />
The SIG is convened by Elena Pierazzo who also manages the TEI-MS-SIG List<br />
<br />
The SIG runs a mailing list on this topic. To join visit http://listserv.brown.edu/tei-ms-sig.html<br />
<br />
=== Activities ===<br />
<br />
The SIG met at the Third Annual TEI Members' Meeting in Nancy, France on 08 November 2003. The report can be found [http://www.tei-c.org.uk/Activities/SIG/Manuscript/mssigr01.html here].<br />
<br />
The second meeting of the SIG was held at the Fourth Annual TEI Members' Meeting at Johns Hopkins University, Baltimore, USA, 23 October 2004. The report can be found [http://www.tei-c.org.uk/Activities/SIG/Manuscript/mssigr02.html here].<br />
<br />
The third meeting of the SIG was held at Seventh Annual TEI Member's Meeting at University of Maryland, College Park, 3nd of November 2007. The agenda of the meeting can be found [[MS SIG Agenda 2007|here]]; the report can be found [[MS SIG Report 07|here]]. During the meeting several task forces were created to deal with specific problems: the task forces main page can be found [[MS task forces|here]].<br />
<br />
=== Useful links ===<br />
<br />
==== Manuscript Description ====<br />
<br />
Projects, resources, guidelines concerning MS description.<br />
<br />
* [http://www.tei-c.org/release/doc/tei-p5-doc/html/MS.html TEI P5: 13. Manuscript Description]<br />
* [http://enrich.manuscriptorium.com ENRICH project] - standardising and aggregating medieval manuscript descriptions. See also [http://tei.oucs.ox.ac.uk/ENRICH/ OUCS ENRICH Website] containing ENRICH Schemas, ODD, Documentation and Training Materials.<br />
* [http://sunsite3.berkeley.edu/Scriptorium/ Digital Scriptorium] (see especially the [http://sunsite3.berkeley.edu/Scriptorium/technical/description_dtd.html DESCRIPTION DTD] page).<br />
* [http://www.hab.de/forschung/projekte/master-e.htm MASTER - Interface format for the description of medieval manuscripts]<br />
* [http://www.tei-c.org/Activities/MS/msw05.xml Reviews of the manuscript description chapter: A summary]<br />
<br />
==== Manuscript Transcription ====<br />
<br />
Projects, resources, guidelines concerning MS transcription.<br />
<br />
* [http://www.cdlib.org/inside/diglib/stwg/ms/ CDL Encoding Guidelines for Manuscripts and Rare Books]<br />
* [http://www.kantl.be/ctb/project/dalf/ DALF: Digital Archive of Letters in Flanders]<br />
* [http://www.scriptorium.columbia.edu/ Digital Scriptorium] (see especially the [https://www1.columbia.edu/sec/cu/libraries/bts/digital_scriptorium/technical/ds-xml/transcription_dtd/index.html TRANSCRIPTION DTD] and [https://www1.columbia.edu/sec/cu/libraries/bts/digital_scriptorium/technical/ds-xml/description_dtd/index.html DESCRIPTION DTD] pages).<br />
* [[EpiDoc]], guidelines for transcribing ancient texts<br />
* [http://skaldic.arts.usyd.edu.au/docs/guidelines/guide.html Guidelines for the electronic edition of the skaldic corpus]<br />
* [http://web.uvic.ca/hrd/lydgate/pilot.htm Partial Transcription of John Lydgate's "Fall of Princes"]<br />
* [http://webapp1.dlib.indiana.edu/newton/index.jsp The Chymistry of Isaac Newton]<br />
* [http://gandalf.aksis.uib.no/menota/guidelines/ The Menota handbook]<br />
* [http://www.newtonproject.ic.ac.uk/prism.php?id=1 The Newton Project] (see also [http://ahds.ac.uk/creating/case-studies/newton/index.htm The Newton Project: Implementing and Exploiting XML]).<br />
* [http://www.whitmanarchive.org/guidelines/ The Walt Whitman Archive Encoding Guidelines for Poetry Manuscripts]<br />
* [http://jefferson.village.virginia.edu/seenet/piers/protocoltran.html Transcriptional Protocols: Piers Plowman Electronic Archive and SEENET]<br />
* [http://elec.enc.sorbonne.fr/chroniqueslatines/ Chroniques latines de Saint-Denis] : critical edition using TEI P4 (but we hope to migrate in P5 this year) : [http://elec.enc.sorbonne.fr/chroniqueslatines/xml/chroniquesstdenis.xml XML Files]<br />
* [http://lemo.irht.cnrs.fr/43/43-12.htm Réflexions sur l'utilisation de la TEI pour encoder les sources diplomatiques] and [http://elec.enc.sorbonne.fr/cartulaireblanc/guidebalisage/ Guide du balisage du Cartulaire blanc] : two resources in French<br />
<br />
[[Category:SIG|MSS]]</div>Elenaphttps://wiki.tei-c.org/index.php?title=SIG:MSS&diff=4728SIG:MSS2008-10-28T19:25:01Z<p>Elenap: /* News */</p>
<hr />
<div>== TEI Special Interest Group on Manuscripts (TEI MS SIG) ==<br />
<br />
=== News ===<br />
<br />
'''Agenda for the SIG meeting: London 8th of November 2008.'''<br />
<br />
* 9:30-11:00 <br />
** Working papers panel: presentations and discussion<br />
* 11:30-13:00 <br />
** End of discussion (if necessary)<br />
** Working Groups:<br />
*** Manuscript description Enhancement (chair: Torsten Schassan); the WG Wiki page can be found [[Manuscript Description enhancement|here]]<br />
*** Genetic editions (chair: Fotis Iannidis); <br />
* 14:00-15:30<br />
** Working Groups: continuation<br />
* 16:00-17:30<br />
** Working Group: report and discussion<br />
** Approval of possible actions (features requests; bug reports, etc.)<br />
** Drawing of an agenda for the SIG on going work<br />
<br />
=== Introduction ===<br />
<br />
The goal of the TEI Special Interest Group on Manuscripts is to bring together users of the TEI who wish to improve the encoding strategies for marking up transcriptions and editions of manuscript materials.<br />
<br />
This SIG will explore a range of issues common to editing manuscripts, including: <br />
# how to handle time based encoding<br />
# how to record place based encoding<br />
# how to encode fragments<br />
# how to record codicology (the substance of the medium, ink stints, etc); Robinson noted that the TEI already has mechanisms to record this, but it needs to be better documented<br />
# issues of substitutions<br />
# issues of variation<br />
# to clarify the role of using the critical apparatus tagset in manuscript transcription (which is dependent on whether one is encoding an edition or encoding a manuscript transcription)<br />
<br />
It will do this by: <br />
* running a mailing list on this topic<br />
* assess the TEI and suggest improvements/alterations to the TEI-Council<br />
<br />
The SIG is setup by: <br />
* Elena Pierazzo of the University of Pisa (Italy)<br />
* Susan Schreibman of the Maryland Institute for Technology in the Humanities (US), who is also a member of the TEI Council.<br />
* Edward Vanhoutte of the Centre for [http://www.kantl.be/ctb/ Scholarly Editing and Document Studies] of the Royal Academy of Dutch Language and Literature (Belgium), who is also a member of the TEI Council.<br />
<br />
The SIG is convened by Elena Pierazzo who also manages the TEI-MS-SIG List<br />
<br />
The SIG runs a mailing list on this topic. To join visit http://listserv.brown.edu/tei-ms-sig.html<br />
<br />
=== Activities ===<br />
<br />
The SIG met at the Third Annual TEI Members' Meeting in Nancy, France on 08 November 2003. The report can be found [http://www.tei-c.org.uk/Activities/SIG/Manuscript/mssigr01.html here].<br />
<br />
The second meeting of the SIG was held at the Fourth Annual TEI Members' Meeting at Johns Hopkins University, Baltimore, USA, 23 October 2004. The report can be found [http://www.tei-c.org.uk/Activities/SIG/Manuscript/mssigr02.html here].<br />
<br />
The third meeting of the SIG was held at Seventh Annual TEI Member's Meeting at University of Maryland, College Park, 3nd of November 2007. The agenda of the meeting can be found [[MS SIG Agenda 2007|here]]; the report can be found [[MS SIG Report 07|here]]. During the meeting several task forces were created to deal with specific problems: the task forces main page can be found [[MS task forces|here]].<br />
<br />
=== Useful links ===<br />
<br />
==== Manuscript Description ====<br />
<br />
Projects, resources, guidelines concerning MS description.<br />
<br />
* [http://www.tei-c.org/release/doc/tei-p5-doc/html/MS.html TEI P5: 13. Manuscript Description]<br />
* [http://enrich.manuscriptorium.com ENRICH project] - standardising and aggregating medieval manuscript descriptions. See also [http://tei.oucs.ox.ac.uk/ENRICH/ OUCS ENRICH Website] containing ENRICH Schemas, ODD, Documentation and Training Materials.<br />
* [http://sunsite3.berkeley.edu/Scriptorium/ Digital Scriptorium] (see especially the [http://sunsite3.berkeley.edu/Scriptorium/technical/description_dtd.html DESCRIPTION DTD] page).<br />
* [http://www.hab.de/forschung/projekte/master-e.htm MASTER - Interface format for the description of medieval manuscripts]<br />
* [http://www.tei-c.org/Activities/MS/msw05.xml Reviews of the manuscript description chapter: A summary]<br />
<br />
==== Manuscript Transcription ====<br />
<br />
Projects, resources, guidelines concerning MS transcription.<br />
<br />
* [http://www.cdlib.org/inside/diglib/stwg/ms/ CDL Encoding Guidelines for Manuscripts and Rare Books]<br />
* [http://www.kantl.be/ctb/project/dalf/ DALF: Digital Archive of Letters in Flanders]<br />
* [http://www.scriptorium.columbia.edu/ Digital Scriptorium] (see especially the [https://www1.columbia.edu/sec/cu/libraries/bts/digital_scriptorium/technical/ds-xml/transcription_dtd/index.html TRANSCRIPTION DTD] and [https://www1.columbia.edu/sec/cu/libraries/bts/digital_scriptorium/technical/ds-xml/description_dtd/index.html DESCRIPTION DTD] pages).<br />
* [[EpiDoc]], guidelines for transcribing ancient texts<br />
* [http://skaldic.arts.usyd.edu.au/docs/guidelines/guide.html Guidelines for the electronic edition of the skaldic corpus]<br />
* [http://web.uvic.ca/hrd/lydgate/pilot.htm Partial Transcription of John Lydgate's "Fall of Princes"]<br />
* [http://webapp1.dlib.indiana.edu/newton/index.jsp The Chymistry of Isaac Newton]<br />
* [http://gandalf.aksis.uib.no/menota/guidelines/ The Menota handbook]<br />
* [http://www.newtonproject.ic.ac.uk/prism.php?id=1 The Newton Project] (see also [http://ahds.ac.uk/creating/case-studies/newton/index.htm The Newton Project: Implementing and Exploiting XML]).<br />
* [http://www.whitmanarchive.org/guidelines/ The Walt Whitman Archive Encoding Guidelines for Poetry Manuscripts]<br />
* [http://jefferson.village.virginia.edu/seenet/piers/protocoltran.html Transcriptional Protocols: Piers Plowman Electronic Archive and SEENET]<br />
* [http://elec.enc.sorbonne.fr/chroniqueslatines/ Chroniques latines de Saint-Denis] : critical edition using TEI P4 (but we hope to migrate in P5 this year) : [http://elec.enc.sorbonne.fr/chroniqueslatines/xml/chroniquesstdenis.xml XML Files]<br />
* [http://lemo.irht.cnrs.fr/43/43-12.htm Réflexions sur l'utilisation de la TEI pour encoder les sources diplomatiques] and [http://elec.enc.sorbonne.fr/cartulaireblanc/guidebalisage/ Guide du balisage du Cartulaire blanc] : two resources in French<br />
<br />
[[Category:SIG|MSS]]</div>Elenaphttps://wiki.tei-c.org/index.php?title=SIG:MSS&diff=4727SIG:MSS2008-10-28T11:34:33Z<p>Elenap: /* News */</p>
<hr />
<div>== TEI Special Interest Group on Manuscripts (TEI MS SIG) ==<br />
<br />
=== News ===<br />
<br />
'''Agenda for the SIG meeting: London 8th of November 2008.'''<br />
<br />
* 9:30-11:00 <br />
** Working papers panel: presentations and discussion<br />
* 11:30-13:00 <br />
** End of discussion (if necessary)<br />
** Working Groups:<br />
*** Manuscript description Enhancement (chair: Torsten Schassan)<br />
*** Genetic editions (chair: Fotis Iannidis)<br />
* 14:00-15:30<br />
** Working Groups: continuation<br />
* 16:00-17:30<br />
** Working Group: report and discussion<br />
** Approval of possible actions (features requests; bug reports, etc.)<br />
** Drawing of an agenda for the SIG on going work<br />
<br />
=== Introduction ===<br />
<br />
The goal of the TEI Special Interest Group on Manuscripts is to bring together users of the TEI who wish to improve the encoding strategies for marking up transcriptions and editions of manuscript materials.<br />
<br />
This SIG will explore a range of issues common to editing manuscripts, including: <br />
# how to handle time based encoding<br />
# how to record place based encoding<br />
# how to encode fragments<br />
# how to record codicology (the substance of the medium, ink stints, etc); Robinson noted that the TEI already has mechanisms to record this, but it needs to be better documented<br />
# issues of substitutions<br />
# issues of variation<br />
# to clarify the role of using the critical apparatus tagset in manuscript transcription (which is dependent on whether one is encoding an edition or encoding a manuscript transcription)<br />
<br />
It will do this by: <br />
* running a mailing list on this topic<br />
* assess the TEI and suggest improvements/alterations to the TEI-Council<br />
<br />
The SIG is setup by: <br />
* Elena Pierazzo of the University of Pisa (Italy)<br />
* Susan Schreibman of the Maryland Institute for Technology in the Humanities (US), who is also a member of the TEI Council.<br />
* Edward Vanhoutte of the Centre for [http://www.kantl.be/ctb/ Scholarly Editing and Document Studies] of the Royal Academy of Dutch Language and Literature (Belgium), who is also a member of the TEI Council.<br />
<br />
The SIG is convened by Elena Pierazzo who also manages the TEI-MS-SIG List<br />
<br />
The SIG runs a mailing list on this topic. To join visit http://listserv.brown.edu/tei-ms-sig.html<br />
<br />
=== Activities ===<br />
<br />
The SIG met at the Third Annual TEI Members' Meeting in Nancy, France on 08 November 2003. The report can be found [http://www.tei-c.org.uk/Activities/SIG/Manuscript/mssigr01.html here].<br />
<br />
The second meeting of the SIG was held at the Fourth Annual TEI Members' Meeting at Johns Hopkins University, Baltimore, USA, 23 October 2004. The report can be found [http://www.tei-c.org.uk/Activities/SIG/Manuscript/mssigr02.html here].<br />
<br />
The third meeting of the SIG was held at Seventh Annual TEI Member's Meeting at University of Maryland, College Park, 3nd of November 2007. The agenda of the meeting can be found [[MS SIG Agenda 2007|here]]; the report can be found [[MS SIG Report 07|here]]. During the meeting several task forces were created to deal with specific problems: the task forces main page can be found [[MS task forces|here]].<br />
<br />
=== Useful links ===<br />
<br />
==== Manuscript Description ====<br />
<br />
Projects, resources, guidelines concerning MS description.<br />
<br />
* [http://www.tei-c.org/release/doc/tei-p5-doc/html/MS.html TEI P5: 13. Manuscript Description]<br />
* [http://enrich.manuscriptorium.com ENRICH project] - standardising and aggregating medieval manuscript descriptions. See also [http://tei.oucs.ox.ac.uk/ENRICH/ OUCS ENRICH Website] containing ENRICH Schemas, ODD, Documentation and Training Materials.<br />
* [http://sunsite3.berkeley.edu/Scriptorium/ Digital Scriptorium] (see especially the [http://sunsite3.berkeley.edu/Scriptorium/technical/description_dtd.html DESCRIPTION DTD] page).<br />
* [http://www.hab.de/forschung/projekte/master-e.htm MASTER - Interface format for the description of medieval manuscripts]<br />
* [http://www.tei-c.org/Activities/MS/msw05.xml Reviews of the manuscript description chapter: A summary]<br />
<br />
==== Manuscript Transcription ====<br />
<br />
Projects, resources, guidelines concerning MS transcription.<br />
<br />
* [http://www.cdlib.org/inside/diglib/stwg/ms/ CDL Encoding Guidelines for Manuscripts and Rare Books]<br />
* [http://www.kantl.be/ctb/project/dalf/ DALF: Digital Archive of Letters in Flanders]<br />
* [http://www.scriptorium.columbia.edu/ Digital Scriptorium] (see especially the [https://www1.columbia.edu/sec/cu/libraries/bts/digital_scriptorium/technical/ds-xml/transcription_dtd/index.html TRANSCRIPTION DTD] and [https://www1.columbia.edu/sec/cu/libraries/bts/digital_scriptorium/technical/ds-xml/description_dtd/index.html DESCRIPTION DTD] pages).<br />
* [[EpiDoc]], guidelines for transcribing ancient texts<br />
* [http://skaldic.arts.usyd.edu.au/docs/guidelines/guide.html Guidelines for the electronic edition of the skaldic corpus]<br />
* [http://web.uvic.ca/hrd/lydgate/pilot.htm Partial Transcription of John Lydgate's "Fall of Princes"]<br />
* [http://webapp1.dlib.indiana.edu/newton/index.jsp The Chymistry of Isaac Newton]<br />
* [http://gandalf.aksis.uib.no/menota/guidelines/ The Menota handbook]<br />
* [http://www.newtonproject.ic.ac.uk/prism.php?id=1 The Newton Project] (see also [http://ahds.ac.uk/creating/case-studies/newton/index.htm The Newton Project: Implementing and Exploiting XML]).<br />
* [http://www.whitmanarchive.org/guidelines/ The Walt Whitman Archive Encoding Guidelines for Poetry Manuscripts]<br />
* [http://jefferson.village.virginia.edu/seenet/piers/protocoltran.html Transcriptional Protocols: Piers Plowman Electronic Archive and SEENET]<br />
* [http://elec.enc.sorbonne.fr/chroniqueslatines/ Chroniques latines de Saint-Denis] : critical edition using TEI P4 (but we hope to migrate in P5 this year) : [http://elec.enc.sorbonne.fr/chroniqueslatines/xml/chroniquesstdenis.xml XML Files]<br />
* [http://lemo.irht.cnrs.fr/43/43-12.htm Réflexions sur l'utilisation de la TEI pour encoder les sources diplomatiques] and [http://elec.enc.sorbonne.fr/cartulaireblanc/guidebalisage/ Guide du balisage du Cartulaire blanc] : two resources in French<br />
<br />
[[Category:SIG|MSS]]</div>Elenaphttps://wiki.tei-c.org/index.php?title=SIG:MSS&diff=4706SIG:MSS2008-10-09T08:27:51Z<p>Elenap: /* News */</p>
<hr />
<div>== TEI Special Interest Group on Manuscripts (TEI MS SIG) ==<br />
<br />
=== News ===<br />
<br />
'''Agenda for the SIG meeting: London 8th of November 2008.'''<br />
<br />
* 9:30-11:00 <br />
** Working papers panel: presentations and discussion<br />
* 11:30-13:00 <br />
** End of discussion (if necessary)<br />
** Working Groups:<br />
*** Manuscript description Enhancement<br />
*** Genetic editions<br />
* 14:00-15:30<br />
** Working Groups: continuation<br />
* 16:00-17:30<br />
** Working Group: report and discussion<br />
** Approval of possible actions (features requests; bug reports, etc.)<br />
** Drawing of an agenda for the SIG on going work<br />
<br />
=== Introduction ===<br />
<br />
The goal of the TEI Special Interest Group on Manuscripts is to bring together users of the TEI who wish to improve the encoding strategies for marking up transcriptions and editions of manuscript materials.<br />
<br />
This SIG will explore a range of issues common to editing manuscripts, including: <br />
# how to handle time based encoding<br />
# how to record place based encoding<br />
# how to encode fragments<br />
# how to record codicology (the substance of the medium, ink stints, etc); Robinson noted that the TEI already has mechanisms to record this, but it needs to be better documented<br />
# issues of substitutions<br />
# issues of variation<br />
# to clarify the role of using the critical apparatus tagset in manuscript transcription (which is dependent on whether one is encoding an edition or encoding a manuscript transcription)<br />
<br />
It will do this by: <br />
* running a mailing list on this topic<br />
* assess the TEI and suggest improvements/alterations to the TEI-Council<br />
<br />
The SIG is setup by: <br />
* Elena Pierazzo of the University of Pisa (Italy)<br />
* Susan Schreibman of the Maryland Institute for Technology in the Humanities (US), who is also a member of the TEI Council.<br />
* Edward Vanhoutte of the Centre for [http://www.kantl.be/ctb/ Scholarly Editing and Document Studies] of the Royal Academy of Dutch Language and Literature (Belgium), who is also a member of the TEI Council.<br />
<br />
The SIG is convened by Elena Pierazzo who also manages the TEI-MS-SIG List<br />
<br />
The SIG runs a mailing list on this topic. To join visit http://listserv.brown.edu/tei-ms-sig.html<br />
<br />
=== Activities ===<br />
<br />
The SIG met at the Third Annual TEI Members' Meeting in Nancy, France on 08 November 2003. The report can be found [http://www.tei-c.org.uk/Activities/SIG/Manuscript/mssigr01.html here].<br />
<br />
The second meeting of the SIG was held at the Fourth Annual TEI Members' Meeting at Johns Hopkins University, Baltimore, USA, 23 October 2004. The report can be found [http://www.tei-c.org.uk/Activities/SIG/Manuscript/mssigr02.html here].<br />
<br />
The third meeting of the SIG was held at Seventh Annual TEI Member's Meeting at University of Maryland, College Park, 3nd of November 2007. The agenda of the meeting can be found [[MS SIG Agenda 2007|here]]; the report can be found [[MS SIG Report 07|here]]. During the meeting several task forces were created to deal with specific problems: the task forces main page can be found [[MS task forces|here]].<br />
<br />
=== Useful links ===<br />
<br />
==== Manuscript Description ====<br />
<br />
Projects, resources, guidelines concerning MS description.<br />
<br />
* [http://www.tei-c.org/release/doc/tei-p5-doc/html/MS.html TEI P5: 13. Manuscript Description]<br />
* [http://sunsite3.berkeley.edu/Scriptorium/ Digital Scriptorium] (see especially the [http://sunsite3.berkeley.edu/Scriptorium/technical/description_dtd.html DESCRIPTION DTD] page).<br />
* [http://www.hab.de/forschung/projekte/master-e.htm MASTER - Interface format for the description of medieval manuscripts]<br />
* [http://www.tei-c.org/Activities/MS/msw05.xml Reviews of the manuscript description chapter: A summary]<br />
<br />
==== Manuscript Transcription ====<br />
<br />
Projects, resources, guidelines concerning MS transcription.<br />
<br />
* [http://www.cdlib.org/inside/diglib/stwg/ms/ CDL Encoding Guidelines for Manuscripts and Rare Books]<br />
* [http://www.kantl.be/ctb/project/dalf/ DALF: Digital Archive of Letters in Flanders]<br />
* [http://www.scriptorium.columbia.edu/ Digital Scriptorium] (see especially the [https://www1.columbia.edu/sec/cu/libraries/bts/digital_scriptorium/technical/ds-xml/transcription_dtd/index.html TRANSCRIPTION DTD] and [https://www1.columbia.edu/sec/cu/libraries/bts/digital_scriptorium/technical/ds-xml/description_dtd/index.html DESCRIPTION DTD] pages).<br />
* [[EpiDoc]], guidelines for transcribing ancient texts<br />
* [http://skaldic.arts.usyd.edu.au/docs/guidelines/guide.html Guidelines for the electronic edition of the skaldic corpus]<br />
* [http://web.uvic.ca/hrd/lydgate/pilot.htm Partial Transcription of John Lydgate's "Fall of Princes"]<br />
* [http://webapp1.dlib.indiana.edu/newton/index.jsp The Chymistry of Isaac Newton]<br />
* [http://gandalf.aksis.uib.no/menota/guidelines/ The Menota handbook]<br />
* [http://www.newtonproject.ic.ac.uk/prism.php?id=1 The Newton Project] (see also [http://ahds.ac.uk/creating/case-studies/newton/index.htm The Newton Project: Implementing and Exploiting XML]).<br />
* [http://www.whitmanarchive.org/guidelines/ The Walt Whitman Archive Encoding Guidelines for Poetry Manuscripts]<br />
* [http://jefferson.village.virginia.edu/seenet/piers/protocoltran.html Transcriptional Protocols: Piers Plowman Electronic Archive and SEENET]<br />
* [http://elec.enc.sorbonne.fr/chroniqueslatines/ Chroniques latines de Saint-Denis] : critical edition using TEI P4 (but we hope to migrate in P5 this year) : [http://elec.enc.sorbonne.fr/chroniqueslatines/xml/chroniquesstdenis.xml XML Files]<br />
* [http://lemo.irht.cnrs.fr/43/43-12.htm Réflexions sur l'utilisation de la TEI pour encoder les sources diplomatiques] and [http://elec.enc.sorbonne.fr/cartulaireblanc/guidebalisage/ Guide du balisage du Cartulaire blanc] : two resources in French<br />
<br />
[[Category:SIG|MSS]]</div>Elenaphttps://wiki.tei-c.org/index.php?title=MilestoneXSLT&diff=4473MilestoneXSLT2008-06-23T15:05:02Z<p>Elenap: New page: == Authorship == {| | ''Author'' | Raffaele Viglianti and Elena Pierazzo, King’s College London, [mailto:raffaele.viglianti@kcl.ac.uk raffaele.viglianti@kcl.ac.uk] [mailto:elena.pierazz...</p>
<hr />
<div>== Authorship ==<br />
{| <br />
| ''Author''<br />
| Raffaele Viglianti and Elena Pierazzo, King’s College London, [mailto:raffaele.viglianti@kcl.ac.uk raffaele.viglianti@kcl.ac.uk] [mailto:elena.pierazzo@kcl.ac.uk elena.pierazzo@kcl.ac.uk]<br />
|- <br />
| ''Last revised''<br />
| 2008-06-23<br />
|-<br />
| ''Previous version''<br />
| none<br />
|}<br />
<br />
<br />
== Summary ==<br />
This is a group of XSLT scripts for managing milestones (page breaks, line breaks, hand shifts, etc.) in XSLT 2.0 (but can work also in 1.0, see below). <br />
These scripts are part of a poster presented at DH2008 by Elena Pierazzo and Raffaele Viglianti: XSLT (2.0) handbook for processing multiple hierarchies.<br />
Three different approaches are presented, ordered by complexity of the input and of the script as well.<br />
<br />
== Required Input ==<br />
Script 1: expanding milestones<br />
<br />
<pre><nowiki><br />
<TEI><br />
<text><br />
<body><br />
<p><br />
Give me then your house &amp; <w>Grounds</w><br />
<lb/><br />
I ask for nothing else <br />
</p><br />
</body><br />
</text><br />
</TEI><br />
</nowiki></pre><br />
<br />
Script 2: splitting elements, then expanding milestones<br />
<br />
<pre><nowiki><br />
<TEI><br />
<text><br />
<body><br />
<p><br />
<del rend=”overstrike”>Card room where<br />
<lb/><br />
nine out of ten had no inclination</del><br />
</p><br />
</body><br />
</text><br />
</TEI><br />
</nowiki></pre><br />
<br />
Script 3: looping on textual nodes<br />
<br />
<pre><nowiki><br />
<TEI><br />
<text><br />
<body><br />
<pb xml:id=”blvolthird-03”/><br />
<div><br />
<p><handShift new=”#a2”/><br />
For James Edward Austen</p><br />
</div><br />
<div><br />
<p><handShift new=”#a2”/><br />
Jane Austen May 6<hi rend=”sup”>th</hi> 1792</p><br />
</div><br />
</body><br />
</text><br />
</TEI><br />
</nowiki></pre><br />
<br />
<br />
== Expected Output ==<br />
<br />
Script 1<br />
<br />
the function would produce the following XML fragment as output:<br />
<pre><nowiki><br />
<TEI><br />
<text><br />
<body><br />
<p><br />
<lb>Give me then your house &amp; <w>Grounds</w></lb><br />
<lb>I ask for nothing else</lb><br />
</p><br />
</body><br />
</text><br />
</TEI><br />
</nowiki></pre><br />
<br />
Script 2<br />
<br />
<pre><nowiki><br />
<TEI><br />
<text><br />
<body><br />
<p><br />
<lb><br />
<del rend=”overstrike”>Card room where</del><br />
</lb><lb><br />
<del rend=”overstrike”>nine out of ten had no inclination</del><br />
</lb><br />
</p><br />
</body><br />
</text><br />
</TEI><br />
</nowiki></pre><br />
<br />
Script 3<br />
<br />
<pre><nowiki><br />
<html><br />
<body><br />
<div class=”pb”>blvolthird-03”</div><br />
<div><br />
<p><span class=”pencil”>For James Edward Austen</span></p><br />
</div><br />
<div><br />
<p><br />
<span class=”default”>Jane Austen May 6</span><sip><span class=”default”>th</span></sup> <span class=”default”>1792</span></p><br />
</div><br />
</body><br />
</html><br />
</nowiki></pre><br />
<br />
<br />
== Known Restrictions or Problems ==<br />
<br />
The code shown below requires XSLT 2. With XSLT 1 it is possible to emulate the “step” approaches by using more than one script and intermediate files<br />
<br />
<br />
The running time is very similar using a standalone saxon process or embedded in Apache Cocoon<br />
<br />
== Code ==<br />
Script 1<br />
<br />
<pre><nowiki><br />
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="2.0" <br />
xpath-default-namespace="http://www.tei-c.org/ns/1.0" xmlns:tei="http://www.tei-c.org/ns/1.0"><br />
<xsl:output method="xml" indent="yes" encoding="UTF-8”/><br />
<xsl:template match="node()|@*"><br />
<!-- Copy the current node --><br />
<xsl:copy><br />
<!-- Including any child nodes it has and any attributes --><br />
<xsl:apply-templates select="node()|@*"/><br />
</xsl:copy><br />
</xsl:template><br />
<xsl:template match="p"><br />
<xsl:variable name="cur-p" select="generate-id(.)"/><br />
<p><xsl:choose><br />
<xsl:when test="lb"><br />
<xsl:for-each select="lb"><br />
<lb><br />
<xsl:sequence select="parent::p/@*"/><br />
<br />
<xsl:apply-templates<br />
select="preceding::*[parent::p[generate-id()=$cur-p]]|preceding::text()[parent::p[generate-id()=$cur-p]]"/><br />
<xsl:apply-templates<br />
select="preceding::*/@*[parent::p[generate-id()=$cur-p]]"/><br />
</lb><br />
<lb><br />
<xsl:sequence select="parent::p/@*"/><br />
<xsl:sequence<br />
select="following::*[parent::p[generate-id()=$cur-p]]|following::text()[parent::p[generate-id()=$cur-p]]"/><br />
<xsl:sequence select="following::*/@*[parent::p[generate-id()=$cur-p]]"/><br />
</lb><br />
</xsl:for-each><br />
</xsl:when><br />
<xsl:otherwise><br />
<xsl:sequence select="."/><br />
</xsl:otherwise><br />
</xsl:choose><br />
</p><br />
</xsl:template><br />
</xsl:stylesheet><br />
</nowiki></pre><br />
<br />
Script 2<br />
<pre><nowiki><br />
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="2.0"<br />
xpath-default-namespace="http://www.tei-c.org/ns/1.0" xmlns="http://www.tei-c.org/ns/1.0"><br />
<xsl:output method="xhtml" indent="yes" encoding="UTF-8"<br />
doctype-public="-//W3C//DTD XHTML 1.0 Strict//EN"/><br />
<xsl:strip-space elements="*"/><br />
<br />
<xsl:variable name="step1"><br />
<xsl:call-template name="one"/><br />
</xsl:variable><br />
<br />
<xsl:variable name="step2"><br />
<xsl:apply-templates select="$step1" mode="step2"/><br />
</xsl:variable><br />
<br />
<xsl:template match="*" mode="step1"><br />
<xsl:copy><br />
<xsl:sequence select="@*"/><br />
<xsl:apply-templates mode="step1"/><br />
</xsl:copy><br />
</xsl:template><br />
<br />
<xsl:template match="del" mode="step1"><br />
<xsl:variable name="cur-del" select="generate-id(.)"/><br />
<xsl:choose><br />
<xsl:when test="lb"><br />
<xsl:for-each select="lb"><br />
<del><br />
<xsl:choose><br />
<xsl:when test="parent::del/@type"><br />
<xsl:variable name="type" select="generate-id(parent::del/@type)"/><br />
<xsl:sequence select="parent::del/@*[generate-id() != $type]"/><br />
</xsl:when><br />
<xsl:otherwise><br />
<xsl:sequence select="parent::del/@*"/><br />
</xsl:otherwise><br />
</xsl:choose><br />
<xsl:apply-templates<br />
select="preceding::*[parent::del[generate-id()=$cur-del]]|preceding::text()[parent::del[generate-id()=$cur-del]]"/><br />
<xsl:apply-templates<br />
select="preceding::*/@*[parent::del[generate-id()=$cur-del]]"/><br />
</del><br />
<br />
<lb><br />
<xsl:sequence select="@*"/><br />
</lb><br />
<br />
<del><br />
<xsl:sequence select="parent::del/@*"/><br />
<xsl:sequence<br />
select="following::*[parent::del[generate-id()=$cur-del]]|following::text()[parent::del[generate-id()=$cur-del]]"/><br />
<xsl:sequence select="following::*/@*[parent::del[generate-id()=$cur-del]]"/><br />
</del><br />
</xsl:for-each><br />
</xsl:when><br />
<xsl:otherwise><br />
<xsl:sequence select="."/><br />
</xsl:otherwise><br />
</xsl:choose><br />
<br />
</xsl:template><br />
<br />
<xsl:template name="one"><br />
<xsl:apply-templates select="TEI" mode="step1"/><br />
</xsl:template><br />
<br />
<xsl:template match="/" mode="step2"><br />
<html><br />
<body><br />
<xsl:apply-templates mode="step2"/><br />
</body><br />
</html><br />
</xsl:template><br />
<br />
<xsl:template match="p" mode="step2"><br />
<xsl:variable name="cur-p" select="generate-id(.)"/><br />
<p><br />
<xsl:choose><br />
<xsl:when test="exists(descendant::lb)"><br />
<xsl:for-each select="descendant::lb"><br />
<xsl:variable name="cur-lb" select="generate-id(.)"/><br />
<span class="line"><br />
<xsl:for-each<br />
select="preceding::node()[ancestor::p[generate-id()=$cur-p]]"><br />
<br />
<xsl:choose><br />
<xsl:when test="not(self::lb)"><br />
<xsl:if<br />
test="generate-id(following::lb[1])=$cur-lb and generate-id(parent::node()[1])=$cur-p"><br />
<xsl:apply-templates select="." mode="step2"/><br />
</xsl:if><br />
</xsl:when><br />
<xsl:otherwise><br />
<xsl:apply-templates select="." mode="step2"/><br />
</xsl:otherwise><br />
</xsl:choose><br />
</xsl:for-each><br />
</span><br />
<xsl:if test="not(following::lb[parent::p[generate-id()=$cur-p]])"><br />
<span class="line"><br />
<xsl:for-each<br />
select="following::*[ancestor::p[generate-id()=$cur-p]]"><br />
<xsl:apply-templates select="." mode="step2"/><br />
</xsl:for-each><br />
</span><br />
</xsl:if><br />
</xsl:for-each><br />
</xsl:when><br />
<xsl:otherwise><br />
<xsl:apply-templates mode="step2"/><br />
</xsl:otherwise><br />
</xsl:choose><br />
</p><br />
</xsl:template><br />
<br />
<xsl:template match="del" mode="step2"><br />
<del><br />
<xsl:apply-templates mode="step2"/><br />
</del><br />
</xsl:template><br />
<br />
<!-- OUTPUTTING --><br />
<br />
<xsl:template match="/"><br />
<xsl:sequence select="$step2"/><br />
</xsl:template><br />
<br />
</xsl:stylesheet><br />
</nowiki></pre><br />
<br />
Script 3<br />
<pre><nowiki><br />
<?xml version="1.0" encoding="UTF-8"?><br />
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="2.0"<br />
xpath-default-namespace="http://www.tei-c.org/ns/1.0" xmlns="http://www.tei-c.org/ns/1.0"><br />
<xsl:output method="xhtml" indent="yes" encoding="UTF-8"<br />
doctype-public="-//W3C//DTD XHTML 1.0 Strict//EN"/><br />
<xsl:strip-space elements="*"/><br />
<br />
<xsl:variable name="step1"><br />
<xsl:call-template name="one"/><br />
</xsl:variable><br />
<br />
<xsl:variable name="step2"><br />
<xsl:apply-templates select="$step1" mode="step2"/><br />
</xsl:variable><br />
<br />
<xsl:template match="*" mode="step1"><br />
<xsl:copy><br />
<xsl:sequence select="@*"/><br />
<xsl:apply-templates mode="step1"/><br />
</xsl:copy><br />
</xsl:template><br />
<br />
<xsl:template match="text()[not(ancestor::teiHeader)]" mode="step1"><br />
<handShift><br />
<xsl:sequence select="preceding::handShift[1]/@new"/><br />
<xsl:value-of select="."/><br />
</handShift><br />
</xsl:template><br />
<br />
<xsl:template match="handShift" mode="step1"/><br />
<br />
<xsl:template name="one"><br />
<xsl:apply-templates select="TEI" mode="step1"/><br />
</xsl:template><br />
<br />
<xsl:template match="/" mode="step2"><br />
<html><br />
<body><br />
<xsl:apply-templates mode="step2"/><br />
</body><br />
</html><br />
</xsl:template><br />
<br />
<xsl:template match="p" mode="step2"><br />
<xsl:variable name="cur-p" select="generate-id(.)"/><br />
<p><br />
<xsl:choose><br />
<xsl:when test="exists(descendant::lb)"><br />
<xsl:for-each select="descendant::lb"><br />
<xsl:variable name="cur-lb" select="generate-id(.)"/><br />
<span class="line"><br />
<xsl:for-each<br />
select="preceding::node()[ancestor::p[generate-id()=$cur-p]]"><br />
<xsl:choose><br />
<xsl:when test="not(self::lb)"><br />
<xsl:if<br />
test="generate-id(following::lb[1])=$cur-lb and generate-id(parent::node()[1])=$cur-p"><br />
<xsl:apply-templates select="." mode="step2"/><br />
</xsl:if><br />
</xsl:when><br />
<xsl:otherwise><br />
<xsl:apply-templates select="." mode="step2"/><br />
</xsl:otherwise><br />
</xsl:choose><br />
</xsl:for-each><br />
</span><br />
<br />
<xsl:if test="not(following::lb[parent::p[generate-id()=$cur-p]])"><br />
<span class="line"><br />
<xsl:for-each<br />
select="following::*[ancestor::p[generate-id()=$cur-p]]"><br />
<xsl:apply-templates select="." mode="step2"/><br />
</xsl:for-each><br />
</span><br />
</xsl:if><br />
<br />
</xsl:for-each><br />
</xsl:when><br />
<xsl:otherwise><br />
<xsl:apply-templates mode="step2"/><br />
</xsl:otherwise><br />
</xsl:choose><br />
</p><br />
</xsl:template><br />
<br />
<xsl:template match="handShift" mode="step2"><br />
<span><br />
<xsl:attribute name="class"><br />
<xsl:choose><br />
<xsl:when test="@new= '#a2'"><br />
<xsl:text>default</xsl:text><br />
</xsl:when><br />
<xsl:when test="@new='#a1'"><br />
<xsl:text>pencil</xsl:text><br />
</xsl:when><br />
</xsl:choose><br />
</xsl:attribute><br />
<xsl:apply-templates mode="step2"/><br />
</span><br />
</xsl:template><br />
<!-- OUTPUTTING --><br />
<br />
<xsl:template match="/"><br />
<xsl:sequence select="$step2"/><br />
</xsl:template><br />
<br />
</xsl:stylesheet><br />
<br />
</nowiki></pre><br />
<br />
<br />
[[Category:XSLT]]</div>Elenaphttps://wiki.tei-c.org/index.php?title=SIG:MSS&diff=4270SIG:MSS2008-03-26T17:16:09Z<p>Elenap: Digital Scriptorium links updated</p>
<hr />
<div>== TEI Special Interest Group on Manuscripts (TEI MS SIG) ==<br />
<br />
=== Introduction ===<br />
<br />
The goal of the TEI Special Interest Group on Manuscripts is to bring together users of the TEI who wish to improve the encoding strategies for marking up transcriptions and editions of manuscript materials.<br />
<br />
This SIG will explore a range of issues common to editing manuscripts, including: <br />
# how to handle time based encoding<br />
# how to record place based encoding<br />
# how to encode fragments<br />
# how to record codicology (the substance of the medium, ink stints, etc); Robinson noted that the TEI already has mechanisms to record this, but it needs to be better documented<br />
# issues of substitutions<br />
# issues of variation<br />
# to clarify the role of using the critical apparatus tagset in manuscript transcription (which is dependent on whether one is encoding an edition or encoding a manuscript transcription)<br />
<br />
It will do this by: <br />
* running a mailing list on this topic<br />
* assess the TEI and suggest improvements/alterations to the TEI-Council<br />
<br />
The SIG is setup by: <br />
* Elena Pierazzo of the University of Pisa (Italy)<br />
* Susan Schreibman of the Maryland Institute for Technology in the Humanities (US), who is also a member of the TEI Council.<br />
* Edward Vanhoutte of the Centre for [http://www.kantl.be/ctb/ Scholarly Editing and Document Studies] of the Royal Academy of Dutch Language and Literature (Belgium), who is also a member of the TEI Council.<br />
<br />
The SIG is convened by Elena Pierazzo who also manages the TEI-MS-SIG List<br />
<br />
The SIG runs a mailing list on this topic. To join visit http://listserv.brown.edu/tei-ms-sig.html<br />
<br />
=== Activities ===<br />
<br />
The SIG met at the Third Annual TEI Members' Meeting in Nancy, France on 08 November 2003. The report can be found [http://www.tei-c.org.uk/Activities/SIG/Manuscript/mssigr01.html here].<br />
<br />
The second meeting of the SIG was held at the Fourth Annual TEI Members' Meeting at Johns Hopkins University, Baltimore, USA, 23 October 2004. The report can be found [http://www.tei-c.org.uk/Activities/SIG/Manuscript/mssigr02.html here].<br />
<br />
The third meeting of the SIG was held at Seventh Annual TEI Member's Meeting at University of Maryland, College Park, 3nd of November 2008. The agenda of the meeting can be found [[MS SIG Agenda 2008|here]]; the report can be found [[MS SIG Report 07|here]]. During the meeting several task forces were created to deal with specific problems: the task forces main page can be found [[MS task forces|here]].<br />
<br />
=== Useful links ===<br />
<br />
==== Manuscript Description ====<br />
<br />
Projects, resources, guidelines concerning MS description.<br />
<br />
* [http://www.tei-c.org/release/doc/tei-p5-doc/html/MS.html TEI P5: 13. Manuscript Description]<br />
* [http://sunsite3.berkeley.edu/Scriptorium/ Digital Scriptorium] (see especially the [http://sunsite3.berkeley.edu/Scriptorium/technical/description_dtd.html DESCRIPTION DTD] page).<br />
* [http://www.hab.de/forschung/projekte/master-e.htm MASTER - Interface format for the description of medieval manuscripts]<br />
* [http://www.tei-c.org/Activities/MS/msw05.xml Reviews of the manuscript description chapter: A summary]<br />
<br />
==== Manuscript Transcription ====<br />
<br />
Projects, resources, guidelines concerning MS transcription.<br />
<br />
* [http://www.cdlib.org/inside/diglib/stwg/ms/ CDL Encoding Guidelines for Manuscripts and Rare Books]<br />
* [http://www.kantl.be/ctb/project/dalf/ DALF: Digital Archive of Letters in Flanders]<br />
* [http://www.scriptorium.columbia.edu/ Digital Scriptorium] (see especially the [https://www1.columbia.edu/sec/cu/libraries/bts/digital_scriptorium/technical/ds-xml/transcription_dtd/index.html TRANSCRIPTION DTD] and [https://www1.columbia.edu/sec/cu/libraries/bts/digital_scriptorium/technical/ds-xml/description_dtd/index.html DESCRIPTION DTD] pages).<br />
* [http://skaldic.arts.usyd.edu.au/docs/guidelines/guide.html Guidelines for the electronic edition of the skaldic corpus]<br />
* [http://web.uvic.ca/hrd/lydgate/pilot.htm Partial Transcription of John Lydgate's "Fall of Princes"]<br />
* [http://webapp1.dlib.indiana.edu/newton/index.jsp The Chymistry of Isaac Newton]<br />
* [http://gandalf.aksis.uib.no/menota/guidelines/ The Menota handbook]<br />
* [http://www.newtonproject.ic.ac.uk/prism.php?id=1 The Newton Project] (see also [http://ahds.ac.uk/creating/case-studies/newton/index.htm The Newton Project: Implementing and Exploiting XML]).<br />
* [http://www.whitmanarchive.org/guidelines/ The Walt Whitman Archive Encoding Guidelines for Poetry Manuscripts]<br />
* [http://jefferson.village.virginia.edu/seenet/piers/protocoltran.html Transcriptional Protocols: Piers Plowman Electronic Archive and SEENET]<br />
* [http://elec.enc.sorbonne.fr/chroniqueslatines/ Chroniques latines de Saint-Denis] : critical edition using TEI P4 (but we hope to migrate in P5 this year) : [http://elec.enc.sorbonne.fr/chroniqueslatines/xml/chroniquesstdenis.xml XML Files]<br />
* [http://lemo.irht.cnrs.fr/43/43-12.htm Réflexions sur l'utilisation de la TEI pour encoder les sources diplomatiques] and [http://elec.enc.sorbonne.fr/cartulaireblanc/guidebalisage/ Guide du balisage du Cartulaire blanc] : two resources in French<br />
<br />
[[Category:SIG|MSS]]</div>Elenaphttps://wiki.tei-c.org/index.php?title=MS_task_forces&diff=3867MS task forces2007-11-16T11:40:51Z<p>Elenap: </p>
<hr />
<div># Genetic editions [[Genetic Editions|group page]]<br />
## Malte Rehbein <br />
## Fotis Jannidis <br />
## Edward Vanhoutte<br />
## Elena Pierazzo<br />
# MsDesc tiding up [[MsDesc enhancement|group page]]<br />
## Dot Porter <br />
## (Gabriel Bodard: a case study about fitting a marble inscribed monument into msDesc)<br />
## Jindřich Marek<br />
## Torsten Schassan<br />
# Facsimile [[facsimile enhancement|group page]]<br />
## Dot Porter <br />
## Hugh Cayssle <br />
## Torsten Schassan<br />
## Roberto Rosselli Del Turco<br />
# Critical Apparatus [[Critical Apparatus enhancement|group page]]<br />
## Hilde Bøe <br />
## Alexey Lavrentev <br />
# Representation of Primary sources enhancement (incl. writing direction) [[Representation of Primary sources enhancement|group page]]<br />
## Hilde Bøe<br />
## Roberto Rosselli Del Turco<br />
## Deborah Wright<br />
## Stephanie A. Schlitz<br />
## Alexey Lavrentev<br />
## Jindřich Marek<br />
## Zdeněk Uhlíř<br />
## Torsten Schassan<br />
## Edward Vanhoutte</div>Elenaphttps://wiki.tei-c.org/index.php?title=SIG:MSS&diff=3866SIG:MSS2007-11-16T11:40:23Z<p>Elenap: /* Activities */</p>
<hr />
<div>== TEI Special Interest Group on Manuscripts (TEI MS SIG) ==<br />
<br />
=== Introduction ===<br />
<br />
The goal of the TEI Special Interest Group on Manuscripts is to bring together users of the TEI who wish to improve the encoding strategies for marking up transcriptions and editions of manuscript materials.<br />
<br />
This SIG will explore a range of issues common to editing manuscripts, including: <br />
# how to handle time based encoding<br />
# how to record place based encoding<br />
# how to encode fragments<br />
# how to record codicology (the substance of the medium, ink stints, etc); Robinson noted that the TEI already has mechanisms to record this, but it needs to be better documented<br />
# issues of substitutions<br />
# issues of variation<br />
# to clarify the role of using the critical apparatus tagset in manuscript transcription (which is dependent on whether one is encoding an edition or encoding a manuscript transcription)<br />
<br />
It will do this by: <br />
* running a mailing list on this topic<br />
* assess the TEI and suggest improvements/alterations to the TEI-Council<br />
<br />
The SIG is setup by: <br />
* Elena Pierazzo of the University of Pisa (Italy)<br />
* Susan Schreibman of the Maryland Institute for Technology in the Humanities (US), who is also a member of the TEI Council.<br />
* Edward Vanhoutte of the Centre for [http://www.kantl.be/ctb/ Scholarly Editing and Document Studies] of the Royal Academy of Dutch Language and Literature (Belgium), who is also a member of the TEI Council.<br />
<br />
The SIG is convened by Elena Pierazzo who also manages the TEI-MS-SIG List<br />
<br />
The SIG runs a mailing list on this topic. To join visit http://listserv.brown.edu/tei-ms-sig.html<br />
<br />
=== Activities ===<br />
<br />
The SIG met at the Third Annual TEI Members' Meeting in Nancy, France on 08 November 2003. The report can be found [http://www.tei-c.org.uk/Activities/SIG/Manuscript/mssigr01.html here].<br />
<br />
The second meeting of the SIG was held at the Fourth Annual TEI Members' Meeting at Johns Hopkins University, Baltimore, USA, 23 October 2004. The report can be found [http://www.tei-c.org.uk/Activities/SIG/Manuscript/mssigr02.html here].<br />
<br />
The third meeting of the SIG was held at Seventh Annual TEI Member's Meeting at University of Maryland, College Park, 3nd of November 2008. The agenda of the meeting can be found [[MS SIG Agenda 2008|here]]; the report can be found [[MS SIG Report 07|here]]. During the meeting several task forces were created to deal with specific problems: the task forces main page can be found [[MS task forces|here]].<br />
<br />
=== Useful links ===<br />
<br />
==== Manuscript Description ====<br />
<br />
Projects, resources, guidelines concerning MS description.<br />
<br />
* [http://www.tei-c.org/release/doc/tei-p5-doc/html/MS.html TEI P5: 13. Manuscript Description]<br />
* [http://sunsite3.berkeley.edu/Scriptorium/ Digital Scriptorium] (see especially the [http://sunsite3.berkeley.edu/Scriptorium/technical/description_dtd.html DESCRIPTION DTD] page).<br />
* [http://www.hab.de/forschung/projekte/master-e.htm MASTER - Interface format for the description of medieval manuscripts]<br />
* [http://www.tei-c.org/Activities/MS/msw05.xml Reviews of the manuscript description chapter: A summary]<br />
<br />
==== Manuscript Transcription ====<br />
<br />
Projects, resources, guidelines concerning MS transcription.<br />
<br />
* [http://www.cdlib.org/inside/diglib/stwg/ms/ CDL Encoding Guidelines for Manuscripts and Rare Books]<br />
* [http://www.kantl.be/ctb/project/dalf/ DALF: Digital Archive of Letters in Flanders]<br />
* [http://sunsite3.berkeley.edu/Scriptorium/ Digital Scriptorium] (see especially the [http://sunsite3.berkeley.edu/Scriptorium/technical/transcription_dtd.html TRANSCRIPTION DTD] page).<br />
* [http://skaldic.arts.usyd.edu.au/docs/guidelines/guide.html Guidelines for the electronic edition of the skaldic corpus]<br />
* [http://web.uvic.ca/hrd/lydgate/pilot.htm Partial Transcription of John Lydgate's "Fall of Princes"]<br />
* [http://webapp1.dlib.indiana.edu/newton/index.jsp The Chymistry of Isaac Newton]<br />
* [http://gandalf.aksis.uib.no/menota/guidelines/ The Menota handbook]<br />
* [http://www.newtonproject.ic.ac.uk/prism.php?id=1 The Newton Project] (see also [http://ahds.ac.uk/creating/case-studies/newton/index.htm The Newton Project: Implementing and Exploiting XML]).<br />
* [http://www.whitmanarchive.org/guidelines/ The Walt Whitman Archive Encoding Guidelines for Poetry Manuscripts]<br />
* [http://jefferson.village.virginia.edu/seenet/piers/protocoltran.html Transcriptional Protocols: Piers Plowman Electronic Archive and SEENET]<br />
* [http://elec.enc.sorbonne.fr/chroniqueslatines/ Chroniques latines de Saint-Denis] : critical edition using TEI P4 (but we hope to migrate in P5 this year) : [http://elec.enc.sorbonne.fr/chroniqueslatines/xml/chroniquesstdenis.xml XML Files]<br />
* [http://lemo.irht.cnrs.fr/43/43-12.htm Réflexions sur l'utilisation de la TEI pour encoder les sources diplomatiques] and [http://elec.enc.sorbonne.fr/cartulaireblanc/guidebalisage/ Guide du balisage du Cartulaire blanc] : two resources in French<br />
<br />
[[Category:SIG|MSS]]</div>Elenaphttps://wiki.tei-c.org/index.php?title=MS_task_forces&diff=3865MS task forces2007-11-16T11:10:30Z<p>Elenap: </p>
<hr />
<div># Genetic editions [[Genetic Editions|group page]]<br />
## Malte Rehbein <br />
## Fotis Jannidis <br />
## Edward Van Houtte<br />
## Elena Pierazzo<br />
# MsDesc tiding up [[MsDesc enhancement|group page]]<br />
## Dot Porter <br />
## (Gabriel Bodard: a case study about fitting a marble inscribed monument into msDesc)<br />
## Jindřich Marek<br />
## Torsten Schassan<br />
# Facsimile [[facsimile enhancement|group page]]<br />
## Dot Porter <br />
## Hugh Cayssle <br />
## Torsten Schassan<br />
## Roberto Rosselli Del Turco<br />
# Critical Apparatus [[Critical Apparatus enhancement|group page]]<br />
## Hilde Bøe <br />
## Alexey Lavrentev <br />
# Representation of Primary sources enhancement (incl. writing direction) [[Representation of Primary sources enhancement|group page]]<br />
## Hilde Bøe<br />
## Roberto Rosselli Del Turco<br />
## Deborah Wright<br />
## Stephanie A. Schlitz<br />
## Alexey Lavrentev<br />
## Jindřich Marek<br />
## Zdeněk Uhlíř<br />
## Torsten Schassan</div>Elenaphttps://wiki.tei-c.org/index.php?title=MS_task_forces&diff=3864MS task forces2007-11-16T10:49:53Z<p>Elenap: </p>
<hr />
<div># Genetic editions <br />
## Malte Rehbein <br />
## Fotis Jannidis <br />
## Edward Van Houtte<br />
## Elena Pierazzo<br />
# MsDesc tiding up <br />
## Dot Porter <br />
## (Gabriel Bodard: a case study about fitting a marble inscribed monument into msDesc)<br />
## Jindřich Marek<br />
## Torsten Schassan<br />
# Facsimile <br />
## Dot Porter <br />
## Hugh Cayssle <br />
## Torsten Schassan<br />
## Roberto Rosselli Del Turco<br />
# Critical Apparatus <br />
## Hilde Bøe <br />
## Alexey Lavrentev <br />
# Representation of Primary sources enhancement (incl. writing direction)<br />
## Hilde Bøe<br />
## Roberto Rosselli Del Turco<br />
## Deborah Wright<br />
## Stephanie A. Schlitz<br />
## Alexey Lavrentev<br />
## Jindřich Marek<br />
## Zdeněk Uhlíř<br />
## Torsten Schassan</div>Elenaphttps://wiki.tei-c.org/index.php?title=MS_task_forces&diff=3862MS task forces2007-11-15T16:59:33Z<p>Elenap: </p>
<hr />
<div># Genetic editions <br />
## Malte Rehbein <br />
## Fotis Jannidis <br />
## Deborah Wright <br />
## Elena Pierazzo<br />
# MsDesc tiding up <br />
## Dot Porter <br />
## (Gabriel Bodard: a case study about fitting a marble inscribed monument into msDesc)<br />
## Jindřich Marek <br />
# Facsimile <br />
## Dot Porter <br />
## Hugh Cayssle <br />
## Torsten Shassan <br />
# Critical Apparatus <br />
## Hilde Bøe <br />
## Alexey Lavrentev <br />
# Writing direction <br />
## Hilde Bøe</div>Elenaphttps://wiki.tei-c.org/index.php?title=MS_task_forces&diff=3861MS task forces2007-11-15T16:55:27Z<p>Elenap: </p>
<hr />
<div># Genetic editions <br />
## Malte Rehbein <br />
## Fotis Jannidis <br />
## Deborah Wright <br />
## Elena Pierazzo<br />
# MsDesc tiding up <br />
## Dot Porter <br />
## Gabriel Bodard <br />
## Jindřich Marek <br />
# Facsimile <br />
## Dot Porter <br />
## Hugh Cayssle <br />
## Torsten Shassan <br />
# Critical Apparatus <br />
## Hilde Bøe <br />
## Alexey Lavrentev <br />
# Writing direction <br />
## Hilde Bøe</div>Elenaphttps://wiki.tei-c.org/index.php?title=SIG:MSS&diff=3860SIG:MSS2007-11-15T16:50:10Z<p>Elenap: /* Activities */</p>
<hr />
<div>== TEI Special Interest Group on Manuscripts (TEI MS SIG) ==<br />
<br />
=== Introduction ===<br />
<br />
The goal of the TEI Special Interest Group on Manuscripts is to bring together users of the TEI who wish to improve the encoding strategies for marking up transcriptions and editions of manuscript materials.<br />
<br />
This SIG will explore a range of issues common to editing manuscripts, including: <br />
# how to handle time based encoding<br />
# how to record place based encoding<br />
# how to encode fragments<br />
# how to record codicology (the substance of the medium, ink stints, etc); Robinson noted that the TEI already has mechanisms to record this, but it needs to be better documented<br />
# issues of substitutions<br />
# issues of variation<br />
# to clarify the role of using the critical apparatus tagset in manuscript transcription (which is dependent on whether one is encoding an edition or encoding a manuscript transcription)<br />
<br />
It will do this by: <br />
* running a mailing list on this topic<br />
* assess the TEI and suggest improvements/alterations to the TEI-Council<br />
<br />
The SIG is setup by: <br />
* Elena Pierazzo of the University of Pisa (Italy)<br />
* Susan Schreibman of the Maryland Institute for Technology in the Humanities (US), who is also a member of the TEI Council.<br />
* Edward Vanhoutte of the Centre for [http://www.kantl.be/ctb/ Scholarly Editing and Document Studies] of the Royal Academy of Dutch Language and Literature (Belgium), who is also a member of the TEI Council.<br />
<br />
The SIG is convened by Elena Pierazzo who also manages the TEI-MS-SIG List<br />
<br />
The SIG runs a mailing list on this topic. To join visit http://listserv.brown.edu/tei-ms-sig.html<br />
<br />
=== Activities ===<br />
<br />
The SIG met at the Third Annual TEI Members' Meeting in Nancy, France on 08 November 2003. The report can be found [http://www.tei-c.org.uk/Activities/SIG/Manuscript/mssigr01.html here].<br />
<br />
The second meeting of the SIG was held at the Fourth Annual TEI Members' Meeting at Johns Hopkins University, Baltimore, USA, 23 October 2004. The report can be found [http://www.tei-c.org.uk/Activities/SIG/Manuscript/mssigr02.html here].<br />
<br />
The third meeting of the SIG was held at Seventh Annual TEI Member's Meeting at University of Maryland, College Park, 3nd of November 2008. The agenda of the meeting can be found [[MS SIG Agenda 2008|here]]; the report can be found [[MS SIG Report 07|here]]. During the meeting several task forces were created to deal with specific problems: the task forces main page cha be found [[MS task forces|here]].<br />
<br />
=== Useful links ===<br />
<br />
==== Manuscript Description ====<br />
<br />
Projects, resources, guidelines concerning MS description.<br />
<br />
* [http://www.tei-c.org/release/doc/tei-p5-doc/html/MS.html TEI P5: 13. Manuscript Description]<br />
* [http://sunsite3.berkeley.edu/Scriptorium/ Digital Scriptorium] (see especially the [http://sunsite3.berkeley.edu/Scriptorium/technical/description_dtd.html DESCRIPTION DTD] page).<br />
* [http://www.hab.de/forschung/projekte/master-e.htm MASTER - Interface format for the description of medieval manuscripts]<br />
* [http://www.tei-c.org/Activities/MS/msw05.xml Reviews of the manuscript description chapter: A summary]<br />
<br />
==== Manuscript Transcription ====<br />
<br />
Projects, resources, guidelines concerning MS transcription.<br />
<br />
* [http://www.cdlib.org/inside/diglib/stwg/ms/ CDL Encoding Guidelines for Manuscripts and Rare Books]<br />
* [http://www.kantl.be/ctb/project/dalf/ DALF: Digital Archive of Letters in Flanders]<br />
* [http://sunsite3.berkeley.edu/Scriptorium/ Digital Scriptorium] (see especially the [http://sunsite3.berkeley.edu/Scriptorium/technical/transcription_dtd.html TRANSCRIPTION DTD] page).<br />
* [http://skaldic.arts.usyd.edu.au/docs/guidelines/guide.html Guidelines for the electronic edition of the skaldic corpus]<br />
* [http://web.uvic.ca/hrd/lydgate/pilot.htm Partial Transcription of John Lydgate's "Fall of Princes"]<br />
* [http://webapp1.dlib.indiana.edu/newton/index.jsp The Chymistry of Isaac Newton]<br />
* [http://gandalf.aksis.uib.no/menota/guidelines/ The Menota handbook]<br />
* [http://www.newtonproject.ic.ac.uk/prism.php?id=1 The Newton Project] (see also [http://ahds.ac.uk/creating/case-studies/newton/index.htm The Newton Project: Implementing and Exploiting XML]).<br />
* [http://www.whitmanarchive.org/guidelines/ The Walt Whitman Archive Encoding Guidelines for Poetry Manuscripts]<br />
* [http://jefferson.village.virginia.edu/seenet/piers/protocoltran.html Transcriptional Protocols: Piers Plowman Electronic Archive and SEENET]<br />
* [http://elec.enc.sorbonne.fr/chroniqueslatines/ Chroniques latines de Saint-Denis] : critical edition using TEI P4 (but we hope to migrate in P5 this year) : [http://elec.enc.sorbonne.fr/chroniqueslatines/xml/chroniquesstdenis.xml XML Files]<br />
* [http://lemo.irht.cnrs.fr/43/43-12.htm Réflexions sur l'utilisation de la TEI pour encoder les sources diplomatiques] and [http://elec.enc.sorbonne.fr/cartulaireblanc/guidebalisage/ Guide du balisage du Cartulaire blanc] : two resources in French<br />
<br />
[[Category:SIG|MSS]]</div>Elenaphttps://wiki.tei-c.org/index.php?title=Modern_MSS&diff=3767Modern MSS2007-11-03T16:09:35Z<p>Elenap: </p>
<hr />
<div>have critical app that aim at classical critical editions, are there other ways to present electronic editions and do we have the tools to publish in the other forms?<br />
<br />
modern text privileges the imitative transcription, don't need the critical app to the same degree as with medieval<br />
<br />
how do we publish modern manuscripts?<br />
<br />
<br />
critical app to record variant readings in medieval tradition; some approaches (i.e. genetic crit) isn't pointing to refused readings and do not utilize the concepts upon which traditional critical app. depend upon<br />
<br />
meaning of <lemma> and <reading> need to consider how modern usage is different; rather that genetic criticism is a different mode that cannot use the apparatus<br />
<br />
some approaches will continue to use the traditional mode<br />
<br />
kinds of texts we have:<br />
single copy text<br />
iterative levels of development<br />
redraft variations:being able to suggest relationships<br />
<br />
<br />
genetic criticism: no copy text, each version is text - maybe do not need critical apparatus<br />
guidelines are not adequately addressed for genetic<br />
<br />
Need a 'use case' for encoding in the geneticial critical mode - which tools to use, or how to express the differences in the semantics of the mark up. Write up (and possibly present) a paper on the use of P5 in genetic criticism and to allow this paper to guide next steps in terms of an addition to the chapter, a tutorial for next year, or and think about whether a new chapter needs to be created.<br />
<br />
current chapter on critical app needs to be addressed as well to the issues new modern editions<br />
<br />
missing: to relate changes over time - sequence attribute of substitution useful to express relative time. Does this address a network or layer of changes? How to express layers of change rather than local change? Can we use this local expression? Perhaps we can find a way to do it but it is not elegant. Can we use groups of changes on substitution for this? Problem that sequence is only for editorial intervention. Can stages be identified as attribute. Stage as analogous to handshift?<br />
<br />
In the case of draft manuscripts which are not books, is the use of <p> appropriate if the sequencing of the segments of text is not part of the text? Is the unit of the page the more appropriate here, and the use of zone? Idea is expressed in org attribute of div.class -- org=composite no claims made about the connection of parts of text. org=uniform do in fact believe there is a logical relation of the textual parts. Can make a div.like element such as block or page which can then use the org attribute. Might be useful to note that one can consider the use of div AB as a physical description rather than a logical description.<br />
<br />
is an empty element to represent stages useful? Need to make some suggestions and then explore the value. Does the use of <addspan> offer some traction on the need to represent stages? Need to test whether empty element or attribute is more useful, need some idea of processing etc.<br />
<br />
Another use case perhaps to express not the unified final text of 'traditional' critical app but rather want to publish in different formats<br />
<br />
does the description module cover all aspects of the modern manuscript? Is it possible to describe the 'dossier' - is this apparatus for genetic criticism, or is it part of the description. Construction of the dossier is the work of the editor, and therefore not a part of the desc? Is it useful to create a corpus, in order to describe the relationship of the texts. Manuscript desc is not the place for this perhaps given that it is a critical intervention. Need to explore tags for description of the framework of a dossier, but this is not the same as the manuscript desc. Given that it is possible to use desc within text, then perhaps the prose can be addressed to this kind of usage in the case of a dossier.<br />
<br />
Would like to ask the TEI to incorporate shapes beyond the rectangular in the interaction with manuscript (facsimilie) images because the rectangle is not always ammenable to the text itself.<br />
<br />
Need to have a way of describing the direction of writing in a div.like element for both medieval and modern manuscripts. Perhaps a global attribute that makes it possible to describe the directionality of a text. <br />
<br />
In modern material have other textual elements, like the 'post-it' or other paper attached to the page. We need to offer an example of how to express the relationship of both the paper and the textual relationships using the elements which we have.<br />
<br />
In different texts we have parts of text which we consider to be part of some genetic process, and we transcribe the other textual segments which are around it. Do we have an appropriate way to describe the relationships of a genetic core and the relationships of this to other textual elements present in the transcription. We can express this using linking, though it is difficult. This should be addressed in some respect in our writing on genetic criticism.</div>Elenaphttps://wiki.tei-c.org/index.php?title=Modern_MSS&diff=3765Modern MSS2007-11-03T16:03:25Z<p>Elenap: </p>
<hr />
<div>have critical app that aim at classical critical editions, are there other ways to present electronic editions and do we have the tools to publish in the other forms?<br />
<br />
modern text privileges the imitative transcription, don't need the critical app to the same degree as with medieval<br />
<br />
how do we publish modern manuscripts?<br />
<br />
<br />
critical app to record variant readings in medieval tradition; some approaches (i.e. genetic crit) isn't pointing to refused readings and do not utilize the concepts upon which traditional critical app. depend upon<br />
<br />
meaning of <lemma> and <reading> need to consider how modern usage is different; rather that genetic criticism is a different mode that cannot use the apparatus<br />
<br />
some approaches will continue to use the traditional mode<br />
<br />
kinds of texts we have:<br />
single copy text<br />
iterative levels of development<br />
redraft variations:being able to suggest relationships<br />
<br />
<br />
genetic criticism: no copy text, each version is text - maybe do not need critical apparatus<br />
guidelines are not adequately addressed for genetic<br />
<br />
Need a 'use case' for encoding in the geneticial critical mode - which tools to use, or how to express the differences in the semantics of the mark up. Write up (and possibly present) a paper on the use of P5 in genetic criticism and to allow this paper to guide next steps in terms of an addition to the chapter, a tutorial for next year, or and think about whether a new chapter needs to be created.<br />
<br />
current chapter on critical app needs to be addressed as well to the issues new modern editions<br />
<br />
missing: to relate changes over time - sequence attribute of substitution useful to express relative time. Does this address a network or layer of changes? How to express layers of change rather than local change? Can we use this local expression? Perhaps we can find a way to do it but it is not elegant. Can we use groups of changes on substitution for this? Problem that sequence is only for editorial intervention. Can stages be identified as attribute. Stage as analogous to handshift?<br />
<br />
In the case of draft manuscripts which are not books, is the use of <p> appropriate if the sequencing of the segments of text is not part of the text? Is the unit of the page the more appropriate here, and the use of zone? Idea is expressed in org attribute of div.class -- org=composite no claims made about the connection of parts of text. org=uniform do in fact believe there is a logical relation of the textual parts. Can make a div.like element such as block or page which can then use the org attribute. Might be useful to note that one can consider the use of div AB as a physical description rather than a logical description.<br />
<br />
is an empty element to represent stages useful? Need to make some suggestions and then explore the value. Does the use of <addspan> offer some traction on the need to represent stages? Need to test whether empty element or attribute is more useful, need some idea of processing etc.<br />
<br />
Another use case perhaps to express not the unified final text of 'traditional' critical app but rather want to publish in different formats<br />
<br />
does the description module cover all aspects of the modern manuscript? Is it possible to describe the 'dossier' - is this apparatus for genetic criticism, or is it part of the description. Construction of the dossier is the work of the editor, and therefore not a part of the desc? Is it useful to create a corpus, in order to describe the relationship of the texts. Manuscript desc is not the place for this perhaps given that it is a critical intervention. Need to explore tags for description of the framework of a dossier, but this is not the same as the manuscript desc. Given that it is possible to use desc within text, then perhaps the prose can be addressed to this kind of usage in the case of a dossier.<br />
<br />
Would like to ask the TEI to incorporate shapes beyond the rectangular in the interaction with manuscript images because the texts are not always ammenable to the text itself.<br />
<br />
Need to have a way of describing the direction of writing in a div.like element for both medieval and modern manuscripts. Perhaps a global attribute that makes it possible to describe the directionality of a text. <br />
<br />
In modern material have other textual elements, like the 'post-it' or other paper attached to the page. We need to offer an example of how to express the relationship of both the paper and the textual relationships using the elements which we have.<br />
<br />
In different texts we have parts of text which we consider to be part of some genetic process, and we transcribe the other textual segments which are around it. Do we have an appropriate way to describe the relationships of a genetic core and the relationships of this to other textual elements present in the transcription. We can express this using linking, though it is difficult. This should be addressed in some respect in our writing on genetic criticism.</div>Elenaphttps://wiki.tei-c.org/index.php?title=Modern_MSS&diff=3763Modern MSS2007-11-03T15:50:56Z<p>Elenap: </p>
<hr />
<div>have critical app that aim at classical critical editions, are there other ways to present electronic editions and do we have the tools to publish in the other forms?<br />
<br />
modern text privileges the imitative transcription, don't need the critical app to the same degree as with medieval<br />
<br />
how do we publish modern manuscripts?<br />
<br />
<br />
critical app to record variant readings in medieval tradition; some approaches (i.e. genetic crit) isn't pointing to refused readings and do not utilize the concepts upon which traditional critical app. depend upon<br />
<br />
meaning of <lemma> and <reading> need to consider how modern usage is different; rather that genetic criticism is a different mode that cannot use the apparatus<br />
<br />
some approaches will continue to use the traditional mode<br />
<br />
kinds of texts we have:<br />
single copy text<br />
iterative levels of development<br />
redraft variations:being able to suggest relationships<br />
<br />
<br />
genetic criticism: no copy text, each version is text - maybe do not need critical apparatus<br />
guidelines are not adequately addressed for genetic<br />
<br />
Need a 'use case' for encoding in the geneticial critical mode - which tools to use, or how to express the differences in the semantics of the mark up. Write up (and possibly present) a paper on the use of P5 in genetic criticism and to allow this paper to guide next steps in terms of an addition to the chapter, a tutorial for next year, or and think about whether a new chapter needs to be created.<br />
<br />
current chapter on critical app needs to be addressed as well to the issues new modern editions<br />
<br />
missing: to relate changes over time - sequence attribute of substitution useful for this; to express relative time. Does this address a network or layer of changes. How to express layers of change rather than local change. Can we use this local expression, perhaps find a way to do it but it is not elegant. Can we use groups of changes on substitution for this? Problem that sequence is only for editorial intervention. Can stages be identified as attribute. Stage as analogous to handshift?<br />
<br />
In the case of draft manuscripts which are not books, is the use of <p> appropriate if the sequencing of the segments of text is not part of the text? Is the unit of the page the more appropriate here, and the use of zone? Idea is expressed in org attribute of div.class -- org=composite no claims made about the connection of parts of text. org=uniform do in fact believe there is a logical relation of the textual parts. Can make a div.like element such as block or page which can then use the org attribute. Might be useful to note that one can consider the use of div AB as a physical description rather than a logical description.<br />
<br />
is an empty element to represent stages useful? Need to make some suggestions and then explore the value. Does the use of <addspan> offer some traction on the need to represent stages? Need to test whether empty element or attribute is more useful, need some idea of processing etc.<br />
<br />
Another use case perhaps to express not the unified final text of 'traditional' critical app but rather want to publish in different formats<br />
<br />
does the description module cover all aspects of the modern manuscript? Is it possible to describe the 'dossier' - is this apparatus for genetic criticism, or is it part of the description. Construction of the dossier is the work of the editor, and therefore not a part of the desc? Is it useful to create a corpus, in order to describe the relationship of the texts. Manuscript desc is not the place for this perhaps given that it is a critical intervention. Need to explore tags for description of the framework of a dossier, but this is not the same as the manuscript desc. Given that it is possible to use desc within text, then perhaps the prose can be addressed to this kind of usage in the case of a dossier.<br />
<br />
Would like to ask the TEI to incorporate shapes beyond the rectangular in the interaction with manuscript images because the texts are not always ammenable to the text itself.<br />
<br />
Need to have a way of describing the direction of writing in a div.like element for both medieval and modern manuscripts. Perhaps a global attribute that makes it possible to describe the directionality of a text. <br />
<br />
In modern material have other textual elements, like the 'post-it' or other paper attached to the page. We need to offer an example of how to express the relationship of both the paper and the textual relationships using the elements which we have.<br />
<br />
In different texts we have parts of text which we consider to be part of some genetic process, and we transcribe the other textual segments which are around it. Do we have an appropriate way to describe the relationships of a genetic core and the relationships of this to other textual elements present in the transcription. We can express this using linking, though it is difficult. This should be addressed in some respect in our writing on genetic criticism.</div>Elenaphttps://wiki.tei-c.org/index.php?title=Modern_MSS&diff=3757Modern MSS2007-11-03T15:33:35Z<p>Elenap: </p>
<hr />
<div>have critical app that aim at classical critical editions, are there other ways to present electronic editions and do we have the tools to publish in the other forms?<br />
<br />
modern text privileges the imitative transcription, don't need the critical app to the same degree as with medieval<br />
<br />
how do we publish modern manuscripts?<br />
<br />
<br />
critical app to record variant readings in medieval tradition; some approaches (i.e. genetic crit) isn't pointing to refused readings and do not utilize the concepts upon which traditional critical app. depend upon<br />
<br />
meaning of <lemma> and <reading> need to consider how modern usage is different; rather that genetic criticism is a different mode that cannot use the apparatus<br />
<br />
some approaches will continue to use the traditional mode<br />
<br />
kinds of texts we have:<br />
single copy text<br />
iterative levels of development<br />
redraft variations:being able to suggest relationships<br />
<br />
<br />
genetic criticism: no copy text, each version is text - maybe do not need critical apparatus<br />
guidelines are not adequately addressed for genetic<br />
<br />
Need a 'use case' for encoding in the geneticial critical mode - which tools to use, or how to express the differences in the semantics of the mark up. Write up (and possibly present) a paper on the use of P5 in genetic criticism and to allow this paper to guide next steps in terms of an addition to the chapter, a tutorial for next year, or and think about whether a new chapter needs to be created.<br />
<br />
current chapter on critical app needs to be addressed as well to new modern editions<br />
<br />
missing: to relate changes over time - sequence attribute of substitution useful for this; to express relative time. Does this address a network or layer of changes. How to express layers of change rather than local change. Can we use this local expression, perhaps find a way to do it but it is not elegant. Can we use groups of changes on substitution for this? Problem that sequence is only for editorial intervention. Can stages be identified as attribute. Stage as analogous to handshift?<br />
<br />
In the case of draft manuscripts which are not books, is the use of <p> appropriate if the sequencing of the segments of text is not part of the text? Is the unit of the page the more appropriate here, and the use of zone? Idea is expressed in org attribute of div.class -- org=composite no claims made about the connection of parts of text. org=uniform do in fact believe there is a logical relation of the textual parts. Can make a div.like element such as block or page which can then use the org attribute. Might be useful to note that one can consider the use of div AB as a physical description rather than a logical description.<br />
<br />
is an empty element to represent stages useful? Need to make some suggestions and then explore the value. Does the use of <addspan> offer some traction on the need to represent stages? Need to test whether empty element or attribute is more useful, need some idea of processing etc.<br />
<br />
Another use case perhaps to express not the unified final text of 'traditional' critical app but rather want to publish in different formats</div>Elenaphttps://wiki.tei-c.org/index.php?title=MS_SIG_Agenda_2007&diff=3731MS SIG Agenda 20072007-11-02T20:58:53Z<p>Elenap: /* MS-SIG 2008 meeting Agenda */</p>
<hr />
<div>[[Category:Scratchpad]]<br />
== MS-SIG 2008 meeting Agenda ==<br />
<br />
# Greetings and introductions<br />
# Group work [[Modern MSS]] - [[Medieval MSS]] - Topic for the discussion:<br />
## The TEI modules that concern manuscripts, that are:<br />
### [http://www.tei-c.org/cms/release/doc/tei-p5-doc/en/html/MS.html MS description]<br />
### [http://www.tei-c.org/cms/release/doc/tei-p5-doc/en/html/TC.html Critical apparatus]<br />
### [http://www.tei-c.org/cms/release/doc/tei-p5-doc/en/html/PH.html Representation of Primary Sources]<br />
## P5 novelties: in which way they solve issues not covered by P4?<br />
## What is still missing?<br />
## What is misleading or incorrectly stated in the prose description of P5 Guidelines?<br />
## Diplomatic/pseudo-facsimilar edition as a case study: do we have everything we need?<br />
## Corrections/additions/substitution vs. critical apparatus.<br />
## '''Enhancement proposals'''<br />
# Plenary discussion, groups report<br />
# Enhancement proposals: list and priorities<br />
# Work volunteering<br />
# What will happen after the meeting?</div>Elenaphttps://wiki.tei-c.org/index.php?title=MS_SIG_Agenda_2007&diff=3730MS SIG Agenda 20072007-11-02T20:53:04Z<p>Elenap: /* MS-SIG 2008 meeting Agenda */</p>
<hr />
<div>[[Category:Scratchpad]]<br />
== MS-SIG 2008 meeting Agenda ==<br />
<br />
# Greetings and presentations<br />
# Groups work on the TEI modules that concern manuscripts, that are:<br />
## [http://www.tei-c.org/cms/release/doc/tei-p5-doc/en/html/MS.html MS description]<br />
## [http://www.tei-c.org/cms/release/doc/tei-p5-doc/en/html/TC.html Critical apparatus]<br />
## [http://www.tei-c.org/cms/release/doc/tei-p5-doc/en/html/PH.html Representation of Primary Sources]<br />
## Topic for the discussion [[Modern MSS]] - [[Medieval MSS]]:<br />
### P5 novelties: in which way they solve issues not covered by P4?<br />
### What is still missing?<br />
### What is misleading or incorrectly stated in the prose description of P5 Guidelines?<br />
### Diplomatic/pseudo-facsimilar edition as a case study: do we have everything we need?<br />
### Corrections/additions/substitution vs. critical apparatus.<br />
### '''Enhancement proposals'''<br />
# Plenary discussion, groups report<br />
# Enhancement proposals: list and priorities<br />
# Work volunteering<br />
# What will happen after the meeting?</div>Elenaphttps://wiki.tei-c.org/index.php?title=MS_SIG_Agenda_2007&diff=3729MS SIG Agenda 20072007-11-02T20:30:22Z<p>Elenap: /* MS-SIG 2008 meeting Agenda */</p>
<hr />
<div>[[Category:Scratchpad]]<br />
== MS-SIG 2008 meeting Agenda ==<br />
<br />
# Greetings and presentations<br />
# Groups work on the TEI modules that concern manuscripts, that are:<br />
## [http://www.tei-c.org/cms/release/doc/tei-p5-doc/en/html/MS.html MS description]<br />
## [http://www.tei-c.org/cms/release/doc/tei-p5-doc/en/html/TC.html Critical apparatus]<br />
## [http://www.tei-c.org/cms/release/doc/tei-p5-doc/en/html/PH.html Representation of Primary Sources]<br />
## Topic for the discussion [[Modern MSS]] - [[Medieval MSS]]:<br />
### P5 novelties: in which way they solve issues not covered by P4?<br />
### What is still missing?<br />
### What is misleading or incorrectly stated in the prose description of P5 Guidelines?<br />
### Diplomatic/pseudo-facsimilar edition as a case study: do we have everything we need?<br />
### '''Enhancement proposals'''<br />
# Plenary discussion, groups report<br />
# Enhancement proposals<br />
# Work volunteering</div>Elenaphttps://wiki.tei-c.org/index.php?title=MS_SIG_Agenda_2007&diff=3728MS SIG Agenda 20072007-11-02T20:29:14Z<p>Elenap: /* MS-SIG 2008 meeting Agenda */</p>
<hr />
<div>[[Category:Scratchpad]]<br />
== MS-SIG 2008 meeting Agenda ==<br />
<br />
# Greetings and presentations<br />
# Groups work on the TEI modules that concern manuscripts, that are:<br />
## [http://www.tei-c.org/cms/release/doc/tei-p5-doc/en/html/MS.html MS description]<br />
## [http://www.tei-c.org/cms/release/doc/tei-p5-doc/en/html/TC.html Critical apparatus]<br />
## [http://www.tei-c.org/cms/release/doc/tei-p5-doc/en/html/PH.html Representation of Primary Sources]<br />
## Topic for the discussion [[Modern MSS]] - [[Medieval MSS]]:<br />
### P5 novelties: in which way they solve issues not covered by P4?<br />
### What is still missing?<br />
### What is misleading or incorrectly stated in the prose description of P5 Guidelines?<br />
### Diplomatic/pseudo-facsimilar edition as a case study: do we have everything we need?<br />
### Enhancement proposals<br />
# Plenary discussion, groups report<br />
# Enhancement proposals<br />
# Work volunteering</div>Elenaphttps://wiki.tei-c.org/index.php?title=MS_SIG_Agenda_2007&diff=3727MS SIG Agenda 20072007-11-02T17:55:40Z<p>Elenap: /* MS-SIG 2008 meeting Agenda */</p>
<hr />
<div>[[Category:Scratchpad]]<br />
== MS-SIG 2008 meeting Agenda ==<br />
<br />
# Greetings and presentations<br />
# Groups work on the TEI modules that concern manuscripts, that are:<br />
## [http://www.tei-c.org/cms/release/doc/tei-p5-doc/en/html/MS.html MS description]<br />
## [http://www.tei-c.org/cms/release/doc/tei-p5-doc/en/html/TC.html Critical apparatus]<br />
## [http://www.tei-c.org/cms/release/doc/tei-p5-doc/en/html/PH.html Representation of Primary Sources]<br />
## Topic for the discussion [[Modern MSS]] - [[Medieval MSS]]:<br />
### P5 novelties: in which way they solve issues not covered by P4?<br />
### What is still missing?<br />
### What is misleading or incorrectly stated in the prose description of P5 Guidelines?<br />
### Enhancement proposals<br />
# Plenary discussion, groups report<br />
# Enhancement proposals<br />
# Work volunteering</div>Elenaphttps://wiki.tei-c.org/index.php?title=MS_SIG_Agenda_2007&diff=3712MS SIG Agenda 20072007-10-31T16:01:45Z<p>Elenap: </p>
<hr />
<div>== MS-SIG 2008 meeting Agenda ==<br />
<br />
# Greetings and presentations<br />
# Groups work on the TEI modules that concern manuscripts, that are:<br />
## [http://www.tei-c.org/cms/release/doc/tei-p5-doc/en/html/MS.html MS description]<br />
## [http://www.tei-c.org/cms/release/doc/tei-p5-doc/en/html/TC.html Critical apparatus]<br />
## [http://www.tei-c.org/cms/release/doc/tei-p5-doc/en/html/PH.html Representation of Primary Sources]<br />
## Topic for the discussion:<br />
### P5 novelties: in which way they solve issues not covered by P4?<br />
### What is still missing?<br />
### What is misleading or incorrectley stated in the prose description of P5 Guidelines?<br />
### Enhancement proposals<br />
# Plenary discussion, groups report<br />
# Enhancement proposals<br />
# Work volunteering</div>Elenaphttps://wiki.tei-c.org/index.php?title=SIG:MSS&diff=3711SIG:MSS2007-10-31T16:00:53Z<p>Elenap: /* Activities */</p>
<hr />
<div>== TEI Special Interest Group on Manuscripts (TEI MS SIG) ==<br />
<br />
=== Introduction ===<br />
<br />
The goal of the TEI Special Interest Group on Manuscripts is to bring together users of the TEI who whish to improve the encoding strategies for marking up transcriptions and editions of manuscript materials.<br />
<br />
This SIG will explore a range of issues common to editing manuscripts, including: <br />
# how to handle time based encoding<br />
# how to record place based encoding<br />
# how to encode fragments<br />
# how to record codicology (the substance of the medium, ink stints, etc); Robinson noted that the TEI already has mechanisms to record this, but it needs to be better documented<br />
# issues of substitutions<br />
# issues of variation<br />
# to clarify the role of using the critical apparatus tagset in manuscript transcription (which is dependent on whether one is encoding an edition or encoding a manuscript transcription)<br />
<br />
It will do this by: <br />
* running a mailing list on this topic<br />
* assess the TEI and suggest improvements/alterations to the TEI-Council<br />
<br />
The SIG is setup by: <br />
* Elena Pierazzo of the University of Pisa (Italy)<br />
* Susan Schreibman of the Maryland Institute for Technology in the Humanities (US), who is also a member of the TEI Council.<br />
* Edward Vanhoutte of the Centre for [http://www.kantl.be/ctb/ Scholarly Editing and Document Studies] of the Royal Academy of Dutch Language and Literature (Belgium), who is also a member of the TEI Council.<br />
<br />
The SIG is convened by Elena Pierazzo who also manages the TEI-MS-SIG List<br />
<br />
The SIG runs a mailing list on this topic. To join visit http://listserv.brown.edu/tei-ms-sig.html<br />
<br />
=== Activities ===<br />
<br />
The SIG met at the Third Annual TEI Members' Meeting in Nancy, France on 08 November 2003. The report can be found [http://www.tei-c.org.uk/Activities/SIG/Manuscript/mssigr01.html here].<br />
<br />
The second meeting of the SIG was held at the Fourth Annual TEI Members' Meeting at Johns Hopkins University, Baltimore, USA, 23 October 2004. The report can be found [http://www.tei-c.org.uk/Activities/SIG/Manuscript/mssigr02.html here].<br />
<br />
The third meeting of the SIG was held at Seventh Annual TEI Member's Meeting at University of Maryland, College Park, 3nd of November 2008. The agenda of the meeting che be found [[MS SIG Agenda 2008|here]]<br />
<br />
=== Useful links ===<br />
<br />
==== Manuscript Description ====<br />
<br />
Projects, resources, guidelines concerning MS description.<br />
<br />
* [http://www.tei-c.org/release/doc/tei-p5-doc/html/MS.html TEI P5: 13. Manuscript Description]<br />
* [http://sunsite3.berkeley.edu/Scriptorium/ Digital Scriptorium] (see especially the [http://sunsite3.berkeley.edu/Scriptorium/technical/description_dtd.html DESCRIPTION DTD] page).<br />
* [http://www.hab.de/forschung/projekte/master-e.htm MASTER - Interface format for the description of medieval manuscripts]<br />
* [http://www.tei-c.org/Activities/MS/msw05.xml Reviews of the manuscript description chapter: A summary]<br />
<br />
==== Manuscript Transcription ====<br />
<br />
Projects, resources, guidelines concerning MS transcription.<br />
<br />
* [http://www.cdlib.org/inside/diglib/stwg/ms/ CDL Encoding Guidelines for Manuscripts and Rare Books]<br />
* [http://www.kantl.be/ctb/project/dalf/ DALF: Digital Archive of Letters in Flanders]<br />
* [http://sunsite3.berkeley.edu/Scriptorium/ Digital Scriptorium] (see especially the [http://sunsite3.berkeley.edu/Scriptorium/technical/transcription_dtd.html TRANSCRIPTION DTD] page).<br />
* [http://skaldic.arts.usyd.edu.au/docs/guidelines/guide.html Guidelines for the electronic edition of the skaldic corpus]<br />
* [http://web.uvic.ca/hrd/lydgate/pilot.htm Partial Transcription of John Lydgate's "Fall of Princes"]<br />
* [http://webapp1.dlib.indiana.edu/newton/index.jsp The Chymistry of Isaac Newton]<br />
* [http://gandalf.aksis.uib.no/menota/guidelines/ The Menota handbook]<br />
* [http://www.newtonproject.ic.ac.uk/prism.php?id=1 The Newton Project] (see also [http://ahds.ac.uk/creating/case-studies/newton/index.htm The Newton Project: Implementing and Exploiting XML]).<br />
* [http://www.whitmanarchive.org/guidelines/ The Walt Whitman Archive Encoding Guidelines for Poetry Manuscripts]<br />
* [http://jefferson.village.virginia.edu/seenet/piers/protocoltran.html Transcriptional Protocols: Piers Plowman Electronic Archive and SEENET]<br />
* [http://elec.enc.sorbonne.fr/chroniqueslatines/ Chroniques latines de Saint-Denis] : critical edition using TEI P4 (but we hope migrate in P5 this year) : [http://elec.enc.sorbonne.fr/chroniqueslatines/xml/chroniquesstdenis.xml XML Files]<br />
* [http://lemo.irht.cnrs.fr/43/43-12.htm Réflexions sur l'utilisation de la TEI pour encoder les sources diplomatiques] and [http://elec.enc.sorbonne.fr/cartulaireblanc/guidebalisage/ Guide du balisage du Cartulaire blanc] : two ressources in french<br />
<br />
[[Category:SIG|MSS]]</div>Elenaphttps://wiki.tei-c.org/index.php?title=SIG:MSS&diff=3710SIG:MSS2007-10-31T16:00:00Z<p>Elenap: /* Activities */</p>
<hr />
<div>== TEI Special Interest Group on Manuscripts (TEI MS SIG) ==<br />
<br />
=== Introduction ===<br />
<br />
The goal of the TEI Special Interest Group on Manuscripts is to bring together users of the TEI who whish to improve the encoding strategies for marking up transcriptions and editions of manuscript materials.<br />
<br />
This SIG will explore a range of issues common to editing manuscripts, including: <br />
# how to handle time based encoding<br />
# how to record place based encoding<br />
# how to encode fragments<br />
# how to record codicology (the substance of the medium, ink stints, etc); Robinson noted that the TEI already has mechanisms to record this, but it needs to be better documented<br />
# issues of substitutions<br />
# issues of variation<br />
# to clarify the role of using the critical apparatus tagset in manuscript transcription (which is dependent on whether one is encoding an edition or encoding a manuscript transcription)<br />
<br />
It will do this by: <br />
* running a mailing list on this topic<br />
* assess the TEI and suggest improvements/alterations to the TEI-Council<br />
<br />
The SIG is setup by: <br />
* Elena Pierazzo of the University of Pisa (Italy)<br />
* Susan Schreibman of the Maryland Institute for Technology in the Humanities (US), who is also a member of the TEI Council.<br />
* Edward Vanhoutte of the Centre for [http://www.kantl.be/ctb/ Scholarly Editing and Document Studies] of the Royal Academy of Dutch Language and Literature (Belgium), who is also a member of the TEI Council.<br />
<br />
The SIG is convened by Elena Pierazzo who also manages the TEI-MS-SIG List<br />
<br />
The SIG runs a mailing list on this topic. To join visit http://listserv.brown.edu/tei-ms-sig.html<br />
<br />
=== Activities ===<br />
<br />
The SIG met at the Third Annual TEI Members' Meeting in Nancy, France on 08 November 2003. The report can be found [http://www.tei-c.org.uk/Activities/SIG/Manuscript/mssigr01.html here].<br />
<br />
The second meeting of the SIG was held at the Fourth Annual TEI Members' Meeting at Johns Hopkins University, Baltimore, USA, 23 October 2004. The report can be found [http://www.tei-c.org.uk/Activities/SIG/Manuscript/mssigr02.html here].<br />
<br />
The third meeting of the SIG was held at Seventh Annual TEI Member's Meeting at University of Maryland, College Park, 3nd of November 2008. The agenda of the meeting che be found [[Agenda2008|here]]<br />
<br />
=== Useful links ===<br />
<br />
==== Manuscript Description ====<br />
<br />
Projects, resources, guidelines concerning MS description.<br />
<br />
* [http://www.tei-c.org/release/doc/tei-p5-doc/html/MS.html TEI P5: 13. Manuscript Description]<br />
* [http://sunsite3.berkeley.edu/Scriptorium/ Digital Scriptorium] (see especially the [http://sunsite3.berkeley.edu/Scriptorium/technical/description_dtd.html DESCRIPTION DTD] page).<br />
* [http://www.hab.de/forschung/projekte/master-e.htm MASTER - Interface format for the description of medieval manuscripts]<br />
* [http://www.tei-c.org/Activities/MS/msw05.xml Reviews of the manuscript description chapter: A summary]<br />
<br />
==== Manuscript Transcription ====<br />
<br />
Projects, resources, guidelines concerning MS transcription.<br />
<br />
* [http://www.cdlib.org/inside/diglib/stwg/ms/ CDL Encoding Guidelines for Manuscripts and Rare Books]<br />
* [http://www.kantl.be/ctb/project/dalf/ DALF: Digital Archive of Letters in Flanders]<br />
* [http://sunsite3.berkeley.edu/Scriptorium/ Digital Scriptorium] (see especially the [http://sunsite3.berkeley.edu/Scriptorium/technical/transcription_dtd.html TRANSCRIPTION DTD] page).<br />
* [http://skaldic.arts.usyd.edu.au/docs/guidelines/guide.html Guidelines for the electronic edition of the skaldic corpus]<br />
* [http://web.uvic.ca/hrd/lydgate/pilot.htm Partial Transcription of John Lydgate's "Fall of Princes"]<br />
* [http://webapp1.dlib.indiana.edu/newton/index.jsp The Chymistry of Isaac Newton]<br />
* [http://gandalf.aksis.uib.no/menota/guidelines/ The Menota handbook]<br />
* [http://www.newtonproject.ic.ac.uk/prism.php?id=1 The Newton Project] (see also [http://ahds.ac.uk/creating/case-studies/newton/index.htm The Newton Project: Implementing and Exploiting XML]).<br />
* [http://www.whitmanarchive.org/guidelines/ The Walt Whitman Archive Encoding Guidelines for Poetry Manuscripts]<br />
* [http://jefferson.village.virginia.edu/seenet/piers/protocoltran.html Transcriptional Protocols: Piers Plowman Electronic Archive and SEENET]<br />
* [http://elec.enc.sorbonne.fr/chroniqueslatines/ Chroniques latines de Saint-Denis] : critical edition using TEI P4 (but we hope migrate in P5 this year) : [http://elec.enc.sorbonne.fr/chroniqueslatines/xml/chroniquesstdenis.xml XML Files]<br />
* [http://lemo.irht.cnrs.fr/43/43-12.htm Réflexions sur l'utilisation de la TEI pour encoder les sources diplomatiques] and [http://elec.enc.sorbonne.fr/cartulaireblanc/guidebalisage/ Guide du balisage du Cartulaire blanc] : two ressources in french<br />
<br />
[[Category:SIG|MSS]]</div>Elenaphttps://wiki.tei-c.org/index.php?title=SIG:MSS&diff=3708SIG:MSS2007-10-31T15:33:54Z<p>Elenap: /* Activities */</p>
<hr />
<div>== TEI Special Interest Group on Manuscripts (TEI MS SIG) ==<br />
<br />
=== Introduction ===<br />
<br />
The goal of the TEI Special Interest Group on Manuscripts is to bring together users of the TEI who whish to improve the encoding strategies for marking up transcriptions and editions of manuscript materials.<br />
<br />
This SIG will explore a range of issues common to editing manuscripts, including: <br />
# how to handle time based encoding<br />
# how to record place based encoding<br />
# how to encode fragments<br />
# how to record codicology (the substance of the medium, ink stints, etc); Robinson noted that the TEI already has mechanisms to record this, but it needs to be better documented<br />
# issues of substitutions<br />
# issues of variation<br />
# to clarify the role of using the critical apparatus tagset in manuscript transcription (which is dependent on whether one is encoding an edition or encoding a manuscript transcription)<br />
<br />
It will do this by: <br />
* running a mailing list on this topic<br />
* assess the TEI and suggest improvements/alterations to the TEI-Council<br />
<br />
The SIG is setup by: <br />
* Elena Pierazzo of the University of Pisa (Italy)<br />
* Susan Schreibman of the Maryland Institute for Technology in the Humanities (US), who is also a member of the TEI Council.<br />
* Edward Vanhoutte of the Centre for [http://www.kantl.be/ctb/ Scholarly Editing and Document Studies] of the Royal Academy of Dutch Language and Literature (Belgium), who is also a member of the TEI Council.<br />
<br />
The SIG is convened by Elena Pierazzo who also manages the TEI-MS-SIG List<br />
<br />
The SIG runs a mailing list on this topic. To join visit http://listserv.brown.edu/tei-ms-sig.html<br />
<br />
=== Activities ===<br />
<br />
The SIG met at the Third Annual TEI Members' Meeting in Nancy, France on 08 November 2003. The report can be found [http://www.tei-c.org.uk/Activities/SIG/Manuscript/mssigr01.html here].<br />
<br />
The second meeting of the SIG was held at the Fourth Annual TEI Members' Meeting at Johns Hopkins University, Baltimore, USA, 23 October 2004. The report can be found [http://www.tei-c.org.uk/Activities/SIG/Manuscript/mssigr02.html here].<br />
<br />
The third meeting of the SIG was held at Seventh Annual TEI Member's Meeting at University of Maryland, College Park, 3nd of November 2008. The agenda of the meeting che be found [[Agenda2008 here]]<br />
<br />
=== Useful links ===<br />
<br />
==== Manuscript Description ====<br />
<br />
Projects, resources, guidelines concerning MS description.<br />
<br />
* [http://www.tei-c.org/release/doc/tei-p5-doc/html/MS.html TEI P5: 13. Manuscript Description]<br />
* [http://sunsite3.berkeley.edu/Scriptorium/ Digital Scriptorium] (see especially the [http://sunsite3.berkeley.edu/Scriptorium/technical/description_dtd.html DESCRIPTION DTD] page).<br />
* [http://www.hab.de/forschung/projekte/master-e.htm MASTER - Interface format for the description of medieval manuscripts]<br />
* [http://www.tei-c.org/Activities/MS/msw05.xml Reviews of the manuscript description chapter: A summary]<br />
<br />
==== Manuscript Transcription ====<br />
<br />
Projects, resources, guidelines concerning MS transcription.<br />
<br />
* [http://www.cdlib.org/inside/diglib/stwg/ms/ CDL Encoding Guidelines for Manuscripts and Rare Books]<br />
* [http://www.kantl.be/ctb/project/dalf/ DALF: Digital Archive of Letters in Flanders]<br />
* [http://sunsite3.berkeley.edu/Scriptorium/ Digital Scriptorium] (see especially the [http://sunsite3.berkeley.edu/Scriptorium/technical/transcription_dtd.html TRANSCRIPTION DTD] page).<br />
* [http://skaldic.arts.usyd.edu.au/docs/guidelines/guide.html Guidelines for the electronic edition of the skaldic corpus]<br />
* [http://web.uvic.ca/hrd/lydgate/pilot.htm Partial Transcription of John Lydgate's "Fall of Princes"]<br />
* [http://webapp1.dlib.indiana.edu/newton/index.jsp The Chymistry of Isaac Newton]<br />
* [http://gandalf.aksis.uib.no/menota/guidelines/ The Menota handbook]<br />
* [http://www.newtonproject.ic.ac.uk/prism.php?id=1 The Newton Project] (see also [http://ahds.ac.uk/creating/case-studies/newton/index.htm The Newton Project: Implementing and Exploiting XML]).<br />
* [http://www.whitmanarchive.org/guidelines/ The Walt Whitman Archive Encoding Guidelines for Poetry Manuscripts]<br />
* [http://jefferson.village.virginia.edu/seenet/piers/protocoltran.html Transcriptional Protocols: Piers Plowman Electronic Archive and SEENET]<br />
* [http://elec.enc.sorbonne.fr/chroniqueslatines/ Chroniques latines de Saint-Denis] : critical edition using TEI P4 (but we hope migrate in P5 this year) : [http://elec.enc.sorbonne.fr/chroniqueslatines/xml/chroniquesstdenis.xml XML Files]<br />
* [http://lemo.irht.cnrs.fr/43/43-12.htm Réflexions sur l'utilisation de la TEI pour encoder les sources diplomatiques] and [http://elec.enc.sorbonne.fr/cartulaireblanc/guidebalisage/ Guide du balisage du Cartulaire blanc] : two ressources in french<br />
<br />
[[Category:SIG|MSS]]</div>Elenaphttps://wiki.tei-c.org/index.php?title=SIG:MSS&diff=3707SIG:MSS2007-10-31T15:26:54Z<p>Elenap: /* Introduction */</p>
<hr />
<div>== TEI Special Interest Group on Manuscripts (TEI MS SIG) ==<br />
<br />
=== Introduction ===<br />
<br />
The goal of the TEI Special Interest Group on Manuscripts is to bring together users of the TEI who whish to improve the encoding strategies for marking up transcriptions and editions of manuscript materials.<br />
<br />
This SIG will explore a range of issues common to editing manuscripts, including: <br />
# how to handle time based encoding<br />
# how to record place based encoding<br />
# how to encode fragments<br />
# how to record codicology (the substance of the medium, ink stints, etc); Robinson noted that the TEI already has mechanisms to record this, but it needs to be better documented<br />
# issues of substitutions<br />
# issues of variation<br />
# to clarify the role of using the critical apparatus tagset in manuscript transcription (which is dependent on whether one is encoding an edition or encoding a manuscript transcription)<br />
<br />
It will do this by: <br />
* running a mailing list on this topic<br />
* assess the TEI and suggest improvements/alterations to the TEI-Council<br />
<br />
The SIG is setup by: <br />
* Elena Pierazzo of the University of Pisa (Italy)<br />
* Susan Schreibman of the Maryland Institute for Technology in the Humanities (US), who is also a member of the TEI Council.<br />
* Edward Vanhoutte of the Centre for [http://www.kantl.be/ctb/ Scholarly Editing and Document Studies] of the Royal Academy of Dutch Language and Literature (Belgium), who is also a member of the TEI Council.<br />
<br />
The SIG is convened by Elena Pierazzo who also manages the TEI-MS-SIG List<br />
<br />
The SIG runs a mailing list on this topic. To join visit http://listserv.brown.edu/tei-ms-sig.html<br />
<br />
=== Activities ===<br />
<br />
The SIG met at the Third Annual TEI Members' Meeting in Nancy, France on 08 November 2003. The report can be found [http://www.tei-c.org.uk/Activities/SIG/Manuscript/mssigr01.html here].<br />
<br />
The second meeting of the SIG was held at the Fourth Annual TEI Members' Meeting at Johns Hopkins University, Baltimore, USA, 23 October 2004. The report can be found [http://www.tei-c.org.uk/Activities/SIG/Manuscript/mssigr02.html here].<br />
<br />
=== Useful links ===<br />
<br />
==== Manuscript Description ====<br />
<br />
Projects, resources, guidelines concerning MS description.<br />
<br />
* [http://www.tei-c.org/release/doc/tei-p5-doc/html/MS.html TEI P5: 13. Manuscript Description]<br />
* [http://sunsite3.berkeley.edu/Scriptorium/ Digital Scriptorium] (see especially the [http://sunsite3.berkeley.edu/Scriptorium/technical/description_dtd.html DESCRIPTION DTD] page).<br />
* [http://www.hab.de/forschung/projekte/master-e.htm MASTER - Interface format for the description of medieval manuscripts]<br />
* [http://www.tei-c.org/Activities/MS/msw05.xml Reviews of the manuscript description chapter: A summary]<br />
<br />
==== Manuscript Transcription ====<br />
<br />
Projects, resources, guidelines concerning MS transcription.<br />
<br />
* [http://www.cdlib.org/inside/diglib/stwg/ms/ CDL Encoding Guidelines for Manuscripts and Rare Books]<br />
* [http://www.kantl.be/ctb/project/dalf/ DALF: Digital Archive of Letters in Flanders]<br />
* [http://sunsite3.berkeley.edu/Scriptorium/ Digital Scriptorium] (see especially the [http://sunsite3.berkeley.edu/Scriptorium/technical/transcription_dtd.html TRANSCRIPTION DTD] page).<br />
* [http://skaldic.arts.usyd.edu.au/docs/guidelines/guide.html Guidelines for the electronic edition of the skaldic corpus]<br />
* [http://web.uvic.ca/hrd/lydgate/pilot.htm Partial Transcription of John Lydgate's "Fall of Princes"]<br />
* [http://webapp1.dlib.indiana.edu/newton/index.jsp The Chymistry of Isaac Newton]<br />
* [http://gandalf.aksis.uib.no/menota/guidelines/ The Menota handbook]<br />
* [http://www.newtonproject.ic.ac.uk/prism.php?id=1 The Newton Project] (see also [http://ahds.ac.uk/creating/case-studies/newton/index.htm The Newton Project: Implementing and Exploiting XML]).<br />
* [http://www.whitmanarchive.org/guidelines/ The Walt Whitman Archive Encoding Guidelines for Poetry Manuscripts]<br />
* [http://jefferson.village.virginia.edu/seenet/piers/protocoltran.html Transcriptional Protocols: Piers Plowman Electronic Archive and SEENET]<br />
* [http://elec.enc.sorbonne.fr/chroniqueslatines/ Chroniques latines de Saint-Denis] : critical edition using TEI P4 (but we hope migrate in P5 this year) : [http://elec.enc.sorbonne.fr/chroniqueslatines/xml/chroniquesstdenis.xml XML Files]<br />
* [http://lemo.irht.cnrs.fr/43/43-12.htm Réflexions sur l'utilisation de la TEI pour encoder les sources diplomatiques] and [http://elec.enc.sorbonne.fr/cartulaireblanc/guidebalisage/ Guide du balisage du Cartulaire blanc] : two ressources in french<br />
<br />
[[Category:SIG|MSS]]</div>Elenap