February 2015 - Tei-council

F2F poll results
by Hugh Cayless 25 Feb '15

25 Feb '15

Looks like we have (sort of) a winner: the week of April 27–May 1. Raffaele marked "if need be" for the 27th–29th and Lou and Fabio for the 29th–May 1. How much of a problem are those conflicts? In particular, would travel to the US or Europe make them impossible? If I’m not mistaken, these are the offers to host we’ve had so far: ## US Boston (Syd) College Park (Raffaele) Ann Arbour (Paul) ## Canada Victoria (Martin) ## Europe Mainz (Peter) Estonia (maybe…) Is that correct? Other takers or ideas? Hugh /** * Hugh A. Cayless, Ph.D * hugh.cayless(a)duke.edu * Duke Collaboratory for Classics Computing (DC3) * http://blogs.library.duke.edu/dcthree/ **/

11 59

Suggested typology for correspAction
by Lou Burnard 18 Feb '15

18 Feb '15

I'd like to propose some change to this. Firstly I find the current descriptions of the various valItems a bit cumbersome and non-idiomatic. e.g. "identifies a/the sending action of the message" The use of "a/the" for "a or the" is not something we do elsewhere, nor do I think it necessary here. It's not obvious what "the sending action of the message" means either -- the message is not carrying out the sending! The description should explain what this value of the @type attribute implies, and therefore in what circumstances it should be chosen. I suggest something like "information concerning the creation or authorship of a message". I'd prefer to see the suggested values as nouns rather than gerunds, as elsewhere. So "despatch" rather than "sending", "receipt" rather than "receiving". (But I appreciate that this may cause some upsets in existing data) I would like to see a suggestion for the "authoring" correspAction, since the text does talk about this (when introducing use of @sameAs) The distinction between "receiving" and "transmitting" needs to be clarified. I would say the same for the distinction between "redirecting" and "forwarding", except that I am not sure that I know what the distinction is in that case. So, my revised valList for correspAction/@type looks like this: <valList type="semi" mode="add"> <valItem ident="creation"> <desc versionDate="2015-02-09" xml:lang="en"> information concerning the creation or authorship of a message</desc> </valItem> <valItem ident="despatch"> <desc versionDate="2015-02-09" xml:lang="en"> information concerning the sending or despatch of a message</desc> </valItem> <valItem ident="receipt"> <desc versionDate="2015-02-09" xml:lang="en"> information concerning the receipt of a message</desc> </valItem> <valItem ident="transmission">  <desc versionDate="2015-02-09" xml:lang="en"> information concerning the transmission of a message after it has been despatched</desc> </valItem> <valItem ident="redirection">  <desc versionDate="2015-02-09" xml:lang="en"> information concerning the redirection or forwarding of a message </desc> </valItem> </valList>

6 14

correspAction example
by Lou Burnard 18 Feb '15

18 Feb '15

In Shakespeare's Twelfth Night, the clown Feste carries a letter to the steward Malvolio. The letter is unsigned, but Malvolio thinks it is from the lady Olivia. In fact, it was written by her maid Maria, in collaboration with Sir Toby Belch. So... <correspAction type="deliveredTo"> <persName>Malvolio</persName> </correspAction> <correspAction type="deliveredBy"> <persName>Feste</persName> </correspAction> <correspAction type="sentBy" subtype="mistaken"> <persName>Olivia</persName> </correspAction> <correspAction type="sentBy" subtype="actual"> <persName>Maria</persName> </correspAction> <correspAction type="sentBy" subtype="actual"> <persName>Sir Toby Belch</persName> </correspAction> Does that sound plausible? Can someone come up with another better example showing a variety of correspActions?

1 0

Spring meeting
by Hugh Cayless 16 Feb '15

16 Feb '15

Can I encourage those of you who haven't participated in the "let's just choose a date and place" poll at http://doodle.com/fk8qbq6rrrn7qugq to do so if you care at all about the outcome? Right now, we're leaning (by one vote) toward Durham at the end of April. I'll plan on closing the poll on Monday. All the best, Hugh

7 14

correspDesc implementation
by Peter Stadler 11 Feb '15

11 Feb '15

Dear all, a brief report on my work on correspDesc. (I’ll respond to Lou’s input separately) (I’m a little bit behind with documentation because my children passed their illnesses on to me …) So, I implemented correspDesc in revision 13129 and only needed three shots to make the Jenkins servers build the Guidelines (Yeah!). That said, I needed several tries locally before (which to my surprise worked almost flawlessly). I found it especially useful to run only the 'p5.xml‘ target which is quite quick and will create p5subset.xml along with p5.xml. This was helpful, because my naive assumption was that everything under P5/Source/Specs would automagically be included. It is not, you rather need a <specGrp> (in some Guidelines chapter?) with Xincludes of the files. * So, question 1: is this a bug or a feature? if it’s a feature (what I do think, because we do not implement elements without accompanying prose, do we?) it should probably be documented in TCW20 or did I missed it?! * question 2: how are the xml:ids (for <specGrp>s, <div>s etc) within the Guidelines chapters created? I just made them up … Best Peter

