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

Re: [tei-council] Something weird about tei-c.org
by Martin Holmes 28 Jul '15

28 Jul '15

Hi Kevin, Sebastian et al, I've just done a quick bugfix for the Roma PHP webapp: <https://sourceforge.net/p/tei/bugs/724/> and tested it locally and it seems to work fine. As far as I can tell from browsing around the projects/tei/web/Vault directory, the current deployed version of Roma on tei-c is 4.15; the new build is 4.18. The system looks similar to the setup for P5, where the "current" symlink points to whatever should be the current version. I think (but I'm not sure) that we can get a new version deployed like this: - Create new 4.18 directory - Get the latest build from Jenkins: <http://teijenkins.hcmc.uvic.ca/job/Roma/lastSuccessfulBuild/artifact/tei-ro…> and unzip it into there. - Change the "current' symlink to point at it. However, there's something slightly odd going on. As far as I understand it, tei-roma/roma.php requires a file called config.php in the same directory. That file is (I thought) created by copying the file config-dist.php to config.php and then customizing it as necessary for the local install. roma/roma.php contains this: require_once( 'config.php' ); so it it's definitely expected to be available. But in current/tei-roma/roma, there is no config.php; there are various versions of config-dist.php resulting from what appears to be an svn conflict, where the differences amount only to the version number and date. So my question is: am I wrong about the fact that config.php is expected to be created from config-dist.php? That is what I did on my local test install, and it worked fine. If I'm right, that would seem to suggest that Roma on tei-c.org has been running slightly misconfigured, and managing without the missing config.php somehow (perhaps error messages are being suppressed). Does anybody know anything about this? I'm not seeing any documentation on how to deploy the PHP Roma, so I've started a new section on the wiki page: <http://wiki.tei-c.org/index.php/Roma#Getting_the_Roma_server_running> Cheers, Martin On 15-07-27 01:44 PM, Kevin Hawkins wrote: > As you've probably seen by now, we did in fact get a notification from > Uptime Robot, and it's already back up. > > This is the first time I've seen the TEI site go down while I'm at my > computer. The ADHO site remained up during that time, and given how > often I've seen notifications that that site goes down while the TEI > site stays up, it appears that these two sites function independently > despite sharing a hosting service. > > Nick, I'm going to turn off the Uptime Robot notifications for the ADHO > site for now. > > Kevin > > On 7/27/15 3:42 PM, Martin Holmes wrote: >> Hi Kevin, >> >> I was just working on Roma on tei-c when it stopped responding. I then >> went to try tei-c.org, and the site doesn't seem to be responding. If >> you ping it, the ping is returned by digitalhumanities.org, so tei-c >> appears to be up for services like isup.me, but wget requests never get >> a response, and I see this proxy error message eventually in my browser: >> >> Proxy Error >> >> The proxy server received an invalid response from an upstream server. >> The proxy server could not handle the request GET /index.xml. >> >> Reason: Error reading from remote server >> >> Additionally, a 502 Bad Gateway error was encountered while trying to >> use an ErrorDocument to handle the request. >> >> Just letting you know, because I don't know whether uptimerobot will >> notice it. >> >> Cheers, >> Martin

3 3

Looks like the SF svn repo is back up
by Martin Holmes 26 Jul '15

26 Jul '15

<http://sourceforge.net/blog/category/sitestatus/> I was able to do an svn update successfully on the TEI repo and my own CodeSharing repo. Cheers, Martin

1 0

F2F in Lyon in Oct
by Syd Bauman 24 Jul '15

24 Jul '15

Hugh -- Do we have definitve dates for the F2F in Lyon in 2015-10 yet? James and I are supposed to be at a meeting in Germany on Thu 10-22, Fri 10-23, and maybe Sat 10-24. The pre-conference workshops will be Mon 10-26, Tue 10-27, and Wed morning 10-28; conference proper from Wed afternoon 10-28 through Sat 10-31.

3 2

ODD question
by Hugh Cayless 22 Jul '15

22 Jul '15

Hello all, Hope your trips home went well (or are going well). I’m having a hard time defining a new spec for <secl>. Does anybody know why https://github.com/hcayless/TEI-Guidelines/blob/secl/P5/Source/Specs/secl.x… <https://github.com/hcayless/TEI-Guidelines/blob/secl/P5/Source/Specs/secl.x…> wouldn’t be picked up by any of the build processes I’m running? It’s as though the file is invisible. There’s clearly some incantation I’m not including, but I don’t know what it is… Thanks, Hugh /** * Hugh A. Cayless, Ph.D * hugh.cayless(a)duke.edu * Duke Collaboratory for Classics Computing (DC3) * http://blogs.library.duke.edu/dcthree/ **/

9 36

bug report: @rend vs @rendition
by Syd Bauman 21 Jul '15

21 Jul '15

