[tei-council] report on <correspDesc> proposal

[Peter Stadler]

Hi Fabio,

many thanks for your comments and encouragement!
We (correspDesc taskforce) had a telco last Friday and discussed your points (minutes to follow).

Am 27.03.2014 um 12:14 schrieb Fabio Ciotti:

> I think it is a good proposal. Only two question:

> 1) I'm not an expert, but in general I tink interoperability is good.
> Did you see the possible intersection wit EAD i  this area?
Well, not EAD specifically but we are looking at Europeana right now. I think establishing interoperability at that level would really rock — but I don’t have any details yet. Anyway, we will have a look at EAD now as well and in the best case this will merge with our Europeana efforts.

> 2) I feel a little bit puzzled by the insertion of this kind of
> metadata inside sourceDesc (in general I think the uses of this
> section in TEI are rather diverse e semantically non coherent). Why
> not in profileDesc (maybe I'm missing something though)?
No, that’s a good point and I know e.g. the "TEI Legal Encoding Extensions" have gone with <profileDesc>. Still, we believe the information to be captured within <correspDesc> is of bibliographic nature (at least to some extent … e.g. letters are frequently cited by date, sender and addressee). So, we made <correspDesc> member of model.biblLike which as a consequence makes <correspDesc> appear in <sourceDesc> (but not only!).

Best
Peter

[1] http://wulibraries.typepad.com/digitalgateway/2010/11/tei-legal-encoding-extensions-first-draft.html

> 2014-03-26 14:34 GMT+01:00 Peter Stadler <stadler at edirom.de>:
>> Dear Council fellows, dear Martin,
>> 
>> one of my actions from the last conf call was to report on the proposal we are currently preparing with the Correspondence SIG task force „correspDesc“. I will do so in some brevity just to outline our roadmap and to point you at the resources we already have. I copied Martin in since one of my questions is whether to turn this into a workshop for the TEI MM at Northwestern (jump to „Workshop“ if you want to skip the report).
>> 
>> Ok, you might know that the <correspDesc> element has been on the SIG’s agenda since its first meeting in 2008. The general idea is to have a dedicated section in the teiHeader for correspondence specific meta data such as sender, addressee, etc. This stems back from the DALF guidelines [1] and was picked up by our own project WeGA [2]. There are more issues to encoding correspondence (postscript, signed/salute etc.) but with our current task force we decided to focus on the meta data first since it seemed less uncontroversial and wouldn’t break current schemas.
>> Apart from creating extra TEI elements and allowing the full fledged standard to be applied to letters and the like we are also looking into extracting a minimal subset for what we call „correspondence interchange format“. The basic idea is to have a simple catalogue (a list) of correspondence items for each repository which can be harvested by a central web service, thus interconnecting letter collections by persons, dates and places.
>> What we’ve done so far is documented at [3], and ODD files and examples can be grabbed at [4].
>> 
>> Roadmap
>> The schema is more or less settled (well, there are still some issues) and right now we are trying to put together and polish the prose descriptions.
>> We will then create a formal feature request for discussion at the Oxford f2f.
>> 
>> Workshop
>> I think the Genetic Encoding group did a good job in organizing a workshop after the approval for disseminating its work. Surely, I don’t want to anticipate Council’s decision on this proposal but if it *was* accepted I think it would be nice to have a workshop for this?! (If we had a workshop, I think we could skip the SIG meeting)
>> Well, I’m just pushing these ideas out since it’s almost end of March … please excuse any shortcomings.
>> 
>> Looking forward to your feedback and all the best
>> Peter
>> 
>> [1] http://ctb.kantl.be/project/dalf/dalfdoc/index.html
>> [2] https://github.com/Edirom/WeGA-ODD
>> [3] http://wiki.tei-c.org/index.php/SIG:Correspondence/task-force-correspDesc
>> [4] https://github.com/TEI-Correspondence-SIG/correspDesc
>> 
>> 
>> --
>> tei-council mailing list
>> tei-council at lists.village.Virginia.EDU
>> http://lists.village.Virginia.EDU/mailman/listinfo/tei-council
>> 
>> PLEASE NOTE: postings to this list are publicly archived
> -- 
> tei-council mailing list
> tei-council at lists.village.Virginia.EDU
> http://lists.village.Virginia.EDU/mailman/listinfo/tei-council
> 
> PLEASE NOTE: postings to this list are publicly archived

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 455 bytes
Desc: Message signed with OpenPGP using GPGMail
Url : http://lists.village.Virginia.EDU/pipermail/tei-council/attachments/20140401/6f4f4b1a/attachment-0001.bin