Re: xmloutputversion change

["Joshua D. Abraham" <jabra () ccs neu edu>]

Great idea Max! 

Regards,
Josh

On 28.Nov.2007 01:52PM -0500, Max wrote:

> Great suggestion, I cannot count the times I have been surprised by
> XML schema changes that broke Nmap::Scanner, including now :p, I
> obviously need to now update my module as it will have broken again
> with the new release if I am understanding correctly :).
>
> I would be hugely in favor of an nmap-xml list, even if it is
> announcement only, where someone could at least send out a 'things
> have changed' notice when the XML schema has changed if maintaining
> the XML version number is not feasible (though I think that the
> version number is a better way to go).
>
> - Max
>
> On Nov 28, 2007 5:53 AM, Lionel Cons <lionel.cons () cern ch> wrote:
> > I've tried nmap-4.23RC2 and noticed that the XML output format changed
> > significantly. In order to help programs that deal with XML files from
> > different Nmap versions, I would suggest to increase xmloutputversion from
> > 1.01 to 1.02.
> >
> > As a general rule, I would suggest to increase xmloutputversion each time
> > there is a change in the XML output format. To my understanding, this is the
> > purpose of this element. This is different from the Nmap version, which
> > could change without affecting the XML output format.
> >
> > If the change is minor (backward compatible, like adding new elements), only
> > the decimal part should be increased, like now. If the change is major (not
> > backward compatible), the integral part should be increased (e.g. 1.02 ->
> > 2.00).
> >
> > Cheers,
> >
> > Lionel Cons
> >
> > _______________________________________________
> > Sent through the nmap-dev mailing list
> > http://cgi.insecure.org/mailman/listinfo/nmap-dev
> > Archived at http://SecLists.Org
>
> _______________________________________________
> Sent through the nmap-dev mailing list
> http://cgi.insecure.org/mailman/listinfo/nmap-dev
> Archived at http://SecLists.Org

-- 
Joshua D. Abraham

_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://SecLists.Org