Home page logo
/

openvas logo OpenVAS mailing list archives

Call for Votes CR #48: Define OMP/OAP in RelaxNG Schema Language
From: Stephan Kleine <bitdealer () gmail com>
Date: Tue, 11 May 2010 02:27:34 +0200
List-id: OpenVAS development <openvas-devel.wald.intevation.org>

On Tuesday May 11 2010 00:24:46 Jan-Oliver Wagner wrote:
On Thursday 06 May 2010 13:23:26 Hartmut Goebel wrote:
Am 22.04.2010 18:57, schrieb Hartmut Goebel:
I've just uploaded change request #48 (see
<http://www.openvas.org/openvas-cr-48.html>) and am looking forward to
you comments on this issue.

Since there were no complaints or objections, I'd like to call for votes
now and would like to ask you to cast your vote by May 16t.

I had not much time to look into this, so sorry for my late comment.

A processable description of the protocols is a good idea in principle.

I am not happy with the bashing language against the current state
of OMP/OAP. It is work in progress and thus by definition not complete
nor bug-free. Justifying RelaxNG with this work-in-progress-state seems
wrong to me. I'd prefer to not leave the text as is.

Figure out some API that makes everyone happy for OMP & OAP and nail that down 
as some _publicly available .xsd_. IOW please create a common XML schema that 
is used and documented. Surely that can be changed from version to version but 
until the very first release there should be some  version set in stone. So 
please get together and figure out how you would like that API / schema.

My 0,02$,

PS: And on a personal note, please spare me that "Relax NG" crap but simply 
stick with some XML schema that can be validated by common tools without any 
further inconveniences.

regards,
Stephan


  By Date           By Thread  

Current thread:
[ Nmap | Sec Tools | Mailing Lists | Site News | About/Contact | Advertising | Privacy ]