Presentation is loading. Please wait.

Presentation is loading. Please wait.

EBusiness and web services Smorgasbord Open Forum 2003 on Metadata Registries 2:00pm to 3:00pm January 23, 2003.

Similar presentations


Presentation on theme: "EBusiness and web services Smorgasbord Open Forum 2003 on Metadata Registries 2:00pm to 3:00pm January 23, 2003."— Presentation transcript:

1 eBusiness and web services Smorgasbord Open Forum 2003 on Metadata Registries 2:00pm to 3:00pm January 23, 2003

2 Open Forum 2003 on Metadata Registries 2 Presenter  David Webber  co-author of ‘ebXML – the new global standard for doing business via the internet’, New Riders Publishing  Chair of the OASIS CAM TC  Co-chair of OASIS/CEFACT ebXML JMT  Pioneering XML eBusiness drrwebber@acm.org http://drrw.net

3 Open Forum 2003 on Metadata Registries 3 Agenda  Part 1 – web services and ebXML  Transports  Alignment – business process automation  Alignment – common semantic mechanisms  Deployment Coordination  Part 2 – assembly mechanisms  Where can you use this?  Address example  Review of XML mechanisms

4 Open Forum 2003 on Metadata Registries 4 Part1 Web services and ebXML Enabling better eBusiness

5 Open Forum 2003 on Metadata Registries 5 Web service – brief history  Trigger point – weakness of HTML model for e- commerce solutions.  Emergence of XML and SOAP messaging.  Bowstreet early market definition and mission.  Formation of UDDI cartel – to facilitate and exploit automation of e-commerce.

6 Open Forum 2003 on Metadata Registries 6 Acronym Soup  XML – Standard Language for denoting information content and process control  SOAP - (Simple Object Access Protocol) XML based Messaging Protocol  UDDI - (Universal Description, Discovery and Integration) Yellow Pages for Web Services  WSDL - (Web Services Description Language)

7 Open Forum 2003 on Metadata Registries 7 Summary of eBusiness Needs  Ability to easily and cost-effectively connect business processes and business information exchanges together  Enable a broad interoperable electronic marketplace  Interface to existing applications

8 Open Forum 2003 on Metadata Registries 8  Solutions and tools that enable customers to reduce costs and improve efficiency by better exploiting information within their eBusiness domains and industries. eBusiness Technology Goals

9 Open Forum 2003 on Metadata Registries 9 Information Landscape  XML enabled  Pervasive across desktop and enterprise solutions  Ad hoc architecture (desktop components), or using formal architecture (eBusiness integration)

10 Open Forum 2003 on Metadata Registries 10 XML itself is not enough.  XML, by itself, does not solve interoperability problems yet it is an important tool for doing so.  XML does not provide instant semantics.  XML by itself is not the magic bullet.  What we need are clear policies and vision of how electronic information enables interoperability

11 Open Forum 2003 on Metadata Registries 11 CPA Components Architectural Conceptual Components Architectural Conceptual UDDI ebXML Business Layers Logical Implementation Physical } Constraints, Context, & Structure 3 3 4 4 Process BPSS transaction schema instance BODs, MIGs, PIPs Documentation 2 2 1 1 5 5 Business Layers Designing for Flexibility

12 Open Forum 2003 on Metadata Registries 12 Business Layers: Objectives  Reduce complexity of managing large numbers of transaction formats - document the differences  Want to speed adoption by formalizing business rules  Want context-driven transaction generation  Empowers business users to build interchange details  Need to define in a neutral format: works with variety of structures, not just XML.  Augment current standards and industry specifications  Provide multi-step process support – UDDI weak here

13 Open Forum 2003 on Metadata Registries 13 World view models  SMALL - Simple consistent integration for day-to- day small business applications (accounting, taxes, catalogues, inventory…)  BROAD - Simple consistent integration across industry verticals (insurance, healthcare, transportation, food services…)  LARGE - And complex large system integration

14 Open Forum 2003 on Metadata Registries 14 Sample Use Cases  eGov – how do I apply for this service on-line?  Business facilitation – can anyone in the organization provide this answer?  If ‘Yes’ how can my software access it?