Sourceforge is currently down, so I'm posting this here in lieu of a bug report. Will transfer it to a ticket assigned to me later. --------- The remarks associated with att.global.rendition say Where both @rendition and @rend are supplied, the latter is understood to override or complement the former. This seems correct to me. The prose of section 1.3.1.1.3 "Rendition Indicators" says In the TEI scheme, it is possible to supply information about the appearance of elements within a source document in the following distinct ways: 1. One or more properties may be specified as the default for all elements of a given type, using the @render attribute to point to rendition elements ; 2. One or more properties may be specified for individual element occurrences, using the @rend attribute with any convenient set of one or more sequence-indeterminate tokens; 3. One or more properties may be specified for individual element occurrences, using the @rendition attribute to point to rendition elements; 4. One or more properties may be supplied explicitly for individual element occurrences, using the @style attribute. If the same property is specified in more than one of the above ways, the one with the highest number in the list above is understood to be applicable. At the very least, 2 & 3 should be reversed, and use of the @selector of <rendition> needs to be added to the list. But the idea that @rend has to be made of tokens (rather than a string) seems incorrect to me; and the idea that they must be "sequence indeterminate" is at best confusing, at worst hogwash. And why does @style override @rend? I think I'd prefer the reverse (but I'm not sure). Typo: extra space before semicolon in <item> #1.

4 9

question on <xenoData>
by Syd Bauman 14 Jul '15

14 Jul '15

First, <xenoData> should be a member of att.declarable. I think that's pretty much a no-brainer, but raise it here in case someone wants to object. But my next issue is at least non-obvious, if not controversial (and I hope it's not). How is a process to know whether the metadata supplied in <xenoData> applies to the TEI document or to the source thereof? Several possibilities jump to mind. 1) It doesn't. This is not our problem. Any project using <xenoData> will know what metadata they are using, so they'll figure it out just fine. 2) We add a new attribute to <xenoData>, @describes. Its possible values are "source" and "transcription" or some such. 3) We use a special @type (with values "source" and "transcription" or some such) for this, even though it's not quite right. 4) We add <xenoData> to att.typed and let projects come up with their own values of @type to assert this information. Maybe with suggested values (4a), maybe not (4b). 5) Instead of making <xenoData> a member of model.teiHeaderPart, and thus a younger sibling of <fileDesc>, we allow <xenoData> to occur as a child of <fileDesc> or as a child of <sourceDesc> (via membership in model.sourceDescPart). In the former case the metadata in <xenoData> is understood to apply to the TEI document; in the latter case the metadata in <xenoData> is understood to apply to the source from which the TEI document was derived. 6) Like (5), but leave <xenoData> as a member of model.teiHeaderPart instead of (6a) or in addition to (6b) a direct child of <fileDesc>. Personally, I'm leaning very strongly towards (2), (5), or (6a). That is, I think (1), (3), (4a), and (4b) are bad ideas, and prefer (6a) to (6b). That said, I'm open to thoughts, ideas, and suggestions.

8 36

feasibility and NVDL (and <xenoData>)
by syd＠paramedic.wwp.neu.edu 11 Jul '15

11 Jul '15

If the content model of <xenoData> is any.XML+, then the valid= of any <egXML> that contains a (valid) <xenoData> had better be "feasible" (or "false", I suppose), lest that <egXML> be flagged as having "error: unfinished element" by ./run-onvdl p5valid.nvdl v.xml If the content model of <xenoData> is any.XML*, then the valid= of the <egXML>s can be "true". This doesn't make sense to me, as the NVDL explicitly allows elements from the namespaces involved. But I'm guessing that before it checks the <egXML> itself for validity against the RELAX NG, it has removed elements from other namespaces (thus leaving an empty <egXML>). What is the difference between using "feasible" and "true" as far as processing is concerned? I.e., how does the feasibly-valid-checker (called p5.nvdl) know to apply the http://www.thaiopensource.com/validate/feasible to those <egXML>s flagged as "feasible" or "true", and how does the truly-valid-checker (called p5valid.nvdl) know not to? Must, of course, be that the latter is run against "v.xml", not p5.xml, but when and how is v.xml generated? For now I've checked in a version (to the P5-for-xenoData/ branch) with any.XML+ that uses "feasible" on its <egXML>s.

1 0

A quick question
by Martin Holmes 08 Jul '15

08 Jul '15

Can someone please remind me how to declare an attribute such that its content can be one or more of a set of values drawn from a fixed list? In other words, a closed valList, but allowing more than one item from the list. I'm sure I must have done this before, but I can't remember it. Cheers, Martin

2 1

readable xenoData
by Syd Bauman 04 Jul '15

04 Jul '15

I've put a complete copy of a P5-for-xenoData/ *with a built set of Guidelines and Exemplars* at http://paramedic.wwp.neu.edu/~syd/temp/TEI_Council/. So see, e.g. http://paramedic.wwp.neu.edu/~syd/temp/TEI_Council/P5-for-xenoData/Guidelin… (And someone let me know what the heck is the problem with the formatting -- it looks awful.) And use the schema at http://paramedic.wwp.neu.edu/~syd/temp/TEI_Council/P5-for-xenoData/Exemplar… to test it out.

3 5

link
by Hugh Cayless 29 Jun '15

29 Jun '15

https://docs.google.com/document/d/17EBZ56GTUpJM1pwhMYXx7NvKqA-W6OYZBv_GeHO…

3 5