Stefan Bodewig wrote: > On Mon, 19 May 2003, peter reilly <[EMAIL PROTECTED]> wrote: > >> 1) are build script authors allowed to specify arbitary >> URIs for ant type definitions? >> I do not think this is a good idea. > > I've seen that Costin and Conor prefer that antlibs specify their URI > themselves. Could anybody please explain why - and at the same time > please also explain why user choice would be bad here? I feel I must > be missing something.
That's consistent with most of the current uses of XML namespaces - you don't see users picking their favorite XHTML or XSLT namespace URI. It's also about tools - things like autocompletion in an xml editor, transformations, etc. I can add more - but I'm curious about the reverse, why would you consider letting the users pick the namespace URI ? If someone looks at a build.xml file, and see an "antlib:net.sf.contrib" he'll probably know what tags are used and understand it. If he sees "myFavoriteAntlib" - and this is associated with contrib in some imported xml file - it'll be a bit harder ( he can still guess from the <if>s ). Costin > >> 2) what should ant do with URIs that it does not recognize? >> >> a) use current method - unknown elements >> b) ignore them >> c) explicty say that the ns uri is not supported >> d) convert them to Text in task/typedefs (the suggestion below) > > I'm on the fence between a) and b) and wouldn't like either c or d too > much. > > Stefan
