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: ebXML JC Teleconference 30 March 2005

First, accept my apologies on this cross-posting as the ebxml-jc site 
needs some access and other updates. Therefore, this posting to all the 
related TCs must be explicit. Those parties interested in ebxml-jc 
should read this message. Thank you.

Reminder ebxml-jc call 30 March 2005
Teleoconference call

Time     Wednesday, 30 March 2005, 07:30am to 08:30am PT
Description     Toll-free (US): 1-877-330-9868, hit ** and when prompted 
Toll-paid: 909-472-3386, enter 877-330-9868 when prompted. Refer to 
Toll-free instructions above to complete.

Meeting Minutes, 16 March 2005 (attached)

Tentative Agenda
1. Update on status summary.
Working summary (attached)

2. Update on technical white paper outline.
a. Do we wish to consider a business scenario to show how the 
specifications may be used together?
b. CC and architecture overview

Working outline updated 29 March 2005 (attached)

3. OASIS Symposium - Lightning Round sessions
4. Update on ebBP-CPPA alignment
5. Other business

ebXML White Paper Synopsis (V 0.6)

- the audience is "technical executive", say CTO and IT management, since they are decision makers on 
adopting ebXML. Yet the style should resonate with vertical users with a B2B experience (e.g. EDI).
- also, for those already familiar with ebXML, the paper should give a feel of the future version.
- Each section would average 3-5 pages (overall paper between 30-50 pages, including figures). 
Sections don't have to give an exhaustive view of the material referred to, nor a balanced summary,
but should convey the rationale behind it, and may focus on a few remarkable features.
Each section could include a short FAQ at the end.
- The outline below is rather classic, in breaking down by component. It could be different: describe
first the ISO version, then separately the future version (But the latter is too unstable today to deserve
a full section.) Or, could downplay the components and focus more on the integrated view, how everything
works together, giving away features details while unwinding scenarios & use cases. I though it would 
be sufficient to have Section 1 do a bit of this binding-it-all-together job.
- we could involve marketing team to do Section #9.

1. ebXML: the Requirements, the Approach 

- short definition: an ISO standard for Exchanging business messages, Conducting trading relationships,
Defining and registering business processes, Communicating data in common terms, Assembling business transactions.

- the business case (EDI-compatible in both content and architecture, accessible to SMEs, non-managed env., 
covering all partners of a supply chain, XML-based)

- (can reuse the EDI / ebXML stack comparison from Jon Bosak)

- an integrated approach of B2B focusing on interoperability needs, yet loose coupling with back-end systems.
eBusiness transactions can be of very different nature.  
Some transactions can be characterized as  "service calls" , others as "document transfer".
An inquiry for catalog information or a status request are usually queries of modest size and stable structure for which a fast response 
is expected, and which can be repeated without trouble if needed.  Such cases fall in the "service call" style.
But many other transactions consist of the exchange of sizeable business documents in very different formats (XML or not), 
and which will be consumed by back-end processes in an asynchronous manner. ebXML Messaging supports these two styles of tansactions,
and in particular the exchange of business documents.

There may be many such business documents of different types between business partners for a domain of application. 
These documents may be complex and likely to evolve via a versioning process over time. The processing of such documents usually requires 
a decoupling with the messaging layer. The consumer of these documents may not be directly a “service” known in advance, but instead a 
business process instance that needs this document at some point in its life cycle, or an application that will consume a batch of these 
at the end of every day, or yet a dispatching system that will forward or queue messages based on content.
Such documents cannot be directly associated with an application service in a predefined way. The coupling between the messaging system
and the consumers of these messages (a business process, an application) must be loose. 

The concept of a message as a “business document” envelope has also given the “message” a certain almost legal status at the end-user level,
 as being a part of a business transaction.  During the processing of a particular message, some actions may be taken that have 
significant business value and yet are independent from the back office application, such as logging for keeping a trace as
 legal evidence of business,  authorization, generation of a confirmation of receipt. 
Although some of these processing  steps may be handled by messaging  intermediaries
 (like in the SOAP processing model), others will depend on the business payload content. 