15 Open Forum 2003 on Metadata Registries 15 ebXML Vision “A semantic registry is the key foundation block upon which global electronic business exchanges will be built”.

16 Open Forum 2003 on Metadata Registries 16 Why Use a Registry?  Foster a collaborative environment across departments, agencies, industry domains  Provide human facing access to resources – portal  Provide machine level access to business semantics and content

17 Open Forum 2003 on Metadata Registries 17 Registry Layers UML Tools XML Content Metadata Information Registry/Repository Web User Interface Program API Support Business Transaction Generators Dictionary Content Transformation Services Scripting Domains Content Discovery Topics and Packages Dynamic Process Component Enabling Industry Dictionary Business Processes Business Transactions Business Forms HTML forms XML Calls Modelling and Workflow Integration Information Store Tools and services High level modelling systems integration Business Process Definitions Workflow Control Interchange Profiles Communications Layer

18 Open Forum 2003 on Metadata Registries 18 Classifications (Ontology)  All registry objects are classified  Objects can be classified under multiple classifications  Classifications can represent different industries, or product categorizations  Classifications are controlled by the registry owner and completely editable  Upload as a full scheme, or create (or edit) schemes node by node

19 Open Forum 2003 on Metadata Registries 19 UDDI Registry  Yellow, White and Green Pages  Registration of “tModels”  Fixed classification model  Provides discovery for web service POPs and then ability to configure to those  Internal use stronger story than external currently

