# Presentation: 273872

## Re: MMF Ontology Registration,ODM, Inference Web and (X)MDR

**OKABE, Masao**
**Corporate Systems Department, Tokyo Electric Power Co., Inc.**
**2005.7.15**

## Use-case: MMF+ODM to Support Inference Web and Explanation Systems 

- 東京電力株式会社・システム企画部・岡部雅夫

- 2005-07-15

## Our understanding of XMDR (1 of 3)

- XMDR is a registry that can register all kind of ontologies, including their contents.
- But, it seems that MDR is a registry for data items, and it is difficult  to extend it to XMDR for all kind of ontologies, including their contents.
- An Ontology here is not limited to a taxonomy of concepts (or data items).
- That means an ontology may contain definitions of concepts and assertions(axioms) related to  individuals
- For example, how can the following sentences be registered in XMDR?
- Example1 (a definition of a concept)
- A mother is a woman who has a person as a child.
- or in DL,  Mother WomanhasChild.Person
- Example2 (an assertion related to individulas)
- There exists a red car.
- or in KIF, exist ?Car ( and (Car ?Car) (hasColor ?Car red) (Color red)))
- or in DL, hasColor.Car Color(red)
- Main extension point of XMDR, compared to MDR, seems to lie in (X)MDR Part2: Semantics (<= Classification schemes)  to support registering a taxonomy of concepts (or data items) as a subclass of Administered_Item.
- But its WD (SC32N1298 dated 2005-04-19) looks different.
- 	It is MDR specifications in OWL.
- 							(continued on next slide)

- 東京電力株式会社・システム企画部・岡部雅夫

- 2005-07-15

## Our understanding of XMDR (2 of 3)

- Main extension of XMDR, compared to MDR, seems to lie in (X)MDR Part2: Semantics (<= Classification schemes)  to support registering a taxonomy of concepts (or data items) as a subclass of Administered_Item.
- But its WD (SC32N1298 dated 2005-04-19) looks MDR specifications in OWL.

- 東京電力株式会社・システム企画部・岡部雅夫

- 2005-07-15

## Our understanding of XMDR (3 of 3)

- What XMDR actually looks like is to define MDR by owl (and CL), rather than UML and to be implemented in RDF.
- BEB: Issue: make the P3 UML model MOF compliant – need to remove the association classes and possibly other adjustments.
- P2 issue: Make the OWL and CL rendering MOF (ODM) compliant. (With mappings to ODM). Visualized version as informative annex.
- But this is a different issue.
- By what ever MDR is defined by UML, OWL, CL , MOF etc, MDR is MDR and essentially the same .
- see XMDR OWL ontology for ISO 11179 at _[http://hpcrd.lbl.gov/SDM/XMDR/ont/iso11179-3v2.owl](http://hpcrd.lbl.gov/SDM/XMDR/ont/iso11179-3v2.owl)_
- 	and XML schema for ISO 11179 Part 3, Edition 2 at _[http://](http://hpcrd.lbl.gov/SDM/XMDR/doc/index.html)__[hpcrd.lbl.gov/SDM/XMDR/doc/index.html](http://hpcrd.lbl.gov/SDM/XMDR/doc/index.html)_
- 	for details.
- also see an example from the new prototype of XMDE on the next two slides

- 東京電力株式会社・システム企画部・岡部雅夫

- 2005-07-15

## An example from a new XMDR prototype (1 of 2)

- <?xml version="1.0" encoding="UTF-8" ?>
- <Concept xmlns="http://hpcrd.lbl.gov/SDM/XMDR/ont/xmdr_2005-06-22.owl#" xmlns:tr="http://xmdr.org/translation/" xmlns:lgCon="http://LexGrid.org/schema/2004/02/LexGrid/concepts" xmlns:lgCommon="http://LexGrid.org/schema/2004/02/LexGrid/commonTypes" xmlns:lgCS="http://LexGrid.org/schema/2004/02/LexGrid/codingSchemes" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" rdf:about="" xml:base="http://erdos.lbl.gov/xmdr2/data/CS-NCI+Thesaurus_05.03f/C16698.xml">
- <source rdf:resource="../CS-NCI+Thesaurus_05.03f.xml" />
- <identifier rdf:parseType="Resource">
- <string rdf:datatype="http://www.w3.org/2001/XMLSchema#string">C16698</string>
-  </identifier>
- <**terminologicalEntry** rdf:parseType="Resource">
- <entryContext rdf:resource="CXT-default.xml" />
- <section rdf:parseType="Resource">
- <**language** rdf:datatype="http://www.w3.org/2001/XMLSchema#string">en</language>
- <**designation** rdf:parseType="Resource">
-  <name xml:lang="en">Human Genetics</name>
-   </designation>
- <**designation** rdf:parseType="Resource">
-  <name xml:lang="en">Human Genetics</name>
-   </designation>
- </section>
- </terminologicalEntry>
- </Concept>

- see  _[http://erdos.lbl.gov/xmdr2/](http://erdos.lbl.gov/xmdr2/)__  for  details_

- 東京電力株式会社・システム企画部・岡部雅夫

- 2005-07-15

## An example from a new XMDR prototype (2 of 2)

- But, this is just an example of some part of the Naming and Definition Region of MDR Part3, implemented in RDF.

- 東京電力株式会社・システム企画部・岡部雅夫

- 2005-07-15

## Re: Four quadrants of MDR (1 of 4)

- This seems one of the main ideas of MDR.
- Each of the 4 metaclasses are a subclass of ‘Administered Item’.

- 東京電力株式会社・システム企画部・岡部雅夫

- 2005-07-15

## Re: Four quadrants of MDR (2 of 4)

- Let’s think about an data item ‘employee_nationality_code’ that is represented by ISO3166 country code.
- This data item can be decomposed (or structured) as follows;

- Note: Role names are omitted just for symplification.

- 東京電力株式会社・システム企画部・岡部雅夫

- 2005-07-15

## Re: Four quadrants of MDR (3 of 4)

-  					 is a Data_Elemant.
-  			 is a Data_Element_Concept.
-  	is a Conceptual_Domain.
-  		  is a Value_Domain.
- Note
- Data_Element_Concept may consists of one class or more than two classes, rather than two classes.

- Nation

- ISO3166 Code

- 東京電力株式会社・システム企画部・岡部雅夫

- 2005-07-15

## Re: Four quadrants of MDR (4 of 4)

-  This scheme works for data items but redundantly and insufficiently.
- Redundantly: The structure of 				         enough.
*Question*
***How can this scheme be applied to ontologies?***

- 東京電力株式会社・システム企画部・岡部雅夫

- 2005-07-15

## Concept

**Concept**

**Sign**

**Object**

**Relation to Meaning Triangle (1 of 2)**

**trout**
***Salmo trutta***
**brown trout**
**truite**

- any of several game fishes of the genus *Salmo*, related to the salmon...

- This is the diagram MDR people often use.
- Elements of Terminology

- 東京電力株式会社・システム企画部・岡部雅夫

- 2005-07-15

## Relation to Meaning Triangle (2 of 2)

- Some MDR people (?) say
- 	the MDR 4 quadrants correspond to
- 	the meaning triangle as follows.

- But, it seems that they are different pictures.

- 東京電力株式会社・システム企画部・岡部雅夫

- 2005-07-15

- Thank you!

- 東京電力株式会社・システム企画部・岡部雅夫

- 2005-07-15