1. OASIS ebXML Registry v3.0 Standard How to Publish, Manage, Govern, Discover, and Reuse Artifacts for eBusiness, SOA and Other Applications ebXML Registry Technical Committee Defining and managing interoperable registries and repositories http://www.oasis-open.org/committees/regrep http://www.oasis-open.org/committees/regrep www.oasis-open.org

2. Agenda n Welcome l Jamie Clark, Director, Standards Development, OASIS n ebXML Introduction l Kathryn Breininger, Chair, ebXML Registry Technical Committee. The Boeing Company n ebXML Registry overview l Farrukh Najmi, Federated Information Management Architect, Sun Microsystems l Carl Mattocks, CEO CHECKMi; consultant, Metropolitan Life Insurance n Demonstration l Farrukh Najmi n Questions and Answers

3. n OASIS is a member-led, international non-profit standards consortium concentrating on structured information and global e-business standards. n Over 650 members n Supports over 60 technical committees producing royalty-free and RAND standards in an open process. Who is OASIS? “The largest standards group for electronic commerce on the Web" SAML WS-Security XACML ebXML UDDI WSDM WSRP CAP Best known for standards like

4. OASIS Members Represent the Marketplace 15% Government & Academic n Governments n Universities n Research centres & related nonprofits 35% Users and influencers n User companies n Vertical industry organisations n Individuals / small consultancies 50% Technology Providers n Software vendors n Industry organisations n Individuals / small developers

5. Common transport (HTTP, etc.) Common language (XML) Discovery Description Orchestration & Management Security & Access Messaging Data Content OASIS work mapped: August 2005 (Newer work in stars) ebXML MSG ebXML BP ebXML CPPA ebXML RegRep ebSOA ebXML IIC

6. n Service-oriented architecture l Built up from user requirements l “Next generation” from EDI, leveraging XML and Web technology l Designed for B2B transactional reliability and enforceability n Joint initiative of UN/CEFACT and OASIS l Phase 1: 1999-2001, initial specifications l Phase 2: 2001-2003, v2 & deployments l Phase 3: 2003-now, enhancements What is (“e-business XML”) ?

7. 5 modular parts to ebXML n Business Process Specification Schema n Core Components n Collaboration Protocol Profiles and Agreements (originally “TPA”) n Message Service (originally “Transport”) n Registry & Repository n OASIS v2 in public review now n v1 from UN/CEFACT in ISO 15000 n v2 from OASIS in ISO 15000

8. ebXML Registry Technical Committee Members n Kathryn Breininger (TC Chair)The Boeing Company n Peter KacandesAdobe Systems n Matthew MacKenzieAdobe Systems n Duane NickullAdobe Systems n Sally FugerAutomotive Industry Action Group (AIAG) n Joseph Chiusano Booz Allen Hamilton n Ivan BediniFrance Telecom n Richard MartellGaldos Systems Inc n Shin TakagiHitachi Systems & Services n Diego BallveIndividual Member n John GillermanIndividual Member n Patrick Hogan Individual Member n Richard ParentIndividual Member n Paul MaciasLMI Government Consulting n Carl MattocksMetLife n Asuman DogacMiddle East Technical University n Evan WallaceNIST n Jeff PollockNetwork Inference n Matthew DoveyOxford University n Nikola StojanovicGS1-US n Goran ZugicSemantion n Monica MartinSun Microsystems n Farrukh NajmiSun Microsystems

9. OASIS ebXML Registry TC Work Status n Two standards developed l ebXML Registry Information Model (RIM) l ebXML Registry Services and Protocols (RS) n Version 2.0 approved as OASIS standards May 2002 l Approved as ISO 15000 parts 3 and 4 March 2004 n Version 3.0 approved as OASIS standards May 2005 n Current work l Developing profiles for specific domains l Updating Technical Notes l Developing Conformance specifications

10. ebXML Vendor Products n Sun Microsystems Inc. n ebXMLsoft Inc. n CHECKMi n Digital Artefacts Inc. n Adobe Systems Inc. n freebXML Registry (open source) n Infravio - X-registry n Xenos Group Inc. – GoXML Registry

