Cooperating Registries Draft Content for OASIS/ebXML Reg/Rep f2f

1. Cooperating RegistriesDraft Content for OASIS/ebXML Reg/Rep f2f November 1, 2001 Bruce Bargmeyer (510) 495-2905 bebargmeyer@lbl.gov

2. Topics to be Covered • Registries with related content • Registry types. • Functionality and content issues • Registry content examples. • Metadata management issues • A proposed solution–Registry interoperation. • Registry standards efforts. • Conference 2003–Demonstrate interoperability. • Standards, software, practice

3. Registries • Using this term loosely, there are several types of registries in the area of data management and interchange. • The registries have some related (overlapping?) content, which is extended and utilized in different ways. • The registries vary according to the intended purpose, granularity of contents, the level of semantics management.

4. Software Component Registries ISO 11179Registries Common Content OASIS/ebXMLRegistries UDDIRegistries Common Content Common Content Common Content OntologicalRegistries Common Content Database Catalogs CASE Tool Repositories Common Content Common Content Types of Registries

5. Types of Registries • OASIS/ebXML XML Registries – XML Artifacts • Register XML Artifacts - Includes schemas and DTDs. XML schema relate to a paper form, EDI document, or reporting requirement. • Emphasis on syntactic (structure) information. • ISO 11179 Metadata Registries – Data Semantics • Register Data Elements, components of data elements and groups of data elements. For example, country codes for customer place of residence. Includes: data element concepts, data elements (including representation), value domains, and (multiple) taxonomies. • Emphasis on semantic information such as definitions of data elements and value meanings, and stewardship responsibilities. • Universal Description, Discovery, and Integration (UDDI) Registries – Web-based Business Services • A White page directory of the business activities of firms. • Emphasis on interface specifications.

6. Types of Registries(continued) • Database System Registries (System Catalogs/Data Dictionaries/ Repositories) – Schema, integrity & operational info. • Includes all elements of database schemas: data elements, relations, integrity constraints. • Emphasis on information required to make database systems work for queries, etc., not on semantic management. • Case Tool Registries (Encyclopedias/Repositories) – Data model and application program logic • Includes information needed to create a database and potentially the program code for a system. Contains database schemas. • Emphasis not on semantic management. • Ontological Registries – Concept Structures • Includes relations among concepts (subsumption, inheritance,…) and axioms for inference among concepts, e.g., temporal/spatial reasoning, etc. • Emphasis is on semantics.

7. Types of Registries(continued) • Software Component Registries--Software Components • Reuse software components built on specific vender platforms such as EJB, COM, CORBA IDL etc. • Include basic common elementary objects and object patterns • Emphasis on reusability of software component to build flexible and standardized business systems.

8. Software Component Registries Common Content RegistriesExample of Common Content Database Catalogs Common Content ISO 11179Registries UDDIRegistries Common Content Common Content Country Name OASIS/ebXMLRegistries CASE Tool Repositories Common Content Common Content OntologicalRegistries Common Content

9. RegistriesManagement of Common Content Overlapping content presents the usual multiple entry, synchronization, and maintenance problems for users. Data management must also accommodate differences in data representation

