Cart
[Home] [By Thread] [By Date] [Recent Entries]
* Henry S. Thompson <ht@i...> [2004-12-23 10:26]:
> Alan Gutierrez <alan-xml-dev@e...> writes:
>
> . . .
>
> > I'm not trying to model an address book, but a generic Java
> > object configuration script.
>
> Ah, then a generic markup design such as you showed us makes perfect
> sense, but you're not going to get much leverage from validation (from
> _any_ schema language. . .), at the generic level.
It is probably enough to make sure that the SAX engine that will
assemble the procedure calls will be called with the right
events in the right order.
But, I've wondered, since I'm looking to create this:
<relay>
<run name="parse">
<set name="uri">./index.xml</set>
</run>
<run name="xinclude"/>
<run name="saxon">
<set name="xslt">./document-to-html.xml</set>
</run>
<run name="serialize">
<put name="output">
<set name="key">method</set>
<set name="value">html</set>
</put>
</run>
</relay>
If each of the Runner classes where to define an XML Schema,
would it be possible to do:
<relay>
<parse>
<uri>./index.xml</uri>
</parse>
<xinclude/>
<saxon>
<xslt>./document-to-html.xml</xslt>
</saxon>
<serialize>
<output key="method">html</output>
</serialize>
</relay>
But, it's the problem with Ant in that a new utility changes the
XML Schema, and I'm not familiar enough with XML Schema to know
if there is an accepted way of "plugging in" new rules, into the
same namespace. It seems like you could put it in a separate
namespace, but that would start to get verbose.
I've got the above configuration engine working, by the way. Not
the pipelines, yet, but the configurator. If anyone has any
insight into this problem, or would like to see the source
released, let me know.
--
Alan Gutierrez - alan@e...
|