11. Sampling of ebXML Registry Deployments n Norway, Finland l Registry-based environment for XML schemas and electronic forms n UN/CEFACT Information Content Management Group l UN registry to store core component artifacts n EDIFrance l Trial project to manage core components and business information entities n Korean KIEC federated registry l Korean ebXML Central Registry and Repository (www.remko.or.kr)www.remko.or.kr n XDS initiative founded by NIST and Integrating the Healthcare Enterprise (IHE) l Collaborating with industry to define clinical document registries n Others l HL7, RosettaNet, US Department of Defense, etc.

12. ebXML Registry 3.0: An Overview www.oasis-open.org

13. Overview n What is ebXML Registry? n Use Cases n Key Features n ebXML Registry in Action n Key Benefits n Future Directions n Summary

14. What is ebXML Registry? n A Service Oriented Architecture registry as well as a repository l Classification of any type of information l Managing relationships between information l Taxonomy hosting, browsing and validation l File/folder organization of information

15. What is ebXML Registry? (2) n A content management system for secure, federated information l Provides services for sharing content and metadata between entities in a federated environment l Lifecycle Management (LCM) actions logged in an audit trail l Supports automatic versioning of objects

16. Use Cases n SOA registry repository n Web content management n Controlled vocabulary n Business process catalog n Electronic forms n ebXML core components catalog n Domain-specific use cases l Electronic medical records (IHE-XDS) l Geological information systems (Open GIS) l Metadata store for grid computing

