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,"
==========
Minutes:
==========
Attendance: