February 2015 - Tei-council

Recommendations on values of @xml:id (FR #540)
by Raffaele Viglianti 31 May '15

31 May '15

Hi all, Martin Mueller asked on the list for recommendations on good uses of xml:ids, which resulted in a good discussion and a FR. I summarized the main suggestions on the ticket on SourceForge, but I post them here as well because I think we need to discuss this further, see below. The Guidelines already have some recommendations (numbering based on doc structure): * The Guidelines already suggest numbering based on doc structure ( http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#CORS2) * Use 3 letters (e.g. from the title)+ 3 digits, incremental. E.g. HOL001, HOL002, etc.. * Same as above, but no fix number of digits. E.g. HOL1, HOL2, etc. * Prefix an id with name of element (this is simpler version of what the Guidelines already recommend) * Give tei:TEI an id and prefix every other id in the document with it (to guarantee cross-corpus uniqueness) These are all reasonable suggestions and there can be plenty more - which is why I think that the TEI should *not* give any recommendation on best practices for xml:id because it's a project management issue, not an encoding one. Myself, I prefer random ids, a practice that avoids introducing yet another level of complexity and data management. I understand the human readability, but sequences are too easily broken. And when parsing, relying on ID content instead of TEI content sounds like a bad idea.

7 16

MsPart Comments
by Hugh Cayless 13 Mar '15

13 Mar '15

Hoping to spark some comment. As you might expect, I'm *strongly* in favor of permitting the use of msPart for describing fragments, so all I have are quibbles: 1) I don't thing the distinction should be "composite" vs. "dispersed". The fragments of a broken up (e.g. papyrus) text aren't necessarily scattered (though they may be), but the text *is* in bits rather than joined or bound together, and those bits may each have their own identifiers and their own histories. 2) In the proposed text rewording "only remaining fragment of a former codex", the word "codex" excludes papyri and inscriptions. 3) I'm not sure I understand the altIdentifier/msPart issue...

7 17

correspAction@type
by Peter Stadler 13 Mar '15

13 Mar '15

The last changes made by Lou introduced the suggested values „sentBy“ „deliveredTo“ etc. to correspAction@type [1]. I’d like to propose skipping the preposition and simply call those „sent“, „delivered“ etc. because we usually describe three things within <correspAction>, i.e. the date, the place and the actor. Since there is not one preposition that (grammatically) fits all items, and because I like the analogy with email terminology, I think it’s best to only have „sent“, „received“, „forwarded“, „redirected“ and „transmitted“. Cheers Peter [1] http://teijenkins.hcmc.uvic.ca/job/TEIP5/lastSuccessfulBuild/artifact/relea…

3 3

next oXygen release
by James Cummings 28 Feb '15

28 Feb '15

As I was asking them about something they told me would be in the oXygen 17 release (being able to populate oXygen forms properties from remote files, e.g. in lists of attribute values from a remote file being used in a dropdown menu) I happen to ask them when oXygen 17 was planned. George answered saying: On 28/02/15 16:16, oXygen XML Editor Support (George Bina) wrote:> Hi James, > > We plan oXygen 17 for end of April / beginning of May. > > Best Regards, > George So that is after our intended release... so let's make that release on time!! -James -- Dr James Cummings, James.Cummings(a)it.ox.ac.uk Academic IT Services, University of Oxford

2 1

msDesc proposal
by Martin Holmes 28 Feb '15

28 Feb '15

I seem to be unable to comment on the msDesc proposal here: <https://docs.google.com/document/d/1bpBPughQp5sOoB13iTMHMeRd88Mjv12_eGZiQXY…> so I'll raise a quick question here. I'm a bit confused about the second definition; where it says: "In this case, the original manuscript is being encoded with msPart in order to provide information about the dispersed parts, or one distinct part is being encoded." Does this mean that, conceivably, the "larger original manuscript" is being encoded with a _single_ msPart, or that it's being encoded with a _series_ of msPart elements, one for each component? Cheers, Martin

5 9

Friday's Telecon; Agenda Items?
by Hugh Cayless 27 Feb '15

27 Feb '15

Dear all, A reminder that our next teleconference will be this Friday, February 27, at 05:30 PST | 08:30 EST | 13:30 GMT | 14:30 CET. I've posted a draft agenda at http://wiki.tei-c.org/index.php/Council_agenda_2015-02 Please add, remove, or modify agenda items as necessary. There are a couple of items we could profitably discuss beforehand on-list, including the transcription of spoken language draft and the suggested msPart updates. All the best, Hugh

5 6

My Conference Info
by Hugh Cayless 27 Feb '15

27 Feb '15

Hi all, I’m having trouble finding the list of international numbers on the Economy Conference Call site, but here’s what was in the email they sent me. You should be able to dial the toll free (US, so prefix +1) number using Skype. Toll-Free: 866-906-0040 Toll: 857-288-2640 Code: 5753850 Here’s the set of number changes that John forwarded me: Locale Old Dialed Number New Dialed Number GERMANY (Land) 08001820270 08001800565 GERMANY (Mobile) 08001820270 08001814978 UK (London Local) 442034785604 442033186423

3 3

Agenda for Friday's Telecon
by Hugh Cayless 27 Feb '15

27 Feb '15

Hi all, I’ve put up an agenda for our teleconference on Friday, Jan 30 at 14:00 GMT: http://wiki.tei-c.org/index.php/Council_agenda_2015-01 <http://wiki.tei-c.org/index.php/Council_agenda_2015-01> It’s mostly a copy of the previous one, on the assumption that we probably didn’t make much progress over the holidays and the review will likely be good for all of us, especially our new members. Please do add new items for discussion (or remove items there’s nothing to report on). It will take me a while to figure out how things work, so reminders of anything I may have missed, or suggestions for how things might be done better are most welcome! All the best, Hugh

8 17

Minutes Link
by Hugh Cayless 27 Feb '15

27 Feb '15

https://docs.google.com/document/d/1bfUCykhiABF7JP_KqSyprrI8n-qgcnMstJhBOuV…

1 0

feedback requested
by Lou Burnard 26 Feb '15

26 Feb '15

Could someone please comment on my proposed actions concerning this longstanding FR? https://sourceforge.net/p/tei/feature-requests/480/ It's the one about classifying the use of @hand better...

2 1