17. Why a SOA Registry/Repository Rising complexity of SOA deployments Many types of artifacts (WSDL, XML Schema, BPEL, policies, XSLT, WSRP Many dependencies and relationships Need for governance of SOA artifacts Need single point of contact to enforce organizational policies An ebXML Registry is the central service that enables SOA governance

18. SOA Scenario With Governance Service Consumer 5 4 Define policies: visibility, access, lifecyle stage, etc. Service Administrator

19. Use cases for SOA Registry/Repository n Automatic validation: key to governance n Service discovery and reuse n Composite services l Playing Lego TM with services artifacts n Service artifact dependency management n Phased deployment of services l Role based access control at each stage n Service evolution and versioning n Change notification

20. Need for an Integrated SOA Registry/Repository n Governance enforced where SOA artifacts are stored n Registry is not enough – need repository l Repository stores the actual artifacts l Registry stores metadata about the artifacts n An integrated registry/repository ensures consistent storage, management and reuse of artifacts according to organizational policies n ebXML registry provides an integrated registry/repository

21. Federated Information Management n Multiple ebXML registries may be federated together to appear as a single virtual registry/repository l Seamless information integration and sharing l Allows local autonomy over data n ebXML registry relies on SAML – the federated identity management standard

22. Adoption within Governments n Governmental bodies are prominent among ebXML Registry adopters for electronic information management and dissemination l Finland: XML Schemas and eForms l UN/CEFACT, EDIFrance: eBiz reference data l US NIST: Clinical documents l Taiwan: eGovernment Platform l Korea: Central Registry and Repository (REMCO) l Canada: Federated SOA Registry

23. Case Study: Government of Canada/Ontario n Vision: Improve service quality to Canadian people and businesses through cost-effective eServices at all levels of government n Target: Leverage the power of XML to deliver those services via collaboration across jurisdictions n Strategy: Enable service delivery infrastructure by utilizing a federated registry and repository

24. Government of Canada (2): Registry/Repository enables e-Government Architecture CALL CENTRE PORTA L COUNTER ENVIRONMENT FUTURE SERVICES - DELIVERY SERVICES - CSDML META DATA CLUS TER SCHE MAS TRANSAC TION SCHEMA S SECU RITY GSRM Models COMMON COMPON ENTS TRANSFORMATI ONS FOR PS PROGRAMS ebXML Registry/ Repository BizPal XML Integration Layer Application Layer Presentatio n Layer Back-End Layer CPSIN CSPN CBSC eContac t Source: Government of Canada

25. Epidemic Management: Working With Other Technologies and Standards Event Notification (SOAP) xForm / XML UBL Messages Browser ebMS Browser Agent Service XACML PDP ebMS DCC Registry XML Policy BPSS Editor CPA Editor DCC Registry CPA BPSS Policy PDF Form / XML

26. The Specifications n ebXML Registry Information Model l Defines what metadata and content can be stored in the registry n ebXML Registry Services and Protocols l Defines the services and service interfaces provided by the registry l Defines the API for accessing the registry n ISO 15000 Standard, Part 3 and 4

27. Profiles Implement Business Context n Enable interoperability within and across domains n Define restriction/extension requirements of usage n Current examples of profiles include l Web Services Profile l WSRP (Remote Portlets) Profile l Open GIS Profile l HL7 Profile l IHE Cross-Enterprise Document Sharing (XDS) l ebXML Core Components Profile

28. Key ebXML Registry Features at a Glance Content Management Federated Architecture Standard Metadata Events Secure Architecture ebXML Registry Classification, Associations, Taxonomies Cataloging, Validation of Content, Ver- sion Control Federated SQL & XML Queries DSig, Role-Based Access Control, Audit Trail Web Services Registry Publish, Discover, Manage/ Govern Web Services Content-Based Event Notification

29. Key Features and Services n Standards: Provides standards-based way to manage information assets n Classification and affiliation: Manages user-defined organization of and relationships among content and metadata n Validation and cataloging: Enforces conformance of content to user-defined standards n Lifecycles: Governance capabilities for managing information asset lifecycles

30. Key Features and Services (2) n Query: Provides flexible mechanisms for content discovery n Security: Manages secure access to information assets n Event notification: Facilitates event- based delivery of information to appropriate personnel or systems n Federation: Enables integration of information assets across organizational boundaries

31. ebXML Registry 3.0: A Brief Demonstration www.oasis-open.org

32.  Publish/subscribe capabilitiesEvent Notification  Distributed content/metadata  Federated queries  Replicated content/metadata  Object relocation Cooperating Registries Support  Content validation  Content cataloging  Content-based discovery Content Management Services Query Enhancements Registry Managed Version Control HTTP Protocol Binding Feature  Robust version control mechanisms based on the DeltaV/WebDAV protocol  Web Browser client to access to registry using HTTP 1.1 protocol  Simple content retrieval  Iterative query support  Parameterized stored queries  Improved Filter Query syntax Description New Features in ebXML Registry 3.0

33. Improved Identifiers Improved Extensibility Security Enhancements Feature  Easier to define new types of requests and responses  XACML-Based Access Control Model  SAML-Based Federated Identity Management  Human-Friendly URN-based Identifiers Description New Features in ebXML Registry 3.0 (2)

34. Key Benefits of ebXML Registry n Provides standard way to manage information assets n Manages user-defined organization of and relationships among content and metadata n Enforces user-defined standards for content n Includes capabilities for managing and governance of information asset lifecycles

35. Key Benefits (2) n Provides flexible mechanisms for content discovery n Manages secure access to information assets n Facilitates event-based delivery of information to appropriate personnel or systems n Enables integration of information assets across organizational boundaries

36. Future Directions n Interoperability testing n Conformance specification n Semantic content management n More profiles (e.g. Dublin Core) n More protocol bindings (SMTP, RM, ebMS, etc.)

37. Summary n ebXML Registry is a standard for secure, federated information management n One registry supporting both SOA and eBusiness use cases n Extensibility enables domain-specific profiling of Registry capabilities n ebXML Registry is being deployed in diverse applications by organizations worldwide

38. Related Links n OASIS ebXML Registry Technical Committee l http://www.oasis-open.org/committees/regrep/ http://www.oasis-open.org/committees/regrep/ l ebXML Registry Information Model v3.0 ebXML Registry Information Model v3.0 l ebXML Registry Services and Protocols v3.0 ebXML Registry Services and Protocols v3.0 n We need your feedback – Send e-mail to: l Regrep-comment@lists.oasis-open.org Regrep-comment@lists.oasis-open.org n Articles on ebXML Registry 3.0 standard l http://xml.coverpages.org/ni2005-02-14-a.html http://xml.coverpages.org/ni2005-02-14-a.html l Searchwebservices article Searchwebservices article n ebXML Registry meta-link page l http://ebxmlrr.sourceforge.net/tmp/ebXMLRegistryLinks.html http://ebxmlrr.sourceforge.net/tmp/ebXMLRegistryLinks.html

39. ebXML Registry 3.0: An Overview Finish www.oasis-open.org