Fw: sgg take on issues that may impact WS-BaseN

[Steve Graham <sggraham@us.ibm.com>]

discussion amongst the editors of WS-BaseN
and the co-chairs with regards WS-BaseN related issues.

sgg

++++++++
Steve Graham
(919)254-0615 (T/L 444)
STSM, IBM Software Group, Web services and SOA
Member, IBM Academy of Technology
<Soli Deo Gloria/>
++++++++

----- Forwarded by Steve
Graham/Raleigh/IBM on 03/28/2005 12:23 PM -----

"Vambenepe, William N" <vbp@hp.com>

03/25/2005 01:20 PM

To	"David Hull" <dmh@tibco.com>, "Murray, Bryan P." <bryan.murray@hp.com>
cc	Steve Graham/Raleigh/IBM@IBMUS, "Peter Niblett" <peter_niblett@uk.ibm.com>
Subject	RE: sgg take on issues that may impact WS-BaseN

Hi WS-BaseN editors,
 
Thanks Steve for listing these
issues on BaseN. I'd like to use the upcoming call (3/28) to make as many
decisions on these as needed so the editors have free reins to put a committee
draft candidate together soon. Do you think the best way would be to send
Steve's list below and make this the heart of the agenda?
 
William

---

From: David Hull [mailto:dmh@tibco.com]
Sent: Monday, March 21, 2005 11:35 AM
To: Murray, Bryan P.
Cc: Steve Graham; Peter Niblett; Vambenepe, William N
Subject: Re: sgg take on issues that may impact WS-BaseN

(re-send: Thunderbird fell over (!) while I was trying
to send the last one)

I'm currently waist-deep in WS-Addressing (and the concall is imminent),
but I am following this discussion, I have read through the whitepaper,
and I hope to have more detailed comments tomorrow.

Murray, Bryan P. wrote: 
Steve,
 
I am not sure where you are going
with this list, but it is a good exercise to evaluate where we are at.
I have added my comments below in <bpm></bpm>
 
Bryan

---

From: Steve Graham [mailto:sggraham@us.ibm.com]
Sent: Friday, March 18, 2005 4:55 PM
To: dmh@tibco.com;
Murray, Bryan P.
Cc: Peter Niblett; Vambenepe, William N
Subject: sgg take on issues that may impact WS-BaseN


WS-BaseN co-editors: 
Please review and comment and then we should post:


WSN1.3: Security section to include more specific advice.
- If we factor security section out of the Whitepaper into BaseN, we would
need to address this issue.  
<bpm>Since the issue is
about the white paper, it seems we will need to discuss this issue no matter
where the security section ends up</bpm> 

WSN1.4: Support for pull-type notification 
- There is a chance that resolution of this issue will impact the WS-BaseN
spec.  
<bpm>Agreed</bpm>

WSN1.5: Term “Event” is not clearly defined 
- I thought we closed this (Issues list still has this as open).  Pretty
straight forward purge of the word "event"

WSN2.6: Third party subscriber can be a security concern
- This is David Hull's to do, make a proposal on DDOS

WSN2.23: Is Subscription a WS Resource? 
- I posted an amendment to my original proposal based on William et al's
"friendly" amendment. 

WSN2.25: Indirection via WSRP and WSRL 
- Not sure how to proceed with this one.  
<bpm>The resolution may
or may not affect WS-BaseN</bpm> 

WSN2.26: Targeting notification consumers 
- Not sure how to proceed with this one.  
<bpm>This seems like something
that might be modeled on top of baseN, instead of being a part of it, however,
the TC could decide that a change needs to be made to baseN</bpm>

WSN2.28: Durable notification delivery 
- Not sure how to proceed with this one.  
<bpm>discussion so far is
leaning towards putting this in a policy statement</bpm>

WSN2.32: Dialect of TopicExpression in Subscribe MUST be specified 
- open-approach agreed, requires editor execution 

WSN2.33: Message ordering/inerleaving 
- open-approach agreed, requires editor execution 

WSN2.34: Additional Fault definitions 
- was resolved in 1.3 e, should be marked resolved.

WSN2.35: Need XSD schema separated from WSDL file 
- was resolved in 1.3 e, should be marked resolved.

WSN2.36: Specify baseline policy behavior 
- Not sure how to proceed with this one.  
<bpm>this needs to wait
until we have decide what we will define policy for, then we can decide
what the defaults are</bpm> 

WSN2.37: TopicExpression RP to have attribute extensibility
- was resolved in 1.3 e, should be marked resolved.

WSN2.38: Topics RP to be renamed as TopicExpression
- was resolved in 1.3 e, should be marked resolved.

WSN2.39: Tighten up the semantics of  “send/delivery”
- David Hull raised this issue.  
<bpm>Approach agreed - perhaps
David can suggest changes</bpm> 

WSN2.40: Use of wsa:RelatesTo in WSN 
- this one might be straight forward.  
<bpm>agreed</bpm>

WSN5.5: WSDL20 Representation 
- may have impact, if we produce a WSDL 2.0 of BaseN
 
<bpm>perhaps it would be
better to leave that for a future version</bpm>

WSN5.6: WSN to utilize WSDL20 functionality 
- should we move WSDL 2.0 into the "next version" list?
 
<bpm>makes sense to me</bpm>

sgg 



++++++++
Steve Graham
(919)254-0615 (T/L 444)
STSM, IBM Software Group, Web services and SOA
Member, IBM Academy of Technology
<Soli Deo Gloria/>
++++++++