20 Open Forum 2003 on Metadata Registries 20  Submissions to W3C of SOAP / WSDL  Formation of OASIS TC’s  UDDI moved to OASIS (http://www.oasis-open.org)  Four initiatives on work flow / business process - BPMI, BPSS, BPM, BPEL4WS -> need just one! (aka SMIL for media flows) (see - http://www.ebpml.org)  Re-alignment with ebXML? (http://www.ebXML.org) Move to standards work

21 Open Forum 2003 on Metadata Registries 21  eAI vendors – inward facing focus  The bulk of the (Web services) work for the next 18 months will be inside the firewall, and it will be integration.”  When questioned about the role of WS in exposing legacy data assets, the answer was resoundingly simple “That is not going to happen,” but a more traditional approach will be used. Polarization of Web Services

22 Open Forum 2003 on Metadata Registries 22 Outward facing  e-Commerce Solution vendors  Use their engines to parametrically drive custom web applications.  Use their engines to manage web applications based on profiles.  Empower business managers to create, customize and manage profiles, which drive the generation of unique application instances.  Assign and manage application variations by User IDs, J2EE roles, rules, entitlements or any other data such as time of day.

23 Open Forum 2003 on Metadata Registries 23 Web Service behaviour? “A web service is a software component that represents a business function (or a business service) and can be accessed by another application (a client, a server or another Web service) over public networks using generally available ubiquitous protocols and transports (i. e. SOAP over HTTP).” -Gartner Group

24 Open Forum 2003 on Metadata Registries 24 ebXML and eBusiness architecture Combining best-of-breed components

25 Open Forum 2003 on Metadata Registries 25 Customers focus

26 Open Forum 2003 on Metadata Registries 26 The Emerging Solution: XML Integration Services SHIFT Hub n’ Spoke, EDI and EAI Ad Hoc XML Integration Services 1980’s 1990’s 2002+ SHIFT

27 Open Forum 2003 on Metadata Registries 27 Building eBusiness Orchestration  Define business ideas and needs  Capture steps and workflow  Then describe the business processing  Top layer – rules and context  Middle layer – industry/application integration  Implementation layer – physical application systems and content delivery / exchange

28 Open Forum 2003 on Metadata Registries 28 Technology Progression Matrix Flat files and sortsMainframesModem dial-up connect Tape drives Tree indexed databases Batch EDIebXMLCOBOL programs RDBMS / SQLClient/ServerInternet / HTML forms 4GL report writers Object OrientedReal-time EDIWeb ServicesHub-and-Spoke systems CASE / UMLBusiness ProcessingebXMLETL MetadataMarketplacesPortals and HTML forms EAI XMLPartner discoveryUDDI / ebXMLXML Integration Services

29 Open Forum 2003 on Metadata Registries 29 Enterprise Service Bus (ESB)  Communications layer  ebXML messaging services  Web services  Internet  Business Process workflows and orchestration  Registry services for metadata and discovery  Content integration at point of use  XML payloads with content vocabulary definitions as well as schema structural layouts  Security and Control mechanisms

30 Open Forum 2003 on Metadata Registries 30 Key Capabilities  Link content to/from existing applications  Provide ebXML and web service delivery mechanisms  Common Business Process Orchestration Server  Industry metadata and templates management  Enable marketplaces with partner discovery and cooperation

31 Open Forum 2003 on Metadata Registries 31 ESB Comparisons Ad hocBrokerESB Minimal re-useRestricted re-useRegistry enabled re-use Problematic contextLoss of original contextRetains context with content Hand-coded mappingsDouble mappings -inbound/outboundSingle map at point of use; context implicitly known Highly customizedFixed central vocabularyPluralistic with open crosswalks and formal extension support Biggest dog wins; smaller dogs have to work hardest Restricts industry interoperabilityEnables open industry interoperability Locally developed componentsVendor proprietary technologyOpen standards architecture Published documentationAdaptors and interface specificationsDiscovery of trading partners, interfaces and metadata Plethora of interfacesRigid informationFluid Information

32 Open Forum 2003 on Metadata Registries 32 Web services and ebXML Web ServicesebXML Type Request/responseCollaboration Communication RPC-style synchronous communication between tightly coupled services, Document-style asynchronous communication between loosely coupled services Synchronous, asynchronous communication Business Service Interface description WSDLCPP, CPA (WSDL within CPP, CPA under research) Protocol and Formats SOAP, XMLebXML Message Service (over SOAP), XML, BPSS (as "business" protocol) Content Standards NoneRecommended Standards (e.g. OAGI BODs) How to find business partners UDDI RegistryebXML Registry (UDDI Registry may point to an ebXML Registry or Registry objects (e.g. CPA)) With thanks to Alan Kotok from his recent article : http://www.webservices.org/index.php/article/articleview/451/1/22/http://www.webservices.org/index.php/article/articleview/451/1/22/

33 Open Forum 2003 on Metadata Registries 33 ebXML adoption today  Automotive industry  Food services industry  Energy industry  Vendors delivering ebMS products – Fujitsu, Sybase, Sterling, GXS, bTrade, Cyclone, TIBCO, Excelon, WebMethods, XML Global, and Sun – with UCC certification

34 Open Forum 2003 on Metadata Registries 34 Industry Trends According to the Gartner Group, by 2003, at least 70 percent of all new applications will be built primarily from components Components allow developers the ability to integrate multiple software modules when creating new applications, reducing in-house programming effort, leveraging sophisticated services, and increasing software quality which can significantly reduce the time, cost and effort of integrations projects. "

35 Open Forum 2003 on Metadata Registries 35 Part 2 Assembly Mechanisms Introduction

36 Open Forum 2003 on Metadata Registries 36 Business Challenges for XML  Totally static transaction formats do not work – need configurable structures  How to apply business context assertions to a information structure?  How to derive a consistent way of specifying the interchange parameters to a partner?  How to enable business domain users to implement the exchanges?

37 Open Forum 2003 on Metadata Registries 37  Objective is to provide context to the postal delivery addressing preferred standard for Postal Address, using levels of business use and quality metrics, to ensure adoption of CIQ.  Address use levels  Level 0 = handwritten postal address – machine scanned  Level 1 = last line (city, state, zip+(postal code) or foreign country  Level 2 = in country simple postal address –As Is concatenated  Level 3 = extended postal address – advanced features  Level 4 = rendering only (external to USPS or business to business use, e.g., shipping / delivery address / bill to / marked for / in care of )  Level 5 = management (internal domestic and international collaboration  Resolve XML approach for supporting postal delivery address requirements.  Manage domestic internal and global international artifacts through common vocabulary or mapping conventions Address Problem Space

38 Open Forum 2003 on Metadata Registries 38  Using W3C Schema to provide for business choice and layers of increasingly refining definitions based on business use  Enable use of platform independent business semantic AssemblyDoc, modeling, or spreadsheet methods  Provide for technology dependent implementation transition  Provide migration from legacy address formats  i.e. DOD and most other legacy environments are at Address use level #2  Provide U.S. Government with standards for harmonization by the authoritative agency source with international consortiums Technology

39 Open Forum 2003 on Metadata Registries 39 Address Use Level Defined (US Postal model example)  Level 0 = handwritten postal address – machine parsed  Level 1 = “last line” - city, state, zip+ (postal code) or foreign country  Level 2 = in country simple postal address – concatenated delivery address line(s)  Level 3 = extended postal address – advanced features »3A = Non-address - business volume (bulk) »3B = delivery address field s (atomic)  Level 4 = Rendering only - external or business to business use, e.g., shipping / delivery/bill to/marked for/in care of  Level 5 =management – advanced features »5A = internal management »5B = international management

40 Open Forum 2003 on Metadata Registries 40 Address Horizontal and Vertical Authoritative Source & Use Matrix A = Government (Domestic) B = Vendor C = International Organization D = Customer E = Consortiums D A B, D, E A C & A Top = Authoritative source Bottom = User and Implementers A, B D B, E A, B, C, E A, C, E

41 Open Forum 2003 on Metadata Registries 41 United States Post Office Delivery Quality Measurement Know the delivery was made to the right person / entity10 Know delivered to person / entity9 Know recipient has not reported a move (Move Update)8 Complete and correct address (Delivery Point Validation)7 Matching address to Postal Database (CASS certified address matching software used) {Matching address to external address} 6 Full element identification with some validation and cross validation (City within State) 5 Full element identification with some validation (valid State)4 Full element identification3 Partial element identification (City-State-ZIP)2 Identified lines of address information1 Multiple lines of unspecified address information0 DescriptionScore

42 Open Forum 2003 on Metadata Registries 42 5 Optional Internal Routing Lines - Mailstop Code - Attention Line - Individual Title - Functional Title - Group, Department, Division Name 3 Business Volume “Bulk” - Optional Endorsement Line - Key Line Data - POSTNET Address Block Barcode 3 Mandatory concatenated lines - Name (Person or Organization) - Delivery Address - “Last Line” - City, State, Zip+ (Postal Code) or Country Grouped View of USPS Physical Postal Address 11 Physical Concatenated Lines:

43 Open Forum 2003 on Metadata Registries 43 Multi-Dimensional Postal Address View USPS Delivery Quality Measurement Business Volume “Bulk” Optional Internal Routing Lines Delivery Address “Last Line” OASIS Address Use Levels Composite Fielded City State Zip+ (Postal Code) 0 0 Interpret Process 1 1 3 3 2 2 4 4 5 5 Country 4 3 0 Country sets 1 2 USPS Physical View 6 6

44 Open Forum 2003 on Metadata Registries 44 Building the right pieces  Need to intelligently use XML – get maximum benefit, while avoiding potential pitfalls.  Exploit work that others have done pathfinder for: OAGIS V8 use of Schema techniques; and best-practices on XML use  Align with ebXML architecture to provide syntax neutral methods wherever possible

45 Open Forum 2003 on Metadata Registries 45 Leveraging CIQ  Need to reflect levels 1 thru 5 of use  CIQ formal detail underpins 5 th level.  Use XML schema techniques to layer granularity above that.  Each granular layer also has country specific models.  Use ebXML AssemblyDoc to capture context structure rules and country models.

46 Open Forum 2003 on Metadata Registries 46 XML business information Schema DeliveryAssembly Schema: Content structure definition and simple content typing Content Assembly: Business logic for content structure decisions and explicit rules to enforce content, and interdependencies, with business exchange context, and content definition cross-references via UID associations Secure Authenticated Delivery and Tracking: Reliable Messaging system, envelope format and payload with exchange participant profile controls UID content referencing system ensures consistent definition usage UID Registry/ Dictionary UID – Universal ID content referencing system values – comprise of domain prefix, six digit integer, optional version, sub-version. XML Information Exchange Quality (and long-term consistency)

47 Open Forum 2003 on Metadata Registries 47  Create dual use schema that is capable of support OASIS {1 - 5} levels of use and the set of quality measures with the business choice for increasing detail granularity  Support and harmonize noun dictionaries across multiple legacy implementations and consortium standards by allowing substitution underneath parents  Use of ebXML UID technique to equate like elements in dictionary Syntax Technical Objectives

48 Open Forum 2003 on Metadata Registries 48 Structure Choices Structure Choices Context Values Context Values Required Content Structure Required Content Structure Process Engine Process Engine Content References Content References 1 Payload / Rendering Payload / Rendering 2 AssemblyDoc Structure AssemblyDoc Structure Payload Assembly 3 Application Database Application Database Registry Components Registry Components Conceptual Logical Physical Concept to Runtime Approach Core Components, and Industry Dictionaries Core Components, and Industry Dictionaries Business Information Entities - BIE

49 Open Forum 2003 on Metadata Registries 49 XML techniques summary  We can use W3C Schema to show basic typing and structural permutations for all address content, matching the 5 levels of the business model.  To provide automation of the business logic at-point- of-use requires ebXML and AssemblyDocs to supplement the Schema.  This gives us short-term implementation today, with long-term extensibility and improvement of business value and information quality.

50 Open Forum 2003 on Metadata Registries 50 Which XML Method(s)?  We need business collaboration on elements syntax:  Global complexType definition?  Global element definition?  or define both?  Reuse  Reference global element in external namespace?  Define local element as substitutionGroup of global element (bring into local namespace)?  Define local element using external Namespace complexType (bring into local namespace)?  Derive by extension, local element can have additional sub- elements added to it?

51 Open Forum 2003 on Metadata Registries 51 Postal Address Conclusions  Support Address Use Levels 1 - 5  Support Delivery Quality Metrics  Make use of Schema in near term  Define Postal Address using both Global complexType and Global Element Definitions  Harmonize USPS & ECCMA approach with CIQ (xAL), HR-XML, postal address  Support Dual Resolution (concatenated and detail)  Align defined detailed elements (include mapping to concatenated)  Establish UID-identified elements to support AssemblyDoc mapping to registry  Define code lists to support rendering requirement  Establish legacy environment compatibility (EDI X12 for DOD)

52 Open Forum 2003 on Metadata Registries 52 Assembly Dissection Required Components and Rendering in XML

53 Open Forum 2003 on Metadata Registries 53 Making Assembly Work  A,B,C,D!  Assembly Structure  Business Context Rules  Content Referencing  Data Validations

54 Open Forum 2003 on Metadata Registries 54 Technology Foundation  Simple XML V1.1  XPath  Neutral approach to structure content  Assertion predicates excludeAttribute() excludeElement() excludeTree() makeOptional() makeMandatory() makeRepeatable() setChoice() setId() setLength() setLimit() setMask() setValue() restrictValues() restrictValuesByUID() useAttribute() useChoice() useElement() useTree() useAttributeByID() useChoiceByID() useElementByID() useTreeByID()

55 Open Forum 2003 on Metadata Registries 55 Simple Example  Simple Purchase Order  Straight up XML structure  Second example – structure choices  Included sub-assemblies

56 Open Forum 2003 on Metadata Registries 56 Additional Information  OASIS ebXML Registry Technical Committee  http://oasis-open.org/committees/regrep/  OASIS CAM (assembly) Technical Committee  http://oasis-open.org/committees/cam/  ebXML.org  http://www.ebxml.org/  http:ebxmlbook.com

57 Open Forum 2003 on Metadata Registries 57 http://www.ebXML.org http://drrw.net Thank you Pioneering XML eBusiness


Download ppt "EBusiness and web services Smorgasbord Open Forum 2003 on Metadata Registries 2:00pm to 3:00pm January 23, 2003."

Similar presentations


Ads by Google