March 2015 - Tei-council - lists.tei-c.org

conference call in 6 hours
by Syd Bauman 27 Mar '15

27 Mar '15

I may be a bit tired, but I plan to attend. (To see why, check out http://bauman.zapto.org/~syd/albums/2015-03-27_car_fire/; interesting to note that the table of metadata is generated with XSLT 1.0.) Can someone post * the phone number to call and conferene number to punch in; and * the URL of the minutes, if we're doing that in GoogleDocs again? Thanks.

1 0

Re: [tei-council] Google Code shutting down
by Martin Holmes 22 Mar '15

22 Mar '15

On 15-03-22 03:04 PM, Sebastian Rahtz wrote: >> On 21 Mar 2015, at 18:00, Martin Holmes <mholmes(a)uvic.ca> wrote: >> While we're looking at these downloads on SF, I think we should now >> remove TEIOO: >> >> <http://sourceforge.net/projects/tei/files/> > yes please. zap it dead. Done. I have copies of the last downloads just in case. They should probably go somewhere for archive, but we're against "obsolete" folders in repos IIRC, so I don't know where we should put them. What about tei-emacs? Cheers, Martin > -- > Sebastian Rahtz > Chief Data Architect > University of Oxford IT Services > 13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431 > > >

1 0

Fwd: Google Code shutting down
by Hugh Cayless 21 Mar '15

21 Mar '15

This affects the TEI Oxygen framework. GitHub anyone? Sent from my phone. Begin forwarded message: > From: google-code-noreply(a)google.com > Date: March 12, 2015 at 21:07:34 EDT > To: philomousos(a)gmail.com > Subject: Google Code shutting down > Reply-To: google-code-noreply(a)google.com > > Code > Hello, > > Earlier today, Google announced we will be turning down Google Code Project Hosting. The service started in 2006 with the goal of providing a scalable and reliable way of hosting open source projects. Since that time, millions of people have contributed to open source projects hosted on the site. > > But a lot has changed since 2006. In the past nine years, many other options for hosting open source projects have popped up, along with vibrant communities of developers. It’s time to recognize that Google Code’s mission to provide open source projects a home has been accomplished by others, such as GitHub and Bitbucket. > > We will be shutting down Google Code over the coming months. Starting today, the site will no longer accept new projects, but will remain functionally unchanged until August 2015. After that, project data will be read-only. Early next year, the site will shut down, but project data will be available for download in an archive format. > > As the owner of the following projects, you have several options for migrating your data. > > epidoc > The simplest option would be to use the Google Code Exporter, a new tool that will allow you to export your projects directly to GitHub. Alternatively, we have documentation on how to migrate to other services — GitHub, Bitbucket, and SourceForge — manually. > > For more information, please see the Google Open Source blog or contact google-code-shutdown(a)google.com. > > -The Google Code team > > Google Inc. 1600 Amphitheatre Parkway, Mountain View, CA 94043 > You have received this mandatory email service announcement to update you about important changes to Google Code Project Hosting. > >

7 10

Dates now fixed for F2F?
by Martin Holmes 20 Mar '15

20 Mar '15

I have a vague memory we're waiting for Paul to confirm, but I'd like to book travel if possible. Cheers, Martin

6 16

#505 Redefine <msPart>
by Peter Stadler 17 Mar '15

17 Mar '15

Dear all, I think we can move on with the ticket 505 „redefine <msPart>“. A I read the responses on TEI-L, there is a majority in favor of widening the semantics of <msPart> to include fragments. The related issue #661 concerned with empty content of <msIdentifier> (or to make it optional) seems to get rejected, in contrast. So, we need to alter the description of <msPart> as well as some prose as explained in [1]. Concerning examples, I can provide a 19th century letter … Stefanie, would you like to go on and implement those changes? Best Peter [1] https://docs.google.com/document/d/1bpBPughQp5sOoB13iTMHMeRd88Mjv12_eGZiQXY…

4 5

Fwd: purifying datatypes
by Lou Burnard 17 Mar '15

17 Mar '15

I just posted a message to the somnolescent tei-odds list on this topic, with some detailed proposals as an attachment did anyone see them?

2 1

@allowText still lurks
by Lou Burnard 17 Mar '15

17 Mar '15

Last time I taught pure ODD (last month, in Paris) someone pointed out to me that we have forgotten to remove @allowText from <content> and from the class att.repeatable. Unless someone comes up with a good reason why not, I propose to remove it tomorrow. We agreed back in November that <textNode> was all we needed.

2 1

Order in listChange
by Raffaele Viglianti 14 Mar '15

14 Mar '15

Hi all, I just wanted to do a final check with you before acting on Bug 706 <https://sourceforge.net/p/tei/bugs/706/>. The comments seem to favour imposing a reverse chronological order of changes on listChange, but that would contradict the role of the optional attribute @ordered. Should we impose a reversed chronological order only when @ordered=true? Should we go as far as making @when required? The examples on the guidelines suggest a reverse chronological order when there is no @ordered and a chronological order when @ordered=true http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-listChange.html Thanks for your input, Raff

5 9

Ticket assignments
by Hugh Cayless 13 Mar '15

13 Mar '15

As you’ll probably have seen from the slew of sourceforge emails, I’ve made an almost totally random assignment of bugs to the folks with the fewest bugs/FRs on their plates. I didn’t assign the one unassigned FR (https://sourceforge.net/p/tei/feature-requests/546/ <https://sourceforge.net/p/tei/feature-requests/546/> —which is Lou’s) because we didn’t get to discuss it. Can we do so now via the list? Thanks all! Hugh

4 7

URLs in example code in the Glines
by Martin Holmes 13 Mar '15

13 Mar '15

HI all, A ticket was just raised: <https://sourceforge.net/p/tei/bugs/744/> by Martin de la Iglesia, who noticed that a couple of URLs in example code were not working. Our current link-checking system doesn't handle this, because it simply checks HTML links in the Guidelines web version; the URLs in examples are of course just rendered as text, so they are not checked. I just link-checked all the URLs in examples -- there are several hundred, but many are duplicates. My question is: should we care if these links are broken? Many are designed not to work anyway (www.example[s].com|org, for instance -- but others are clearly intended to be genuine. There are many duplicates, but if I filter out the dupes and the example.x ones, there are 9 404s, a 303 and a few missing hostnames. Is it worth following up on this to fix these, and adding this sort of check to the current link checking, or is it not worth the trouble? Cheers, Martin

1 0