RE: [ebxml-msg] latest editorial updates on WD 17

David:

- mostly, Delivery Assurances definitions (not 
specification) have been added. Note they are not supposed to affect in any way 
the conformance of implementations to the RM protocol - which remains the main 
focus of WS-RM. These DAs represent some common definitions that can be the 
basis for developers to build reliability features on top of the RM protocol. In 
other words, the DAs are defined, but not specified (remain out of 
scope).

- a feature like MakeConnection has been made more 
accessory (in a separate document) and not explicitly referenced anymore in the 
core spec.

- other lesser updates.

 

In terms of  OSS implementation, I think there 
used to be an Apache project early on , not sure if it is 
up-to-date.

 

Jacques

From: David RR Webber (XML) 
[mailto:] 
Sent: Saturday, March 17, 2007 9:05 
AM
To: Durand, Jacques R.
Cc: 

Subject: RE: [ebxml-msg] latest 
editorial updates on WD 17

Jacques,

 

Is there a summary somewhere of CD7 and what is new / updated in it?

 

Also - I like the idea of supporting the latest iteration.  A little 
bit of care is needed in case its not just incremental - but actually a major 
change.  (I have in mind the OASIS CIQ v3 from v2 - which would be an 
example of where adopting the latest would have significant impacts).

 

Otherwise though - being able to support the latest maintenance release is 
obviously a good option.

 

Is there a reference download site or import / include link we could point 
to? (e.g. sourceforge?)

 

Thanks, DW

"The way to be is to do" - Confucius (551-472 
B.C.)

-------- 
  Original Message --------
Subject: [ebxml-msg] latest editorial updates on 
  WD 17
From: "Durand, Jacques R." <>
Date: 
  Thu, March 15, 2007 6:54 pm
To: 
  <>

  
1. as WS-RX voted 
  a CD7 today, I propose we make sure to keep the WS-ReliableMessaging binding 
  intro up-to-date (see 1st paragraph under B2 appendix). The referenced CD 
  should by now CD7.

  
 

  
2. A reminder that 
  we agreed in last meeting on adding an example of Receipt signal mesage. Here 
  is a rough starting point for it (from snippets taken on Dale's emails). It 
  would be nice to align the <ebbpsig:MessagePartNRInformation> content 
  with parts of the acknowledged message example..

  
 

  
Message 
  1:

  
 

  
 

  
<SOAP:Envelope 
  xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"

  
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

  
xsi:schemaLocation="http://schemas.xmlsoap.org/soap/envelope/

  
http://schemas.xmlsoap.org/soap/envelope/">

  
<SOAP:Header>

  
<ebms:Messaging 
  xmlns:ebms="http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-3_0.xsd"

  
        
  xmlns:ds="http://www.w3.org/2000/09/xmldsig#">

  
    <ebms:UserMessage>

  
        
  <ebms:MessageInfo>

  
            
  <ebms:TimeStamp>2000-07-25T12:19:05</ebms:TimeStamp>

  
            
  <ebms:MessageId></ebms:MessageId>

  
         </ebms:MessageInfo>

  
      ....

  
    </ebms:UserMessage>

  
</ebms:Messaging> 
  

  

  
</SOAP:Header>

  
<SOAP:Body>

  
....

  

  
</SOAP:Body>

  
</SOAP:Envelope>

  
 

  
Receipt for Message 1: 

  
 

  

  
<SOAP:Envelope 
  xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"

  
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

  
xsi:schemaLocation="http://schemas.xmlsoap.org/soap/envelope/

  
http://schemas.xmlsoap.org/soap/envelope/">

  
<SOAP:Header>
<ebms:Messaging 
  xmlns:ebms="http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-3_0.xsd"

  
    
  xmlns:ebbpsig="http://docs.oasis-open.org/ebxml-bp/ebbp-signals-2.0"

  
    
  xmlns:ds="http://www.w3.org/2000/09/xmldsig#">

  
    
  <ebms:SignalMessage>

  
        
  <ebms:MessageInfo>

  
            
  <ebms:TimeStamp>2000-07-25T12:19:35</ebms:TimeStamp>

  
            
  <ebms:MessageId></ebms:MessageId>

  
            
  <ebms:RefToMessageId></ebms:RefToMessageId>

  
        
  </ebms:MessageInfo>

  
       
  <ebms:Receipt>

  
           
  <ebbpsig:NonRepudiationInformation> 
  
                
  <ebbpsig:MessagePartNRInformation>

  
                    
  <ebbpsig:MessagePartIdentifier> 
  </ebbpsig:MessagePartIdentifier>

  
                    
  <ds:Reference> 
  all the ds reference stuff</ds:Reference>

  
                
  </ebbpsig:MessagePartNRInformation>

  
                
  <ebbpsig:MessagePartNRInformation>

  
                    
  <ebbpsig:MessagePartIdentifier> 
  </ebbpsig:MessagePartIdentifier>

  
                    
  <ds:Reference> 
  all the ds reference stuff </ds:Reference>

  
                
  </ebbpsig:MessagePartNRInformation>

  
            
  </ebbpsig:NonRepudiationInformation>

  
      </ebms:Receipt>

  
    
  </ebms:SignalMessage>

  
</ebms:Messaging> 
  

  

  

  
</SOAP:Header>

  
<SOAP:Body>

  

  
</SOAP:Body>

  
</SOAP:Envelope>