Bi Weekly TC meeting

When:  May 22, 2013 from 12:00 to 13:00 (PT)
Description:

Bi-weekly TC meeting. Agenda will be decided and published before the meetings.

 

------------------------------------------------------- 

 

Topic: Bi-Weekly ebms TC meeting 
Date: Every 2 weeks on Wednesday, from Wednesday, May 22, 2013 to Wednesday, December 18, 2013 
Time: 12:00 pm, Pacific Daylight Time (San Francisco, GMT-07:00) 
Meeting Number: 204 744 318 
Password: as4 
Host Key: 870819 

------------------------------------------------------- 
To join the meeting online 
------------------------------------------------------- 
1. Go to https://ciscosales.webex.com/ciscosales/j.php?ED=218232647&UID=481888762&PW=NMGViODQ5OTYy&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 number (US/Canada): +1-408-525-6800 
Global call-in numbers: https://ciscosales.webex.com/ciscosales/globalcallin.php?serviceType=MC&ED=218232647&tollFree=0 

Access code:204 744 318 


==========
Agenda:

Jira Issues to be discussed:

EBXMLMSG-05 - AS4 Section 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-06 : AS4 Section 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.

 

EBXMLMSG-09 : AS4, Core Spec - Receipt format for reception awareness

 

The use of UserMessage elements for reception awareness was discussed at length, my proposal would be to not reopen the format discussiong but instead relax the schema to allow the use by dropping the requirement that content of receipt be from another namespace. 

 

 

 

AS4 uses copies of UserMessage elements in receipt for non-repudation awareness. This satifies the requirement that the content of Receipt is a non-empty sequence, but the UserMessage element is from the same ebMS namespace as the Receipt, whereas the schema requires it to be from another namespace. We missed this when we changed the format for reception awareness receipts. 

 

 



==========
Minutes:

==========
Attendance:

Related Content