Hiya,
[originally sent notice of this from wrong account so didn't get
posted, but that gave me chance to try to reproduce]
I was teaching some people encoding 17thC petitions to use Roma
and had a problem while demonstrating it. I created a
customisation, building up from the minimal suggested one, added
some more modules, showed them what that did, generated schemas,
documentation, etc. all fine. Then I had customised div/@type to
be required and have some values, and saved the customisation,
and when I generated the schema the next time it had an EGE
OxGarage error in it instead of the schema. I tried various ways
to get it to give me a schema, but it wouldn't. I started again,
did precisely the same things, it worked fine. I did that again,
saved a customisation, uploaded it again as a new start, and then
it wouldn't give me the generated schema again.
However, the students all used it fine with no incident. I just
tried to reproduce it again now and it all worked fine with no
problems.
I suspect that we should monthly or something restart Oxgarage
(which is doing these transformations) and clean out any
temporary files. Its flakiness leads me to believe that it is
likely to be something memory related or similar that comes and
goes and has nothing to do with what I'm actually doing in Roma.
Thought I'd mention it in case others had other suggestions.
-James
--
Dr James Cummings, James.Cummings(a)it.ox.ac.uk
Academic IT Services, University of Oxford
