RE: WAS Action Items

Team

 

Just a note. If we can use the 
list rather than personal emails as much as possible it ensures everyone is in 
the loop and that conversations and decisions are archived. Appreciated. 

From: Peter Michalek 
[mailto:] 
Sent: Monday, March 29, 2004 5:17 
PM
To: Mark Curphey; 'David Raphael'; 

Subject: RE: WAS Action 
Items

David,

So now that meeting 
minutes are out – do you want to proceed Dave? I don’t want to modify stuff that 
would conflict and make it difficult to merge, so please look at my proposal 
below and confirm if it works for you.

Peter

 

 

 

From: Peter 
Michalek [mailto:] 
Sent: Friday, March 26, 2004 2:29 
PM
To: 'Mark Curphey'; 'David Raphael'; 
''
Subject: RE: WAS Action 
Items

 

Ok, I’ll hold 
off.

 

From: Mark 
Curphey [mailto:] 
Sent: Friday, March 26, 2004 1:51 
PM
To: Peter Michalek; David 
Raphael; 
Subject: RE: WAS Action 
Items

 

Gents

 

If its OK with you can 
I get the meeting minutes out this weekend and then allocate tasks on the list ? 

 

Mark 
Curphey
Consulting Director
Foundstone, Inc.
Strategic 
Security

949.297.5600 x2070 Tel
781.738.0857 Cell
949.297.5575 
Fax

http://www.foundstone.com

This 
email may contain confidential and privileged information for the sole use of 
the intended recipient. Any review or distribution by others is strictly 
prohibited. If you are not the intended recipient, please contact the sender and 
delete all copies of this message. Thank you. 

 

 

From: Peter 
Michalek [mailto:] 
Sent: Friday, March 26, 2004 4:48 
PM
To: 'David Raphael'; Mark 
Curphey; 
Subject: RE: WAS Action 
Items

David,

 

To streamline the 
action items and get a more mature schema soon to be posted, I suggest that we 
subdivide the work and then merge it.

I think I have the 
latest schema as you modified it before we left. It doesn’t matter to me how we 
divide the work, e.g.:

I could 
take:

1) Initial annotation 
on vulntypes - i.e. the following nodes:

a)

                                    
<xsd:element name="vulnTypes" 
type="vulnTypes">

                                                
<xsd:annotation>

                                                            
<xsd:appinfo></xsd:appinfo>

                                                
</xsd:annotation>

                                    
</xsd:element>

 

b)

            
<xsd:complexType name="vulnTypes">

                        
<xsd:sequence>

                                    
<xsd:element name="vuln">

                                                
<xsd:complexType>

                                                            
<xsd:sequence>

                                                                        
<xsd:element name="vuln" type="vulnList" />

                                                            
</xsd:sequence>

                                                
</xsd:complexType>

                                    
</xsd:element>

                        
</xsd:sequence>

            
</xsd:complexType>

 

c)

            
<xsd:simpleType name="vulnList">

 

2)       
proposal for Id – that 
is nodes:

o        
                                                            
<xsd:element name="ID" type="ID">

 

 

3)       
proposal for digital 
signature (I discussed it with the author or XKMS and it seems feasible while 
keeping it optional)

 

 

 

That would start moving 
forward the action items 1, 2, 7, 5 of your original list. 

 

I can do some of this 
work over the weekend. I’ll be fairly busy otherwise in the next few weeks with 
the end of our product release here at my company.

I would assume you’ll 
be the keeper of the master document and do the merge later, although if you 
think you won’t modify it over the weekend, it may be easier if I am the keeper 
for the next few days.

 

Peter

 

 

 

 

From: David 
Raphael [mailto:] 
Sent: Wednesday, March 24, 2004 6:29 
PM
To: 
; ; 

Subject: WAS Action 
Items

 

Here are the basic Actions 
Items I recorded.  This is pretty rough, but it is a start.  

 

/d