Consider the following;
<?xml version="1.0"?>
<project name="Demonstrate namespace options" default="demo">
<RDF:RDF xmlns:RDF="http://www.w3c.org/RDF/";
xmlns:DC="http://purl.org/RDF/DC/";>
<RDF:Description
RDF:HREF="http://purl.org/metadata/dublin_core_elements"; DC:Title="namespace build"
DC:Creator="Jim Fuller"
DC:Subject="xml namespaces" DC:Description="Contains Ant artifacts for building" DC:Publisher="Webcomposite s.r.o." DC:Format="text/html" DC:Type="Technical Report" DC:Language="en" DC:Date="12/22/2003"/>
</RDF:RDF>
<description>intermixing of namespaces</description>
<target name="demo" description="build entry point">
<echo message="successful build"/>
</target>
</project>
XML Namespaces was initially created to avoid collision within documents
that have multiple xml vocabularies.
Ant seems to assume by default that all namespaces have something to do with build processing...is their any convention planned for having Ant ignore specific namespace elements...or more usefully all namespaces that have no Ant processing associated with it ?
hmm. this looks more like you want XML in ant with no ant processing in it.
For instance, the above example maybe generated by a sophisticated XML editor that uses Dublin Core and RDF as a method of tracking versions of the build.xml file. This is a simple use case, there are other more important use cases involving xml db repositories.
Ant1.7 lets you have any XML you like inside some task. So you could have a <comment> task that required valid XML and took whatever was inside. Or even an <rdf> task that required valid RDF
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
