340 likes | 491 Views
www.oasis-open.org. OASIS ebXML Registry and Repository v3.0 Standards Functions, applications and interoperability Kathryn Breininger The Boeing Company Chair OASIS ebXML Registry Technical Committee. Overview. What is ebXML? ebXML Registry Overview Key Features Use Cases Key Benefits
E N D
www.oasis-open.org OASIS ebXML Registry and Repository v3.0 StandardsFunctions, applications and interoperabilityKathryn BreiningerThe Boeing CompanyChair OASIS ebXML Registry Technical Committee
Overview • What is ebXML? • ebXML Registry Overview • Key Features • Use Cases • Key Benefits • ebXML Registry TC Work • Summary
What is ebXML (“e-business XML”) ? • UN/CEFACT • United Nations Centre for Trade Facilitation and Electronic Business • Created and maintains the UN/EDIFACT standards for Electronic Data Interchange (EDI) • OASIS • Organization for Advancement of Structured Information Standards • Consortium hosting XML and related standards work • Joint initiative of UN/CEFACT and OASIS • Phase 1: 1999-2001, initial specifications • Phase 2: 2001-2003, v2 & deployments • Phase 3: 2003-now, v3 & enhancements • Service-oriented architecture • Built up from user requirements • “Next generation” from EDI, leveraging XML and Web technology • Designed for B2B transactional reliability and enforceability • Semantic and technical interoperability
ebXML Modules • Business Process (ebBP) (submission to ISO this summer) • Support for complex business interactions • Choreography (public process) • Binding to message protocols via CPA • Collaboration Protocols Agreements (CPA) ISO 15000-1 • Bilateral message service and partner configuration • Binding to the ebXML Messaging Service (ebMS) • Messaging Service (ebMS) ISO 15000-2 • Secure, reliable messaging, binding to CPA • Version 2 certified interoperable messaging since 2002 • Registry & Repository ISO 15000-3 and 15000-4 • Information model and registry services • Core Components • Information model for vocabularies and business documents
ebXML Registry Technical Committee • Defining and managing interoperable registries and repositories • The OASIS ebXML Registry TC develops specifications to achieve interoperable registries and repositories, with an interface that enables submission, query and retrieval on the contents of the registry and repository • http://www.oasis-open.org/committees/regrep
OASIS ebXML Registry TC Deliverables • ebXML Registry Information Model (RIM) v3.0 • Defines what metadata and content can be stored in the registry • ebXML Registry Services and Protocols (RS) v3.0 • Defines the services and service interfaces • Defines the API for accessing the registry/repository • Ongoing work • Developing profiles for specific domains • Developing conformance specifications
What is ebXML Registry? • A registry as well as a repository • Classifies of any type of information • Manages relationships between information objects • Supports taxonomy hosting, browsing and validation • Organizes and manages information • A content management system for secure, federated information • Provides services for sharing content and metadata between entities in a federated environment • Logs lifecycle management actions in an audit trail • Supports automatic versioning of objects
Library Manages books, journals, CDs, etc Shelves contain items Catalog describes items Library network ebXML Registry Manages digital content Repository contains digital content Registry describes digital content Registry federation ebXML Registry is Like a Library
ebXML Registry is Used to… • Manage information • Describe information with metadata • Discover information • Share information securely over the web with role-based access control • Share information across organizational boundaries • Link content through relationships • Navigate to related content • Deliver notification of changes
Attributes for Object Registration • Classifications • Zero or more classifications (taxonomies) • Description • Textual description • External Identifiers • Zero or more – serve as alternate identifiers for the object • Logical ID • Each object must have a Logical ID • Name • Human readable object name • Object type • Each registry object has an object type referenced to a classification node • Status (object life cycle) • Approved, deprecated, submitted, withdrawn • Version • Information about the specific version of the object • Slot • Provides a way to dynamically add attributes – enables extensibility of the information model
Key ebXML Registry Features at a Glance Registration, Discovery, Queries ebXMLRegistry Registry Repository Federated Queries, Inter-registry links Taxonomies, Classifications, Associations Federated Information Manage-ment Standard Metadata Content management Secure Architecture Cataloging,Content Validation,Version Control,Lifecycle Support,Extensible Information Model Digital Signatures,Audit Trail,Access Control,SAML SSO Events Content-Based Event Notification
Key Features and Services • Standard metadata • Provides standards-based way to manage information assets • Classification and affiliation • Manages user-defined organization of and relationships among content and metadata • Content validation and cataloging • Enforces conformance of content to user-defined standards • Lifecycle management • Provides governance for managing information asset lifecycles
Key Features and Services (2) • Event notification and subscription • Facilitates event-based delivery of information to appropriate personnel or systems • Security • Manages secure access to information assets • Federation • Enables integration of information assets across organizational boundaries • Query and Discovery • Provides flexible mechanisms for content discovery
Federated InformationManagement • Multiple ebXML registries may be federated together to appear as a single virtual registry/repository • Seamless information integration and sharing • Allows local autonomy over data • ebXML registry relies on Security Assertion Markup Language (SAML) – the federated identity management standard
Many Diverse Use Cases • Service Oriented Architecture (SOA) registry repository • Web content management • Controlled vocabulary management • Taxonomies, ontologies, etc. • Business process catalog • Electronic forms • ebXML core components catalog • Domain-specific use cases • Electronic medical records (IHE-XDS) • Geological information systems (Open GIS) • Metadata store for grid computing
Need for SOA Registry/Repository • Rising complexity of SOA • Many types of artifacts (WSDL, XML Schema, BPEL, policies, XSLT, WSRP • Many dependencies and relationships • Governance of SOA artifacts • Single point of contact to enforce organizational policies • Governance enforced where SOA artifacts are stored • Registry is not enough – need repository • Repository stores the actual artifacts • Registry stores metadata about the artifacts • An integrated registry/repository ensures consistent storage and access • Management and reuse of artifacts according to organizational policies
4 SOA Scenario With Governance 5 Define policies: visibility, access, lifecyle stage, etc. Service Administrator Service Consumer
Case Study: Government of Canada/Ontario • Vision • Improve service quality to Canadian people and businesses through cost-effective eServices at all levels of government • Target • Leverage the power of XML to deliver those services via collaboration across jurisdictions • Strategy • Enable service delivery infrastructure by utilizing a federated registry and repository
eContact CBSC CALL CENTRE PORTAL CSPN COUNTERENVIRONMENT CPSIN FUTURESERVICES - DELIVERYSERVICES - BizPal Government of Canada:Registry/Repository enables e-Government Architecture ebXML Registry/Repository CSDML META DATA CLUSTERSCHEMAS TRANSACTIONSCHEMAS SECURITY GSRM Models COMMONCOMPONENTS TRANSFORMATIONSFOR PS PROGRAMS Presentation Layer ApplicationLayer XML IntegrationLayer Back-EndLayer Source: Government of Canada
United Nations Standard Products & Services Code (UNSPSC) Use Case UNSPSC and ebXML registry/repository deployment template available August 2007
GS1 US Use Cases • EPCglobal US Consortium Proof of Concept • Federated registries & repositories of artifacts • RosettaNet Partner Interface Processes (PIPs) • XML Schema Definitions (XSDs) and Instance Messages • Electronic Product Code Information Services (EPCIS) Events • Global Data Synchronization Network (GDSN) Data Pool • Core engine for handling item and price synchronization • Registry and Repository of PIP Artifacts • Storing of PIP XSDs and other business artifacts related to PIPs • Exporting of PIP packages
Profiles for Specific Use Cases • Enable interoperability within and across domains • Define restriction/extension requirements of usage • Committee approved profile • ebXML Registry Profile for Web Ontology Language (OWL) • Profiles in work • Deployment Profile Template for ebXML Registry 3.0 • Profile for WSDL • Profile for XML Schemas • Web Services Profile • WSRP (Remote Portlets) Profile • Profile for Namespaces • Profiles for specific domains • Open GIS Profile • HL7 Profile • IHE Cross-Enterprise Document Sharing (XDS) • ebXML Core Components Profile
Who is Using ebXML Registry/Repository • Government • Government of Norway • Government of Finland • Government of Ontario • Government of Canada • US Department of Defense • US Internal Revenue Service • US Department of Education • Industry • France Telecom • Korean ebXML Central Registry & Repository (REMKO)
Who is Using ebXML Registry/Repository (2) • Organizations • The UN/CEFACT Information Content Management Group (ICG) • Statistical Data and Metadata Exchange • XDS initiative to Integrate the Healthcare Enterprise (IHE) • US National Institute of Standards and Technologies (NIST) • National Institute of Health (NIH) • Open GIS • ADNOM, a federated registry for Administrative Nomenclature • EDIFRANCE • GS1 US • Health Level 7 – Manage HL7 • DISA Registry Initiative (Drive)
ebXML Registry/Repository Products • Sun Service Registry • Adobe LifeCycle Form Manager • WebMethods Infravio X-Registry • Digital Artefacts • Semantion Registry and Repository 2.5 ebXML Open Source Projects • Eclipse Open healthcare Foundation IHE • IBM Interoperational health Informaiton Infrastructure • freebXML BP • freebXML CC • freebXML Registry open source project (OMAR) • http://ebxmlrr.sourceforge.net/wiki/Overview • http://ebxmlrr.sourceforge.net/wiki/Showcase
Key Benefits of ebXML Registry • Provides a minimal core information model • Standard across all domains • Defined by UML • Mapped to XML Schema • Permits object-oriented and dynamically extensible classes • Class extension via Object Types • Attribute extension via Slots • Allows profiles to define standard extension to the core model
Key Benefits (2) • Provides standard inter-object relationship mechanism • Association class • Association types defined by taxonomy • Enforces user-defined standards for content • Validation and cataloging services • Provides management and governance of information asset lifecycles • Lifecycle status • Object versioning support • Provides flexible mechanisms for content discovery • Stored parameterized queries • SQL query syntax
Key Benefits (3) • Manages secure access to information assets • Role-based access control • Complete audit trail • Facilitates event-based delivery of changes to information assets • Notification delivery • Subscription services • Enables integration of information assets across organizational boundaries • Inter-registry object references • Federated queries across multiple registries
OASIS ebXML Registry TC Activities • New Committee Approved Specification • ebXML Registry Profile for Web Ontology Language (OWL) • Documents in Work • Deployment Profile Template for ebXML Registry 3.0 • Profile for WSDL • Profile for XML Schemas • Profile for Namespaces • Developing additional profiles for specific domains • Open GIS Profile • HL7 Profile • IHE Cross Document Sharing (XDS) • ebXML Core Components Profile • Developing conformance specifications • Education and marketing activities • ebXML Registry Webinar June 2007 • ebXML online community http://ebxml.xml.org/regrep • ebXML Registry podcast April 2006
Future Directions • Approve OWL Profile as standard • Develop additional profiles • Expand protocol bindings • REST, ebXML Messaging, SMTP • Increase type extensibility • Provide full text indexing and search • Enable check-in, checkout, locking, merge
Summary • ebXML Registry/Repository is a standard (OASIS and ISO) for secure, federated information management • It has a standards-based integrated registry and repository • It supports many diverse use cases • SOA use cases • eBusiness use cases • Its extensibility features enable many domain-specific profiles • It is being deployed in diverse applications by organizations worldwide
Related links • OASIS ebXML RegRep Technical Committee • Home page: http://www.oasis-open.org/committees/regrep/ • Specifications: http://docs.oasis-open.org/regrep/v3.0/regrep-3.0-os.zip • Profiles: http://ebxmlrr.sourceforge.net/wiki/index.php/Overview#Profiles_of_ebXML_Registry_Standard • Comments list: Regrep-comment@lists.oasis-open.org • Online community: http://ebxml.xml.org/regrep • Wiki: http://wiki.oasis-open.org/regrep/FrontPage • freebXML Registry Open Source Project • Home page: http://ebxmlrr.sourceforge.net • Other Resources on ebXML RegRep • Overview: http://ebxmlrr.sourceforge.net/ • Article: http://xml.coverpages.org/ni2005-02-14-a.html • Article: http://blogs.zdnet.com/service-oriented/?p=868