OASIS ebXML Messaging Services TC

Event Title : Bi Weekly TC meeting Date : Wednesday, 27 February 2013, 09:30am to 10:30am PST 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 ................... Owner : Makesh Rao Group : OASIS ebXML Messaging Services TC Sharing : This event is not shared to any other groups. Recurrence This event is part of a series with 22 more events. The next 4 events in this series: Wednesday, 13 March 2013, 09:30am to 10:30am PDT Wednesday, 27 March 2013, 09:30am to 10:30am PDT Wednesday, 10 April 2013, 09:30am to 10:30am PDT Wednesday, 24 April 2013, 09:30am to 10:30am PDT BEGIN:VCALENDAR CALSCALE:GREGORIAN METHOD:PUBLISH VERSION:2.0 PRODID:-//Kavi Corporation//NONSGML Kavi Groups//EN X-MS-OLK-FORCEINSPECTOROPEN:TRUE BEGIN:VTIMEZONE TZID:America/Los_Angeles BEGIN:STANDARD DTSTART:20001029T020000 RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10;UNTIL=20061029T090000Z TZNAME:PST TZOFFSETFROM:-0700 TZOFFSETTO:-0800 END:STANDARD BEGIN:STANDARD DTSTART:20071104T020000 RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=11 TZNAME:PST TZOFFSETFROM:-0700 TZOFFSETTO:-0800 END:STANDARD BEGIN:DAYLIGHT DTSTART:20000402T020000 RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=4;UNTIL=20060402T100000Z TZNAME:PDT TZOFFSETFROM:-0800 TZOFFSETTO:-0700 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:20070311T020000 RRULE:FREQ=YEARLY;BYDAY=2SU;BYMONTH=3 TZNAME:PDT TZOFFSETFROM:-0800 TZOFFSETTO:-0700 END:DAYLIGHT END:VTIMEZONE BEGIN:VEVENT CATEGORIES:MEETING STATUS:CONFIRMED TRANSP:OPAQUE DTSTAMP:20130221T000000Z DTSTART;VALUE=DATE-TIME;TZID=America/Los_Angeles:20130227T093000 DTEND;VALUE=DATE-TIME;TZID=America/Los_Angeles:20130227T103000 SEQUENCE:24 SUMMARY:Bi Weekly TC meeting 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 ...................

Group: OASIS ebXML Messaging Services TC
Creator: Makesh Rao URL: https://www.oasis-open.org/apps/org/workgroup/ebxml-msg/event.php?event_id=34674 UID: https://www.oasis-open.org/apps/org/workgroup/ebxml-msg/event.php?event_id=34674 BEGIN:VALARM ACTION:DISPLAY DESCRIPTION:REMINDER TRIGGER;RELATED=START:-PT00H15M00S END:VALARM RRULE:FREQ=WEEKLY;INTERVAL=2;COUNT=22 END:VEVENT END:VCALENDAR BEGIN:VCALENDAR CALSCALE:GREGORIAN METHOD:PUBLISH VERSION:2.0 PRODID:-//Kavi Corporation//NONSGML Kavi Groups//EN X-MS-OLK-FORCEINSPECTOROPEN:TRUE BEGIN:VTIMEZONE TZID:America/Los_Angeles BEGIN:STANDARD DTSTART:20001029T020000 RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10;UNTIL=20061029T090000Z TZNAME:PST TZOFFSETFROM:-0700 TZOFFSETTO:-0800 END:STANDARD BEGIN:STANDARD DTSTART:20071104T020000 RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=11 TZNAME:PST TZOFFSETFROM:-0700 TZOFFSETTO:-0800 END:STANDARD BEGIN:DAYLIGHT DTSTART:20000402T020000 RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=4;UNTIL=20060402T100000Z TZNAME:PDT TZOFFSETFROM:-0800 TZOFFSETTO:-0700 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:20070311T020000 RRULE:FREQ=YEARLY;BYDAY=2SU;BYMONTH=3 TZNAME:PDT TZOFFSETFROM:-0800 TZOFFSETTO:-0700 END:DAYLIGHT END:VTIMEZONE BEGIN:VEVENT CATEGORIES:MEETING STATUS:CONFIRMED TRANSP:OPAQUE DTSTAMP:20130116T000000Z DTSTART;VALUE=DATE-TIME;TZID=America/Los_Angeles:20130130T093000 DTEND;VALUE=DATE-TIME;TZID=America/Los_Angeles:20130130T103000 SEQUENCE:44 SUMMARY:Bi Weekly TC meeting DESCRIPTION:
Bi-weekly TC meeting. Agenda will be decided and published before the meetings.







