DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=28729>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=28729 Introducing an <annotation> element ------- Additional Comments From [EMAIL PROTECTED] 2004-05-03 21:22 ------- I would prefer not adding annotation element that is almost identical to an XML comment. If you wanted to support Javadoc-style information, I would suggest allowing rdf:Description elements to appear as children of projects, tasks and types. Unless the rdf:about attribute was specified, the description would apply to the containing project, task or type. <project xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"; xmlns:dc="http://purl.org/dc/elements/1.1/";> <rdf:Description> <dc:title>Sample build file including RDF descriptions</dc:title> <dc:creator>Curt Arnold</dc:creator> <dc:date dc:qualified="created">2004-05-03</dc:date> <dc:description>This is a sample build file including Resource Description Framework (http:// www.w3.org/rdf) using statements from Dublin Core metadata.</dc:description> </rdf:Description> </project> This avoids Ant from creating its own metadata system that would need to be mapped eventually to RDF. It would obviously be more complicated than using straight XML comments, but if you aren't needing to make unambiguous statements, you could still use XML comments. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
