ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Erik Hatcher" <>
Subject Re: Docs out of sync
Date Fri, 21 Jun 2002 03:22:23 GMT
But how realistic or useful would a DTD be for build.xml?  There is so much
dynamic capability, first with taskdef and typedefs defining new elements
and now with my DynamicConfigurator enhancement.

I'm guessing you mean simply for the current built-in/optional tasks.  Even
for those it would be tough to define a rigorous DTD, I'd suspect, as the
logic of whats acceptable and unacceptable is in the Java code logic at the

Quite a challenge, but well worth the efforts!


----- Original Message -----
From: "J.Pietschmann" <>
To: "Ant Developers List" <>
Sent: Thursday, June 20, 2002 3:32 PM
Subject: Re: Docs out of sync

> Rob Oxspring wrote:
> > What are the options here then? a few spring to mind but we need to get
> > out in the open if a proper decision is to be arrived at.
> I'd think of:
> - Write a DTD for build.xml. Start with a strict one.
> - Verify all build.xml you can take hold of. Verification
>    problems point to omissions in the DTD.
>    I can provide tools/support if needed.
> - Use cyberneko to transform the DTD into an XSchema
>    I can provide support if needed.
> - Fine tune by introducing data types and other stuff like
>    dependencies between attributes and child elements into
>    the XSchema. I *think* I can provide some support here too.
>    There is also the XML-dev list...
> - Verify all build.xml you can take hold of with the schema.
>    Verification problems point to errors in the fine tuning.
>    I can provide tools/support for this step.
> - Write an XML file with more extensive documentation. An
>    initial skeleton for the doc can be built with XSLT.
>    The doc can use markup as placeholders to pull in data
>    from the schema (like attribute types) when transformed
>    into an xdoc XML.
>    I can provide some supprot for design and tools.
> - Improve and maintain the schema and the docs. Use an XSLT
>    based checker to endure consistency between schema and doc.
> > 4) I really no nothing about it but would XSchema have any useful syntax
> > that we could steal?
> XSchema is a real PITA unless you restrict yourself to a
> managable subset. It has some advantages though (tool support,
> in particular Xerces 2 can validate a document against an XSchema)
> J.Pietschmann
> --
> To unsubscribe, e-mail:   <>
> For additional commands, e-mail: <>

To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message