3 7

Backlinks at element description
by Peter Stadler 11 Feb '15

11 Feb '15

How do I get those nice backlinks (see the link "[2.4.4 Abstracts]“ at http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-abstract.html) into my correspDesc element description. Is this listRef/ptr-magic? Best Peter

2 1

correspDesc desc update
by Lou Burnard 11 Feb '15

11 Feb '15

As most of you will have noticed, over the weekend Peter quite rightly added a new section to the Header chapter describing correspDesc, along with associated ODDs to implement the proposals. I feel very guilty for not having found time to feedback suggestions for the new text (which I promised to do months ago).,.. but here they are now! I haven't checked the following in yet, but am happy to do so. As the section is quite short, I am just pasting it into this message. We're all grown ups here and can cope with a few TEI tags, right? My revisions are mostly to enlarge and make a bit more explicit what the examples are doing, plus a few other things changed for conformity with house style. I have however reordered the original, putting correspContext first, since it is simpler and shorter than the rest and I didn't want to introduce new subsections. I am not certain that I've properly understood the last and first examples, so please read my rewording carefully! -------- <div type="div3" xml:id="HD44CD"> <head>Correspondence Description</head> The <gi>correspDesc</gi> element is used within the <gi>profileDesc</gi> element to provide detailed correspondence-specific metadata, concerning in particular the communicative aspects (sending, receiving, forwarding etc.) associated with acts of of correspondence. This information is intended to complement the description of the objects recording correspondence activities (such as letters), typically provided by the <gi>sourceDesc</gi> element. <specList> <specDesc key="correspDesc"/> </specList> The <gi>correspDesc</gi> element contains the elements <gi>correspAction</gi> and <gi>correspContext</gi>, describing the actions identified and the context in which the correspondence occurs respectively. <specList> <specDesc key="correspAction" atts="type"/> <specDesc key="correspContext"/> </specList> Acts of correspondence typically do not occur in isolation from each other. The <gi>correspContext</gi> element is used to group references relevant to the item of correspondence being described, typically to other items such as the item to which it is a reply, or the item which replies to it: <egXML xmlns="http://www.tei-c.org/ns/Examples"> <correspContext> <ref type="replyTo" target="#CLF0102">Previous letter of Chamisso to de La Foye: 16 January 1807</ref> <ref type="replyFrom" target="#CLF0104">Next letter of Chamisso to de La Foye: 07 May 1810</ref> </correspContext> </egXML> Many types of correspondence action may be distinguished. The <att>type</att> attribut should be used to indicate the type of action being documented, using values such as those suggested above. The following basic example uses <gi>correspAction</gi> to describe the sending of a letter by Adelbert von Chamisso from Vertus at 29 January 1807 to Louis de La Foye at Caen. The date of reception is unknown: <egXML xmlns="http://www.tei-c.org/ns/Examples"> <correspAction type="sending"> <persName>Adelbert von Chamisso</persName> <placeName>Vertus</placeName> <date when="1807-01-29">29 January 1807</date> </correspAction> <correspAction type="receiving"> <persName>Louis de La Foye</persName> <placeName>Caen</placeName> <date>unknown</date> </correspAction> </egXML> Several senders, recipients, etc. can be specified for a single <gi>correspAction</gi> if the action is considered to apply to them all acting as a single group. In the following example three people are considered to have received the communication. <egXML xmlns="http://www.tei-c.org/ns/Examples"> <correspAction type="receiving"> <persName>Hermann Hesse</persName> <persName>Ninon Hesse</persName> <placeName>Montagnola</placeName> </correspAction> </egXML>  The <att>subtype</att> attribute may be used to further distinguish types of action. In the following example, an e-mail is sent to two people directly and to a third by blind copy (<term>cc</term>). <egXML xmlns="http://www.tei-c.org/ns/Examples"> <correspAction type="sending"> <persName>PN0001</persName> <date when="1999-06-02">Wed, 02 Jun 1999</date> </correspAction> <correspAction type="receiving" subtype="to"> <persName>PN0002</persName> </correspAction> <correspAction type="receiving" subtype="to"> <persName>PN0003</persName> </correspAction> <correspAction type="receiving" subtype="cc"> <persName>PN0004</persName> </correspAction> </egXML> The same person may often be associated with many actions. For example, it will often be the case that the author and sender of a message are identical, and that many individual letters will need to be associated with the same person. The <att>sameAs</att> attribute defined in section <ptr target="#SAIE"/> may be used to indicate that the same name applies to many actions. Its value will usually be the identifier of an element defining the person or name concerned, which is supplied elsewhere in the document. <egXML xmlns="http://www.tei-c.org/ns/Examples"> <correspAction type="sending"> <name sameAs="#author"/> </correspAction> </egXML>  It is assumed that each correspondence action applies to a single act of communication. It may however be the case that the same physical object is involved in several such acts, if for example person A sends a letter to person B, who then annotates it and sends it on to person C, or if persons A and B both use the same document to convey quite different messages. In such situations, multiple <gi>correspDesc</gi> elements should be supplied, one for each communication. In the following example, the same document contains distinct messages, sent by two different people. to the same destination: <gi>correspDesc</gi> is used for each separately: <egXML xmlns="http://www.tei-c.org/ns/Examples"> <correspDesc xml:id="message1"> <correspAction type="sending"> <persName>John Gneisenau Neihardt</persName> <placeName>Branson (Montgomery)</placeName> <date>17 December 1932</date> </correspAction> <correspAction type="receiving"> <persName xml:id="JTH">Julius Temple House</persName> <placeName>New York</placeName> </correspAction> </correspDesc> <correspDesc xml:id="message2"> <correspAction type="sending"> <persName>Enid Neihardt</persName> <placeName>Branson (Montgomery)</placeName> <date>17 December 1932</date> </correspAction> <correspAction type="receiving"> <persName sameAs="#JTH"/> <placeName>New York</placeName> </correspAction> </correspDesc> </egXML>

2 3

Bug and FR assignments
by Hugh Cayless 10 Feb '15

10 Feb '15

Hi all, As promised, I’ve gone through the unassigned bugs and feature requests and assigned them, mostly arbitrarily based on who’s currently working on the fewest things. For the new folks: being assigned a Feature Request doesn’t mean just go do it :-), it means you’re responsible for making sure it gets discussed adequately and then implemented, revised, broken up into smaller implementable chunks, rejected, quietly neglected for years, etc. Do speak up if you think an assignment is grossly unfair! I haven't assigned the latest FR, https://sourceforge.net/p/tei/feature-requests/546/ <https://sourceforge.net/p/tei/feature-requests/546/> yet, because it looked like there’s much active discussion with possibly some consensus emerging. All the best, Hugh

