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, February 27, 2013 to Wednesday, December 18, 2013
Time: 9:30 am, Pacific Standard Time (San Francisco, GMT-08:00)
Meeting Number: 204 744 318
Password: 123
Host Key: 870819 (use this to reclaim host privileges)
-------------------------------------------------------
To join the meeting online(Now from mobile devices!)
-------------------------------------------------------
1. Go to https://cisco.webex.com/ciscosales/j.php?ED=218232647&UID=481888762&PW=NZDM4N2I2NzFl&RT=MiM0
2. If requested, enter your name and email address.
3. If a password is required, enter the meeting password: 123
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:204 744 318
CCP:+14085256800x204744318#
IMPORTANT NOTICE: This WebEx service includes a feature that allows audio and any documents and other materials exchanged or viewed during the session to be recorded. By joining this session, you automatically consent to such recordings. If you do not consent to the recording, discuss your concerns with the meeting host prior to the start of the recording or do not join the session. Please note that any such recordings may be subject to discovery in the event of litigation.
....................Stop copying here ...................
==========
Agenda:
Jira Issues to be discussed
EBXMLMSG-04: Core Spec - Error Reporting, SOAP Faults - Finalize discussion
Section 6.6 describe the use of SOAP Faults with "failure" errors in a way that may not be compatible with the example in section 5.5.
See discussion on https://lists.oasis-open.org/archives/ebxml-msg/201301/msg00020.html.
EBXMLMSG-07: Core Spec Section 5.2.2.4 - Party Id, error of severity "error"
Section talks about an error with severity "error", but according to section 6.2.5 this should be severity "failure".
This happens also in other places.
EBXMLMSG-08: Core Spec Section 6.2.9 -XSD Type for error detail element
Section 6.2.9 of the core spec explains the usage of the //eb:Error/eb:ErrorDetail element as: "provides additional details about the context in which the error occurred. For example, it may be an exception trace".
The ebMS XSD defines the type of this as xsd:token. According to the XML Schema specification this means the value of this element must "not contain the carriage return (#xD), line feed (#xA) nor tab (#x9) characters, have no leading or trailing spaces (#x20) and have no internal sequences of two or more spaces" (quoted text taken from XML Schema spec).
I think the type definition unnecessarily limits the text that can provided and makes it more difficult to provide a useful context of the error.
==========
Minutes:
==========
Attendance: