ebXML Day at XML DevCon 2001
Date: Thu, 08 Feb 2001 18:07:02 -0800 From: Ken North <ken_north@compuserve.com> To: xml-dev@lists.xml.org Subject: [ANN] Free ebXML classes on April 9 (XML DevCon 2001, New York City)
Persons wishing to attend free ebXML Day classes can pre-register for a Special Events Pass to XML DevCon Spring 2001. Browse to the conference web site and click on the Registration tab: www.xmldevcon2001.com/NY/. ebXML Day at XML DevCon 2001 (New York City, April 9) ebXML Day on April 9, 2001 in New York City will educate developers about three new important specifications produced by the ebXML initiative. ebXML is a partnership between the United Nations, the Organization for the Advancement of Structured Information Standards (OASIS), and over 100 member organizations. Its purpose is to develop specifications and standards for a global eBusiness infrastructure. ebXML Day includes three classes scheduled concurrently with XML DevCon Spring 2001 at the New York Marriott Marquis Hotel. The class schedule is: 2:00-3:00 pm ebXML Registry & Repository 3:00-4:00 pm B2B Integration with Electronic Trading Partner Agreements 4:00-5:00 pm ebXML Message Service 1. ebXML Message Service Presented by: Dick Brooks, Group 8760 This session will provide an in-depth overview of the ebXML Message Service. We will explore the details of the MIME multipart/related packaging solution, the ebXML Header document and its relationship to required behaviors of a compliant ebXML Message Service implementation. We will also explore the business quality messaging characteristics of the ebXML Message Service; reliable delivery and security. 2. ebXML Registry & Repository Presented by: Farukh Najmi, Sun Microsystems The ebXML Registry Specification defines a robust information model for business registries as well as a specification of the interface and behavior of ebXML compliant registries. This paper will introduce the audience to the ebXML Registry specifications and share the experience gained from implementing an ebXML Registry. 3. Business to Business Integration with Electronic Trading Partner Agreements Presented by: Dr. Martin Sachs, T. J. Watson Research Center, IBM In business-to-business interactions spanning electronic commerce, supply-chain management, and other applications, the terms and conditions describing the interactions between businesses can be expressed as a contract known as a Trading Partner Agreement (TPA). The TPA includes both business terms and conditions and the Information Technology specifications for exchanging information electronically. An ebXML team is defining a standardized electronic language or Collaboration Protocol Agreement (CPA) that describes the IT specifications. A single business can describe its IT capabilities in a Collaboration Protocol Profile (CPP). Two parties' CPPs can be composed into a CPA that expresses their common capabilities. From the CPA, configuration information and code that embodies the IT specifications can be generated automatically at each trading-partner's site, thus assuring that the two parties are compatibly configured to do electronic business. The CPA expresses the rules of interaction between the parties to the CPA while maintaining complete independence of the internal processes at each party from the other parties. It represents a long-running conversation that comprises a single unit of business. This talk summarizes the needs of inter-business electronic interactions. Then it describes the basic principles of electronic CPPs and CPAs, followed by a discussion of the proposed CPP-CPA language. A conceptual run-time system called the business protocol framework (BPF) provides various tools and run-time services that support CPA-based interaction and integration with business applications. The talk concludes with a brief description of composing a CPA following a party discovery process such as might be used with information in an ebXML, UDDI, or similar repository.
Prepared by Robin Cover for The XML Cover Pages archive. See: "Electronic Business XML Initiative (ebXML)."
