ebBP Teleconference Call 11 April 2006 Present: Green Moberg Nagahashi Schlegel St. Amand Webber Martin Regrets: None Quorum achieved. Agenda: 1. Approval of minutes 28 March and 4 April 2006. Approved. No objections. 2. Committee Specification update: URLs resolved and documents under revision See: http://www.oasis-open.org/apps/org/workgroup/ebxml-bp/email/archives/200604/msg00009.html Also see [1] for corrections. Martin: Reached agreement with OASIS. The documents were generated and uploaded today. See [1]. Please review as manual changes had to be made to what MS Word and XMLSpy generate: a. Titles b. Schema location and relevant paths (hrefs, for example). c. Also found we need to make an update to WS-Addressing and WSDL v2.0. Moberg/Green: These are editorial and can be done in the process to ready the documents. Action: Martin/Make revisions as specified in a.-c. once Green and Moberg review the documents as uploaded. Status: Complete as of 11 April 2006. See [1]. 3. ebBP IIC profile: Comments from team. (Open-Martin integration of comments from last meeting as found in Meeting Minutes, 4 April 2006). Martin: Changes are still underway but the document is not yet ready. Are there other comments? Moberg: How do these profiles relate to the registry? Martin: Registry profiles are normative, specific (more granular) and targeted to developers. The ebXML IIC templates for each specification are focused on deployment and more general purpose. Registry team has asked about an ebBP profile. Moberg: Need to have some relationship between the two. Should raise this comment to the ebxml-jc - how do we explain to users the connection? Schlegel: There is a relationship between UBL, ebBP, CPPA, and registry. Martin: As indicated, the Registry profiles are normative functionality and targeted. Moberg: Need to investigate alignment of the templates and profiles. Alignment is needed to encourage end users to make decisions to develop ebBP. Martin: This can be used to develop a profile that allows managing and discovering ebBP artifacts. Moberg: Correlate options with search criteria. As we get more interested in alignment of registry with deployment considerations, this becomes particularly relevant. Martin: This is similar to the discussion in registry where we asked for use cases so consumers can understand for what the associations, slots, classifications, etc. are used. Action: Martin/Send information to ebxml-jc, and Registry chair and lead. Status: Done 11 April 2006. Schlegel: One standard interface is perceived by an ebXML Registry profile rather than a user guide like ebXML IIC. Moberg: Are the queries useful to end users - this is an alignment question? Schlegel: I am working on an CPPA Registry profile. There is one for ebBP needed as well. It is a natural next-step. Moberg: This is also important for visibility functions for ebSOA group. UN/CEFACT has categories of systems for search and discovery. Martin: An .xsd version is planned to make it easier to do this (for ebXML IIC templates). Team: General agreement that an ebBP profile for Registry should be pursued after we get to OASIS Standard. 4. Other business a. OASIS Symposium presentation: Under development. Martin: Defer this week as the slides are not ready. b. Benefits of ebXML, Webber (Reference request from Mike Rawlins) Webber: Revamped my previous document (2005). Najmi is also planning to provide information to Rawlins. What about ebBP? Deadline is 21 April 2006. Martin: Should this be put in a positive and professional vernacular? Webber: Yes. Martin: Could we use the FAQ to develop an answer for ebBP? St. Amand: Need more information to say either way. Webber: Add spec progress, adoption and user community involvement. Martin: I will send the ebxml-jc summary and ask if this starts to do what is needed to send to Rawlins. Action: Martin/Send ebxml-jc draft summary to ebBP list to look at ebBP section. Status: Done 11 April 2006. Webber: Need to tout the new ground-breaking capabilities in ebBP such as ability to drive context. People need to be aware of the opportunity. Martin: Will start with summary and post to the team. Webber: There has been problems with funding for agencies. Now and 2008, with QuickSilver for governments, they wish to save $20 billion to get rid of paper processing. Some feel eGovernment is a failure. We need to start to identify with such information to continue to encourage user communities interested in ebBP. [1] Email sent 11 April 2006 and updates made (cut-paste typo): Spec (.doc): http://www.oasis-open.org/apps/org/workgroup/ebxml-bp/download.php/17637/ebxmlbp-v2.0.3-Spec-cd-en.zip (public: http://www.oasis-open.org/committees/download.php/17637/ebxmlbp-v2.0.3-Spec-cd-en.zip) Spec (.pdf): http://www.oasis-open.org/apps/org/workgroup/ebxml-bp/download.php/17638/ebxmlbp-v2.0.3-Spec-cd-en-pdf.zip (public: http://www.oasis-open.org/committees/download.php/17638/ebxmlbp-v2.0.3-Spec-cd-en-pdf) Spec (.html, tech spec): http://www.oasis-open.org/apps/org/workgroup/ebxml-bp/download.php/17639/ebxmlbp-v2.0.3-Spec-cd-en-html.zip (public: http://www.oasis-open.org/committees/download.php/17639/ebxmlbp-v2.0.3-Spec-cd-en-html.zip) Spec (.html, Appendices): http://www.oasis-open.org/apps/org/workgroup/ebxml-bp/download.php/17640/ebxmlbp-v2.0.3-Spec-cd-Appendices-en-html.zip (public: http://www.oasis-open.org/committees/download.php/17640/ebxmlbp-v2.0.3-Spec-cd-Appendices-en-html.zip) Schema (.xsd): http://www.oasis-open.org/apps/org/workgroup/ebxml-bp/download.php/17641/ebxmlbp-v2.0.3-Schema-cd-en.zip (public: http://www.oasis-open.org/committees/download.php/17641/ebxmlbp-v2.0.3-Schema-cd-en.zip) SignalSchema (.xsd): http://www.oasis-open.org/apps/org/workgroup/ebxml-bp/download.php/17642/ebxmlbp-v2.0.3-SignalSchema-cd-en.zip (public: http://www.oasis-open.org/committees/download.php/17642/ebxmlbp-v2.0.3-SignalSchema-cd-en.zip) Document (Schema): http://www.oasis-open.org/apps/org/workgroup/ebxml-bp/download.php/17643/ebxmlbp-v2.0.3-Document-cd-Schema-en.zip (public: http://www.oasis-open.org/committees/download.php/17643/ebxmlbp-v2.0.3-Document-cd-Schema-en.zip) Document (SignalSchema): http://www.oasis-open.org/apps/org/workgroup/ebxml-bp/download.php/17644/ebxmlbp-v2.0.3-Document-cd-SignalSchema-en.zip (public: http://www.oasis-open.org/committees/download.php/17644/ebxmlbp-v2.0.3-Document-cd-SignalSchema-en.zip) Document (Supplements): http://www.oasis-open.org/apps/org/workgroup/ebxml-bp/download.php/17645/ebxmlbp-v2.0.3-Document-cd-Supplements-en.zip (public: http://www.oasis-open.org/committees/download.php/17645/ebxmlbp-v2.0.3-Document-cd-Supplements-en.zip)