ISO/IEC JTC 1/SC 32 N 0722

Transcription

1 ISO/IEC JTC 1/SC 32 N 0722 Date: REPLACES: -- ISO/IEC JTC 1/SC 32 Data Management and Interchange Secretariat: United States of America (ANSI) Administered by Pacific Northwest National Laboratory on behalf of ANSI DOCUMENT TYPE TITLE SOURCE PROJECT NUMBER STATUS REFERENCES ACTION ID. REQUESTED ACTION DUE DATE Other Document (Open) Presentation - WG 2 Tutorial at Victoria Larry Fitzwater FYI Number of Pages 49 LANGUAGE USED DISTRIBUTION English P & L Members SC Chair WG Conveners and Secretaries Douglas Mann, Secretariat, ISO/IEC JTC 1/SC 32 Pacific Northwest National Laboratory *, 901 D Street, SW., Suite 900, Washington, DC, , United States of America Telephone: ; Facsimile; +1; MannD@battelle.org available from the JTC 1/SC 32 WebSite *Pacific Northwest National Laboratory (PNL) administers the ISO/IEC JTC 1/SC 32 Secretariat on behalf of ANSI

2 WG2 Tutorial ISO/JTC1/SC32 Larry Fitzwater (202)

3 WG 2 Areas of Focus Metadata Registries. IT Enablement. Metamodel Framework. Conceptual Graphs and Knowledge Interchange Format. 2

4 Topics to be Covered Registries: A common interest of SC 32 WGs. 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

5 Registries Using this term loosely, there are several types of registries in the area of data management and interchange. The registries have some common, 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

6 Types of Registries Database Catalogs ISO Registries UDDI Registries OASIS/ebXML Registries CASE Tool Repositories Software Component Registries Ontological Registries 5

7 Types of Registries OASIS/ebXML (Organization for the Advancement of Structured Information Standards/electronic business XML) 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 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. UDDI (Universal Description, Discovery, and Integration) Registries Web-based business services. A White page directory of the business activities of firms. Emphasis on interface specifications. 6

8 Types of Registries (continued) Database System Registries (System Catalogs/Data Dictionaries/ Repositories) Schema, integrity & operational information. 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

9 Types of Registries (continued) Software Component Registries Software components. Reuse software components built on specific vendor platforms such as EJB (Enterprise Java Beans), COM, and CORBA IDL(Common Object Request Broker Architecture Interface Definition Language), etc. Include basic common elementary objects and object patterns. Emphasis on reusability of software component to build flexible and standardized business systems. 8

10 Registries Example of Database Catalogs ISO Registries UDDI Registries OASIS/ebXML Registries Country Name CASE Tool Repositories Software Component Registries Ontological Registries 9

11 Registries Management of Overlapping content presents the usual multiple entry, synchronization, and maintenance problems for users. Data management must also accommodate differences in data representation. 10

12 Example of Country Identifier Data Element Concept Name: Country Identifiers Context: Definition: Unique ID: 5769 Conceptual Domain: Maintenance Org.: Steward: Classification: Registration Authority: Others Data Elements Algeria Belgium China Denmark Egypt France... Zimbabwe Name: Algeria Context: Belgium Definition: China Unique ID: 4572 Value Domain: Denmark Maintenance Org. Egypt Steward: France Classification:... Registration Authority: Zimbabwe Others ISO 3166 English Name L`Algérie Belgique Chine Danemark Egypte La France... Zimbabwe ISO 3166 French Name DZ BE CN DK EG FR... ZW ISO Alpha Code DZA BEL CHN DNK EGY FRA... ZWE ISO Alpha Code ISO Numeric Code 11

13 ISO Registry Data Element List Address Group <?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> Name Street Address City, State Postal Code Country 33c 12

14 OASIS/ebXML XML Registry Collaboration Partner #1 REPOSITORY VI304 Dollars X12 Unit Price EDIFACT List Price Currency <?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> Collaboration Partner #2 Schema or Template <Rep href= >DISA</Rep> <ELEMENT rep= DISA name= Country Biz = VI304 > Schema or Template <Rep href= >DISA</Rep> <ELEMENT rep= DISA name= CntryCode Biz = VI304 > XML Instance <Country>JPN</Country> XML Instance <CntryCode>JPN</CntryCode> 13

15 UDDI Registry Business-to-Business <?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> 14

16 Case Tool Repository 15

17 Database Catalog 16

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

19 An Example of Software Component Registry 18

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

21 Consolidation or Interoperation? Does one registry acquire all of the key functionalities? Do distinct capabilities require multiple registries with interoperability? 20

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

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

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

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

26 Interoperation of Registries Database Catalogs ISO Registries UDDI Registries OASIS/ebXML Registries Interoperation CASE Tool Repositories Software Component Registries Ontological Registries 25

27 A Look at the Development Efforts How can we work toward interoperability? Standards developers. Software developers. Practitioners. 26

28 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. 27

29 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. 28

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

31 Metadata Registry Efforts ISO/IEC 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 bits and bytes; metadata refers to descriptions of other data. 30

32 Metadata Registry Efforts (continued) Major aspects of ISO/IEC 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 and with the registries handling deeper levels of semantic management. 31

33 country

34

35 34

36 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. 35

37 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. 36

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

39 Software Component Registry Efforts A lot of actual commercial base software component registries are available in the market. Flashline.com, ComponentAA, ComponentSquar.com Sometimes those components are called Business Objects. Software components are developed and reused among specific vendor platforms, such as EJB, COM, and CORBA with their own manner. No common framework is available so far, to share components among registries. 38

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

41 Four General Registry Areas A 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). 40

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

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

44 What is it we need to interoperate? A business object framework for the common content and how the registries might interoperate: ebxml (electronic business XML). UN/CEFACT (United Nations Centre for Trade Facilitation and Electronic Business). OMG (Object Management Group). CBOP (Consortium for Business Object Promotion). SC

45 For the Interoperability of Registries Software Component Registry ISO Registries Meta-model FW UDDI Registries OASIS/ebXML Registries Business Object Registry CASE Tool Repositories Database Catalogs Ontological Registries 44

46 Close look at Meta-model Framework for the Interoperability Software Component Registries Meta-meta model ISO Registries Meta-model for Registering constructs Meta-model for Mapping UDDI Registries OASIS/ebXML Registries Registry CASE Tool Repositories Database Catalogs s Terminologies Codes Ontologies Object Patterns Ontological Registries 45

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

48 Conference 2003 Open 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, The Conference intends to encourage progress toward interoperability and showcase progress made. 47

49 Discussion Larry Fitzwater