OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-msg message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Groups - Event "Bi Weekly TC meeting" modified


Event Title: Bi Weekly TC meeting

Date: Wednesday, 24 April 2013, 09:30am to 10:30am PDT
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

Here are the Jira issues we will try to address:

EMXMLMSG01: Corrections in Profile

 

1. In-line citations: In-line citations such as [ebMS3-CP] aren't linked back to the entry in the References section. 

Most specs link these types of references. They are sometimes bolded, sometimes not and thought that inconsistency might confuse some readers. 

- Need to link back and have consistent font representations. 

2. There are a number of broken links in the spec document. Many of these turn out to be links to faux URLs on the OASIS website (e.g. 

http://www.oasis-open.org/committees/ebxml-msg/push) or to docs.oasis-open.org (e.g. 

http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/ns/core/200704/responder)

The narrative explains that these are only meant to be identifiers, not links, however they are coded as live links in the document. They are broken links in the document and may give readers an incorrect expectation about what they can find on the web site. 

- Correct the broken links or make them as identifiers and not links 

3. We also noted some links where the URL appears in black but the link is indeed intended to be live, e.g.: 

 4.3 Processing Mode Parameter being present with the value http://www.w3.org/2003/05/soap-envelope/role/ultimateReceiver

 

EBXMLMSG02: ebMS Core Schema correction - Quickly Revisit

 

1) the type of eb:Property is of type Property, an extension of non-empty-string; the ebMS3 schema does not reference xs:anySimpleType. 

2) the @type attribute is missing from the XML Schema at http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/core/ebms-header-3_0-200704.xsd

The type attribute is useful so my preference would be to add it back to the schema.

 

This section of EBMS3CORE states the following about eb:Property: 

An eb:Property element is of xs:anySimpleType (e.g. string, URI) and has two attributes: 

• @name: The value of this REQUIRED attribute must be agreed upon between partners. 

• @type: This OPTIONAL attribute allows for resolution of conflicts between properties with the same name, and may also help with Property grouping, e.g. various elements of an address. 

 

EBXMLMSG03: (Sec 5.8 of AS4) Correction of statement for Receipt generation

 

For Section 5.1.8, although the statement in the feature table 2.1.1: 

"...Use of the ebbpsig:NonRepudiationInformation element (as defined in [ebBP-SIG]) is REQUIRED as content for the eb:Receipt message," 

 



Owner: Makesh Rao
Group: OASIS ebXML Messaging Services TC
Sharing: This event is not shared to any other groups.
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:20130424T093000
DTEND;VALUE=DATE-TIME;TZID=America/Los_Angeles:20130424T103000
SEQUENCE:65
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	Here are the Jira issues
  we will try to address:\n\n	EMXMLMSG01: Corrections in
  Profile\n\n	 \n\n	1. In-line citations: In-line citations
  such as [ebMS3-CP] aren&#39\;t linked back to the entry in
  the References section. \n\n	Most specs link these types of
  references. They are sometimes bolded\, sometimes not and
  thought that inconsistency might confuse some readers.
  \n\n	- Need to link back and have consistent font
  representations. \n\n	2. There are a number of broken links
  in the spec document. Many of these turn out to be links to
  faux URLs on the OASIS website (e.g.
  \n\n	http://www.oasis-open.org/committees/ebxml-msg/push) or
  to docs.oasis-open.org (e.g.
  \n\n	http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/ns/core/200704/responder).
  \n\n	The narrative explains that these are only meant to be
  identifiers\, not links\, however they are coded as live
  links in the document. They are broken links in the document
  and may give readers an incorrect expectation about what
  they can find on the web site. \n\n	- Correct the broken
  links or make them as identifiers and not links \n\n	3. We
  also noted some links where the URL appears in black but the
  link is indeed intended to be live\, e.g.: \n\n	 4.3
  Processing Mode Parameter being present with the value
  http://www.w3.org/2003/05/soap-envelope/role/ultimateReceiver\n\n	
  \n\n	EBXMLMSG02: ebMS Core Schema correction - Quickly
  Revisit\n\n	 \n\n	1) the type of eb:Property is of type
  Property\, an extension of non-empty-string\; the ebMS3
  schema does not reference xs:anySimpleType. \n\n	2) the
  @type attribute is missing from the XML Schema at
  http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/core/ebms-header-3_0-200704.xsd\n\n	The
  type attribute is useful so my preference would be to add it
  back to the schema.\n\n	 \n\n	This section of EBMS3CORE
  states the following about eb:Property: \n\n	An eb:Property
  element is of xs:anySimpleType (e.g. string\, URI) and has
  two attributes: \n\n	&bull\; @name: The value of this
  REQUIRED attribute must be agreed upon between partners.
  \n\n	&bull\; @type: This OPTIONAL attribute allows for
  resolution of conflicts between properties with the same
  name\, and may also help with Property grouping\, e.g.
  various elements of an address. \n\n	 \n\n	EBXMLMSG03: (Sec
  5.8 of AS4) Correction of statement for Receipt
  generation\n\n	 \n\n	For Section 5.1.8\, although the
  statement in the feature table 2.1.1: \n\n	&quot\;...Use of
  the ebbpsig:NonRepudiationInformation element (as defined in
  [ebBP-SIG]) is REQUIRED as content for the eb:Receipt
  message\,&quot\; \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=34678
UID:https://www.oasis-open.org/apps/org/workgroup/ebxml-msg/event.php?event_id=34678
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT00H15M00S
END:VALARM
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:20130221T000000Z
DTSTART;VALUE=DATE-TIME;TZID=America/Los_Angeles:20130313T093000
DTEND;VALUE=DATE-TIME;TZID=America/Los_Angeles:20130313T103000
SEQUENCE:67
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\nGroup: OASIS ebXML Messaging Services
  TC\nCreator: Makesh Rao
URL:https://www.oasis-open.org/apps/org/workgroup/ebxml-msg/event.php?event_id=34675
UID:https://www.oasis-open.org/apps/org/workgroup/ebxml-msg/event.php?event_id=34675
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT00H15M00S
END:VALARM
RRULE:FREQ=WEEKLY;INTERVAL=2;COUNT=21
EXDATE;VALUE=DATE-TIME;TZID=America/Los_Angeles:20130424T093000
EXDATE;VALUE=DATE-TIME;TZID=America/Los_Angeles:20130424T093000
END:VEVENT
END:VCALENDAR


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]