Description:
Additional TC meetings to go over Jira issues
Topic: ebMS TC meeting
Date: Every 2 weeks on Wednesday, from Wednesday, May 29, 2013 to Wednesday, July 24, 2013
Time: 12:00 pm, Pacific Daylight Time (San Francisco, GMT-07:00)
Meeting Number: 203 842 277
Password: as4
Host Key: 178523
-------------------------------------------------------
To join the meeting online(Now from mobile devices!)
-------------------------------------------------------
1. Go to https://ciscosales.webex.com/ciscosales/j.php?ED=227372142&UID=481888762&PW=NNTRhM2EyMTEw&RT=MiM0
2. If requested, enter your name and email address.
3. If a password is required, enter the meeting password: as4
4. Click "Join".
5. If the meeting includes a teleconference, follow the instructions that appear on your screen.
-------------------------------------------------------
To join the audio conference only
-------------------------------------------------------
To receive a call back, provide your phone number when you join the meeting, or call the number below and enter the access code.
Call-in toll-free number (US/Canada): +1-866-432-9903
Call-in toll number (US/Canada): +1-408-525-6800
Toll-free dialing restrictions: http://www.webex.com/pdf/tollfree_restrictions.pdf
Access code:203 842 277
==========
Agenda:
EBXMLMSG-5 3.2 Reception Awareness feature, retries
Description of reception awareness does not describe what to do when an error is encountered when sending a message that causes no receipt to be delivered. With some errors (e.g. HTTP connection issues) we want the sending MSH to retry, but with others (e.g. ebMS errors) there is no point in retrying, so the MSH should probably report the error directly.
See discussion in thread starting with https://lists.oasis-open.org/archives/ebxml-msg/201301/msg00015.html.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
EBXMLMSG-6 3.2 Reception awareness, validation of receipts
The spec does not specify if the sending MSH should check that a receipt is valid and what it should do if it is not
See thread starting at https://lists.oasis-open.org/archives/ebxml-msg/201301/msg00016.html.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
EBSMLMSG-16 AS4 Section 5.1.8 Generating Receipts Profiling Rule (a) interpretation
Section 5.1.8 Generating Receipts Profiling Rule (a) of the AS4 spec reads as follows
When a Receipt is to be used solely for reception awareness, the sender of the Receipt MUST contain a copy of the eb:UserMessage structure of the received AS4 message.
This is open to misinterpretation as it could mean that either the receipt must contain a copy of the eb:UserMessage structure or the Sender must keep a copy of that. My thinking is that it should read as one the following
1 When a Receipt is to be used solely for reception awareness, the sender of the Receipt MUST retain a copy of the eb:UserMessage structure of the received AS4 message.
or
2 When a Receipt is to be used solely for reception awareness, the sender must include a copy of the eb:UserMessage structure of the received AS4 message in the receipt.
==========
Minutes:
==========
Attendance: