Goal

1
(No Transcript)
2
Goal

• To manage the Life Cycle of XMDR
• Our approaches are
• Suggest two kinds of new classes to exist Use
  case Model
• First Version control classes are
  VersionControledEntity, VersionConroledItem,
  VersionControledProperty
• Second History control attributes and
  relationship areEffectiveStartDate,
  EffectiveEndDate and BeforeInstance(?)
  relationship
• Suggest enhanced XMDR Web Interface Design which
  are related to our Life cycle Management
• Text Search
• Advanced Text Search
• RDQL Query
• SPARQL Query
• Advanced Inference Search

3
Core Idea - New XMDR Class Model
History managing relationships are added
History managing relationships are added
History handling attributes are added
History handling attributes are added
Version control classes are added
4
Version control classes

• VersionControledEntity
• Basic version control
• Should be realized by Ontology and OntologyItem
• VersionConroledItem
• It includes tree hierarchy control
• Should be realized by OntologyItem and its
  subclass
• VersionControledProperty
• Used to control the property change, such as the
  property domain and property range.
• Should be realized by the properties among
  Ontology and OntologyItems

5
History control attributes

• Attributes for Historical data management
• EffectiveStartDate
• EffectiveEndDate
• Relationships for Historical data search
• Before Instance of Ontology
• Before Instance of Ontology Item
• Add upper two attributes and relationship to
  xmdrOntology and xmdrOntologyItem classes to
  maintain the effective term and to point the
  before instance

6
Enhanced XMDR Web Interface

• Text Search
• Advanced Text Search
• RDQL Query
• SPARQL Query
• Advanced Inference Search
• Add Calendar List box graphic inputs to get
  appropriate results are related to Version
  History management

7
Approach to Implementation
Input Search Keyword Version Control,
Historical Date
Search Optimal Ontology with Version and
Historical Date
New Ontology Document with Version and Historical
Date
User Interface
Search Engine
Ontology Documents
8
Text Search
History Date
Version List
3.1 (Created 2006.06.01)
Default Today
3.0 (Created 2006.01.01) 2.0 (Created
2005.06.01) 1.0 (Created 2005.02.25)
Default Last Version
Search Priority
History Date
Version
Default History Date Just Optional!
Some case version and date can not become AND
condition
9
Advanced Text Search
History Date
Version List
Search Priority
History Date
Version
10
RDQL Query
History Date
Version List
Search Priority
History Date
Version
Our porposal
As an example, try the query SELECT ?x WHERE
(?x rdftype xmdrOntology)

AND (2006-06-06date 3.1version)
11
Advanced Inference Search
History Date
Version List
Search Priority
History Date
Version
12
Search Engines
XMDR.OWL.XML
13
New XML Documents with Version History Date
14
Outputs
Original Output
Mid Step Output
15
Conclusions

• Our Contributions
• Satisfy the Ontology Lifecycle management in
  Extend Feature
• Future Works
• Find a solution for SPARQL Query
• Because, we need a time to understand about RDF
  in detail
• Implementation for Other Parts
• We concentrated the Text Search
• Other parts are challenge