Back when I taught TEI (sounds grand, but all I'm saying is that it's
happened, but not recently), I applied what you say about projects below
(need for transparency) to the "pre-scripted sequence of transformations".
I would edit ODD in oXygen, load it into Roma, do a sanity check and
then generate RNG, which had to be moved by hand to the appropriate
directory, but that was about the only (minor) hurdle. What I thought I
gained was that it wasn't a magical process, but rather a transparent
development cycle that happened outside of the TEI instance and that
influenced its status.
I mention this as an argument against making such per-scripting an
essential feature. There is life outside of it and it's not such a bad
On 11/07/16 16:06, Lou Burnard wrote:
> Another essential feature for me would be the ability to access a
> pre-scripted sequence of transformations etc. in the way that oXygen
> currently does when generating RNG and XHTML from an ODD file. It's
> currently done with an Ant script, but any scripting language will do. I
> routinely do an exercise which involves editing an ODD, generating a
> schema, using it to create a new file, e da capo. This is easy and
> seamless in oXyGen: doing it via the oXGarage web interface would be
> cumbersome and confusing.
> I'm less persuaded of the essentialness of being able to package things
> up in an oXyGen project file. For me, this is something that comes later
> on in a project, when its constituents are more stable: it's not
> something I'd expect beginners to be exposed to. Beginners need to know
> what the various components of the process are, not be protected from them.
Piotr Bański, Ph.D.
Institut für Deutsche Sprache,
68-161 Mannheim, Germany