You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ant.apache.org by Eugen Kuleshov <eu...@home.com> on 2000/08/02 04:20:43 UTC

Re: Utah

James Duncan Davidson wrote:
 
> > I've read your document whiteboard\utah\design guide.xml from current
> > Ant snapshot. There are great ideas.
> Actually, the Utah stuff is superceed by the "spec" document which is also
> in the repository. But thanks ! :)
> 
> > But I have just small comment. How
> > about create DTD for build.xml file. It helps to validate build.xml
> > strucrure and make much simplier creating GUI tools for managing
> > build.xml
> By design, the build.xml file can't have a DTD that works in all case. The
> structure would have to change. There is a tool in the current distribution
> that lets you build a DTD from a set of tasks that will work.

  wich tool?
 
> Most of the recent editors to come out are starting to acknowledge that XML
> has powerful uses that aren't 1:1 compatible with DTDs. For example, the new
> XMetal allows creating XML docs that don't have a DTD.

  of course it's not a problem to create XML without DTD. But for
authomatical generetion or validation or XSLT transformation better if
we will have DTD. It also maid simplier writing specialized editor for
Utah's build.xml
 
> In any case, please continue this conversation on the Ant-Dev mailing list.
> I don't really like having technical discussions on Ant outside of that
> forum. :)

  ok

  Eugen.

Re: Utah

Posted by Sebastien Pierre <sp...@rational.com>.
Eugen Kuleshov wrote:
> 
> > Most of the recent editors to come out are starting to acknowledge that XML
> > has powerful uses that aren't 1:1 compatible with DTDs. For example, the new
> > XMetal allows creating XML docs that don't have a DTD.
> 
>   of course it's not a problem to create XML without DTD. But for
> authomatical generetion or validation or XSLT transformation better if
> we will have DTD. It also maid simplier writing specialized editor for
> Utah's build.xml

For example having a DTD could help automatically building a user
interface using the DTD (I have a prototype of a Java tool that
generates a whole UI from a bunch of XML files).
[I would suggest that task create their own subset of the "And DTD",
like a getElementsDeclaration() that would return a string or a
DocumentFragment]

For me DTDs are very important, and are quite fast. The only real
problem is that they do not really support namespaces.

Cheers,
Seb.
-- 
Sebastien Pierre.-  spierre@rational.com \ Bored of Notepad,
R a t i o n a l   software | XML          \ WordPad or UltraEdit ?
. Rational Unified Process | technology    \ try Vim !
. Vancouver, B.C,  -Canada | intern         \ <http://www.vim.org>