Extending the MDR for the Semantic Web Enforcing the MDR for supporting ontology concept - PowerPoint PPT Presentation

1 / 17
About This Presentation
Title:

Extending the MDR for the Semantic Web Enforcing the MDR for supporting ontology concept

Description:

The Ontology Example can be classified into two levels. Class level and Instance level ... Relation information (properties) between instances ... – PowerPoint PPT presentation

Number of Views:43
Avg rating:3.0/5.0
Slides: 18
Provided by: metadatas2
Category:

less

Transcript and Presenter's Notes

Title: Extending the MDR for the Semantic Web Enforcing the MDR for supporting ontology concept


1
Extending the MDR for the Semantic Web-
Enforcing the MDR for supporting ontology concept
-
  • 6 December 2007
  • ISO/IEC SC 32/WG 2 Interim Meeting
  • Seoul, Korea
  • Dongwon Jeong (djeong_at_kunsan.ac.kr), Kunsan
    National University
  • Doo-Kwon Baik (baikdk_at_korea.ac.kr), Korea
    University

2
Motivation and Background
MDR (ISO/IEC 11179)
Environment Change (Semantic Web)
Next?
An Extension of the MDR, which can support the
Semantic Web Concept
3
Motivation and Background (cont.)
  • Semantic Web (SW) and Ontology
  • Semantic Web
  • is recognized as a next generation Web
    (Intelligent Web)
  • To realize the Semantic Web, ontologies (Web
    Ontologies) should be built
  • Web Ontology
  • consists of classes, instances, properties
  • Class Concept, Type
  • Instance Individual, Object
  • Property Relation, Role
  • Ref. Lecture Notes Ontology Languages for the
    Semantic Web, http//www.cs.man.ac.uk/horrocks/Te
    aching/cs646/
  • can be expressed as 3-tuple, ltsubject, predicate,
    objectgt
  • Triple set (Statement set)

4
Motivation and Background (cont.)
  • An Ontology Example
  • Ref. RDF Primer W3C Recommendation 10 February
    2004

nancy
frank
hasMother
fred
Staff
frances
rdfssubClassOf
rdfssubClassOf
Male
Female
rdfssubClassOf
rdfssubClassOf
spencer
Person
author
cook
author
eatCheese
author
author
moveCheese
crisis
Book
5
Motivation and Background (cont.)
  • The Ontology Example can be classified into two
    levels
  • Class level and Instance level

nancy
frank
hasMother
fred
Staff
frances
rdfssubClassOf
rdfssubClassOf
Male
Female
rdfssubClassOf
rdfssubClassOf
spencer
Person
author
cook
author
eatCheese
author
author
moveCheese
crisis
Book
6
Motivation and Background (cont.)
  • MDR Standardization Status
  • ISO/IEC 11179 has been being extended for
    supporting the ontology concept
  • The extension is for support the ontology concept
    at the class level
  • No consideration at the instance level (WG2
    Note This is not true)
  • A Key Region of the Extension Part (ISO/IEC 11179
    CD2, ED. 3)
  • Relations Region

7
Purpose
  • Main Goal of our Proposal
  • Enforcing the current MDR for the Semantic Web by
    managing data at the instance level as well as at
    the concept level
  • This Proposal is
  • to support an ontology registration at the
    instance level as well as at the concept level
  • to endow the MDR to more powerful reasoning
    ability
  • to make it suitable for the Semantic Web
    environment
  • to make it more practical

8
Progress Status
  • Discussion History of the Proposal
  • SC32 Study Periods Meeting, Clearwater, FL,
    February 2007
  • SC32 Plenary and WG Meetings
  • Request for a study period on Extending the
    metadata Registry for the Semantic Web
  • Documents SC32N1659, WG2N1043
  • In this Meeting, SC32/WG2 Interim Meeting
  • More clear scope definition
  • More details of our proposal
  • Metamodels
  • Registration processes
  • Hope to get much more comments

