RE: [wsn] Clarification of the status of WSN 2.24

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

ok, agreed.  Thanks for the clarification.

++++++++
Steve Graham
(919)254-0615 (T/L 444)
STSM, On Demand Architecture
Member, IBM Academy of Technology
<Soli Deo Gloria/>
++++++++

"Patil, Sanjay" <sanjay.patil@sap.com>

11/17/2004 03:47 PM

To	Steve Graham/Raleigh/IBM@IBMUS
cc	wsn@lists.oasis-open.org
Subject	RE: [wsn] Clarification of the status of WSN 2.24

Hi Steve, thanks for figuring
out the mystery :-)  Yes, the status for WSN2.24 got wrongly placed
under WSN2.23. Sorry about that. I will fix the error and upload the new
version soon.
 
To recap ...here is the status
as I remember (I also checked the meeting minutes and the Action Item reminder
email William sent out today)
 
WSN2.23: The correct status is:
Open. 
The pending AI here is ..

    OPEN - Steve: Create two versions of the subscriptionManager interface, one simple where the subscription doesn't use WS-RP and a complete one (from Oct F2F,  issue WSN2.23)

WSN2.24: The correct status is: Open - approach agreed

Agreed Approach: Replace "Implied Resource Pattern" with "WS-Resource Access Pattern".

Thanks,
Sanjay
 
 
-----Original Message-----
From: Steve Graham [mailto:sggraham@us.ibm.com]
Sent: Wednesday, Nov 17, 2004 11:38 AM
To: Steve Graham
Cc: wsn@lists.oasis-open.org
Subject: Re: [wsn] Clarification of the status of WSN 2.24


Further follow up.  On a review of the issues list, the status of WSN 2.23:
       Status:   Open - approach agreed
Date: Oct 28, 2004

Agreed approach: Replace "Implied Resource Pattern" with "WS-Resource Access Pattern".

Looks more like what the status should look like for WSN2.24.

The proposed recommendation for WSN 2.23 had little to do with WS-RAP, but discussed adding a destroy() (unsubscribe()) operation:
       Proposed Recommendations

        Notes

This is the first out of the three issues substituting issue WSN2.2

During Oct 04 F2F, this issue was discussed. The group decided to provide an explicit Destroy operation on Subscription that does not utilize WS-ResourceLifetime.

The underlying rationale behind this decision was to ensure that the core semantics of WS-BaseNotification is self contained and a dependency on WS-RP and WS-RL is introduced only for advanced functionalities, thus allowing simple implementations to remain simpler.

We need to clarify the disposition of WSN 2.23 and WSN 2.24.

sgg
++++++++
Steve Graham
(919)254-0615 (T/L 444)
STSM, On Demand Architecture
Member, IBM Academy of Technology
<Soli Deo Gloria/>
++++++++

Steve Graham/Raleigh/IBM@IBMUS

11/17/2004 01:27 PM

To	wsn@lists.oasis-open.org
cc
Subject	[wsn] Clarification of the status of WSN 2.24

I am confused about the status of WSN 2.24.  From the reading of the text (included below) in the issues list, I thought we had an agreed resolution to this issue from the Oct f2f.  Why is this issue still marked as status: open?

I move that we change the status of this item to Open - approach agreed

sgg

      WSN2.24: Use of term -- Implied Resource Pattern
In several places in the specifications, references are made to IRP and how its use is mandated.

Issue: The precise semantics of IRP is unclear and currently being worked on by WS-RF.

        Specifications

·        WS-BaseNotification
      Proposed Recommendations

WSN specifications to be updated based on the IRP revision under WSRF.

        Notes

This is the second out of the three issues substituting issue WSN2.2

During London F2F on July 30, 2004, this issue was marked as blocked on -- pending IRP clarification from WSRF.

The group agreed to revisit this issue before publishing the next WSN specification drafts. Ideally, the WSRF TC should have resolved the IRP clarification issue before WSN publishes the next specification drafts.

During Oct 04 F2F, this issue was discussed. WS-Resource specification was presented that clarifies the semantics of what was before called as - Implied Resource Pattern.  

It was agreed to replace the utterances of Implied Resource Pattern in all the WS-N specification with WS-Resource Access Pattern, the new terminology introduced by the WS-Resource specification.

        Status:   Open

Date: July 29, 2004

        Contact:

David Hull

        Cross Reference:

Previous issue: WSN2.2

++++++++
Steve Graham
(919)254-0615 (T/L 444)
STSM, On Demand Architecture
Member, IBM Academy of Technology
<Soli Deo Gloria/>
++++++++