ebXML Registry and Repository

1. ECOM Seminar Saturday 11/11/2000 ebXML Registry and Repository

2. Presented by Scott Nieman Project Leader: ebXML Registry and Repository Solutions Director: e-Business Integration Norstan Consulting

3. Mission Statement • The ebXML registry and repository project team will deliver requirements and specifications for the creation and use of a registry and repository. The registry and repository will be comprehensive, distributed, business analysis driven, and support the runtime and development viewpoints of the ebXML architecture.

4. Project Objective • To define the business and functional requirements for an ebXML registry and repository • XML-based interfaces to interact with the registry and repository

5. Deliverable Scope • Develop a functional requirement document • use cases and other UML artifacts • detailed prose describing how to use the system • XML Interfaces: application-programming interface • Multi-phased approach for the specification of supporting services • limited to essential features • ebXML does not intend to implement a registry and repository itself

6. Work Items: Specifications • Business Requirements (complete) • UML Model • Business Domain Model • ebXML Registry Services; XML Service Interfaces • ebXML Repository Information Model

7. Business Requirements • Storage of items in their original form • Distributed Registries; “single global repository” no longer a valid concept in Internet age • Apply Best Practices; • reuse of best of breed if possible • Future proof specifications • Features • Allow the query and retrieval of items • Support a standards development workflow • Allow the comparison of object to a checklist of features; e.g., ensure consistent UML models • Allow the transformation to / from different forms, e.g., UML/XMI to XML, tpaML formation • Allow the discovery of a registry’s specific interfaces/ capabilities • Provide a logging mechanism such as transactional events

8. Architecture: Distributed Registries • Publish and Subscribe Architecture • Association of objects between registries • Metadata Exchange • XMI probable • Monitor of events • Versioning • Submission of like-objects • Publish via ebXML Messaging Service • Multi-level subscription • Service Interfaces • Collections of like-objects • Individual objects

9. DNS-like Registry of Registries 2 Return list of hits plus all repositories that were not accessed. From there the user could link to the document of choice. Search App OASIS or other official site Registry of Registries A global search may go through potentially thousands of registries each of which may in turn have thousands of repositories. 3 Registry Repository 1 Registry … Registry … Original document in intended format including multimedia attachments Repository Repository Repository … Repository Repository Repository

10. Business Domain • Define the scope of the “system” • Driven by ebXML Architecture • Driven by ebXML Requirements • High Level Use Cases • Actor Generalizations; hierarchical view of all role players • Domain Package Diagram; partitions use cases and services that support them • ebXML Specified Services • Registration Authority Specified Services; value added • Traceable to the Business Requirements

11. Domain Use Case Register Company Submit Object Store Object Classify Object Subscribe Retrieve Map between Specifications

12. Actor Generalization ISO 11179 terminology Extended as needed

13. Domain Package Diagram Used to organize use cases and state machines Services UI Applications Services are dependent on each other Messaging Storage Security

14. Registry Services Life cycle management Query Interface Discovery Service Logging Publish Subscription Library Control System Transformation Workflow Quality Assurance Service

15. ebXML Registry Specifications • ebXML Business Domain Specification • ebXML specified services vs. RA specified services • ebXML Registry Services • ebXML Registry Information Model

16. ebXML Specified Services • Life cycle management • Query • Interface Discovery Service • Logging • Publish • Subscription

17. ebXML Registry Service - Interfaces Authentication & Authorization Enables Pub-Subon Registry Data Party Registration Object Life Cycle Querying Objects Interface Discovery

18. Life-Cycle Management Service • Storage of anything that can be classified; including classification schemes themselves • Submission • Classification via metadata • Classification of single object by multiple schemes • Metadata versioning; draft, public review, standard/ specification • Object versioning; new, deprecation of prior version

19. Typical use cases for object life cycle Life cycle Management

20. Query Service • Ad-hoc Query Construction via Classification Scheme • URI Specific • Browsing via Classification Scheme • Indexing by Classification Scheme • Metalevel independent Schemes support • Multiple Viewpoints; pickNewRoot() allows support of Topic Maps • Schemes at all OMG metalevels M0, M1, M2, and M3 (e.g., ebXML BP, UML metamodel, MOF) • Canonical Query Syntax required • No intent to reinvent the wheel • OQL and Quilt are candidates

21. Guest Users Ad hoc Collections Metadata Objects Applications Metadata Objects Query Use Case

22. Interface Discovery Service • This service will allow the discovery of the set of implemented interfaces and detailed operations for a particular registry instance • Registries are not required to implement ALL of the ebXML Registry Service interfaces • This may be represented as an XML document, similar to Web Services Description Language without the slippery stuff (SOAP)

23. Logging Service • Logging of events • Many types of events • Single API for all services to call • XML based syntax • Model to be defined

24. Subscription Service • Allows a Party to subscribe to a Registry and public accessible events • Versioning of an object • Submission of like-objects • Party can use a check-box approach to subscribe based on roles

