Groups - Event "Bi Weekly 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:20130410T000000Z
DTSTART;VALUE=DATE-TIME;TZID=America/Los_Angeles:20130522T093000
DTEND;VALUE=DATE-TIME;TZID=America/Los_Angeles:20130522T103000
SEQUENCE:104
SUMMARY:Bi Weekly TC meeting
DESCRIPTION:\n	Bi-weekly TC meeting. Agenda will be decided and
  published before the meetings.\n\n	 \n\n	 \n\n	 \n\n	
  \n\n	-------------------------------------------------------
  \n\n	 \n\n	Topic: Bi-Weekly ebms TC meeting \n\n	Date: Every
  2 weeks on Wednesday\, from Wednesday\, February 27\, 2013
  to Wednesday\, December 18\, 2013 \n\n	Time: 9:30 am\,
  Pacific Standard Time (San Francisco\, GMT-08:00)
  \n\n	Meeting Number: 204 744 318 \n\n	Password: 123
  \n\n	Host Key: 870819 (use this to reclaim host
  privileges)\n\n	
  \n\n	-------------------------------------------------------
  \n\n	To join the meeting online(Now from mobile devices!)
  \n\n	-------------------------------------------------------
  \n\n	1. Go to
  https://cisco.webex.com/ciscosales/j.php?ED=218232647&UID=481888762&PW=NZDM4N2I2NzFl&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: 123 \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:204 744 318 \n\n	 \n\n	 \n\n	 \n\n	
  \n\n	CCP:+14085256800x204744318# \n\n	 \n\n	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. \n\n	....................Stop copying here
  ...................\n\nAgenda: \n	Jira Issues to be
  discussed:\n\n	EBXMLMSG-05 - AS4 Section 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-06 : AS4 Section 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	EBXMLMSG-09 : AS4\, Core Spec - Receipt format for
  reception awareness\n\n	 \n\n	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. \n\n	&lt\;xsd:complexType
  name=&quot\;Receipt&quot\;&gt\; \n\n	&lt\;xsd:sequence&gt\;
  \n\n	&lt\;xsd:any processContents=&quot\;lax&quot\;
  maxOccurs=&quot\;unbounded&quot\;/&gt\;
  \n\n	&lt\;/xsd:sequence&gt\; \n\n	&lt\;/xsd:complexType&gt\;
  \n\n	 \n\n	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.
  \n\n	&lt\;xsd:complexType name=&quot\;Receipt&quot\;&gt\;
  \n\n	&lt\;xsd:sequence&gt\; \n\n	&lt\;xsd:any
  namespace=&quot\;##other&quot\;
  processContents=&quot\;lax&quot\;
  maxOccurs=&quot\;unbounded&quot\;/&gt\;
  \n\n	&lt\;/xsd:sequence&gt\; \n\n	&lt\;/xsd:complexType&gt\;
  \nGroup: OASIS ebXML Messaging Services TC\nCreator: Makesh
  Rao
URL:https://www.oasis-open.org/apps/org/workgroup/ebxml-msg/event.php?event_id=34680
UID:https://www.oasis-open.org/apps/org/workgroup/ebxml-msg/event.php?event_id=34680
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT00H15M00S
END:VALARM
END:VEVENT
END:VCALENDAR