I am not proposing that Ant becomes more of a golden hammer then it already is... also I have not seen anyone wanting xslt to be a process router....nor am I asking xslt to do this. XSLT does however allow you to have multiple namespaced xml...of course xslt is a language for transforming xml...so you would expect this.
I am working on a process router using an NLG type language...so I did see some possibilities with Ant, though really, I would rather be able to pass through an xml document without having to spend the cycles to extract the ant build information out of my xml....remember in the near distant future we will have to deal with the differences between an XML file versus an XML document, the former being bound to the underlying operating systems method of handling files/directories, the latter being the object of this discussion. > I in particular do not like the business of a programming language > (which is > what ANT XML really is) where non-understood things are silently > ignored. (-1) [Jim Fuller] completely agree with this statement, though I think the idea of a processing switch that turns off strict 'ant' processing would be useful to have intermingled xml documents, e.g. build.namespace with a variety of flags with the default. > I think that causes more harm than good. I think stuff that must be > ignored > (ant the writer knows about it) must be somehow marked as such (e.g., > <?ant-ignore ...?>). [Jim Fuller] I don't understand why one can't use the XML method of using namespaces to avoid collision....consider the following project build which maybe developed by multiple developers, this example has other concepts that are periphery to my main arg (like a default Ant namespace) <project xmlns="http://ant.apache.org/ant/v16"; name="demo" default="build" basedir="."> <rdf:Description xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"; xmlns:dc="http://purl.org/dc/elements/1.1/"; ID="build"> <dc:subject>build</dc:subject> <dc:subject>some software project</dc:subject> <rdf:revision> <rdf:Description xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax ns#" xmlns:dc="http://purl.org/dc/elements/1.1/"; ID="buildl.1"> <dc:version>1</version> <dc:creator>Jim Fuller</dc:creator> <dc:date>2001-11-25</dc:date> <dc:description>Build file that demonstrates the intermingling of xml elements.</dc:description> </rdf:Description> </rdf:revision> </rdf:Description> <target name="clean"> </target> <target name="create"> <rdf:Description xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"; xmlns:dc="http://purl.org/dc/elements/1.1/"; ID="build"> <dc:subject>build</dc:subject> <dc:subject>docs subproject</dc:subject> </rdf:Description> </target> <target name="docs"> <rdf:Description xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"; xmlns:dc="http://purl.org/dc/elements/1.1/"; ID="build"> <dc:subject>build</dc:subject> <dc:subject>docs subproject</dc:subject> </rdf:Description> </target> <target name="test"> <rdf:Description xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"; xmlns:dc="http://purl.org/dc/elements/1.1/"; ID="build"> <dc:subject>build</dc:subject> <dc:subject>test subproject</dc:subject> <rdf:revision> <rdf:Description xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax ns#" xmlns:dc="http://purl.org/dc/elements/1.1/"; ID="build1.2"> <dc:version>2</version> <dc:creator>Bobby Fuller</dc:creator> <dc:date>2002-11-25</dc:date> <dc:description>amended all java tests to include debug information.</dc:description> </rdf:Description> </rdf:revision> </rdf:Description> </target> <target name="build"> </target> </project> the above example shows a build file being 'tagged' with xml to reflect author information...I don't think that this is such a strange use case...though of course I wouldn't impose this format when primarily using manual text editor...this is of course xml generated with other tools. By putting in an ant element or XML PI you are forcing the ant authors idea of XML structure onto everyone else who may have related build meta data...which is fine if you always consider that build.xml will reside in a standalone file with no integration or association to other meta data. All right I will stop beating this dead horse, thx for the time. Regards, Jim Fuller --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
