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:20130508T093000
DTEND;VALUE=DATE-TIME;TZID=America/Los_Angeles:20130508T103000
SEQUENCE:85
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-04: Core Spec -  Error Reporting\,
  SOAP Faults - Finalize discussion\n\n	 \n\n	Section 6.6
  describe the use of SOAP Faults with &quot\;failure&quot\;
  errors in a way that may not be compatible with the example
  in section 5.5. \n\n	See discussion on
  https://lists.oasis-open.org/archives/ebxml-msg/201301/msg00020.html.
  \n\n	 \n\n	EBXMLMSG-07: Core Spec Section 5.2.2.4 - Party
  Id\, error of severity &quot\;error&quot\;\n\n	 \n\n	Section
  talks about an error with severity &quot\;error&quot\;\, but
  according to section 6.2.5 this should be severity
  &quot\;failure&quot\;. \n\n	This happens also in other
  places.\n\n	 \n\n	EBXMLMSG-08: Core Spec Section 6.2.9 -XSD
  Type for error detail element\n\n	 \n\n	Section 6.2.9 of the
  core spec explains the usage of the
  //eb:Error/eb:ErrorDetail element as: &quot\;provides
  additional details about the context in which the error
  occurred. For example\, it may be an exception trace&quot\;.
  \n\n	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 &quot\;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&quot\; (quoted text
  taken from XML Schema spec). \n\n	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. \nGroup: OASIS ebXML Messaging Services
  TC\nCreator: Makesh Rao
URL:https://www.oasis-open.org/apps/org/workgroup/ebxml-msg/event.php?event_id=34679
UID:https://www.oasis-open.org/apps/org/workgroup/ebxml-msg/event.php?event_id=34679
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT00H15M00S
END:VALARM
END:VEVENT
END:VCALENDAR