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

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

Oxygen release
by Martin Holmes 20 Apr '15

20 Apr '15

George Bina confirms there will be no new Oxygen release before 17, scheduled for the end of April/beginning of May. That's perfect timing for us. It gives a window of three weeks for our version of the plugin to be out in the wild and in general use before the Oxygen guys build the version they'll be including with the Oxygen distro. Cheers, Martin

5 6

@degree deprication
by Syd Bauman 01 Apr '15

01 Apr '15

We're scheduled to remove @degree in 7.5 months. Should we be removing it from examples now? It occurs in 6 of them, all in "Certainty, Precision, and Responsibility": .../div[1]/div[2]/div[4]/specGrp[1]/elementSpec[1]/exemplum[1]/teix:egXML[1]/teix:precision[1] .../div[1]/div[2]/div[4]/specGrp[1]/elementSpec[1]/exemplum[1]/teix:egXML[1]/teix:precision[2] .../div[2]/p[5]/teix:egXML[1]/teix:precision[1] .../div[2]/p[5]/teix:egXML[1]/teix:precision[2] .../div[2]/p[6]/teix:egXML[1]/teix:residence[1]/teix:precision[1] .../div[2]/p[7]/teix:egXML[1]/teix:precision[1]

3 4

Poll for dataNode discussion
by Hugh Cayless 31 Mar '15

31 Mar '15

Dear all, At the meeting this morning we decided to try to kill two birds with one stone: we want to have a proper discussion of Lou's proposals for pointing to datatypes in Pure ODD (see http://sourceforge.net/p/tei/feature-requests/530/) and we want to see if Google Hangouts are a suitable medium for meetings. We agreed to try to do this next week, at around the same time as we hold Council meetings, with as many people as we can manage. Here's the poll: http://doodle.com/nbhyigzs94vqida8 It would be nice if we could get a bunch of you in, just so that we'll have a proper test and discussion. I don't think this will take a full hour, though of course it depends how chatty/argumentative we are. :-)

4 5

Fwd: Build failed in Jenkins: TEIP5-Test #2588
by Martin Holmes 30 Mar '15

30 Mar '15

