Revision Summary Date Revision History Revision Class Comments 4/8/2008 0.1 New Version 0.1 release 6/20/2008 0.2 Clarified the meaning of the technical content. 7/25/2008 1.0 Updated and revised the technical content. 8/29/2008 1.0.1 Editorial Changed language and formatting in the technical content. 10/24/2008 1.0.2 Editorial Changed language and formatting in the technical content. 12/5/2008 2.0 Updated and revised the technical content. 1/16/2009 2.0.1 Editorial Changed language and formatting in the technical content. 2/27/2009 2.0.2 Editorial Changed language and formatting in the technical content. 4/10/2009 2.0.3 Editorial Changed language and formatting in the
4/23/2010 3.0.1 Editorial Changed language and formatting in the technical content. 6/4/2010 3.0.2 Editorial Changed language and formatting in the technical content. 7/16/2010 4.0 Major Updated and revised the technical content. 8/27/2010 4.0 None No changes to the meaning, language, or formatting of the technical content. 10/8/2010 4.0 None No changes to the meaning, language, or formatting of the technical content. 11/19/2010 4.0 None No changes to the meaning, language, or formatting of the technical content. 1/7/2011 4.0 None No changes to the meaning, language, or formatting of the technical content.
2/11/2011 4.0 None No changes to the meaning, language, or formatting of the technical content. 3/25/2011 4.0 None No changes to the meaning, language, or formatting of the technical content. 5/6/2011 4.0 None No changes to the meaning, language, or formatting of the technical content. 6/17/2011 4.1 Minor Clarified the meaning of the technical content. 9/23/2011 4.1 None No changes to the meaning, language, or formatting of the technical content. 12/16/2011 5.0 Major Updated and revised the technical content. 3/30/2012 5.0 None No changes to the meaning, language, or formatting of the technical content.
7/12/2012 5.0 None No changes to the meaning, language, or formatting of the technical content. 10/25/2012 5.0 None No changes to the meaning, language, or formatting of the technical content. 1/31/2013 5.0 None No changes to the meaning, language, or formatting of the technical content. 8/8/2013 5.0 None No changes to the meaning, language, or formatting of the technical content. 11/14/2013 5.0 None No changes to the meaning, language, or formatting of the technical content. 2/13/2014 5.0 None No changes to the meaning, language, or formatting of the technical content. 5/15/2014 5.0 None No changes to the
Message 2: SequenceAcknowledgement(BufferRemaining = 1) Message 2 in Figure 4 contains the sent by the RMD in response to message 1. Line numbers 1-24 in Table 2 are the SOAP envelope of message 2. Line 11 shows that the RMD has received the first message in the Sequence. Lines 13-17 show the element with a value of 1. This means the RMD is capable of receiving one more message. Table 2 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 <s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope" > <s:Header> <r:SequenceAcknowledgement> <r:Identifier> urn:uuid:0b162747-99cf-479c-972f-95b776e141c3 </r:Identifier> <r:AcknowledgementRange Lower="1" Upper="1"> </r:AcknowledgementRange> <netrm:BufferRemaining > 1 </netrm:BufferRemaining> </r:SequenceAcknowledgement> <a:Action s:mustUnderstand="1"> http://schemas.xmlsoap.org/ws/2005/02/rm/SequenceAcknowledgement </a:Action> </s:Header> <s:Body></s:Body> </s:Envelope> Message 3: Sequence(MessageNumber = 2) Message 3 in Figure 4 is the second message in the Sequence sent by the RMS. Line numbers 1-19 in 3 are the SOAP envelope of message 3. Line 11 shows this to be the second message in the Sequence. Table 3
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 <s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope" xmlns:r="http://schemas.xmlsoap.org/ws/2005/02/rm" xmlns:a="http://www.w3.org/2005/08/addressing" > <s:Header> <r:Sequence s:mustUnderstand="1"> <r:Identifier> urn:uuid:0b162747-99cf-479c-972f-95b776e141c3 </r:Identifier> <r:MessageNumber>2</r:MessageNumber> </r:Sequence> <a:Action s:mustUnderstand="1"> http://tempuri.org/IAFCEExampleContract/Operation1 </a:Action> <a:To s:mustUnderstand="1">http://localhost/AFCEExample</a:To> </s:Header> <s:Body>...</s:Body> </s:Envelope> Message 4: SequenceAcknowledgement(BufferRemaining = 0) Message 4 in Figure 4 contains the sent by the RMD in response to message 2. Line numbers 1-24 in 4 are the SOAP envelope of message 4. Line 11 shows that the RMD has received the first and second messages in the Sequence. Lines 13-17 show the element with a value of 0. This means the RMD is not capable of receiving more messages until the AD comes online and starts processing the ones already received. Table 4
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 <s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope" xmlns:r="http://schemas.xmlsoap.org/ws/2005/02/rm" > <s:Header> <r:Sequence s:mustUnderstand="1"> <r:Identifier> urn:uuid:0b162747-99cf-479c-972f-95b776e141c3 </r:Identifier> <r:MessageNumber>3</r:MessageNumber> </r:Sequence> <a:Action s:mustUnderstand="1"> http://tempuri.org/IAFCEExampleContract/Operation1 </a:Action> <a:To s:mustUnderstand="1">http://localhost/AFCEExample</a:To> </s:Header> <s:Body>...</s:Body> </s:Envelope> Message 7: SequenceAcknowledgement(BufferRemaining = 0) Message 7 in Figure 4 contains the sent by the RMD in response to message 6. Line numbers 1-24 in Table 7 are the SOAP envelope of message 7. Line 11 shows that the RMD has received the first, second, and third messages in the Sequence. Lines 13-17 show the element with a value of 0. This 0 value means that the RMD is once again incapable of receiving more messages. Table 7
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 <s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope" xmlns:r="http://schemas.xmlsoap.org/ws/2005/02/rm" xmlns:a="http://www.w3.org/2005/08/addressing" > <s:Header> <r:SequenceAcknowledgement> <r:Identifier> urn:uuid:0b162747-99cf-479c-972f-95b776e141c3 </r:Identifier> <r:AcknowledgementRange Upper="3"> </r:AcknowledgementRange> <netrm:BufferRemaining > 0 </netrm:BufferRemaining> </r:SequenceAcknowledgement> <a:Action s:mustUnderstand="1"> http://schemas.xmlsoap.org/ws/2005/02/rm/SequenceAcknowledgement </a:Action> </s:Header> <s:Body></s:Body> </s:Envelope>
Index A Abstract data model RMD 11 11 RMS 14 13 14 10 10 8 B 10 10 C 8 27 D Data model - abstract RMD 11 11 RMS 14 13 14 E 10 Examples message 17 18 19 20 21 22 23 17 17 F 9 G 6 H Header block 10 10 triggered events 12 15 I 25 25 7 Initialization 12 14 6 L Local events RMD 12 12 13 13 RMS 15 16 M Message 17 18 19 20 21 22 23 17 processing 12 15 Messages 10 10 10 10 10 N 7 O 7 P 25 8 8 26