Groups - Event "ebMS TC meeting" modified

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:20130524T000000Z
DTSTART;VALUE=DATE-TIME;TZID=America/Los_Angeles:20130529T120000
DTEND;VALUE=DATE-TIME;TZID=America/Los_Angeles:20130529T130000
SEQUENCE:1
SUMMARY:ebMS TC meeting
LOCATION:WebEx dial in
DESCRIPTION:\n	Additional TC meetings to go over Jira issues\n\n	 \n\n	
  \n\n	Topic: ebMS TC meeting \n\n	Date: Every 2 weeks on
  Wednesday\, from Wednesday\, May 29\, 2013 to Wednesday\,
  July 24\, 2013 \n\n	Time: 12:00 pm\, Pacific Daylight Time
  (San Francisco\, GMT-07:00) \n\n	Meeting Number: 203 842 277
  \n\n	Password: as4 \n\n	Host Key: 178523\n\n	
  \n\n	-------------------------------------------------------
  \n\n	To join the meeting online(Now from mobile devices!)
  \n\n	-------------------------------------------------------
  \n\n	1. Go to
  https://ciscosales.webex.com/ciscosales/j.php?ED=227372142&UID=481888762&PW=NNTRhM2EyMTEw&RT=MiM0
  \n\n	2. If requested\, enter your name and email address.
  \n\n	3. If a password is required\, enter the meeting
  password: as4 \n\n	4. Click &quot\;Join&quot\;. \n\n	5. If
  the meeting includes a teleconference\, follow the
  instructions that appear on your screen. \n\n	
  \n\n	-------------------------------------------------------
  \n\n	To join the audio conference only
  \n\n	-------------------------------------------------------
  \n\n	To receive a call back\, provide your phone number when
  you join the meeting\, or call the number below and enter
  the access code. \n\n	Call-in toll-free number (US/Canada):
  +1-866-432-9903 \n\n	Call-in toll number (US/Canada):
  +1-408-525-6800 \n\n	Toll-free dialing restrictions:
  http://www.webex.com/pdf/tollfree_restrictions.pdf \n\n	
  \n\n	Access code:203 842 277 \n\nAgenda: \n	 \n\n	EBXMLMSG-5
  3.2 Reception Awareness feature\, retries\n\n	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. \n\n	See discussion in thread starting with
  https://lists.oasis-open.org/archives/ebxml-msg/201301/msg00015.html.
  \n\n	----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------\n\n	EBXMLMSG-6
  3.2 Reception awareness\, validation of receipts\n\n	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 \n\n	See
  thread starting at
  https://lists.oasis-open.org/archives/ebxml-msg/201301/msg00016.html.\n\n	----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------\n\n	EBSMLMSG-16
  AS4 Section 5.1.8 Generating Receipts Profiling Rule (a)
  interpretation\n\n	Section 5.1.8 Generating Receipts
  Profiling Rule (a) of the AS4 spec reads as follows \n\n	
  \n\n	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.
  \n\n	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 \n\n	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.
  \n\n	or \n\n	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. \n\n	 \n\n	 \nGroup: OASIS ebXML Messaging Services
  TC\nCreator: Makesh Rao
URL:https://www.oasis-open.org/apps/org/workgroup/ebxml-msg/event.php?event_id=35610
UID:https://www.oasis-open.org/apps/org/workgroup/ebxml-msg/event.php?event_id=35610
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT00H15M00S
END:VALARM
END:VEVENT
END:VCALENDAR