Raff, your commit seems to have failed to build, and the email that Jenkins tried to send you to let you know bounced (the SF server says rviglianti(a)users.sourceforge.net does not exist). Could you take a look at the error message below and see if you can fix the problems? It looks as though: < <ERROR>egXML points to non-existent #VESA-eg-1 < (TEI[1]/text[2]/body[3]/div["VE"]/div["VESA"]/p[6]/) </ERROR> you didn't actually add VESA-eg-1 to the Bibliography. < <ERROR>id 'said1297' used more than once</ERROR> < <ERROR>id 'said1298' used more than once</ERROR> < <ERROR>id 'said1299' used more than once</ERROR> xml:ids were used multiple times, which I think is a no-no, even in examples; they're also validated. Cheers, Martin -------- Forwarded Message -------- Subject: Build failed in Jenkins: TEIP5-Test #2588 Date: Mon, 30 Mar 2015 01:17:28 +0100 From: tei(a)oucs.ox.ac.uk To: sebastian.rahtz(a)it.ox.ac.uk, mholmes(a)uvic.ca, rviglianti(a)users.sourceforge.net See <http://bits.nsms.ox.ac.uk:8080/jenkins/job/TEIP5-Test/2588/changes> Changes: [rviglianti] Added subsection suggesting strategies to encode textual structures across verses. Fixes bug #705 ------------------------------------------ Started by an SCM change Building in workspace <http://bits.nsms.ox.ac.uk:8080/jenkins/job/TEIP5-Test/ws/> Updating svn://svn.code.sf.net/p/tei/code/trunk/P5 at revision '2015-03-30T01:15:08.397 +0100' U Source/Guidelines/en/VE-Verse.xml At revision 13190 [workspace] $ /bin/sh -xe /tmp/hudson6312426556303253728.sh ++ pwd + make INJENKINS=true XSL=/srv/hudson/jobs/TEIP5-Test/workspace/../../Stylesheets/lastSuccessful/archive/dist/xml/tei/stylesheet clean validate test (cd Exemplars; make clean) make[1]: Entering directory `/srv/hudson/jobs/TEIP5-Test/workspace/Exemplars' rm -f *.xsd *.dtd *.doc.* *.rnc tei*.xsl tei*.rng *.compiled* *~ *.xi *.isosch *.epub *.pdf *.html *.nvdl *-examples* rm -f exnames.xml rm -f enrich.rng isofs.rng rm -f names.xml *properties rm -f [A-Z]*xml make[1]: Leaving directory `/srv/hudson/jobs/TEIP5-Test/workspace/Exemplars' (cd Test; make clean) make[1]: Entering directory `/srv/hudson/jobs/TEIP5-Test/workspace/Test' rm -f test*.doc.xml test*.rnc test*.dtd test*.compiled.* test*.xsd test*.rnc test*.rng test*.xsl test*.isosch rm -rf LOG *~ *.xsd Schema RomaResults DTD rm -rf *.doc.* rm -f detest.log detest.log.all rm -f *-examples.rng *-examples.rnc *test*.nvdl *-ex.odd rm -f detest.rnc detest.rng detest.dtd detest.isosch make[1]: Leaving directory `/srv/hudson/jobs/TEIP5-Test/workspace/Test' rm -rf release Guidelines Guidelines-web Schema DTD dtd Split rm -rf Guidelines.??? Guidelines-* rm -f *.isosch.xsl rm -f *.stamp rm -f *.xsd rm -f Exemplars/stdout rm -f Test/*.isosch rm -f Test/detest.dtd Test/detest.rnc Test/detest.rng Test/detest.xsl rm -f Test/stdout rm -f Utilities/guidelines.xsl rm -f anything buildweb.xml rm -f p5.sch p5.isosch p5.xml p5subset.xml p5subset.json p5subset.js rm -f p5attlist.txt rm -f p5odds-examples.rng p5odds-examples.rnc p5odds.rng p5odds.rnc p5odds.isosch rm -f pdfbuild.log rm -f stripspace.xsl.model rm -f tei-*.zip rm -f tei-p5-*_*build rm -f tei-p5-*_*changes rm -f tei-p5-*_*deb rm -f teiwebsiteguidelines.zip rm -rf FASC-* rm -rf catalogue.* modList rm -rf valid v.xml ValidatorLog.xml Utilities/pointerattributes.xsl graphics.sh missfont.log v.body v.header Schematron1.xml Schematron2.xml Checking you have running XML tools and Perl before trying to run transform... Ant:/usr/bin/ant Perl:/usr/bin/perl Java:/usr/bin/java xmllint:/usr/bin/xmllint touch check.stamp get latest date: if [ svn = "svn" ] ; \ then \ if [ true ] ; \ then svn info --xml svn://svn.code.sf.net/p/tei/code/trunk/P5 ; \ else svn info --xml ; \ fi > repodate.xml ; \ fi if [ svn = "git" ] ; \ then \ git log --max-count=1 --pretty=format:"<info type=\"git\"><entry><commit revision=\"%h\"><date>%ai</date></commit></entry></info>" > repodate.xml ; \ fi BUILD: Generate modular DTDs, Schemas, Schematron and miscellaneous outputs ANT_OPTS="-Xss2m -Xmx752m -Djava.awt.headless=true" ant -q -lib Utilities/lib/jing.jar:Utilities/lib/saxon9he.jar -f antbuilder.xml -DXSL=/srv/hudson/jobs/TEIP5-Test/workspace/../../Stylesheets/lastSuccessful/archive/dist/xml/tei/stylesheet -DDRIVER=Source/guidelines-en.xml base subset outputs [echo] make modular DTDs, RELAXNG schemas, json, odd schemas, schematron files [echo] Using /srv/hudson/jobs/TEIP5-Test/workspace/../../Stylesheets/lastSuccessful/archive/dist/xml/tei/stylesheet for XSL stylesheets [echo] Do ODD processing for p5odds.odd [echo] Do ODD processing for p5odds-examples.odd BUILD SUCCESSFUL Total time: 1 minute 16 seconds BUILD: Generate modular RELAX NG (compact) schemas using trang (cd Schema; for i in *rng; do java -jar ../Utilities/lib/trang.jar $i `basename $i .rng`.rnc;done) touch schemas.stamp BUILD: Check validity with rnv if we have it command -v rnv && rnv -v p5odds.rnc p5.xml /usr/bin/rnv rnv version 1.7.10 p5.xml BUILD: Check validity with special-purpose XSL code, looking for bad links etc ANT_OPTS="-Xss2m -Xmx752m -Djava.awt.headless=true" ant -q -lib Utilities/lib/saxon9he.jar -f antbuilder.xml -DXSL=/srv/hudson/jobs/TEIP5-Test/workspace/../../Stylesheets/lastSuccessful/archive/dist/xml/tei/stylesheet validators [echo] Run Schematron script (normal part of Guidelines) [echo] Run Schematron script (Examples in Guidelines marked as valid) [echo] Run ad hoc XSLT validators BUILD SUCCESSFUL Total time: 33 seconds <Messages> <ERROR>egXML points to non-existent #VESA-eg-1 (TEI[1]/text[2]/body[3]/div["VE"]/div["VESA"]/p[6]/) </ERROR> <ERROR>egXML points to non-existent #VESA-eg-1 (TEI[1]/text[2]/body[3]/div["VE"]/div["VESA"]/p[6]/) </ERROR> <ERROR>id 'said1297' used more than once</ERROR> <ERROR>id 'said1298' used more than once</ERROR> <ERROR>id 'said1299' used more than once</ERROR> <WARNING>Schematron warning: WARNING: use of deprecated method — the use of the altIdentifier element as a direct child of the msPart element will be removed from the TEI on 2016-09-09 [Test: child::tei:altIdentifier] Location: /TEI[1]/text[1]/body[1]/div[10]/div[10]/specGrp[1]/elementSpec[1]/exemplum[2]/egXML[namespace-uri()='http://www.tei-c.org/ns/Examples'][1]/msDesc[namespace-uri()='http://www.tei-c.org/ns/Examples'][1]/msPart[namespace-uri()='http://www.tei-c.org/ns/Examples'][1]</WARNING> <WARNING>Schematron warning: WARNING: use of deprecated attribute — @degree of the precision element will be removed from the TEI on 2015-11-12. [Test: @degree] Location: /TEI[1]/text[1]/body[1]/div[21]/div[1]/div[2]/div[4]/specGrp[1]/elementSpec[1]/exemplum[1]/egXML[namespace-uri()='http://www.tei-c.org/ns/Examples'][1]/precision[namespace-uri()='http://www.tei-c.org/ns/Examples'][1]</WARNING> <WARNING>Schematron warning: WARNING: use of deprecated attribute — @degree of the precision element will be removed from the TEI on 2015-11-12. [Test: @degree] Location: /TEI[1]/text[1]/body[1]/div[21]/div[1]/div[2]/div[4]/specGrp[1]/elementSpec[1]/exemplum[1]/egXML[namespace-uri()='http://www.tei-c.org/ns/Examples'][1]/precision[namespace-uri()='http://www.tei-c.org/ns/Examples'][2]</WARNING> <WARNING>Schematron warning: WARNING: use of deprecated attribute — @degree of the precision element will be removed from the TEI on 2015-11-12. [Test: @degree] Location: /TEI[1]/text[1]/body[1]/div[21]/div[2]/p[5]/egXML[namespace-uri()='http://www.tei-c.org/ns/Examples'][1]/precision[namespace-uri()='http://www.tei-c.org/ns/Examples'][1]</WARNING> <WARNING>Schematron warning: WARNING: use of deprecated attribute — @degree of the precision element will be removed from the TEI on 2015-11-12. [Test: @degree] Location: /TEI[1]/text[1]/body[1]/div[21]/div[2]/p[5]/egXML[namespace-uri()='http://www.tei-c.org/ns/Examples'][1]/precision[namespace-uri()='http://www.tei-c.org/ns/Examples'][2]</WARNING> <WARNING>Schematron warning: WARNING: use of deprecated attribute — @degree of the precision element will be removed from the TEI on 2015-11-12. [Test: @degree] Location: /TEI[1]/text[1]/body[1]/div[21]/div[2]/p[6]/egXML[namespace-uri()='http://www.tei-c.org/ns/Examples'][1]/residence[namespace-uri()='http://www.tei-c.org/ns/Examples'][1]/precision[namespace-uri()='http://www.tei-c.org/ns/Examples'][1]</WARNING> <WARNING>Schematron warning: WARNING: use of deprecated attribute — @degree of the precision element will be removed from the TEI on 2015-11-12. [Test: @degree] Location: /TEI[1]/text[1]/body[1]/div[21]/div[2]/p[7]/egXML[namespace-uri()='http://www.tei-c.org/ns/Examples'][1]/precision[namespace-uri()='http://www.tei-c.org/ns/Examples'][1]</WARNING> </Messages> (grep -q "<ERROR>" ValidatorLog.xml;if [ $? -ne 1 ] ; then echo "Oh dear me. ERROR found";diff ValidatorLog.xml expected-results/ValidatorLog.xml;false; fi) Oh dear me. ERROR found 2,8d1 < <ERROR>egXML points to non-existent #VESA-eg-1 < (TEI[1]/text[2]/body[3]/div["VE"]/div["VESA"]/p[6]/) </ERROR> < <ERROR>egXML points to non-existent #VESA-eg-1 < (TEI[1]/text[2]/body[3]/div["VE"]/div["VESA"]/p[6]/) </ERROR> < <ERROR>id 'said1297' used more than once</ERROR> < <ERROR>id 'said1298' used more than once</ERROR> < <ERROR>id 'said1299' used more than once</ERROR> make: *** [valid] Error 1 Build step 'Execute shell' marked build as failure

