1 Extended Metadata Registry (XMDR) November 2004 Bruce Bargmeyer +1 (510) 495-2905 [email protected] ISO/IEC JTC 1/SC 32/WG 2

1

Extended Metadata Registry (XMDR)

November 2004

Bruce Bargmeyer+1 (510) [email protected]

ISO/IEC JTC 1/SC 32/WG 2

2

Topics

XMDR project direction What, when, who, how

XMDR relationship to WG 2 projects A view of semantics based computing Some specific semantics challenges Some technology choices A preview of issues to be raised for Parts 2 and 3 Frank Olken will describe some of the content and

ontology issues and approaches

3

XMDR Project Direction

Extend the capabilities of 11179 metadata registries to register complex metadata structures (concept structures, terminologies) Ontologies, Graphs, Taxonomies, Thesauri, …

This presentation will use the term “concept structures” as synonymous with “complex metadata structures”

Extend the capabilities of 11179 metadata registries to record correlations and interrelations between data (e.g., data elements & domains) and other concept structures.

Extend the capabilities of 11179 metadata registries to record correlations and interrelations between the various concept structures themselves.

4

XMDR & SC 32/WG 2

Propose draft text for 11179 Part 2, Version 3 Preview November 2004 WG 2 meeting Proposals April 2005 WG 2 meeting

Propose issues for 11179 Part 3, Version 3

Test & demo extended 11179 capabilities in a reference implementation Tests & demo starting March 2005 Register concept structures nominated by

participants

5

XMDR Project Direction

Part of an Interagency/International Cooperation on Ecoinformatics Sponsors & participants: EPA, EEA, USGS, DOD, NCI, Mayo Clinic

Extend semantics management capabilities for ISO/IEC 11179 Produce design for next generation of operational ISO/IEC

11179 registries Test & demo extended 11179 capabilities in a reference

implementation Research, develop, evaluate, adapt, extend, and demonstrate

techniques and technologies for semantics based computing Facilitate early adoption of these technologies

Establish best practices for semantic web and semantic based computing

Forging Semantics Based Computing

6

Project Direction - Ecoinformatics

Information science and information technology for the environment

Sound information as the basis for environmental policy, decisions, and action

Information technology that supports and enables development of sound information

Facilitate interaction with environmental information Human - Computer Computer - Computer

7

People Involved

XMDR Project at LBNL (Ecoinformatics +) LBNL: Bruce Bargmeyer, Frank Olken, Kevin Keck, John

McCarthy (ret. consulting) DOD: Nancy Lawler & Sam Chance EPA: Larry Fitzwater, Howard Tsai, Linda Spencer, William

Sonntag USGS: Gail Hodge (IIA, for USGS) (Lisa Zolly, USGS, is joining

L8) Mayo Clinic: Harold Solbrig NCI: Sherri De Coronado, Denise Warzel

SC 32/WG 2, INCITS-L8 Ashton Computing & Management: Judith Newton Farance Inc. (consulting)

8

XMDR Liaison Activities

OMG Ontology Development Metamodel (ODM) W3C Semantic Web Best Practices and

Deployment Working Group Ecoterm EU Joint Research Center (EDEN-IW) National Science Foundation (Ecoinformatics) Interagency/International Cooperation on

Ecoinformatics

9

Project Direction

What the project is not: An attempt to make 11179 metadata registries

be a development and maintenance facility for every type of concept structure

An attempt to standardize the complete range of terminology servers

10

XMDR Relationship to WG 2 Projects - Introduction

Real World

ModelingTools

Model Artifactsand Exchange

Applications

Methodologies/tools: EDR, NIAM, O-O, RDF, UML, Ontology

CDIF, (UML: MDL, XMI), OWL, CL & SCL (KIF)

