RE: [ws-rx-editors] RE: Submission of WS-RM, WS-RMP and WS-MC specifications for OASIS standardization

Thanks Doug,

 

  I'll check that out ... could be that one of the PR 
notices used those links.

 

Mary

  

  
  From: Doug Davis [mailto:] 
  
Sent: Thursday, April 26, 2007 10:30 AM
To: 
  
Cc: Mary McRae; 'Patil, Sanjay'; 
  
Subject: Re: [ws-rx-editors] RE: 
  Submission of WS-RM, WS-RMP and WS-MC specifications for OASIS 
  standardization

  

Mary, 
  so far it looks good.  One thing I did 
  notice is that the ppt and diff files are in the namespace directories - we 
  should probably remove those since there's no need for people to download 
  them. And, in fact, I don't think we even have pointers to them. 
  

thanks
-Doug
______________________________________________________
STSM 
   |  Web Services Architect  |  IBM Software Group
(919) 
  254-6905  |  IBM T/L 444-6905  |   
  

  
    
    

      "Mary McRae" 
        <> 
Sent by: Mary McRae <> 
        
04/26/2007 10:15 AM 
        
          
          

            
              
Please respond 
              to
<>

      
        
          
          

            
              
To

            "'Patil, Sanjay'" 
              <> 
          

            
              
cc

            <> 
          

            
              
Subject

            [ws-rx-editors] RE: Submission of 
              WS-RM, WS-RMP and WS-MC specifications for OASIS 
              standardization

        
          
          

            
            

Hi Sanjay et al, 
  
  
  I've uploaded all of the files 
  to docs - I would greatly appreciate it if you or the editors could check to 
  make sure everything is working as expected before announcements go out on 
  Tuesday. 
  
Thanks! 
  
Mary 

  
  From: Patil, Sanjay 
  [mailto:] 
Sent: Thursday, April 12, 2007 6:16 
  PM
To: 
Cc: 
  
Subject: Submission of WS-RM, 
  WS-RMP and WS-MC specifications for OASIS standardization

  
Hi Mary, 
  
Now that the WS-RX TC has approved the WS-RM, 
  WS-RMP and WS-MC specification set (by a special majority vote) as Committee 
  Specification and ready for submission to OASIS membership for a 
  standardization vote, I am hereby submitting the package containing the 
  relevant documents and other information. 
  
Please acknowledge this submission and also feel 
  free to let me know if anything is missing or if you need any further 
  information, etc. 
  
Regards, 
Sanjay 
  
PS: Please note that the links to documents in the 
  package below will be active only after expanding the attached archive in the 
  OASIS document repository. Please also copy the specification documents from 
  their "This Version" locations to their "Latest Version" locations. 
  
------------------------------------------------------------------------------------------------------------------- 
  
Attached ZIP archive contains the specification 
  documents in 
different (including editable) formats along with the 
  associated artifacts. 
<<WS-RX_CS_DirStructured.zip>> 
  
The Web Services Reliable Exchange (WS-RX) TC has 
  submitted the 
following specification set: 
  
(a) Links to the approved Committee Specification 
  in the TC's document 
repository, and any appropriate supplemental documentation for 
  the 
specification, both 
  of which must be written using the OASIS templates. 
  
The specification may not have been changed 
  between its approval as a 
Committee Specification and its submission to OASIS for 
  consideration as 
an 
  OASIS Standard, except for the changes on the title page and 
  running 
footer noting 
  the approval status and date. 
  
Web Services ReliableMessaging 1.1 
PDF - http://docs.oasis-open.org/ws-rx/wsrm/200702/wsrm-1.1-spec-cs-01.pdf 
HTML - http://docs.oasis-open.org/ws-rx/wsrm/200702/wsrm-1.1-spec-cs-01.html 
Schema - http://docs.oasis-open.org/ws-rx/wsrm/200702/wsrm-1.1-schema-200702.xsd 
WSDL - http://docs.oasis-open.org/ws-rx/wsrm/200702/wsdl/wsrm-1.1-wsdl-200702.wsdl 
RDDL - http://docs.oasis-open.org/ws-rx/wsrm/200702/wsrm-1.1-rddl-200702.html 
  
Web Services ReliableMessaging Policy 
  1.1 
PDF - http://docs.oasis-open.org/ws-rx/wsrmp/200702/wsrmp-1.1-spec-cs-01.pdf 
HTML - http://docs.oasis-open.org/ws-rx/wsrmp/200702/wsrmp-1.1-spec-cs-01.html 
Schema - http://docs.oasis-open.org/ws-rx/wsrmp/200702/wsrmp-1.1-schema-200702.xsd 
RDDL - http://docs.oasis-open.org/ws-rx/wsrmp/200702/wsrmp-1.1-rddl-200702.html 
  
Web Services MakeConnection 1.0 
  
PDF - http://docs.oasis-open.org/ws-rx/wsmc/200702/wsmc-1.0-spec-cs-01.pdf 
HTML - http://docs.oasis-open.org/ws-rx/wsmc/200702/wsmc-1.0-spec-cs-01.html 
Schema - http://docs.oasis-open.org/ws-rx/wsmc/200702/wsmc-1.0-schema-200702.xsd 
WSDL - http://docs.oasis-open.org/ws-rx/wsmc/200702/wsdl/wsmc-1.0-wsdl-200702.wsdl 
RDDL - http://docs.oasis-open.org/ws-rx/wsmc/200702/wsmc-1.0-rddl-200702.html 
  
(b) The editable version of all files that are part 
  of the Committee 
Specification; 
  