25. Publish Service • Allows the monitoring of defined events similar to a listening service • May listen to logging service events only • Forcing the registry to know when, how, and who to publish to may not scale • Details to be refined

26. Registration Authority Specified Services • Library Control System • Transformation • Workflow • Quality Assurance Service

27. Library Control System Use Case • Classic versioning environment • Reservation • Message based alerts

28. Transformation Services • Provide various forms of transformations including • UML to XML generation • business process definitions • XML Schema and DTD generation • Trading partner agreement formation • NOT for production runtime data; i.e., NOT for purchase order, invoice, etc. transformations

29. Transformation of two trading partner profiles Scenario: Trading Partner 1 queries and discovers Trading partner 2 TPA consummated; sent to Trading Partner 2 for review and acceptance Trading Partner Agreement formation **Legal Constraint Prevent Storage of TPA in Repository Trading Partner Profile 1 Transformation Rules Trading Partner Agreement** Trading Partner Profile 2 Destination Source

30. Conversion of UML Models to XML • Business process definitions • XML Schema and DTD generation • Populate classification scheme XML Schema XML Process Definition Transformation Rules XMI (MOF.DTD) Populate Classification Scheme** Source Destination **Classification Scheme assignment or population if metalevel >M0

31. Workflow Service • Cross reference to the actor instances, their roles, and the services that they are allowed to access • Supports use cases that are interactions to registry services (<<UI>>, <<Application>> packages) • Typical scenarios: • Submission of objects by SO • Classification by SO • Elaboration of Classification by RA • Assignment of object review to RA individual • Promotion of submission to new work item, NWI to specification, review cycles, etc.

32. Quality Assurance Service • Allows the definition of a checklist of required elements for a Managed Object • Allows a submitted object to be parsed and compared to a checklist of required elements; this uses the transformation service • Scenario: XMI submission of UML model conforming to UN/CEFACT Modelling Methodology • Output may be a list of missing items

33. Registry Information Model

34. Repository Information Model • Based heavily on ANSI ASC X3.285 • Submission to ISO 11179 • Refinement of OASIS (XML.ORG) Information Model • Key concepts • Classification Scheme support • Managed Objects • Storage of anything • Flexible associations • Subscription to managed objects (in progress)

35. Ability to Group related objects together as collection An object instance stored outside the registry, e.g. on the web e.g businesses, services, templates, protocol definitions, schemas, etc Classifies an object, classifications can be grouped into hierarchies A submission may be more than one Managed object e.g. a Party that submitted something ebXML Reg-Rep Information Model Ability to associate items to others

36. Information Model: Object Class Diagram Special Type of ManagedObject critical to the Registry itself An object instance stored outside the registry, e.g. on the web Special Type of Association where the “to” is a ClassificationNode

37. Associations • Managed Object to one or more Classification schemes • Object to Object • Object to Collection of Objects • Classifications to other Classification to provide context to a classification

38. Traditional Classification Scheme • Taxonomies Industry HealthCare Automotive Retail Geography USA Japan Europe Toyota:object Ford:object Nissan:object BMW:object Chevy:object

39. Examples Classification Schemes • Business Process Models* • Industry, international, standards • Business Message specifications* • XML, EDI; protocol specific • UML; protocol independent • Trading Partner Profiles* • Capabilities including product service, transport, business process scenarios, business messages, security • UML Profiles – metamodels • Stereotypes, tagged values, syntax, semantics, model management • Common Business Objects • Patterns • Hillside Community Pattern Language *ebXML Areas

40. Business Use Cases • Interact with use case ACROSS services • User Interface Based • Submission • Work in Progress • Ad-hoc Query • Technical Specification Review • Application to Registry Based • Business Application; e.g., software agents • Mapping Tools; tpaML formation; specification transformation rule development • Software Development IDE

41. example Submission Use Case Diagram

42. Viewpoints: SO creates Specifications SO creates software Company Registration Use Case Diagram

43. What about Universal Definition, Discovery, and Integration (UDDI]??

44. UDDI White and Yellow pages -Business & Service definitions Binding Templates describe how to exchange messages Flexible categorization of businesses and services Specific categorizations defined SOAP based APIs for registration and search – concrete syntax Protocol for Replication between operators Agreement to operate/replicate registries Comparing UDDI & ebXML • ebXML • Reg-Rep can hold Business and Service specifications plus much more • TP (CPP) used to define message exchange for Reg-Rep • Flexible categorization of anything in registry • Ability to submit any classification schemes; BP, CC, TP important • General Service Interface definitions, mapped to TRP & XML DTDs • Distributed; No replication; publish-subscribe interactions • No need to replicate; information owner manages their own knowledge

45. Possible UDDI Binding to ebXML Reg-Rep

46. Plan: Registry Business Domain

47. Plan: Registry Information Model

48. Plan: Registry Services

49. Plan: Registry Services (cont)