[tei-council] Release guidelines

[Martin Holmes]

On 13-12-11 02:52 PM, Sebastian Rahtz wrote:
>
> On 11 Dec 2013, at 20:10, Martin Holmes <mholmes at uvic.ca> wrote:
>
>> I think it should point to the file in the release package itself:
>>
>> /usr/share/xml/tei/odd/p5.nvdl
>>
>> so presumably the link should go:
>>
>> ../../p5.nvdl
>>
>> shouldn't it? Otherwise anyone who opens a spec file may well find it doesn't validate, because we've made changes in the repo which change the schema on Jenkins.
>
> which may or not be what they want to know, of course
>
> do relative links work in oXygen?

Absolutely. I use them in virtually all my xml-model PIs.

>
>> Or am I misunderstanding something here?
>
> i don’t know, to be honest, it’s such a hypothetical situation.

I don't think it is, actually. People working in the SVN Source need to 
be validating against the latest schemas (which since so few of us can 
build locally now, are on Jenkins). People working with Spec files from 
a distributed package need to be validating against the schema that was 
distributed with those Spec files. In both situations, confusing 
invalidities will arise pretty quickly if they're pointing at the wrong 
schema.

It may be the case that very few people edit or validate Spec files from 
the distro packages or from tei-c.org, though.

Cheers,
Martin

>
> --
> Sebastian Rahtz
> Director (Research) of Academic IT
> University of Oxford IT Services
> 13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431
>
>

-- 
Martin Holmes
University of Victoria Humanities Computing and Media Centre
(mholmes at uvic.ca)