1 0

Development version of oxygen-tei plugin available
by Martin Holmes 08 Feb '15

08 Feb '15

Hi all, I now have a development build of the oxygen-tei add-on working. You can subscribe from here: <http://teijenkins.hcmc.uvic.ca/job/oxygen-tei/lastSuccessfulBuild/artifact/…> If you're brave enough to try it, uninstall the regular version of the add-on before installing this one. I can also confirm that James was right: you can provide access to multiple versions of the plugin, allowing people to roll back to a previous version if something breaks, by providing multiple <xt:extension> elements in the updateSite.oxygen file. This seems to be working well with the URL above: if, when you're subscribing to the plugin (Help / Install New Add-Ons) you uncheck the "Show only the latest versions of the add-ons", you'll see there are three versions available. I have it set up so we'll keep the last ten versions available. I've subscribed myself, so I should be able to see if anything goes wrong. If you do test it, be aware that if you have transformation scenarios (for instance) that depend on the absolute location of the TEI extension framework, those paths will no longer work; Oxygen stores the add-on data in a path which includes a modified version of the URL of the updateSite.oxygen file. It's easy to change back to the standard TEI release, though. A new version of the plugin will be built and "released" every time the Stylesheets or P5 are rebuilt; the former triggers the latter, so the overall process takes quite a while, but the build of the oxygen-tei plugin itself takes only a few seconds. I'm copying Sebastian on this because my Jenkins is still reporting build failures and successes to him, as the Oxford one does to me, and I want to confirm that this should continue (or if it shouldn't, then what should happen instead). I'd also like to get this setup working on the Oxford Jenkins so we have some redundancy. The next step is to create some tests we can run in Oxygen to check core functionality of the add-on. I envisage this as an Oxygen project with a bunch of sample files that are transformed or otherwise manipulated and the results checked. These files would presumably live in the oxygen-tei repo. Cheers, Martin

5 27

getting mad with makefile
by Fabio Ciotti 07 Feb '15

07 Feb '15

Hi all, I'm struggling with Makefile from svn repo. Any time I try to make I have this error BUILD FAILED /media/Archivio/src/tei-code/P5/antbuilder.xml:102: Fatal error during transformation using /usr/share/xml/tei/stylesheet/odds/odd2relax.xsl: A sequence of more than one item is not allowed as the result of function tei:generateRefPrefix() ("TEI_model.contentPart", "TEI_model.contentPart", ...) ; SystemID: file:/usr/share/xml/tei/stylesheet/odds/teiodds.xsl; Line#: 2339; Column#: -1 The first time I've run it this morning (after implementing a ticket) it has worked. Then before to check I thought to implement a couple of other tickets, make again to see if something had broken and the error jumped out, but it has apparently nothing to do with my modifications. I have already tried to: make clean 1000 times delete and download again my stylesheets deb try to use online stylesheets as referenced in the makefile (nope the URL is broken) re-checkout the trunk and try the build with an untouched svn local copy curse all the possible deities hit the pc with a baseball bat any hint??? f

3 4