http://docs.oasis-open.org/ws-rx/wsrm/200702/wsrm-1.1-spec-cs-01.doc 
http://docs.oasis-open.org/ws-rx/wsrmp/200702/wsrmp-1.1-spec-cs-01.doc 
http://docs.oasis-open.org/ws-rx/wsmc/200702/wsmc-1.0-spec-cs-01.doc 
  
(c) Certification by the TC that all schema and XML 
  instances included 
in 
  the specification, whether by inclusion or reference, including 
fragments of such, are well formed, 
  and that all expressions are valid; 
  
All schema and XML instances included in the 
  specification are well 
formed and all expressions are valid. 
  
(d) A clear English-language summary of the 
  specification; 
  
The WS-ReliableMessaging 1.1 specification consists 
  of multiple parts. 
  
The core WS-ReliableMessaging 1.1 document defines 
  a protocol for 
reliable 
  message exchange between two Web services, even in the presence 
of network or system failures. For 
  example, the protocol can ensure the 
resending of messages that have been lost, and can 
  ensure that duplicate 
messages are not delivered. The protocol allows Web service nodes 
  to 
implement a variety 
  of delivery assurances, including At Most Once, At 
  
Least Once, Exactly Once and In Order 
  delivery of messages. The protocol 
fundamentally defines a one-way reliable channel (known as a 
  Sequence), 
but also 
  includes mechanisms to optimize the creation of two-way 
  
reliable exchanges. The protocol is 
  designed to compose with other 
relevant standards such as WS-Security and 
  WS-SecureConversation. The 
protocol allows developers to add reliable 
  delivery of messages to their 
applications on a variety of platforms, 
  including Java and .NET. 
  
The WS-ReliableMessaging Policy 1.1 document 
  defines an XML policy 
language that enables Web services to advertise their support for 
  the 
WS-ReliableMessaging specification. The specification is designed 
  for 
use with the 
  WS-Policy Framework. The language aids the interoperability 
of nodes that support 
  WS-ReliableMessaging by publishing their support 
  
and requirements for aspects of reliable 
  messaging. For example, an 
endpoint may use this specification to indicate 
  that it requires that 
the reliable message protocol to be secured using 
  transport level 
security. WS-ReliableMessaging Policy is designed to be 
  used with other 
policy languages, such as WS-Security Policy, in the scope 
  of the 
WS-Policy Framework. 
  
The WS-MakeConnection 1.0 document defines a 
  protocol that can be 
used to allow two-way communications when only a transport 
  specific 
back-channel 
  (such as the HTTP response mechanism) is available. For 
  
example, this allows a client to establish 
  a two-way reliable 
message exchange even in the presence of firewalls and network 
  address 
translation, 
  that otherwise would prevent the server from initiating 
connections to the 
  client. 
  
(e) A statement regarding the relationship of this 
  specification to 
similar work of other OASIS TCs or other standards developing 
  organizations; 
  
-- The OASIS WS-Reliable Messaging (WSRM) TC also 
  defines a reliable 
messaging specification for Web services. The WS-RX TC 
  and 
WS-ReliableMessaging specification focuses on creating a 
  specification 
that 
  works in conjunction with and composes with other specifications, 
in 
  particular the WS-Addressing, WS-Security and WS-SecureConversation, 
and 
  WS-Policy Framework specifications. 
  
(f) Certification by at least three OASIS member 
  organizations that they 
are successfully using the specification; 
  
  
Certification via email: 
  
WSO2: 
http://www.oasis-open.org/apps/org/workgroup/ws-rx/email/archives/200702/msg00068.html 
http://www.oasis-open.org/committees/download.php/23441/MinutesWSRX-2007-03-29-1.htm 
  
IBM: 
http://www.oasis-open.org/apps/org/workgroup/ws-rx/email/archives/200702/msg00069.html 
http://www.oasis-open.org/committees/download.php/23441/MinutesWSRX-2007-03-29-1.htm 
  
SAP AG: 
http://www.oasis-open.org/apps/org/workgroup/ws-rx/email/archives/200703/msg00000.html 
http://www.oasis-open.org/committees/download.php/23441/MinutesWSRX-2007-03-29-1.htm 
  

  
(g) The beginning and ending dates of the public 
  review(s), a pointer to 
the announcement of the public review(s), and a pointer to an 
  account of 
each of the 
  comments/issues raised during the public review period(s), 
  
along with its resolution; 
  
First Public Review: 24 August 2006 to 21 October 
  2006 
Second Public 
  Review: 12 February 2007 to 27 February 2007 
  
Announcement of the first Public 
  Review: 
http://lists.oasis-open.org/archives/tc-announce/200608/msg00005.html 
  
Announcement of the second Public 
  Review: 
http://lists.oasis-open.org/archives/tc-announce/200702/msg00004.html 
  
Public Review Issue and Resolution Log: 
http://docs.oasis-open.org/ws-rx/issues/pr/Issues.xml 
  
(h) An account of and results of the voting to 
  approve the specification 
as a Committee Specification, including the date of the ballot and 
  a 
pointer to the 
  ballot; 
  
TBD 
  
(i) An account of or pointer to votes and comments 
  received in any 
earlier 
  attempts to standardize substantially the same specification, 
together with the originating TC's 
  response to each comment; 
  
This is the first submission to the OASIS 
  membership 
  
(j) A pointer to the publicly visible comments 
  archive for the 
originating TC; 
  
http://lists.oasis-open.org/archives/ws-rx-comment/ 
  
(k) A pointer to any minority reports submitted by 
  one or more Members 
who 
  did not vote in favor of approving the Committee Specification, 
which report may include statements 
  regarding why the member voted 
against the specification or that the member believes that 
  Substantive 
Changes 
  were made which have not gone through public review; or 
  
certification by the Chair that no minority 
  reports exist. 
  
There are no minority reports.