Post on 26-Dec-2015
WG2 Tutorial
ISO/JTC1/SC32
Larry Fitzwater(202) 260-3071fitzwater.larry@epa.gov
SDC-0002-021-JE-4029
2
SDC-0002-021-JE-4029
WG 2 Areas of Focus
Metadata Registries. IT Enablement. Metamodel Framework. Conceptual Graphs and Knowledge
Interchange Format.
3
SDC-0002-021-JE-4029
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.
4
SDC-0002-021-JE-4029
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
SDC-0002-021-JE-4029
Types of Registries
Common Content
OASIS/ebXMLRegistries
Common Content
ISO 11179Registries
Common Content
OntologicalRegistries
Common Content
DatabaseCatalogs
Common Content
CASE ToolRepositories
Common Content
UDDIRegistries
SoftwareComponentRegistries
Common Content
6
SDC-0002-021-JE-4029
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
SDC-0002-021-JE-4029
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
SDC-0002-021-JE-4029
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
SDC-0002-021-JE-4029
RegistriesExample of Common Content
Common Content
OASIS/ebXMLRegistries
Common Content
ISO 11179Registries
Common Content
OntologicalRegistries
Common Content
CASE ToolRepositories
Common Content
UDDIRegistries
CountryName
SoftwareComponentRegistries
Common Content
Common Content
DatabaseCatalogs
10
SDC-0002-021-JE-4029
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
SDC-0002-021-JE-4029
Data Elements
DZ
BE
CN
DK
EG
FR
. . .
ZW
ISO 3166English Name
ISO 31663-Numeric Code
012
056
156
208
818
250
. . .
716
ISO 31662-Alpha Code
Algeria
Belgium
China
Denmark
Egypt
France
. . .
Zimbabwe
Name:Context:Definition:Unique ID: 4572Value Domain:Maintenance Org.Steward:Classification:Registration Authority:Others
ISO 3166French Name
L`Algérie
Belgique
Chine
Danemark
Egypte
La France
. . .
Zimbabwe
DZA
BEL
CHN
DNK
EGY
FRA
. . .
ZWE
ISO 31663-Alpha Code
Example of Common ContentCountry Identifier
Algeria
Belgium
China
Denmark
Egypt
France
. . .
Zimbabwe
Name: Country IdentifiersContext:Definition:Unique ID: 5769Conceptual Domain:Maintenance Org.:Steward:Classification:Registration Authority:Others
DataElementConcept
12
SDC-0002-021-JE-4029
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>
ISO 11179 Registry
33c
NameStreet AddressCity, State Postal CodeCountry
13
SDC-0002-021-JE-4029
OASIS/ebXML XML Registry
<Country>JPN</Country>
VI304
List PriceCurrency
Dollars
XML Instance
Unit Price
XML Instance
<CntryCode>JPN</CntryCode>
Collaboration
Partner #1
X12
EDIFACT
<Rep href= “http://www.disa.mil”>DISA</Rep>
<ELEMENT rep= ‘DISA’ name=‘Country’ Biz =‘VI304’ >
<Rep href= “http://www.disa.mil”>DISA</Rep>
<ELEMENT rep= ‘DISA’ name=‘Country’ Biz =‘VI304’ >
Schema or Template
<Rep href= “http://www.disa.mil”>DISA</Rep> <ELEMENT rep= ‘DISA’ name=‘CntryCode’ Biz =‘VI304’ >
<Rep href= “http://www.disa.mil”>DISA</Rep> <ELEMENT rep= ‘DISA’ name=‘CntryCode’ Biz =‘VI304’ >
Schema or Template
Collaboration
Partner #2
<?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
14
SDC-0002-021-JE-4029
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
17
SDC-0002-021-JE-4029
Ontological Registry
Concept Concept
ConceptConcept Geographic Area
Geographic Sub-Area
Country
Country Identifier
Country Name Country Code
Short Name ISO 31662-Character
Code
ISO 31663- Character
Code
Long Name
DistributorCountry Name
Mailing AddressCountry Name ISO 3166
3-Numeric CodeFIPS Code
19
SDC-0002-021-JE-4029
Needs for Registry Interoperation
System Development
PDES/STEP Registry
Manufacturing
UDDI
Component Registry
GCI Registry
EAN Registry
CPFR Registry
RosettaNet Registry
Business Negotiation
Vendor Catalog
Shipper Catalog
Business Category
Shipping
Customer Support
CALS
Production Planning
Consumer Profile
ebXML Registry
20
SDC-0002-021-JE-4029
Consolidation or Interoperation?
Does one registry acquire all of the key functionalities?
Do distinct capabilities require multiple registries with interoperability?
21
SDC-0002-021-JE-4029
UDDIOASIS/ebXMLXML Registry
ISO 11179MetadataRegistry
OntologicalRegistryDatabase
Catalog (e.g., SQL)
Consolidation or Interoperation?(continued)
CASE ToolEncyclopedia
25
SDC-0002-021-JE-4029
Interoperation of Registries
Common Content
OASIS/ebXMLRegistries
Common Content
ISO 11179Registries
Common Content
OntologicalRegistries
Common Content
DatabaseCatalogs
Common Content
CASE ToolRepositories
Common Content
UDDIRegistries
Interoperation
SoftwareComponentRegistries
Common Content
26
SDC-0002-021-JE-4029
A Look at theDevelopment Efforts
How can we work toward interoperability? Standards developers. Software developers. Practitioners.
27
SDC-0002-021-JE-4029
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
SDC-0002-021-JE-4029
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
SDC-0002-021-JE-4029
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.
1
2
3
4
Company X
Company Z
Public XMLSchema
Repository1
2
4
3
XML Schema provides cross-organizational XML document interoperability.
30
SDC-0002-021-JE-4029
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
SDC-0002-021-JE-4029
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.
35
SDC-0002-021-JE-4029
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
SDC-0002-021-JE-4029
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
SDC-0002-021-JE-4029
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).
38
SDC-0002-021-JE-4029
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
SDC-0002-021-JE-4029
Interoperability
Interoperability approaches. Standards developers.
Liaison between standards committees. Software developers.
Interoperability conformance testing. Practitioners.
Single points of data entry, interchange between software.
40
SDC-0002-021-JE-4029
Four General Registry AreasA Work in Progress
Discovery mechanisms. Repositories of XML artifacts. Semantic registries–Business content mapping. Application Program Interfaces (APIs).
Work with NIST and others in the XML Working Group to prepare report covering registries including descriptions of:
41
SDC-0002-021-JE-4029
11179 - OASIS/ebXML Integration Approach
ISO 11179Registry
Extractor
XML Interface Service
ebXMLRegistry
ebXML Transport Layer
DataSemanticContent
ClassificationsAssociations
Marked content domain for extractionClassification synchronization
XMLSyntactic Content
ClassificationsAssociations
ebXML Interface Service
42
SDC-0002-021-JE-4029
UDDI and Metadata Registry Interoperability
(White Pages)
(Yellow Pages)
(Green Pages)
Publisher
Subscriber
(Brown Pages) (Green Pages)
Run-TimeBuild-Time
InformationMetadata
i.e., Ontologies, Taxonomies,Models, etc.
AccessMetadata
i.e., Security, Required
Technologies, APIs, etc.
(Brown Pages)ISO/IEC 11179
+ other
JointCommonCatalog
43
SDC-0002-021-JE-4029
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
SDC-0002-021-JE-4029
For the Interoperability of Registries
Common Content
OASIS/ebXMLRegistries
Common Content
ISO 11179Registries
Common Content
OntologicalRegistries
Common Content
DatabaseCatalogs
Common Content
CASE ToolRepositories
Common Content
UDDIRegistries
Meta-model FW
Business Object Registry
Software Component
Registry
Software Component
RegistryCommon Content
45
SDC-0002-021-JE-4029
Close look at Meta-model Framework for the Interoperability
Meta-model for Mapping
Meta-model for
Registering constructs
Common Contents
Terminologies
Codes
Ontologies
Object PatternsCommon Content
OntologicalRegistries
Common Content
CASE ToolRepositories
Common Content
UDDIRegistries
Common Content
OASIS/ebXMLRegistries
Common Content
ISO 11179Registries
Common Content
DatabaseCatalogs
Registry
SoftwareComponentRegistries
Common ContentMeta-meta model
46
SDC-0002-021-JE-4029
Meta-model Framework
Registry A
User
Registry B Registry C
Local meta-model
RegistryFederation
Standard Value
Domain
Standard Modeling Facility
Standard Identification & Classification
Scheme
Meta-models
Standard Value
Domain
Meta-meta-model
Common Meta-models
Meta-model FrameworkTerminology &
Ontology
Local meta-model Local meta-model
Standard Modeling Constructs
Standard Modeling
Constructs
47
SDC-0002-021-JE-4029
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.