+---+---+---+---+---+---+---+---+---+---+---+

You are invited to an online meeting using WebEx.



Meeting Number: 206273018

Meeting Password: ebms



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

To join this meeting (Now from mobile devices!)

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

1. Go to https://cisco.webex.com/cisco/e.php?AT=SI&MK=206273018



2. Enter the meeting password: ebms

3. Click 'Join Now'.

4. Follow the instructions that appear on your screen.





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

ALERT:Toll-Free Dial Restrictions for (408) and (919) Area Codes

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



The affected toll free numbers are: (866) 432-9903 for the San Jose/Milpitas area and (866) 349-3520 for the RTP area.



Please dial the local access number for your area from the list below:

- San Jose/Milpitas (408) area: 525-6800

- RTP (919) area: 392-3330



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

To join the teleconference only

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

1. Dial into Cisco WebEx (view all Global Access Numbers at http://cisco.com/en/US/about/doing_business/conferencing/index.html )

2. Follow the prompts to enter the Meeting Number (listed above) or Access Code followed by the # sign.



San Jose, CA: +1.408.525.6800 RTP: +1.919.392.3330



US/Canada: +1.866.432.9903 United Kingdom: +44.20.8824.0117



India: +91.80.4350.1111 Germany: +49.619.6773.9002



Japan: +81.3.5763.9394 China: +86.10.8515.5666



http://www.webex.com/



CCP:+14085256800x206273018#



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.

Group: OASIS ebXML Messaging Services TC
Creator: Makesh Rao URL: https://www.oasis-open.org/apps/org/workgroup/ebxml-msg/event.php?event_id=34672 UID: https://www.oasis-open.org/apps/org/workgroup/ebxml-msg/event.php?event_id=34672 BEGIN:VALARM ACTION:DISPLAY DESCRIPTION:REMINDER TRIGGER;RELATED=START:-PT00H15M00S END:VALARM RRULE:FREQ=WEEKLY;INTERVAL=2;COUNT=2 END:VEVENT END:VCALENDAR

Hi Makesh and all,   I understand that in ebMS3/AS4 the validation of business document payload is irrelevant as it's said in AS4 spec: The semantics for sending back an eb:Receipt message is as follows: a wellformed ebMS user message has been received and the MSH is taking responsibility for its processing (additional application-level delivery semantics, and payload validation semantics are not relevant). However one of our prospects asked us the question: if we detect the error in the payload (validation error, etc) and want to send back an error message to the sender, what's the messaging vehicle we should use to carry the error? I guess this is a typical question that a future ebMS3/AS4 adopters will ask, especially when they are already used to the ebMS2 messaging choreography.   In ebMS2 an ebBP receipt can be sent back asynchronously to report the success/failure of the business document validation. So I would like to know how it is considered to integrate ebMS3/AS4 with ebBP (as I know the current version is 2.0.4, which was announced in 2006, before ebMS3.0 was finalized)? Or what's the best practice regarding to this matter?   Thanks, Rong

Hello Rong,   The ebBP signal messages can be used with ebMS3 as they can be used with ebMS2.  The difference with the ebMS3/AS4 receipt signals are that those are generated by the MSH and are SignalMessage elements in the eb:Messaging container.  The ebBP signals,  if they are generated by some application or middleware to express positive or negative acceptance or an application level receipt,  would be carried as payloads for UserMessage elements as they would be submitted to the responding MSH, rather than generated in it.  They would have the same Service but a different Action in the message header.     E.g. if there is a service Ordering with an action PlaceOrder ,  an acceptance response signal could have actions AcceptOrderPlacement or RejectOrderPlacement and a value for RefToMessageId set to the accepted user message.  If the order is positively accepted and an OrderResponse document is generated (from an XML business document/vocabulary standard like UBL or GS1), that document could be returned in a second response message.   Alternatively, a common practice is to only use negative acceptance for generic failures like schema validation (or even non-wellformedness) and use the business response from the business document standard to include the other acceptance cases. This way there is only one response,  either the generic negative acceptance (e.g. from ebBP) or a business transaction specific business response to express other negative, positive or partial acceptance.   Pim    From: ebxml-msg@lists.oasis-open.org [mailto:ebxml-msg@lists.oasis-open.org] On Behalf Of Rong Xing Sent: 05 March 2013 20:49 To: Makesh Rao; ebxml-msg@lists.oasis-open.org Subject: [ebxml-msg] What's the best practice to report an business level error with AS4? Hi Makesh and all,   I understand that in ebMS3/AS4 the validation of business document payload is irrelevant as it's said in AS4 spec: The semantics for sending back an eb:Receipt message is as follows: a wellformed ebMS user message has been received and the MSH is taking responsibility for its processing (additional application-level delivery semantics, and payload validation semantics are not relevant). However one of our prospects asked us the question: if we detect the error in the payload (validation error, etc) and want to send back an error message to the sender, what's the messaging vehicle we should use to carry the error? I guess this is a typical question that a future ebMS3/AS4 adopters will ask, especially when they are already used to the ebMS2 messaging choreography.   In ebMS2 an ebBP receipt can be sent back asynchronously to report the success/failure of the business document validation. So I would like to know how it is considered to integrate ebMS3/AS4 with ebBP (as I know the current version is 2.0.4, which was announced in 2006, before ebMS3.0 was finalized)? Or what's the best practice regarding to this matter?   Thanks, Rong

Pim,   Thanks for the clear explanation, which definitely helps me a lot.   Rong   From: ebxml-msg@lists.oasis-open.org [mailto:ebxml-msg@lists.oasis-open.org] On Behalf Of Pim van der Eijk Sent: Wednesday, March 06, 2013 2:27 AM To: ebxml-msg@lists.oasis-open.org; 'Makesh Rao' Subject: RE: [ebxml-msg] What's the best practice to report an business level error with AS4?   Hello Rong,   The ebBP signal messages can be used with ebMS3 as they can be used with ebMS2.  The difference with the ebMS3/AS4 receipt signals are that those are generated by the MSH and are SignalMessage elements in the eb:Messaging container.  The ebBP signals,  if they are generated by some application or middleware to express positive or negative acceptance or an application level receipt,  would be carried as payloads for UserMessage elements as they would be submitted to the responding MSH, rather than generated in it.  They would have the same Service but a different Action in the message header.     E.g. if there is a service "Ordering" with an action "PlaceOrder",  an acceptance response signal could have actions "AcceptOrderPlacement" or "RejectOrderPlacement" and a value for RefToMessageId set to the accepted user message.  If the order is positively accepted and an OrderResponse document is generated (from an XML business document/vocabulary standard like UBL or GS1), that document could be returned in a second response message.   Alternatively, a common practice is to only use negative acceptance for generic failures like schema validation (or even non-wellformedness) and use the business response from the business document standard to include the other acceptance cases. This way there is only one response,  either the generic negative acceptance (e.g. from ebBP) or a business transaction specific business response to express other negative, positive or partial acceptance.   Pim     From: ebxml-msg@lists.oasis-open.org [ mailto:ebxml-msg@lists.oasis-open.org ] On Behalf Of Rong Xing Sent: 05 March 2013 20:49 To: Makesh Rao; ebxml-msg@lists.oasis-open.org Subject: [ebxml-msg] What's the best practice to report an business level error with AS4? Hi Makesh and all,   I understand that in ebMS3/AS4 the validation of business document payload is irrelevant as it's said in AS4 spec: The semantics for sending back an eb:Receipt message is as follows: a wellformed ebMS user message has been received and the MSH is taking responsibility for its processing (additional application-level delivery semantics, and payload validation semantics are not relevant). However one of our prospects asked us the question: if we detect the error in the payload (validation error, etc) and want to send back an error message to the sender, what's the messaging vehicle we should use to carry the error? I guess this is a typical question that a future ebMS3/AS4 adopters will ask, especially when they are already used to the ebMS2 messaging choreography.   In ebMS2 an ebBP receipt can be sent back asynchronously to report the success/failure of the business document validation. So I would like to know how it is considered to integrate ebMS3/AS4 with ebBP (as I know the current version is 2.0.4, which was announced in 2006, before ebMS3.0 was finalized)? Or what's the best practice regarding to this matter?   Thanks, Rong