9
Scope Conceptual Model
MDR (Metadata registry)
11179 Ed. 2
To support the ontology concept
11179 Part 3, Ed. 3 (Concepts Properties)
Proposal
Semantic (Instance, Individual)
Registry (Individuals Properties)
To support the ontology concept at the instance
level
register
Ontology Registration Process
For a standardized ontology registration
10
Scope Key Issues
  • Metamodels for Data Management
  • The following data should be managed
  • Instances
  • Mapping information between Concepts and
    Instances
  • Relation information (properties) between
    instances
  • Assumption (?)
  • Concepts and relevant properties are managed by
    the current extension
  • Ontology Registration Processes
  • Main processes
  • Concept-to-Instance mapping process
  • Valid Instance-to-Instance property assignment
    process
  • User groups
  • Groups for submission, verification,
    administration, etc.
  • Roles of each group

11
Metamodels for Data Management
  • Data to be Managed (i.e., required metamodels)
  • Generating (Instantiating) Instances
  • Concept-to-Instance relations
  • Mapping information between Concepts and
    Instances, ltConcept, Instancegt Pairs
  • Concepts at the concept level (MDR) Instances at
    the instance level (Proposal)
  • Instance-to-Instance relations
  • Relation information (properties) between
    instances
  • Reuse properties at the concept level for
    instance-to-instance links

author
Person
Book
Concept Level
Instance Level
12
Metamodel for Data Management (cont.)
  • Metamodel for Management of Information
  • concept-to-individual relations, individuals,
    individual-to-individual relations

Concept
Concept_Property
link
end

2..
abstraction
reused
1
1
Concept_Instance_Link
CP_IP_Link
concept_id1..1 Concept Instance_id1..n
Instance
CP_id1..1 Concept_Property IP_id1..1
Instance_Property
reuse
instantiation


Instance_Property
Instance
  • CP Concept_Property
  • IP Instance_Property

link
end

2..
13
Metamodel for Data Management (cont.)
  • Considering the Relations Region

Link_End
Relation_Role
link_end_role1..1Relation_Role
link
end
Link
Concept
Relation

2..

reused
abstraction
1
1
Concept_Instance_Link
CP_IP_Link
concept_id1..1 Concept Instance_id1..n
Instance
CP_id1..1 Concept_Property IP_id1..1
Instance_Property
instantiation
reuse


Instance_Property
Instance
link
end

2..
14
Metamodel for Data Management (cont.)
  • Considering the Relations Region
  • Link_End and Instance_Link_End

link
end
Link
Concept
Relation

2..
Link_End
Relation_Role
link_end_role1..1Relation_Role
reused
abstraction
1
1
Necessary or Not
Concept_Instance_Link
CP_IP_Link
concept_id1..1 Concept Instance_id1..n
Instance
CP_id1..1 Concept_Property IP_id1..1
Instance_Property
Instance_Link_End
link_end_role1..1Relation_Role
instantiation
reuse


Instance_Property
Instance
link
end

2..
15
Ontology Registration Process
repetition
Statement Registration (Register a Statement,
ltInstance, Property, Instancegt)
Valid Property Assignment (Select Valid
Properties for two Instances)
Concept-to-Instance relations
Instance to Concept Mapping (Map an Instance to a
Concept)
Concept-to-Instance relations
Instance Generation (Instance Set)
Instance list
16
Conclusion and Next Step
  • Summary of the Current Development Status
  • Defined a metamodel for the instance management
  • Defined the registration processes
  • Further Work for the Next Plenary Meeting
  • Definition of more metamodels
  • for support of multiple ontologies
  • for management of additional information, if
    needed
  • Definition of user groups and their roles
  • Providing various and concrete examples
  • Defining data models for practical use
  • RDB-based model and/or OODB-based model
  • might be provided as an appendix
  • And ......

17
Q/A
Thank you! Dongwon Jeong (djeong_at_kunsan.ac.kr),
Kunsan National University Doo-Kwon Baik
(baikdk_at_korea.ac.kr), Korea University
Write a Comment
User Comments (0)
About PowerShow.com