These functions will need to be performed before the message reaches its final destination - requiring even more decoupling with the
 consuming application or “service”.
The ebXML model is aligned with this perspective of a message being a business item, which must allow for various ways of coupling
with the consumer of this business item.
The resulting architecture is of a clear separation between the messaging layer and the business process layer, with options for
integration in form of bindings.

- transitioning to ebXML (migration path)
- anatomy of an ebXML deployment (showing architecture, the interaction steps in usage scenarios)

2. ebXML Messaging

2.1 - Messaging Overview
- Requirements and design principles, (SOAP on pervasive Internet transports, reliability and security, 
smooth EDI transition, etc.) 

2.2 Status of ebXML Messaging Standards
  - ebMS v2.0 OASIS Standard
  - ebMS v3.0 Effort

2.3 Current Features
    - Feature Set
    -  Relationship to other standards and specifications

2.4 Future Plans
    -  Overview
    -  Feature Set (overview)
    -  Relationship to other specifications and standards

. leveraging Web services protocols for security, reliability.
. support for low-level payload processing (payload services)
. support for various message exchange patterns that map to business transactions.
. support for connectivity constraints (occasional connectivity, firewall restrictions, light ebMS clients)

2.5 Business scenario example
2.6 References and materials

3. ebXML BPSS - Business Transactions and Collaborations

3.1  ebBP Overview
     - Business Collaboration
     - Design principles

    * What it is and how does it relate to ebXML BPSS: Standard language
      for business collaboration
          o Supporting process design and description
          o Enabling collaboration monitoring and validation
          o Guiding execution
    * Design principles based on business semantics: [1]
          o Standard business transaction patterns
          o State alignment
          o Binary and multi-party collaboration
          o Composition: Visibility and relationships
          o Enabling web services (abstract)
          o Party and role definitions
          o Enabling the process lifecycle

3.2  Status of ebXML BPSS Standard
     - ebBP v2.0 pre-Committee Draft

3.3  Current Features
     - Features Overview
     = Relationship to other standards and specifications

Relationship to ebMS and CPPA
 a. Opportunities and challenges
 b. Conformance testing in the future (link to IIC work)

3.4  Future Plans
	- Release of v2.0 
  	- Business requirements identified
3.5	Use cases for ebBP

 Telecommunications (M. Roberts)
 Financial services (M. Arrott)
 Automotive (Moberg)
 Retail (Yunker)

3.6	References and related materials

4. Collaboration Protocol Agreements

4.1 CPP/CPPA Overview
    - What is ebXML CPPA?
    - Business needs and requirements

4.2 Status of ebXML CPP/CPA Standard
    - CPP/CPA v2.0 OASIS Standard
    - CPP/CPA v2.1 errata

4.3 Current Features
   - Technical capabilities
   - Configuring public shared protocols
   - Enabling collaboration monitoring
   - Relationship to other standards and specifications

4.4 Future Plans
   - Current errata (v2.1)
   - Protocol profile negotiation 
   - Relationship with ebMS and ebBP
   - Future versions

4.5 Use cases for ebXML CPP/CPA
   - Deployment scenario

4.6 References and related materials

5. The Registry-Repository

5.1 ebXML Registry and Repository Overview
    - Business requirements
    - Design principles

  (requirements & design principles, summary of salient features, use case, relationship with other ebXML parts)
  Design principles and focus areas

5.2 Status of ebXML Registry Services (RS) and Registry Information Model (RIM) Standards
    - ebRS and ebRIM v2.0 OASIS Standards
    - ebRS and ebRIM v3.0 Committee Drafts

5.3 Current Features
    - Feature Overview
    - Relationship to other standards and specifications

  Enhanced or new v3.0 features
  * HTTP bindings
  * Registry Managed Version Control
  * Query enhancements
  * Content Management Services
  * Federated Registry
  * Access control and authorization based on the XACML 1.0 standard
  * Content based Event Notification
  * Federated Identity Management support using SAML 2.0 Single Sign On (SSO)
  * Alignment with recent standards and specifications including web services
  * Extensiblity of registry protocol where new types of requests and responses may be defined easily

