[tei-council] pesky PIs

[Sebastian Rahtz]

On 26 Apr 2013, at 21:24, Lou Burnard <lou.burnard at retired.ox.ac.uk>
 wrote:

> On 26/04/13 11:33, Sebastian Rahtz wrote:
>> I'd like to switch that to tei-c.org in due course. don't forget that the XML catalog which oxygen uses will sort this out for you, by pointing at local copies, when we get it right 
> 
> As with James's response this is vaguely promising. Can you be more precise? When is "in due course"? What do you mean by "when we get it right"?
> 
its a boot-strapping thing. the last release has to be capable of editing the current release. Until today's crop of schema
files get into the right place in the release, with the correct contents, we have to point to the dev server. So after the next
release, we change all the PIs to point at www.tei-c.org, and we update the oXygen TEI framework's catalog files to
make requests for http://www.tei-c.org/release/xml/tei/..... point to the local copy. So you'll be happily editing offline then,
without even knowing it.

when you want to validate against the schema you are currently changing (ie you're editing div.xml, changing its content model,
and want to validate the egXMLs against what you are now doing), you've got a bit of a chicken and egg situation. You have to
regenerate the schemas in order to validate against them. you have two choices 

    * change the oXygen catalog file to redirect the path to the .nvdl file to your just generated schema
    * use an external validator to check your file ("onvdl p5.nvdl Source/Spec/div.xml")

either way you need a local build setup to regenerate the schema.

Otherwise you have to wait for Jenkins to check it all for you.


> well  actually, I'm expecting to be doing quite a bit of tweaking of p5odds.odd as and when we start implementing the foxglove proposals -- but i agree this is not as annoying as not being able to validate when offline

changing ODD to foxglove-enabled is the sort of thing that happens once every 10 years, and
will be done by people who have sophisticated local setups. the whole xml-model PI setup is
to assist folk (the great majority of the council and other committers) who don't edit ODD
all the time, and want it to Just Work when they load up stamp.xml to add an attribute or edit a
content model.
--
Sebastian Rahtz      
Director (Research) of Academic IT
University of Oxford IT Services
13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431