[tei-council] validation of spec files

[Peter Stadler]

What are "alpha/beta versions“? 

Am 12.10.2014 um 17:29 schrieb Martin Holmes <mholmes at uvic.ca>:

> For a true release, the proper target for the schema pointer is the Vault, because that version of that ODD is only going to be expected to validate against the schemas for its own release. However, that won't work for alpha/beta versions because there will be no such version in the Vault, so they should presumably still point at Jenkins (or at perhaps at the NVDL in their own alpha or release).
> 
> Could we do this just with relative paths? 
> 
> Cheers,
> Martin
> ________________________________________
> From: tei-council-bounces at lists.village.Virginia.EDU [tei-council-bounces at lists.village.Virginia.EDU] on behalf of James Cummings [james.cummings at it.ox.ac.uk]
> Sent: October 12, 2014 8:26 AM
> To: tei-council at lists.village.Virginia.EDU; Lou Burnard
> Subject: Re: [tei-council] validation of spec files
> 
> If I remember correctly jenkins doesn't even run on tei.it.ox.ac.uk (bogof) that just proxies bits.nsms.ox.ac.uk for that url. So two potential points is failure.
> 
> James
> 
> --
> Dr James Cummings, (from phone) james.cummings at it.ox.ac.uk
> IT Services, University of Oxford.
> 
> -----Original Message-----
> From: Lou Burnard [lou.burnard at retired.ox.ac.uk]
> Received: Sunday, 12 Oct 2014, 15:38
> To: tei-council at lists.village.Virginia.EDU [tei-council at lists.village.Virginia.EDU]
> Subject: Re: [tei-council] validation of spec files
> 
> Presumably he re-instated the URL "tei.it.ox.ac.uk",  which he had
> previously removed in an excess of zeal
> 
> 
>  On 12/10/14 15:04, Martin Holmes wrote:
>> What exactly did you fix, and how did you fix it? My impression was that
>> we were planning to discuss exactly what we should do. Ideally, release
>> versions should point to the nvdl in their own release, while dev
>> versions should always point to the Jenkins file, I think.
>> 
>> It's pretty important that the spec files point to something, and
>> (especially while we're actually working on changes to ODD itself), also
>> important that they not point to an obsolete release version.
>> 
>> Cheers,
>> Martin
>> 
>> On 14-10-12 06:35 AM, Sebastian Rahtz wrote:
>>> I fixed tei.it this morning in a fit of madness. It's an interesting question which schema the Specs  should point to. But it's not an urgent question.
>>> 
>>> Sebastian
>>> 
> 
> --
> 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
> --
> 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
> -- 
> 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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 455 bytes
Desc: Message signed with OpenPGP using GPGMail
Url : http://lists.village.Virginia.EDU/pipermail/tei-council/attachments/20141012/8faa09b4/attachment.bin