WG2%20Tutorial%20ISO/JTC1/SC32 - PowerPoint PPT Presentation

About This Presentation
Title:

WG2%20Tutorial%20ISO/JTC1/SC32

Description:

WG2 Tutorial ISO/JTC1/SC32 Larry Fitzwater (202) 260-3071 fitzwater.larry_at_epa.gov SDC-0002-021-JE-4029 – PowerPoint PPT presentation

Number of Views:155
Avg rating:3.0/5.0
Slides: 46
Provided by: engl246
Learn more at: https://jtc1sc32.org
Category:

less

Transcript and Presenter's Notes

Title: WG2%20Tutorial%20ISO/JTC1/SC32


1
WG2 TutorialISO/JTC1/SC32
Larry Fitzwater (202) 260-3071 fitzwater.larry_at_epa
.gov
SDC-0002-021-JE-4029
2
WG 2 Areas of Focus
  • Metadata Registries.
  • IT Enablement.
  • Metamodel Framework.
  • Conceptual Graphs and Knowledge Interchange
    Format.

3
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 solutionRegistry interoperation.
  • Registry standards efforts.
  • Conference 2003Demonstrate interoperability.
  • Standards, software, practice.

4
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.

5
Types of Registries
6
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 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.
  • 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.

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

8
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.

9
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
Software Component Registries
Common Content
Common Content
10
Registries Management 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.

11
Example of Common ContentCountry Identifier
Data Elements
DZ BE CN DK EG FR . . . ZW
012 056 156 208 818 250 . . . 716
Algeria Belgium China Denmark Egypt France . .
. Zimbabwe
LAlgérie Belgique Chine Danemark Egypte La
France . . . Zimbabwe
DZA BEL CHN DNK EGY FRA . . . ZWE
Name Context Definition Unique ID 4572 Value
Domain Maintenance Org. Steward Classification
Registration Authority Others
ISO 3166 English Name
ISO 3166 3-Numeric Code
ISO 3166 2-Alpha Code
ISO 3166 French Name
ISO 3166 3-Alpha Code
12
ISO 11179 Registry
lt?xml version"1.0"?gt ltshipTo
gt ltnamegtAlice Wilsonlt/namegt
ltstreetgt161 North
Streetlt/streetgt ltcitygtHappy
Valleylt/citygt
ltstategtMOlt/stategt
ltzipgt63105lt/zipgt ltcountry
codegtUSAlt/country codegt
lt/shipTogt
13
OASIS/ebXML XML Registry
lt?xml version"1.0"?gt ltshipTo
gt ltnamegtAlice Wilsonlt/namegt
ltstreetgt161 North
Streetlt/streetgt ltcitygtHappy
Valleylt/citygt
ltstategtMOlt/stategt
ltzipgt63105lt/zipgt ltcountry
codegtUSAlt/country codegt
lt/shipTogt
REPOSITORY
VI304
Dollars
X12
Unit Price
EDIFACT
List Price
Collaboration Partner 1
Collaboration Partner 2
Currency
ltRep href http//www.disa.milgtDISAlt/Repgt
ltELEMENT rep DISA nameCountry Biz
VI304 gt
Schema or Template
Schema or Template
ltRep href http//www.disa.milgtDISAlt/Repgt
ltELEMENT rep DISA nameCntryCode Biz
VI304 gt
XML Instance
XML Instance
ltCountrygtJPNlt/Countrygt
ltCntryCodegtJPNlt/CntryCodegt
14
UDDI Registry
lt?xml version"1.0"?gt ltshipTogt
ltnamegtAlice Wilsonlt/namegt
ltstreetgt161 North
Streetlt/streetgt ltcitygtHappy
Valleylt/citygt
ltstategtMOlt/stategt
ltzipgt63105lt/zipgt ltcountry
codegtUSAlt/country codegt
lt/shipTogt
Business-to-Business
15
Case Tool Repository
16
Database Catalog
17
Ontological Registry
18
An Example of Software Component Registry
19
Needs for Registry Interoperation
ebXML Registry
Business Category
EAN Registry
RosettaNet Registry
GCI Registry
CPFR Registry
Component Registry
Business Negotiation
UDDI
Consumer Profile
Vendor Catalog
Shipper Catalog
System Development
Production Planning
CALS
Customer Support
PDES/STEP Registry
Shipping
Manufacturing
20
Consolidation or Interoperation?
  • Does one registry acquire all of the key
    functionalities?
  • Do distinct capabilities require multiple
    registries with interoperability?

21
Consolidation or Interoperation? (continued)
22
Consolidation or Interoperation? (continued)
23
Consolidation or Interoperation? (continued)
24
Consolidation or Interoperation? (continued)
25
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
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 bits 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 and with the
    11179 registries handling deeper levels of
    semantic management.

32
country
SDC-0002-021-JE-4029
33
SDC-0002-021-JE-4029
34
(No Transcript)
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 betweenSC 32 WGs.

37
CASE Tool Repository Efforts
  • There are several proprietary encyclopedia/reposit
    ory 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).

38
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.

39
Interoperability
  • Interoperability approaches.
  • Standards developers.
  • Liaison between standards committees.
  • Software developers.
  • Interoperability conformance testing.
  • Practitioners.
  • 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 registriesBusiness content mapping.
  • Application Program Interfaces (APIs).

41
11179 - OASIS/ebXML Integration Approach
Data Semantic Content
ISO 11179 Registry
Classifications Associations
Extractor
Marked content domain for extraction Classificatio
n synchronization
XML Interface Service
XML Syntactic Content
ebXML Registry
Classifications Associations
42
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 (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 32.

44
For the Interoperability of Registries
45
Close look at Meta-model Framework for the
Interoperability
Software Component Registries
Common Content
Meta-meta model
Meta-model for Registering constructs
Meta-model for Mapping




Registry
46
Meta-model Framework
Meta-model Framework
Standard Identification Classification Scheme
Terminology Ontology
Meta-meta-model
Standard Modeling Constructs
Meta-models
Standard Value Domain
Common Meta-models
Standard Modeling Constructs
Standard Value Domain
Standard Modeling Facility
Local meta-model
Local meta-model
Local meta-model
Registry A
Registry B
Registry C
RegistryFederation
User
47
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,

The Conference intends to encourage progress
toward interoperability and showcase progress
made.
48
Discussion
  • Larry Fitzwater
  • fitzwater.larry_at_epa.gov

SDC-0002-021-JE-4029
Write a Comment
User Comments (0)
About PowerShow.com