2 2

datatypes coming back to bite us
by Syd Bauman 30 Mar '15

30 Mar '15

As you may recall, on our conference call Fri we agreed I'd try to get Schematron checks for the default value problems Lou pointed out in FR 546[1] ready for inclusion in next release. The cases that we'd like to check are * If the attribute being defined is required, a default value should not be defined. * If the attribute being defined has a closed list of values, then the default value should be among the enumerated list. That second one causes a problem; I've hit a predictable snag. We have explicitly (and unwisely IMHO) permitted whitespace in the value of an attribute defined as a member of an enumerated set of values. Thus it is perfectly legal in TEI to have <valItem ident="Bono"/> <valItem ident="Enya"/> <valItem ident="Diana"/> <valItem ident="Prince"/> <valItem ident="Madonna"/> <valItem ident="Pat Benetar"/> <valItem ident="Diana Prince"/> <valItem ident="Michael Jackson"/> As I've argued before, this makes it difficult to differentiate multiple singleton values from single multiples. E.g., presume the above list is associated with <datatype minOccurs="1" maxOccurs="3"> <rng:ref name="data.enumerated"/> </datatype> Then is the value "Diana Prince" one value or two?[2] This problem comes up because we actually have a <defaultVal> that has multiple singleton values: namely the default for the optional @type of <metDecl>, is "met real". (AFAIK we don't have any @ident of <valItem> that contain whitespace.) Now, since the attributes allows 1-3 occurrences of its closed value list of "met", "real", and "rhyme", we (humans) know that the default value must be two singleton values, "met" and "real". But the Schematron check is a different story. If I write the test to match the datatype, I would use string( chlid::defaultVal ) = child::valList/valItem/@ident But that means "met real" doesn't match. If I write the test to presume whitespace-separated singletons, I would use tokenize( normalize-space( child::defaultVal ),' ') = child::valList/valItem/@ident (And remember, these are XPath 2 expressions, so the '=' operator operates on sequences, not single values.) The problem with writing the test that 2nd way is that then a user who takes advantage of the fact that we allow spaces in enumerated lists will get a false error message when she tries <attDef ident="Q1" mode="add"> <defaultVal>one two</defaultVal> <valList type="closed"> <valItem ident="one two"/> <valItem ident="three four"/> </valList> </attDef> (And, I'd have to do better than normalize-space() if we wanted to take possible leading or trailing space into account.) I'm really not sure what to do about this. Possibilities include: 1) Use the first method (string), and change the build process so that the error on "met real" is ignored. 2) Change the definition of <metDecl> so that the default value of @type is discussed in prose, not given in <defaultVal>. 3) Change the test to use the first method (string) iff maxOccurs is 1 (or unspecified), and to use the second method (tokenize) iff maxOccurs is 2+ (or "unbounded"). Other suggestions? I think (1) and (2) are pretty much cop-outs, but not crazy. I think either may be acceptable as a temporary hack, but neither is a good long-term solution. I think (3) does the easy cases right, but I haven't thought through the harder cases. (That said, probably no one should be using the harder cases.) Notes ----- [1] https://sourceforge.net/p/tei/feature-requests/546/?page=0 [2] To complicate things we've (very unwisely IMHO) defined @ident of <valItem> and the content of <defaultVal> as rng:string and <rng:text>, respectively, as opposed to rng:token (or better yet, something that does not allow whitespace like data.word). That said a) our ODD processing software silently converts the value of @ident of <valItem> from rng:string to rng:token b) even using rng:token doesn't really fix this problem c) no matter what you do, you probably don't get the results you expect Let me know if you want evidence of (c).

