[OWASP-GUIDE] a note on validation

Gene McKenna mckenna at bluedot.com
Mon Jan 27 17:56:27 EST 2003


And if you don't what "lint" is or how it works, you can
also use XML Spy to check that the document is both
well-formed and in conformance with the DocBook DTD.
This is relatively easy to do.

GENE


> -----Original Message-----
> From: owasp-guide-admin at lists.sourceforge.net
> [mailto:owasp-guide-admin at lists.sourceforge.net]On Behalf Of Alex
> Russell
> Sent: Monday, January 27, 2003 10:27 AM
> To: owasp-guide at lists.sourceforge.net
> Subject: Re: [OWASP-GUIDE] a note on validation
>
>
> Ok, seems there's been some confusion about this.
>
> Here's what I'm NOT saying:
>
> I'm NOT saying that any contribution will be rejectd from the Guide.
> I'm NOT saying that a contributor will be removed from the project for
> comitting bad XML.
> I'm NOT saying that the moon is lime green on tuesdays.
>
> With that out of the way, here's what I AM saying:
>
> If you commit something, please lint it first, keeping the CVS
> tree in good
> order will save us a lot of problems down the line as we look to do
> automated builds and the like. If you do happen to check in
> something that
> isn't well formed, the editors may fix or rescind your commit. If we back
> out a patch, you'll get a mail explaining why and requesting that you fix
> and commit again. That's NOT a rejection of your contribution, just a
> mention that it needs work and that we'd love to have it when it's ready.
>
> I'm not looking to alienate anyone here, just to make sure that CVS stays
> clean.
>
> Sorry if I came off a bit strong earlier.
>
> --
> Alex Russell
> alex at netWindows.org
> alex at SecurePipe.com
>
>
> -------------------------------------------------------
> This SF.NET email is sponsored by:
> SourceForge Enterprise Edition + IBM + LinuxWorld
http://www.vasoftware.com
_______________________________________________
Owasp-guide mailing list
Owasp-guide at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owasp-guide





More information about the Owasp-guide mailing list