5.4 Future Plans
    - Moving ebRS and ebRIM v3.0 to OASIS Standards
    - Future business requirements identified

5.5 Use cases for ebRS and ebRIM

5.6 References and related materials

6. Standardizing Content
   - Core components

6.1 Overview
    - Definition
    - Responsible organization
    - Relationship to other specifications

6.2 Examples of business document specifications used with ebXML
    - OASIS Business Object Documents (BoDs)
    - Universal Business Language (UBL)
    - Relationship to ebXML Core Components (overview)

7. Testing ebXML

7.1 ebXML IIC Overview
    - Design principles
        Testing approach
    - Conformance and interoperability framework
    - Conformance and interoperability testing

7.2 Status of ebXML IIC Test Framework Standards
    - v1.1 ebXML IIC Test Framework Committee Draft
    - Deployment Template
    - Other framework artifacts from ebXML IIC

7.3 Current Features
    - Conformance testing
    - Interoperability profiles

    - Interoperablity testing and badging

. status in US, with UCC/DGI (for ebMS)
. status in Asia, (ECOM / ebXML Asia)
. status in Europe (CEN/ISSS, ETSI).

    - Testing environment

- Challenges of testing B2B interoperability.
- The IIC approach (conformance + interoperability, standard scripting of test suites, automation,...)

7.4 Future Plans

7.5 Use Cases for ebXML IIC Test Framework

Note: May want to move status and operational details in Section 7.3 to this section.

7.6 References and related materials

8. Deploying ebXML in a SOA environment
- Relationship to other standards
- where ebXML fits in (example arch from GM)
- pilot projects (AIAG...)

9. Who deploys ebXML 
- survey 
- what do people do with ebXML, value they see.

Summary (sent 15 March 2005)
Question: On future update, add CC, architecture.
Question: On future update, do we add adoption indicators.

Summary of specification progress within OASIS:
JC reference (original draft): http://www.oasis-open.org/apps/org/workgroup/ebxml-jc/email/archives/200502/msg00012.html

Slightly updated:

   * ebMS: v3.0 (in work, draft)
         o Draft in work. F2F held in January 2005, however progress
           has been slower than anticipated with a small group.
           Although progress has been slow, key changes are in work
           such as integration with WS-Reliability, payload services,
           security improvements, WS-I BP conformance, at a minimum.
         o Working document reference:
           (February 2005)
         o Status: May meet at OASIS symposium. No projected date for
           v3.0 Committee Draft status.
   * ebReg/Rep v3.0 (Committee Specifications approved, 15 March 2005)
         o v3.0 RIM and RS achieved Committee Draft in February 2005 and concluded public review 14 March 2005.
           The ebXML RIM and RS Committee Specifications were approved 15 March 2005, which lays the groundwork
           to move to OASIS standard.
         o Significant improvements have been made including SAML
           support, WS-I BP compliance, event notification, content
           management capabilities, etc.
         o Specification references:
         o FAQ summary: http://www.ebxml.org/ebusinessxmlregistry.pdf
         o Capabilities summary update:
           http://xml.coverpages.org/ni2005-02-14-a.html (from Cover Pages)
   * ebCPPA v2.1 (in work, draft)
         o Errata v2.1 distributed in draft form in early February
           2005. Work continues slowly on negotiation and alignment
           with ebMS and ebBP specification development in the areas of
           role bindings, transactions, etc. Progress has been made in
           abstracting some of the ebCPPA concepts to enable effective
           use of many underlying protocols such as those for web
           services, AS2, etc.
         o Errata v2.1 reference:
   * ebBP: v2.0 (in work, TC review of pre-Committee Draft started 23 Feb 2005)
         o Package includes schema, XSLT example
           transform for v1.01=>2.0 migration, signals schema and
           example, comments and work item list, glossary. Many
           improvements have been made in state transitions,
           composability (ComplexBTA and OperationMapping), role
           binding and monitoring constructs. In addition, the BT
           patterns have been concretized and extensible patterns
           developed to enable the user community.
	o  A pre-notification was sent to key user
           communities to solicit early comments and investment. Valuable feedback has been received and 
           comments are under review and resolution underway.
         o Specification draft reference:
         o Pre-notification reference:

   * ebXML IIC v1.1 (Committee Draft package)
         o In January 2005, the IIC updated its conformance and
           interoperability packages including the IIC framework and
           achieved v1.1
         o Committee Draft status. This v1.1 update provides many
           improvements, and has also resulted in a freely available
         o from NIST. Improvements include more comprehensive web
           services and ebXML testing support. The team has also been
           working with OASIS on interoperability planning for expanded
           activities within OASIS standardization development and with
           a TAB subteam that is investigating how to rationalize
           conformance criteria (including informal discussions with W3C).
         o NIST open implementation: http://ebxmltesting.nist.gov/.
           Three implementations have been conducted by NIST, Korbit,
           and Drake Certivo.
         o v1.1 IIC Committee Drafts:

