[tei-council] validation of spec files

[Martin Holmes]

That file exists -- I just looked at it. Spec files validate absolutely fine for me. You're right that we point at the Jenkins URL on purpose because we do make changes to things, and there's no point validating the latest versions of spec files against an old version of the schema.

Cheers,
Martin
________________________________________
From: tei-council-bounces at lists.village.Virginia.EDU [tei-council-bounces at lists.village.Virginia.EDU] on behalf of Lou Burnard [lou.burnard at retired.ox.ac.uk]
Sent: October 11, 2014 4:14 PM
To: TEI Council
Subject: [tei-council] validation of spec files

I've just noticed (why did it take me so long) that the versions of
*spec files in my locally checked out copy of the P5 source all have a
PI, oxyGen for the use of, which points to a non existent place, like this:

<?xml-model
href="http://tei.it.ox.ac.uk/jenkins/job/TEIP5/lastSuccessfulBuild/artifact/release/xml/tei/odd/p5.nvdl"
type="application/xml"
schematypens="http://purl.oclc.org/dsdl/nvdl/ns/structure/1.0"?>

You might think that this ought to point to the latest release on
www.tei-c.org. I suspect that we changed this because you want to be
using the last successful build on Jenkins when you're checking that a
forthcoming release works. But then the address of the Oxford jenkins
changed, and the files didn't get updated to reflect it.

You won't be inconvenienced by this unless you try to validate an
individual spec file, of course. But it doesn't seem a good idea to have
a non-doing PI cluttering up all of our source files.


--
tei-council mailing list
tei-council at lists.village.Virginia.EDU
http://lists.village.Virginia.EDU/mailman/listinfo/tei-council

PLEASE NOTE: postings to this list are publicly archived