SIG meeting Lyon: Difference between revisions

From TEIWiki
Jump to navigation Jump to search
← Older edit

Seifert (talk | contribs)

1 user group
204 edits
Seifert (talk | contribs)
editors
204 edits
Seifert (talk | contribs)
editors
204 edits
 
(6 intermediate revisions by the same user not shown)
Line 1: Line 1:
==TEI SIG on Correspondence - Minutes Lyon, Oct 29, 2015==
==TEI SIG on Correspondence - Minutes Lyon, Oct 29, 2015==


Status: draft --[[User: sabine seifert]], 06 December 2015 (EST)
Status: draft --[[User: Seifert]], 06 December 2015 (EST)


===Attendees===
===Attendees===
Line 7: Line 7:
* Peter Stadler, [http://www.weber-gesamtausgabe.de/de/A009001 University of Paderborn, Carl Maria von Weber Collected Works]  
* Peter Stadler, [http://www.weber-gesamtausgabe.de/de/A009001 University of Paderborn, Carl Maria von Weber Collected Works]  
* Sabine Seifert, [http://tei.ibi.hu-berlin.de/berliner-intellektuelle/ Humboldt University Berlin, Berlin Intellectuals 1800-1830], [http://www.fontanearchiv.de/ Theodor Fontane Archive, University of Potsdam]
* Sabine Seifert, [http://tei.ibi.hu-berlin.de/berliner-intellektuelle/ Humboldt University Berlin, Berlin Intellectuals 1800-1830], [http://www.fontanearchiv.de/ Theodor Fontane Archive, University of Potsdam]
*Stefan Dumont, [http://www.bbaw.de/telota Berlin-Brandenburg Academy of Sciences and Humanities]
* Stefan Dumont, [http://www.bbaw.de/telota Berlin-Brandenburg Academy of Sciences and Humanities]
* Anne Baillot, [http://tei.ibi.hu-berlin.de/berliner-intellektuelle/ Humboldt University Berlin, Berlin Intellectuals 1800-1830]
* Anne Baillot, [http://tei.ibi.hu-berlin.de/berliner-intellektuelle/ Humboldt University Berlin, Berlin Intellectuals 1800-1830]
* Patrizia Rebulla, [letters.mozartways.com Université Libre de Bruxelles]
* Patrizia Rebulla, [letters.mozartways.com Université Libre de Bruxelles]
Line 25: Line 25:
===Discussion===
===Discussion===


- SIG for computer-mediated communication: they work on the same problems as we do concerning the meta data and the structure of the communication
* SIG for Computer-Mediated Communication
- Peter: we should join forces with them, <post> element for a tweet or a posting what would be a letter for us, they want to file a feature request for that
- they work on the same problems as we do concerning meta data and the structure of the communication
- they took our <correspAction> and made an attribute out of it
 
- Stefan: just wrote a blog post on CMIF
- <post> element for a tweet or a posting what would be a letter for us - they plan to file a feature request for that
- Anne: meeting of CostAction and Mapping the Republic of Letters, we should talk to Pip Willcox to make correspDesc and correspSearch known
 
- Stefan: in contact with these people
- they took our <correspAction> and turned it into an attribute
- Anne: perhaps we should write a little standard text to send around to make our work known
 
- Peter: we should join forces with them
 
 
* "correspSearch"
- Stefan reported on the work on the web service [http://correspsearch.bbaw.de correspSearch]
 
- he wrote a blog post on the [http://digiversity.net/2015/perspectives-of-the-further-development-of-the-correspondence-metadata-interchange-format-cmif/ "Perspectives of the further development of the Correspondence Metadata Interchange Format (CMIF)"]
 
 
- Mariana: Does "correspSearch" accept meta data in other languages?
 
- Stefan: with authority files etc. no problem


- Mariana: Does correspSearch accept meta data in other languages? Stefan: with authority files etc. no problem
- Peter: information on language of letter in CMIF might be helpful
- Peter: information on language of letter in CMIF might be helpful
- Patrizia: case of translations of one letter into different languages
- Patrizia: case of translations of one letter into different languages
- Stefan: introducing this feature in correspSearch might be a good idea


- Stefan: introducing this feature in "correspSearch" might be a good idea
* spread the word
- Anne: recent meeting of CostAction and [ http://republicofletters.stanford.edu/ Mapping the Republic of Letters]
- we should talk to Pip Willcox to make <correspDesc> and "correspSearch" known
- we could write a little standard text to send around to make our work known
* best-practice model
- Patrizia asks for a structure that could be copied, for a best-practice model
- Patrizia asks for a structure that could be copied, for a best-practice model
- Peter: this is our next step to develop a best-practice model, already some example online on GitHub and in TEI Guidelines
- Maria: We could prepare some stylesheets
- Anne: a collection of examples perhaps better because less normative


- Peter: our next step is to develop a best-practice model
- already some [https://github.com/TEI-Correspondence-SIG/correspDesc/tree/master/examples examples online on GitHub] and in TEI Guidelines [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/examples-correspDesc.html (eg.g. here)]
- Maria: we could also prepare some stylesheets
- Peter: possible to create stylesheets to convert regular <correspDesc> to CMIF
- Stefan: use cases for that needed
- stylesheets for extracting all <correspDesc> elements from a corpus
* envelopes
- Mariana: problems with envelopes, where to encode the occurrence of an envelope
- Mariana: problems with envelopes, where to encode the occurrence of an envelope
- Peter: address can be part of header and also body (normalized data vs. transcription of address)
 
- occurrence of envelope should go into physDesc → example
- occurrence of envelope should go into <physDesc> → example
- How does DALF P5 do that?
 
- Peter: address can be part of <teiHeader> and also of <body> (normalized data vs. transcription of address)
 
- How does DALF P5 do that? [http://ctb.kantl.be/project/dalf/P5/DALF_P5-p0.1.zip (ODD file, documentation, schema, and example in this zip file)]
 
 
* type of correspondence and taxonomy
- Mariana: encoding of type of correspondence and attachments, non-textual assets found in the envelope
- Mariana: encoding of type of correspondence and attachments, non-textual assets found in the envelope
- counter-argument was: type of correspondence belongs to profileDesc
 
- counter-argument was: type of correspondence belongs to <profileDesc>
 
- SIG could come up with a taxonomy/thesaurus as a suggestion
- SIG could come up with a taxonomy/thesaurus as a suggestion
- perhaps libraries, archives, post museums already have taxonomies
- perhaps libraries, archives, post museums already have taxonomies
- Patrizia: in Paris is a museum of letters and correspondence, with another branch in Brussels
- Patrizia: in Paris is a museum of letters and correspondence, with another branch in Brussels
- Stefan: ask mailing list
- Stefan: ask mailing list


- Peter: possible to create stylesheets to convert regular correspDesc to CMIF
- Stefan: use cases for that needed
- stylesheets for extracting all correspDescs from a corpus


- Mariana: Do older versions of Oxygen work with correspDesc?
* oXygen XML editor
- Mariana: Do older versions of Oxygen work with <correspDesc>?
 
- Peter: these files don’t validate, one could update the TEI Add on
- Peter: these files don’t validate, one could update the TEI Add on


Future plans
===Future plans===
- examples
* provide examples
- documentation
* provide documentation
- taxonomy/thesaurus as a suggestion
* taxonomy/thesaurus as a suggestion
- best-practice model
* provide best-practice model
- stylesheets for extracting all correspDescs from a corpus
* provide stylesheets for extracting all <correspDesc> elements from a corpus
- long-term goal: textual features
* long-term goal: How to encode textual features with TEI?

Latest revision as of 14:49, 6 December 2015

TEI SIG on Correspondence - Minutes Lyon, Oct 29, 2015

Status: draft --User: Seifert, 06 December 2015 (EST)

Attendees

Attendees gave a short introduction on their ongoing and/or planned projects:

Report on last year’s activities

It was a successful year:

  • further development of <correspDesc> and introduction into the TEI standard
  • workshop on "Encoding correspondence meta data with <correspDesc>" held at the TEI conference 2015
  • accepted article for jTEI: "Towards a model for encoding correspondence in the TEI. Developing and implementing <correspDesc>" by Marcel Illetschko, Sabine Seifert, Peter Stadler (not yet published)
  • further development of the Correspondence Metadata Interchange format (CMI)
  • collaboration for the development of the web service correspSearch

Discussion

  • SIG for Computer-Mediated Communication

- they work on the same problems as we do concerning meta data and the structure of the communication

- <post> element for a tweet or a posting what would be a letter for us - they plan to file a feature request for that

- they took our <correspAction> and turned it into an attribute

- Peter: we should join forces with them


  • "correspSearch"

- Stefan reported on the work on the web service correspSearch

- he wrote a blog post on the "Perspectives of the further development of the Correspondence Metadata Interchange Format (CMIF)"


- Mariana: Does "correspSearch" accept meta data in other languages?

- Stefan: with authority files etc. no problem

- Peter: information on language of letter in CMIF might be helpful

- Patrizia: case of translations of one letter into different languages

- Stefan: introducing this feature in "correspSearch" might be a good idea


  • spread the word

- Anne: recent meeting of CostAction and [ http://republicofletters.stanford.edu/ Mapping the Republic of Letters]

- we should talk to Pip Willcox to make <correspDesc> and "correspSearch" known

- we could write a little standard text to send around to make our work known


  • best-practice model

- Patrizia asks for a structure that could be copied, for a best-practice model

- Peter: our next step is to develop a best-practice model

- already some examples online on GitHub and in TEI Guidelines (eg.g. here)

- Maria: we could also prepare some stylesheets

- Peter: possible to create stylesheets to convert regular <correspDesc> to CMIF

- Stefan: use cases for that needed

- stylesheets for extracting all <correspDesc> elements from a corpus


  • envelopes

- Mariana: problems with envelopes, where to encode the occurrence of an envelope

- occurrence of envelope should go into <physDesc> → example

- Peter: address can be part of <teiHeader> and also of <body> (normalized data vs. transcription of address)

- How does DALF P5 do that? (ODD file, documentation, schema, and example in this zip file)


  • type of correspondence and taxonomy

- Mariana: encoding of type of correspondence and attachments, non-textual assets found in the envelope

- counter-argument was: type of correspondence belongs to <profileDesc>

- SIG could come up with a taxonomy/thesaurus as a suggestion

- perhaps libraries, archives, post museums already have taxonomies

- Patrizia: in Paris is a museum of letters and correspondence, with another branch in Brussels

- Stefan: ask mailing list


  • oXygen XML editor

- Mariana: Do older versions of Oxygen work with <correspDesc>?

- Peter: these files don’t validate, one could update the TEI Add on

Future plans

  • provide examples
  • provide documentation
  • taxonomy/thesaurus as a suggestion
  • provide best-practice model
  • provide stylesheets for extracting all <correspDesc> elements from a corpus
  • long-term goal: How to encode textual features with TEI?
Retrieved from "https://wiki.tei-c.org/index.php?title=SIG_meeting_Lyon&oldid=14638"