Presentation on theme: "Practical ebXML Registry uses for interoperable eBusiness"— Presentation transcript:
1 Practical ebXML Registry uses for interoperable eBusiness Open Forum 2003 on Metadata Registries8:40am to 10amJanuary 22, 2003
2 Presenter David Webber http://drrw.net co-author of ‘ebXML – the new global standard for doing business via the internet’, New Riders PublishingChair of the OASIS CAM TCCo-chair of OASIS/CEFACT ebXML JMTPioneering XML eBusiness
3 Agenda Part 1 – XML integration Part 2 – Demonstration / Technologies W3C approach – web-centricebXML approach -Registry-centric / assembly / core componentsUpcoming Registry developmentsebXML V3.0 enhancementsPartner discovery / UDDIPart 2 – Demonstration / TechnologiesReview of OAGIS V8.0 technologyebXML Registry and Content ClassificationSummary / Q&A
11 XML Management Challenges <lat_deg>30N</lat_deg><latitude units=“degrees” hemisphere=“north”>30</latitude><latitude><hemisphere>N</hemisphere><degrees>30</degrees></latitude>XML schemas and XML documents can be developed with a text editor, although there are free or cheaply-available tools to assist in their production. This creates a situation where the bar is so low that it becomes trivial to develop a vocabulary – one that is well-formed and valid and non-interoperable with others.These 3 XML fragments are:Equally valid ways to express the same data in XMLWell-formed per W3C SpecificationDifferent terms and syntaxNOT INTEROPERABLE!
12 Lessons Learned Expect Heterogeneity! No Single Standard can be imposed!Various industry communities will adopt multiple “standards:”Government (message, database, symbology), Commercial, International, de facto/legacy etc.
13 W3C Schema ProvidesDefinition of all permitted element structural combinationsAbility to define local typing constraintsAbility to create re-usable chunks of structure elements
14 W3C Schema weaknessesPermitted combinations of attributes within elementsContent assembled from multiple namespaces and cross-associationsContext mechanism has to be externally resolved using XSLTAll semantics are in the schema
16 What does ebXML do? “Who, What, When, How” Trading Profile Management and Discovery.Assembly of transaction content.Establishing consistent data definitionsBusiness Process Collaboration.Message Handling ServicesWeb Services
17 ebXML Registry Mission Collaboration - give industry groups and enterprises the ability to share business semantic information and business process interfaces.Semantics - provide universal infrastructure that seamlessly delivers semantic integration into business applications.Interfaces - open deployment machine-to-machine and user web enabled visual.
19 ebXML Registry capabilities Provides services for sharing informationProvides publishing and discovery of informationAccessible as a web serviceCommunicates using XML based request and responsesProvides mechanisms to store and retrieve persistent informationIncludes a Repository
20 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 semantics.XML by itself is not the magic bullet.What we really need is a consistent set of methods for building interoperable eBusiness systems using XML – “railroads and telephony”.
21 XML Information Exchange Quality (and long-term consistency)ebXML Secure Authenticated Delivery and Tracking:ebXML Messaging system, envelope format and payload with exchange source profile (CPP) controlsDeliveryAssemblyXMLContent Assembly:Business logic forcontent structure decisions andexplicit rules to enforce content,and interdependencies, withbusiness exchange context,and content definitionUID referencesSchema:Content structure definitionandsimple content typingSchemaRegistry/Dictionarybusiness informationUID content referencing systemensures consistent definition usageUID
22 Consistent Meaning Business Collaboration Partner #1 Collaboration XML InstanceXML InstanceData<ListPrice>9.99</ListPrice><UnitPrice>9.99</UnitPrice>Machine-to-Machine<Currency>$</Currency>
23 Context Everywhere! OAG304 Schema or Template Schema or Template RegistryOAG304CollaborationPartner #2UnitPriceDollarsCollaborationPartner #1ListPriceCurrencySchema or TemplateSchema or Template<Rep href= “http://www.oag.org”>OAG</Rep><ELEMENT rep= ‘OAG’ name=‘ListPrice’ uid =‘OAG304 ><Rep href= “http://www.oag.org”>OAG</Rep><ELEMENT rep= ‘OAG’ name=‘UnitPrice uid =‘OAG304 >XML InstanceXML InstanceData<ListPrice>9.99</ListPrice><UnitPrice>9.99</UnitPrice><Currency>$</Currency>UIDs allow for domain crosswalks and light transactions
25 Information Methodologies TOPDOWN APPROACHUMM / UML ModelingBOTTOMUP APPROACHUN/CEFACT Core ComponentsPayload MetadataFinal Business PayloadPayload MetadataInformation ComponentsLegacy Data
26 Registry-centric benefits Legacy payloads can be used “as is”Supports vocabulary alignment and multi-lingual element tagsMinimizes overhead in payload itself – can be just simple structureProvides ability to do automated mappingUses Content Assembly Mechanism to capture business rules and context parameters (OASIS CAM TC)
27 Business Process Pyramid Collaboration PartnerAgreementsCollaboration PartnerProfiles5ContractBusinessIntegrationRegistryTaxonomyBP Specification4WorkflowProcessXFormsSpecificationsSchema3MessagesAssembliesArtifact relationshipsWeb Services2Motivation Time PeoplePresentationRolesRulesEventsThis pyramid is the “snapshot” of all the critical components needed for consistent ebusinessinformation processes. Therefore – take-away is that XML needs to provide these BOTH asData components, and also XML scripts. XML can describe both data and processes asMachine executable definitions.Directory ServicesTechnologyIntegrationData/Codes Services/Functions Network1ebMS/SOAPNounsVerbsSecure contentdelivery
29 Concept to Runtime Approach Business Re-usable Information Components- BRICsRegistryComponentsVocabulariesandIndustry DictionariesPhysicalConceptualApplicationDatabaseStructureChoices12RequiredContentStructure3Payload MappingContentAssemblyMechanismTemplateProcessEngineContentReferencesContextValuesPayload /RenderingLogical
31 Registry LookupGoXML Transform provides direct Registry lookup based on “UIDs”. UID, unique identifiers, provide a mechanism to normalize data from various parties.We create Core Components for, say a business term like telephone, then we use the UID contained in that CC in our transformation.UID lookups from Transform can be either a design-time lookup to enhance the output structure tag, or a run-time lookup to resolve codes. The code lists are found in the registry by their relationship to a given CC.Lookups can take place against a single element or an entire sub-tree.One could use this feature to convert terms used in incoming documents match those terms that are internally used.Example: Purchase order arrives, and it always says “SKU”, but internally you use the full term “Stock Keeping Unit”, or a different term like “Product Code”. Use the registry lookup to build a transformation that inserts the correct code into the transformed document. Then, use the run-time registry lookup to actually resolve the SKU code to the Product Code you use internally. The Registry Code-List facility lets you upload codes lists so you can do this.
32 eBusiness Runtime Components CPP/ABP RulesBPEEebXMLMessageContentBPSSebXML MSURL configPortSecurityI/OApp ServerPayload(s)O/SRegistry Server
33 Backend Integration BP Rules BPEE API TRANSFORMS ebXML MS I/O AssemblyTemplatesCPP/ABP RulesBPSSBPEETRANSFORMSAPIebXML MSI/OApp ServerInstancevaluesTransformTemplatesO/S
34 Upcoming Features, Implementing ebXML, and Registry Demonstration Part 2Upcoming Features,Implementing ebXML, andRegistry Demonstration
36 New Features in Version 3.0 Cooperating registriesEvent notificationHTTP interface to registryContent management servicesIterative query support
37 Cooperating Registries Enables multiple ebXML Registries to work together to address user needsBased on a loosely-coupled federation modelAllows local autonomy to each registry operatorEnables smaller registries to access resources of larger registriesEnables federated queries to multiple registriesInter-registry object referencesA registry may belong to multiple Federations
38 Event NotificationEnables notification of events regarding registry objectsClients may be registry users or other registriesLeverages existing Registry Services interfacesSubscription Service registers clients for notificationSupports notification and programmaticFlexible notification optionsReferences to eventActual eventObjects affected by the event
39 HTTP Interface to Registry Provides a pure HTTP interface to RegistryDoes not require SOAPRegistry objects and Repository items addressable via URLsAllows ebXML Registries to interoperate with other types of registriesImproves access to Registry content
40 Content Management Services Enables content management based on object typeContent cataloging and validationValidate on submissionCataloging metadata applied on submissionContent-based publish, discovery and subscribeUser-defined relationships between contentAssociations of internal and external classificationInvocation control file defines rules for cataloging service
42 Deploying ebXML Technologies Planning and Implementation Guide
43 Deployment PlanningIncremental adoption of components and operational maturityPlan 1 year, 2 year and 5 years out.Issues, implementation criteria, ROI, support, interoperability, XML.Schema neutral content assembly.Separation of business semantics from XML mechanics.Web services and discovery.
44 Implementing ebXML roadmap Existing IntegrationNew Deployment1Install messaging2Create partner delivery details3Document business processAgree on business process4Migrate existing payloads to new deliveryMake assembly definitionsSelect payload standardsMap to applicationsBuild payload contentAdopt Business Process automation - BPSS5Cross reference assembly to registry dictionary6Publish details to registryI N C R E A S I N G M A T U R I T Y
45 Some ebXML selection metrics B2B or large A2A Environments— extending or integrating enterprise systems, or when loosely coupled messaging is desirableNeed Reliable Messaging— when enterprise services perform updates, insert, or deletes to the underlying data model, reliable messaging becomes criticalSecurity is a Concern—when different security profiles and requirements exist between trading partnersHigh scalability requirements—ebXML’s loosely coupled messaging architecture allows for horizontal scalability, queuing, and clusteringWant to Leverage Industry Standards—XML grammars, business process modelling and trading partner agreements
46 Main ebXML conceptsBusiness Processes – defined as models in UMM, scripted in XMLBusiness Messages – content agnostic - exchanged using ebMSTrading Partner Agreement – specifies parameters for businesses to interface with each other – expressed in XMLMessaging Layer – moves the actual XML data between trading partners – ebMSCore components – library of pre-defined business vocabulary artifactsCollaboration Registry - Provides a “container” for process models, vocabularies, assembly templates, partner profiles + discovery.
47 Additional Information OASIS ebXML Registry Technical CommitteeOASIS CAM (assembly) Technical CommitteeebXML.orgVersion 2.0 ImplementationsOpen Source Implementationebxmlsoft Inc. ImplementationXMLGlobal Implementation
48 Pioneering XML eBusiness Thank youPioneering XML eBusiness