10. Name: Country Identifiers Context: Definition: Unique ID: 5769 Conceptual Domain: Maintenance Org.: Steward: Classification: Registration Authority: Others DataElementConcept Algeria Belgium China Denmark Egypt France . . . Zimbabwe Example of Common ContentCountry Identifier Data Elements Algeria Belgium China Denmark Egypt France . . . Zimbabwe L`Algérie Belgique Chine Danemark Egypte La France . . . Zimbabwe DZ BE CN DK EG FR . . . ZW DZA BEL CHN DNK EGY FRA . . . ZWE 012 056 156 208 818 250 . . . 716 Name: Context: Definition: Unique ID: 4572 Value Domain: Maintenance Org. Steward: Classification: Registration Authority: Others ISO 3166 3-Alpha Code ISO 3166 English Name ISO 3166 French Name ISO 3166 2-Alpha Code ISO 3166 3-Numeric Code

11. Software Component Registries Common Content RegistriesExample of Common Content Database Catalogs Common Content ISO 11179Registries UDDIRegistries Table Column Data Element Common Content Common Content Business Specification Country Name OASIS/ebXMLRegistries CASE Tool Repositories XML Tag Attribute Common Content Common Content TermHierarchy OntologicalRegistries Business Object Common Content

12. Data Element List – Address Group 33c Name Street Address City, State Postal Code Country ISO 11179 Registry <?xml version="1.0"?> <shipTo > <name>Alice Wilson</name> <street>161 North Street</street> <city>Happy Valley</city> <state>MO</state> <zip>63105</zip> <country code>USA</country code> </shipTo>

13. OASIS/ebXML XML Registry <?xml version="1.0"?> <shipTo > <name>Alice Wilson</name> <street>161 North Street</street> <city>Happy Valley</city> <state>MO</state> <zip>63105</zip> <country code>USA</country code> </shipTo> Repository VI304 Dollars X12 UnitPrice EDIFACT ListPrice Collaboration Partner #1 Collaboration Partner #2 Currency <Rep href= “http://www.disa.mil”>DISA</Rep> <ELEMENTrep= ‘DISA’name=‘Country’Biz =‘VI304’ > Schema or Template <Rep href= “http://www.disa.mil”>DISA</Rep> <ELEMENTrep= ‘DISA’name=‘CntryCode’Biz =‘VI304’ > Schema or Template XML Instance XML Instance <Country>JPN</Country> <CntryCode>JPN</CntryCode>

14. UDDI Registry <?xml version="1.0"?> <shipTo> <name>Alice Wilson</name> <street>161 North Street</street> <city>Happy Valley</city> <state>MO</state> <zip>63105</zip> <country code>USA</country code> </shipTo> Business-to-Business

15. Case Tool Repository

16. Database Catalog

17. Concept Concept Concept Concept Geographic Area Geographic Sub-Area Country Country Identifier Country Name Country Code ISO 3166 2-Character Code ISO 3166 3- Character Code Short Name Long Name Mailing Address Country Name ISO 3166 3-Numeric Code FIPS Code Distributor Country Name Ontological Registry

18. An Example of Software Component Registry

19. Needs for Registry Interoperation ebXML Registry EAN Registry RosettaNet Registry Business Category GCI Registry CPFR Registry Component Registry Business Negotiation UDDI Consumer Profile Vender Catalog Shipper Catalog System Development Production Planning CALS Customer Support PDES/STEP Registry Shipping Manufacturing

20. Consolidation or Interoperation?(continued) • Does one registry acquire all of the key functionalities? • Do distinct capabilities require multiple registries with interoperability?

21. Ontological Registry ISO 11179 Metadata Registry CASE Tool Encyclopedia Database Catalog (e.g., SQL) OASIS/ebXML XML Registry UDDI Consolidation or Interoperation?

22. Ontological Registry ISO 11179 Metadata Registry CASE Tool Encyclopedia UDDI Database Catalog (e.g., SQL) OASIS/ebXML XML Registry Consolidation or Interoperation?

23. Ontological Registry ISO 11179 Metadata Registry CASE Tool Encyclopedia Database Catalog (e.g., SQL) OASIS/ebXML XML Registry UDDI Consolidation or Interoperation?

24. Ontological Registry ISO 11179 Metadata Registry CASE Tool Encyclopedia Database Catalog (e.g., SQL) OASIS/ebXML XML Registry UDDI Consolidation or Interoperation?

25. Software Component Registries ISO 11179Registries Common Content OASIS/ebXMLRegistries UDDIRegistries Common Content Common Content Common Content OntologicalRegistries Common Content Database Catalogs CASE Tool Repositories Common Content Common Content Interoperation of Registries Interoperation

26. A Look at theDevelopment Efforts How can we work toward interoperability? • Standards developers • Software developers • Practitioners

27. XML Registry Efforts • OASIS Registry/Repository Specification • OASIS and ebXML have merged into a single OASIS Technical Committee chaired by NIST. • OASIS specifications strength is in its classification capabilities. Associations among objects make it easy to compare versions of similar objects. • OASIS allows organizations to register, classify, capture associations and dependencies, and record additional metadata for their objects of choice. • XML interface provides easy access. Members can exchange information with one another. • Major advantage is that the interface can remain stable for each interchange partner.

28. XML Registry Efforts(continued) • OASIS Registry/Repository Specification (continued) • Registered objects associated with two pieces of information: • An electronic file consisting of a specific digital instance. The file containing the registered object is maintained by a repository. • Metadata for naming, describing, and locating the registered object and identifying its associations and relationships with other objects. The metadata is maintained by the registry. • Registry and repository are tied together in that the metadata includes a globally unique locator for a file. • Benefits of storing metadata in a registry include: reuse of data and metadata, efficient version control, unified understanding of registered objects, and promotion of consistency across organizational areas. • May be a driving force in commercial implementations that are interoperable between trading partners and meet government needs.

29. Public XML Schema Repository Company X 1 4 Company Z 3 3 2 1 2 4 Speaking the Same Language Company X publishes an XML Schema in a public repository. Company Z retrieves XML Schema from repository and generates XML document from it. Company Z sends XML document to Company X over shared communications link. Company X verifies correctness of received XML document by checking it against well-known Schema. XML Schema provides cross-organizational XML document interoperability.

30. Metadata Registry Efforts • ISO/IEC 11179 – Metadata Registries Background • Specifies basic aspects of the kind and quality of metadata necessary to describe data, and the management and administration of that metadata in a metadata registry. • Applies to the formulation of data representations, meanings, and relationships between them to be shared, independent of the organization that produces the data. • Focuses on semantics (the meaning of data) and management of semantic change. • Does not apply to the physical representation of data as bit and bytes; metadata refers to descriptions of other data.

31. Metadata Registry Efforts (continued) • Major aspects of ISO/IEC 11179 family of international standards apply to activities including: • The definition, specification and contents of data element dictionaries or data registries, including interchanging or referencing among various collections of data elements. • The design and specification of application-oriented data models, databases and message types for data interchange. • The actual use of data in communications and information processing systems. • Interchanging or referencing among various collections of data elements. • Major implementations for ISO/IEC exist for environment, healthcare, intelligent transportation system, aviation, demographic and other programmatic areas. • The desire is to make these metadata registries interoperate with XML registries, with the 11179 registries handling deeper levels of semantic management.

32. country

35. Business Registry Efforts • UDDI effort defines a set of specifications making business accelerate use of B2B and commerce over the Internet easier. • This direct application-to-application integration is a core building block of the digital economy and will help reduce many of the configuration and compatibility problems. • UDDI is based on existing Internet standards and is platform and implementation neutral. • A formal standard is expected. Specification may have relevance to XML and metadata registries that could be registered in UDDI registries.

36. Database Catalog Efforts • SQL has the concept of a catalog • Has info that database needs to operate • Not necessarily sharable • SQL has concept of Schema • Metadata accessible by SQL • Relational systems may have a “dictionary”, but not specified by a standard • Area of possible coordination between SC 32 WGs

37. CASE Tool Repository Efforts • There are several proprietary encyclopedia/repository products. • Difficult to specify common model • SC 7/WG 11 & CDIF (CASE Tool Interchange Format committee) have established a common core of content and an interchange specification • OMG: UML metamodel describes UML Objects, the Meta Object Facility (MOF) provides a container & XMI provides for metadata transfer • OMG: UML Profile (set of stereotypes for particular domain

38. Software Component Registry Efforts • Commercial base software component registries are available in the market. Flashline.com, ComponentAA, ComponentSquar.com • Sometime, those components are called Business Objects • Software components are developed and reused among specific vender platforms, such as EJB (Enterprise Java Beans), COM, CORBA with their own manner • No common framework is available so far, to share components among registries

39. Interoperability • Interoperability approaches • Standards developers • Liaison between Standards committees. • Software developers • Interoperability conformance testing. • Practioners • Single points of data entry, interchange between software.

40. Four General Registry AreasA Work in Progress Work with NIST and others in the XML Working Group to prepare report covering registries including descriptions of: • Discovery mechanisms. • Repositories of XML artifacts. • Semantic registries–Business content mapping. • Application Program Interfaces (APIs).

41. ebXML Interface Service ebXML Transport Layer 11179 - OASIS/ebXML Integration Approach Data Semantic Content ISO 11179 Registry Classifications Associations Extractor Marked content domain for extraction Classification synchronization XML Interface Service XML Syntactic Content ebXML Registry Classifications Associations

42. Publisher Joint Common Catalog Subscriber (White Pages) (Yellow Pages) (Brown Pages) ISO/IEC 11179 + other Access Metadata Information Metadata (Green Pages) Run-Time i.e., Security, Required Technologies, APIs, etc. i.e., Ontologies, Taxonomies, Models, etc. Build-Time (Brown Pages) (Green Pages) UDDI and Metadata Registry Interoperability

43. What is it we need to interoperate? • A business object framework for the common content and how the registries might interoperate. (ebXML, UN-CEFACT, OMG, CBOP, SC 32)

44. ISO 11179Registries OASIS/ebXMLRegistries UDDIRegistries Common Content Common Content Common Content OntologicalRegistries Common Content Database Catalogs CASE Tool Repositories Common Content Common Content For the Interoperability of Registries Metamodel Framework for Business Object Registries Metamodel Framework Business Object Registry

45. ISO 11179Registries OASIS/ebXMLRegistries UDDIRegistries Common Content Common Content Common Content OntologicalRegistries Registry Common Content Database Catalogs Common Contents Terminologies Codes Ontologies Object Patterns CASE Tool Repositories Common Content Common Content Close Look at Metamodel Framework for the Interoperability Meta-meta model Metamodel for Registering Constructs Metamodel for Mapping

46. Software Component Registry Common Content ISO 11179Registries OASIS/ebXMLRegistries UDDIRegistries Common Content Common Content Common Content OntologicalRegistries Common Content Database Catalogs CASE Tool Repositories Common Content Common Content For the Interoperability of registries Metamodel FW Business Object Registry

47. Software Component Registries ISO 11179Registries Common Content OASIS/ebXMLRegistries UDDIRegistries Common Content Common Content Common Content OntologicalRegistries Common Content Database Catalogs Common Contents CASE Tool Repositories Terminologies Codes Ontologies Object Patterns Common Content Common Content Close look at Metamodel Framework for the Interoperability Meta-meta model Metamodel for Registering constructs Metamodel for Mapping Registry

48. Metamodel Framework Standard Identification & Classification Scheme Terminology & Ontology Meta-meta model Standard Modeling Constructs Standard Modeling Constructs Standard Value Domain Standard Value Domain Meta models Common Meta models Standard Modeling Facility Metamodel Framework Local metamodel Local metamodel Local metamodel Registry A Registry B Registry C Registry Federation User

49. Conference 2003Open Forum • Major topic: Interoperability of registries • Participants: • Standards developers. • Software developers. • Practitioners. • Related topics: • Tutorials on the standards. • Tracks for application areas: Environment, Transportation, Healthcare, Energy, Aeronautics & Space, Demographics, … Conference is intended to encourage progress toward interoperability and showcase progress made.

50. Discussion Bruce Bargmeyer BEBargmeyer@lbl.gov