ebXML JC Meeting 16 March 2005



1. ebXML adoption initiative - and user community requirements channeling - Status

Link to white paper and status summary (of specification development and adoption proliferation).

Martin: Asked team members to review. 
Jones: Looks good for ebMS.

ACTION: Any updates from Jones for ebMS.
Email inquiry sent 29 March 2005.

Breininger: TC process goes into effect 15 April 2005. Need to know how to handle if in middle of the process using new TC process.
Durand: No changes required.
Moberg: What about CC and architecture? We could mention the transaction types are being used for ebXML - OASIS BoDs and UBL for example.
This relates to ebXML Core Components (UBL is compatible with these).

ACTION: Martin-Query John Hardin and Jamie Clark on this item for architecture.
Email sent 29 March 2005.

Team: Discussion was to integrate CC and architecture overview into the white paper outline and status summary.

Moberg: Received a question from the medical industry - SAML and Registry. Is this a part of ebMS v3.0 or WS-Security with a SAML profile?
This industry appears to be moving data with SAML and Liberty. Passed this information to Najmi for registry.
Still trying to understand if any messaging requirements exist.
Will bring to the JC when more information is available.

2. Update on integration and functional separation between specs - e.g. ebBP and CPPA alignment (Martin)

Martin: ebBP and CPPA working on Action-Service-Context-Role and Operation Mapping.
Moberg: Need editor for negotiation specification.
Martin: Discovery via a registry is another touchpoint. More updates will be provided as work progresses.

3. White paper (Martin): White paper update (brief) sent to list 15 March 2005. Work with ebSOA.

Martin: Still open for messaging.
Durand: This doesn't need to be well-polished but visible information about the specifications, adoption and use.
In flux right now with ebMS v3.0.
Martin: Should we take this in the context of a business scenario?
Moberg: Online and downloadable.
Martin: Discuss in more substance next time.

4. Other business
a. Continue ebSOA-JC collaboration.
Breininger: Need to invite John Hardin to attend from ebSOA and then approve.
Durand: Yes, that is the process.

Action: Provide invitation to Hardin. Then we can approve his participation.
Email sent and invitation accepted 29 March 2005.

b. Other items: OASIS symposium: Status updates.

Martin and Moberg will not; Jones has no commitment. Not sure where ebMS TC is going and may have F2F shortly
thereafter.  Durand and Breininger will attend. ebBP and IIC hoped to discuss ebBP test assertions.

Use of IIC framework
Durand: NIST implementation is available (test driver): ebxmltesting.nist.gov
Interest from Oracle, RosettaNet (MMS project), and Sonic in using this (uncertain with what transport).
ebXML Asia interested in using test framework for conformance testing (using NIST test driver).

Breininger: Ended public review period for Reg/Rep. Seven minor comments received and resolved.
TC approved all the comment resolution, the specifications are Committee Drafts and promotion to OASIS Standard
candidates. Compiling and sent submission package.
Distribute to OASIS membership for two weeks 1 April and then seek vote.
May be approved by 30 April 2005 (projected).

Durand: Info for white paper and status summary

Advise on what the correct questions are.

Doesn't write properly into Outlook.
Kavi calendar notice, vCalendar request.
Query Scott McGrath
Send notice re: concern.

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