SQL (relational), Object, Semantic Web(might be agent based, grids, etc.

Metamodel constructs: CDIF Core, MOF, XML-Schema, RDFS, ODM, OWL, Common Logic (CL)

11

11179 Semantics Management

Real World

ModelingTools


Applications

Methodologies: EDR, NIAM, O-O, RDF, UML, Ontology

CDIF, (UML- MDL, XMI), OWL, CL & SCL (KIF)

SQL, Object, RDF, Semantic Web

Metamodel constructs: CDIF Core, MOF, XML-Schema, RDFS, ODM, OWL, CLMDR Semantics

Management:Data elements,Domains,Concepts, Terms …

12

ISO

ANSIIndustryGov’t

Country

Country changesCZ Czechoslovakia*

CZ Czech Republic**LO Slovakia**

Change

MDR – Keeping Track of the Real World

13

SC 32 Standards & Projects

Real World

ModelingTools


Applications




WG 3 - SQL

Metamodel constructs: CDIF Core, MOF, XML-Schema, RDFS, ODM, OWL, CL

WG 2 - MMF (19763), CL (24707) &MOF PAS submission

WG 2 - MMF (19763), CL (24707) &XMI PAS submission

WG 2 – 11179

WG 2 - 20944

MDR SemanticsManagement:Data elements,Domains,Concepts, Terms …

WG2 - 20943

14

XMDR Focus




WG 3 - SQL

Metamodel constructs: CDIF Core, MOF, XML-Schema, RDFS, ODM, OWL, CL

WG 2 - MMF (19763), CL (24707) &MOF PAS submission

WG 2 - MMF (19763), CL (24707) &XMI PAS submission

XMDR project

XMDR project

XMDR project

Real World

ModelingTools


Applications

WG 2 – 11179Parts 2 & 3

WG 2 - 20944


WG2 - 20943

15

A Current Example

Real World

Modelingtool

Model artifact/exchange

Application OWI Knowledge Server Application

Ontology Works Inc. (OWI)IODE data modeling tool

Domain ontology expressed in Simple Common Logic(based on Draft ISO/IEC 24707


16

Another Current Example

Real World

Modelingtool

Model artifact/exchange

Application

OWI Knowledge Server Application, possibly built on Objectivity as the persistent objectStore (DBMS)

Protégé ontology tool

Domain ontology expressed in As an OWL ontology


17

Semantics Based Computing

What is it? Evolution of semantics management Evolution of technologies that utilize

semantics

18

Semantics based computing

Computation based on the meaning of data rather than on the manipulation of syntactic structures.

19 19

Global Ontology Observation Station

U nit Determinant

Medium

AnalyticalFraction TimeStamp

NERIObservationCharacteristics NERITime

NERIStation

Table(x) Table(y) Table(z) Table(m)

Local Ontology

Local DB Schema

Semantic Mapping

20

Metadata RegistriesSemantics Management Evolution

Initial “data standards”, evolved to stronger semantics management

Common data across information systems (data standards)

Database (schema) integration Data use - metadata Warehouse support – schema and metadata XML support (schema) “Backed into” concept/terminology support

(deeper semantics) Next: Semantics servers -- for semantic web and

semantics based computing

21

Past, Present, … Future?

Lots of users Lots of information systems

Lots of DataSources

UsersUsers

EEA

DOE

DoD

EPAenvironagricultureclimatehuman healthindustrytourismsoilwaterair

123345445670248591308

123345445670248591308

3268082513485038270800002178

3268082513485038270800002178

text data

environagricultureclimatehuman healthindustrytourismsoilwaterair

123345445670248591308

123345445670248591308

3268082513485038270800002178

3268082513485038270800002178

text

ambienteagriculturatiemposalud hunanoindustriaturismotierraaguaaero

123345445670248591308

123345445670248591308

3268082513485038270800002178

3268082513485038270800002178

text data

data

environagricultureclimatehuman healthindustrytourismsoilwaterair

123345445670248591308

123345445670248591308

3268082513485038270800002178

3268082513485038270800002178

text data

Others . . .

ambienteagriculturatiemposalud hunoindustriaturismotierraaguaaero

123345445670248591308

123345445670248591308

3268082513485038

3268082513485038270800002178

text data

22

Data Standards

Avoid a combinatorial explosion of data content, description, and metadata arrangements for information access and exchange. Data standards and metadata registries can help.

23

Data Element ConceptAfghanistan

Belgium

China

Denmark

Egypt

France

Germany

…………

Data ElementsData ElementsAFG

BEL

CHN

DNK

EGY

FRA

DEU

…………

ISO 3166English Name

ISO 31663-Numeric Code

004

056

156

208

818

250

276

…………

ISO 31663-Alpha Code

Afghanistan

Belgium

China

Denmark

Egypt

France

Germany

…………

Name:Context:Definition:Unique ID: 4572Value Domain:Maintenance Org.:Steward:Classification:Registration Authority:Others

Name:Context:Definition:Unique ID: 3820Value Domain:Maintenance Org.:Steward:Classification:Registration Authority:Others

Name:Context: Definition:Unique ID: 1047Value Domain:Maintenance Org.:Steward:Classification:Registration Authority:Others

Name: Country IdentifiersContext:Definition:Unique ID: 5769Conceptual Domain:Maintenance Org.:Steward:Classification:Registration Authority:Others

24

Data_Element_Concept_Relationship

<<Required>> type_description

Non_enumerated_Domain

<<Required>> description

Value_Domain_Relationship

<<Required>> type_description

Enumerated_Domain

Permissible_Value

<<Required>> item<<Required>> begin_date<<Conditional>> end_date

2..n

1..*

+member_of2..n

+specifing1..*

allowed_value

Value_Meaning

<<Required>> identifier<<Optional>> description<<Required>> begin_date<<Conditional>> end_date

2..n

0..*

+contained_in2..n

+containing

0..*

permissib le_value

1..*

0..*

+represented_by

1..*

+representing0..*

permissib le_value_meaning

Conceptual_Domain

<<Optional>> administered_component_information : Administered_Component<<Optional>> dimensionality

0..*0..*

+containing

0..*

comceptual_domain_relationship

+contained_in0..*

1..*

0..*

+containing

1..*

+contained_in

0..*

value_meaning_set

Value_Domain

<<Optional>> administered_component : Administered_Component<<Optional>> name<<Required>> datatype : Datatype<<Optional>> maximum_character_quantity<<Optional>> minimum_character_quantity<<Optional>> format<<Optional>> unit_of_quantity : Unit_of_Quantity

0..*

0..1

+contained_in

0..*

value_domain_relationship

+containing

0..1 0..*

1..1

+representing0..*

+specified_by

1..1

specification

Example

<<Required>> item

Data_Element_Concept

<<Required>> administered_component : Administered_Component<<Optional>> object_class : Object_Class<<Optional>> object_class_qualifier<<Optional>> property : Property<<Optional>> property_qualifier

0..1

0..* +containing0..1

data_element_concept_relationship

+contained_in0..*

1..10..*+specifing

1..1+having

0..*

data_element_concept_conceptual_domain_relationship

Data_Element

<<Required>> administered_component : Administered_Component<<Required>> representation_class : Representation_Class<<Optional>> representation_class_qualifier

0..* 1..1

+represented_with

0..*+providing_representation_for

1..1

representation

1..*

1..*

+represented_by

1..*

+representing1..*

exemplication

0..*

1..1

+providing_representation_to

0..*

+represented_by

1..1

expression

Rule

<<Optional>> administered_component : Administered_Component<<Required>> description

Source_Data_Element

0..*

1..*

+containing

0..*

+contained_in

1..*

derivation_input

0..1

1..1

+is_input_to0..1

+resulting_from

1..1

derivation_output

1..1

0..*

+is_formula_for1..1

+used_by0..*

derivation

Proposal for Comments11179-3 RevisionDD Mann

PAGE 111179-3 METAMODELMain Model

NOTE:

This model represents the logical structure of a registry for data elements and related components that are in a "recorded" or higher registration status.

For UML v1.3 documentation see:ftp://ftp.omg.org/pub/docs/ad/99-06-08.pdf

1999-12-13

AFG

BEL

CHN

DNK

EGY

FRA

DEU

…………

004

056

156

208

818

250

276

…………

Afghanistan

Belgium

China

Denmark

Egypt

France

Germany

…………

25

State Laws

CAA

CWA

RCRA

TSCA

“

“

State Regs

Fed Air Reg

Fed Water Reg

Fed RCRA Reg

Fed TSCA Reg

“

“

SeparateData

Repositories

RegulatedFacility

SeparateRegs/

Procedures

SeparateEnvironmental

MediaLegislation

Then there is one point of access to our environmental data resources:

CompleteWarehouseRepository

RegulatedFacility

Public/Environmental

Regulators/Environmental

Community

June 1996

26

Data and Semantics Management

DictionaryKeyword

Keyword

OntologyOntology TermsTerms

DataDataElementsElements

Thesaurus

DBMS/XML/ Documents

Semantic

Web Concepts

27

ISO/IEC 11179 Metadata Registries

Metadata Registry

Terminology Thesaurus Themes

DataStandards

Ontology GEMET

StructuredMetadata

Evolving toward stronger semantics management

Metadata Registries

Companies

Universities

Agencies

DataServices

SemanticServices

Others

UsersUsers

September 2004

En

viro

nm

enta

l D

ata

Gri

d

Environmental Computer GridHigh Performance, cluster, Personal

Environmental SemanticsGrid

Terminology Thesaurus Ontology Taxonomy

StructuredMetadata

ComputationServices

Software:Models, Visualization, AnalysisAgent systemsSemantic Based Computing

DataStandards

29

Metadata Registries

Companies

Universities

Agencies

DataServices

SemanticServices

Others

UsersUsers

September 2004

En

viro

nm

enta

l D

ata

Gri

d

Environmental Computer GridHigh Performance, cluster, Personal

Terminology Thesaurus Ontology Taxonomy

StructuredMetadata

ComputationServices

Software:Models, Visualization, AnalysisAgent systemsSemantic Based Computing

DataStandards

Environmental SemanticsGrid

30

What is it ? [2]

Semantics based computing: Applications that take the meaning of data into account to direct the processing.

Establish linkage between concepts referenced in text and related data in databases

Semantic Web Support agent-based development of actionable

data, for informed decision making.

31

Some Challenges

Translate the 11179 UML model into an ontology, manually.

Translate the 11179 UML model into an ontology, automated.

Identify emerging technology for building reference implementation, develop architecture

Identify test concept structures and sources Characterize concept structures Identify extensions needed for 11179 Propose extensions needed for 11179

32

Manual TranslationUML 11179 to an Ontology

Use Protégé tool and OWL specification Frank will show tell all about it

33

Automated Translation 11179 UML Metamodel to an OWL Ontology

Part 3 metamodel as Rational Rose UML MDL file

34

ISO/IEC 11179Expressed as an Ontology

<?xml version="1.0" encoding="ISO-8859-1"?><rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xmlns:owl="http://www.w3.org/2002/07/owl#" xmlns="http://www.owl-ontologies.com/unnamed.owl#" xml:base="http://www.owl-ontologies.com/unnamed.owl"> <owl:Ontology rdf:about=""/> <owl:Class rdf:ID="Registrar"> <rdfs:subClassOf rdf:resource="http://www.w3.org/2002/07/owl#Thing"/> <rdfs:subClassOf> <owl:Restriction> <owl:cardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#int" >1</owl:cardinality> <owl:onProperty> <owl:ObjectProperty rdf:ID="contact"/> </owl:onProperty> </owl:Restriction> </rdfs:subClassOf> <rdfs:subClassOf> <owl:Restriction>

35

36

Potential Standards/Technologies

DBMS Object, XML, Relational, RDF/Graph, Logic, Text, Document, Multimedia

Knowledge Representation Web Ontology Language (OWL) Simple Common Logic (SCL)

Middleware/Messaging Cocoon 2, Jini, CoABS, JMS, XMLBlaster, SOAP

XML [Semantic] Web Services Axis, JWSDP

Agent Development ABLE, JADE

Engines/Servers OMS (IBM), Federator/OMS (OWI) Jess

37

Content andContent Characterization

A

B

C

B B

C C C C

Directed Acyclic Graphs, Cyclic, Undirected, …

Frank Olken to tell about this.

38

PreviewSuggested Changes for P2/P3 (cont.)

Issue 1. Make "relation" an administered item. The relationship could be managed as part of the structure in which they are involved. Alternatively, in Clauses 4.10 and 4.11, possibly treat the subject role as an aggregate association. This is an alternative way of administering relationships, more in line with current practice.

39

PreviewSuggested Changes for P2/P3 (cont.)

Issue 2. Rename the "horizontal" role and association names in Clause 4.7.3, Figure 3. E.g., Value_Domain should not have the role "representing" going in two directions. The association name "data_element_representation" may be impacted by the change in role names. Note that the role between the top two boxes is labeled "having" and "specifying", while the role between the bottom two boxes is labeled "represented_by" and "representing". The relationship between the upper two boxes and bottom two should be symmetric. Also, "having" could better be "specified_by". (We also have possible alternate proposals for labels.)

40

Preview of Issues (cont.)

Issue 3: Identify the types of correspondences between concepts. The point is to record the types of overlap between the concepts. An alternative is translation tables, which record pairs of IDs linking concepts without any more specific "type" information.

41

PreviewSuggested Changes for P2/P3

Issue 4. Directed Relationships as replacement to "association" and "related to" in Clauses 4.10 and 4.11. Note that in Clause 4.11, "concept_relation" is directed, but no inverse is specified.

Issue 5. Replace the "string" value to a relation instance. This applies to Clause 4.10:

clasification_scheme_item_relationship_type_description Clause 4.11:data_element_concept_relationship_type_description concept_relationship_type_description

42

Next Year: Proposed

Service Oriented Architecture

43

Eighth International Open Forum on Metadata Registries

Semantic Interoperability: Where Meaning Meets Metadata.

Open Forum 2005

April 11-14, 2005Berlin, Germany

Berlinopenforum.de