1 1

#705 <lg> cannot contain <q>, <seg>, etc.
by Raffaele Viglianti 29 Mar '15

29 Mar '15

Hi all, I've drafted a new section for chapter 6 Verse, to address bug #705 [1] The new section would come right after the section "Components of the Verse Line" [2] Here is the draft: https://gist.github.com/raffazizzi/c70e1565bc4b83d4a043#file-vesa Please let me know if you have any comments. If we're happy with it, I'd like to commit it before the freeze on Monday. Thanks! Raff [1] https://sourceforge.net/p/tei/bugs/705/ [2] http://www.tei-c.org/release/doc/tei-p5-doc/en/html/VE.html#VESE

4 5

Bleeding-edge version of the Oxygen plugin
by Martin Holmes 27 Mar '15

27 Mar '15

Hi all, Following up on the meeting today: The plugin subscription URL is: <http://teijenkins.hcmc.uvic.ca/job/oxygen-tei/lastSuccessfulBuild/artifact/…> It gets updated frequently; if it breaks, let me know asap. The last ten builds are retained, so you can in theory easily roll back. Cheers, Martin

1 0

Reminder: telecon on Friday
by Hugh Cayless 27 Mar '15

27 Mar '15

This will be the one with the time shift: March 27, 8:30 am EDT, 5:30 PDT, 12:30 GMT, 13:30 CET. I've put up a stub agenda at http://wiki.tei-c.org/index.php/Council_Agenda_2015-03 Please add items you think should be discussed or reported on. I'm at a meeting Mon.-Wed., so won't be able to do much prep. We grumbled a bit about the medium at the last meeting and wondered about trying a Google Hangout instead. Is this something everyone would like to try next time? Sent from my phone.

6 9

Agenda/Minutes Doc
by Hugh Cayless 27 Mar '15

27 Mar '15

https://docs.google.com/document/d/1Pu_EFOSHMcoOsXfhUEcx9M9OUJJMbueXspLsiVG… Just grabbing some coffee. I'll go ahead and set the call up now.

1 0

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

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