Ontology development for GEOSS - OGC Network
Ontology development for GEOSS - OGC Network
Ontology development for GEOSS - OGC Network
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
<strong>Ontology</strong> <strong>development</strong> <strong>for</strong> <strong>GEOSS</strong><br />
Masahiko Nagai, Ryosuke Shibasaki<br />
Earth Observa7on Data Integra7on and Fusion Research Ini7a7ve<br />
The University of Tokyo, Japan<br />
<strong>GEOSS</strong> Workshop XXV<br />
Perspec7ves on <strong>GEOSS</strong> Architecture: Principles and Implementa7on<br />
PALACIO DE CONGRESOS, VALENCIA, SPAIN<br />
3‐4 DECEMBER 2008
In our research, <strong>Ontology</strong> holds the key to the<br />
Interoperability of Observa7on data.
เกษตรก<br />
รรม<br />
D<br />
B<br />
<br />
biolog<br />
y<br />
term<br />
<br />
DB<br />
DB<br />
DB<br />
Agricult<br />
ure<br />
DB<br />
temp<br />
DB<br />
<br />
Data DB cannot be used<br />
without understanding<br />
Hydrol<br />
ogy<br />
of data defini7on<br />
term<br />
DB<br />
DB<br />
Air temperature<br />
Landuse<br />
Classifica<br />
tion<br />
schema<br />
DB<br />
Climatology<br />
DB<br />
a specifica7on of a<br />
Health<br />
conceptualiza7on<br />
Science<br />
“<strong>Ontology</strong>”<br />
DB
Challenge <strong>for</strong> Data Management & Fusion<br />
New Challenge of Data Management and Fusion
GEO 2009‐2011 WORK PLAN<br />
1.1 COMMON INFRASTRUCTURE<br />
AR-09-01: <strong>GEOSS</strong> Common Infrastructure (GCI)<br />
Address the core architectural principles in <strong>GEOSS</strong>, and provide useful guidelines<br />
and tools to GEO Members and Participating Organizations in the establishment<br />
and operation of <strong>GEOSS</strong>.<br />
c) <strong>GEOSS</strong> Best Practices Registry (<strong>for</strong>mer DA-06-09)<br />
This sub-task is led by Japan and IEEE<br />
Support the operation and upgrade of the <strong>GEOSS</strong> Best Practices Registry. The<br />
registry should be capable of including best practices in observation, modeling<br />
and analyses, ontologies, capacity building, existing cost-benefit sharing<br />
mechanisms and examples (data sharing, cooperative data acquisition, joint<br />
<strong>development</strong>, joint flight, collaborative sciences, etc) and other relevant GEO best<br />
practices. This sub-task will work in coordination with the GEO Committees,<br />
Members and Participating Organizations, who will provide the content <strong>for</strong> the<br />
registry.
GEO 2009‐2011 WORK PLAN<br />
1.1 COMMON INFRASTRUCTURE<br />
AR-09-01: <strong>GEOSS</strong> Common Infrastructure (GCI)<br />
Address the core architectural principles in <strong>GEOSS</strong>, and provide useful guidelines<br />
and tools to GEO Members and Participating Organizations in the establishment<br />
and operation of <strong>GEOSS</strong>.<br />
d) <strong>Ontology</strong> and Taxonomy Development<br />
This sub-task is led by Japan and IEEE<br />
As part of the Best Practices Registry, create an <strong>Ontology</strong> and Taxonomy section<br />
to get an overview of available ontologies and taxonomies. Compare and analyze<br />
ontologies and taxonomies such as to avoid unnecessary overlaps and conflicts.<br />
As appropriate, develop ontologies and taxonomies stored in the Best Practices<br />
Registry into standards. Assist in the deployment of a reference able ontology <strong>for</strong><br />
Earth observation to link the User Requirements Registry with the Components<br />
and Services Registry.
<strong>GEOSS</strong> Best Prac7ce
<strong>GEOSS</strong> Best Prac7ce ‐Data and Architecture‐
<strong>GEOSS</strong> Best Prac7ce ‐Ontologies‐
System Architecture <strong>for</strong> <strong>Ontology</strong> Development<br />
<strong>Ontology</strong><br />
Management<br />
Tier<br />
<strong>Ontology</strong> Manager<br />
‐ Domain management<br />
‐ Editor management<br />
‐ Term management<br />
<strong>Ontology</strong><br />
Construction<br />
Tier<br />
Seman7c MediaWiki<br />
‐ XML converter<br />
‐ Table editor<br />
<strong>Ontology</strong><br />
Application<br />
Tier<br />
<strong>Ontology</strong><br />
Viewer<br />
Reverse<br />
Dic7onary<br />
Rela7on<br />
Finder
System Architecture <strong>for</strong> <strong>Ontology</strong> Development<br />
<strong>Ontology</strong><br />
Management<br />
Tier<br />
<strong>Ontology</strong> Manager<br />
‐ Domain management<br />
‐ Editor management<br />
‐ Term management<br />
<strong>Ontology</strong><br />
Construction<br />
Tier<br />
Seman7c MediaWiki<br />
‐ XML converter<br />
‐ Table editor<br />
<strong>Ontology</strong><br />
Application<br />
Tier<br />
<strong>Ontology</strong><br />
Viewer<br />
Reverse<br />
Dic7onary<br />
Rela7on<br />
Finder
<strong>Ontology</strong> Manager (<strong>for</strong> Editor)<br />
name e-mail affiliation affiliation <br />
date
<strong>Ontology</strong> Manager (<strong>for</strong> Term)<br />
term field editor date<br />
id editing cond.
System Architecture <strong>for</strong> <strong>Ontology</strong> Development<br />
<strong>Ontology</strong><br />
Management<br />
Tier<br />
<strong>Ontology</strong> Manager<br />
‐ Domain management<br />
‐ Editor management<br />
‐ Term management<br />
<strong>Ontology</strong><br />
Construction<br />
Tier<br />
Seman7c MediaWiki<br />
‐ XML converter<br />
‐ Table editor<br />
<strong>Ontology</strong><br />
Application<br />
Tier<br />
<strong>Ontology</strong><br />
Viewer<br />
Reverse<br />
Dic7onary<br />
Rela7on<br />
Finder
<strong>Ontology</strong> Development by Seman7c MediaWiki
Table Editor <strong>for</strong> Seman7c MediaWiki
Table Editor <strong>for</strong> Seman7c MediaWiki
System Architecture <strong>for</strong> <strong>Ontology</strong> Development<br />
<strong>Ontology</strong><br />
Management<br />
Tier<br />
<strong>Ontology</strong> Manager<br />
‐ Domain management<br />
‐ Editor management<br />
‐ Term management<br />
<strong>Ontology</strong><br />
Construction<br />
Tier<br />
Seman7c MediaWiki<br />
‐ XML converter<br />
‐ Table editor<br />
<strong>Ontology</strong><br />
Application<br />
Tier<br />
<strong>Ontology</strong><br />
Viewer<br />
Reverse<br />
Dic7onary<br />
Rela7on<br />
Finder
<strong>Ontology</strong> Viewer
<strong>Ontology</strong> Viewer<br />
Landuse in Thailand<br />
Landuse in Indonesia
System Architecture <strong>for</strong> <strong>Ontology</strong> Development<br />
<strong>Ontology</strong><br />
Management<br />
Tier<br />
<strong>Ontology</strong> Manager<br />
‐ Domain management<br />
‐ Editor management<br />
‐ Term management<br />
<strong>Ontology</strong><br />
Construction<br />
Tier<br />
Seman7c MediaWiki<br />
‐ XML converter<br />
‐ Table editor<br />
<strong>Ontology</strong><br />
Application<br />
Tier<br />
<strong>Ontology</strong><br />
Viewer<br />
Reverse<br />
Dic7onary<br />
Rela7on<br />
Finder
Development of Reverse Dic7onary<br />
What is Reverse dictionary<br />
Dictionary: “technical term” “definition”<br />
Reverse Dictionary: “list of words” or “explanation” “technical term”
Development of Reverse Dic7onary<br />
It is developed based on GETA (National Institute of In<strong>for</strong>matics, Japan).<br />
It is tools <strong>for</strong> manipulating large dimensional sparse matrices <strong>for</strong> text retrieval.<br />
Sentence<br />
Rain<br />
Precipitation of<br />
liquid water, either<br />
in the <strong>for</strong>m of drops<br />
of more than 0.5<br />
mm diameter, or of<br />
smaller, widely<br />
scattered drops.<br />
Word<br />
Segmentation<br />
Precipitation<br />
of<br />
liquid<br />
water,<br />
either<br />
in<br />
the<br />
<strong>for</strong>m<br />
of<br />
drops<br />
of<br />
more<br />
than<br />
<br />
WORDS<br />
precipitation<br />
Similality<br />
liquid<br />
water<br />
drops<br />
<br />
SENTENCE<br />
rain<br />
acid rain<br />
drizzle<br />
precipitation<br />
Sprinkling<br />
<br />
1 1<br />
1 1 2 3 1<br />
1 1 1 1 3<br />
2 1 1 1<br />
1 2
Reverse Dic7onary
Reverse Dic7onary
Visual Reverse Dic7onary
In<strong>for</strong>ma7on Retrieval with transla7on Service<br />
<br />
<br />
<br />
<br />
University of Tokyo<br />
Transla8on<br />
“Rice Blast”<br />
Scien8sts<br />
(Foreigners)<br />
Portal Site<br />
<br />
ข้าว, โรค, เทา ,<br />
เชื้อ <br />
<br />
MediaWiki<br />
โรค<br />
ไหม้ <br />
<br />
Reveres dic7onary<br />
In<strong>for</strong>ma7on Retrieval
Development of Agriculture In<strong>for</strong>ma7on Portal
Reverse Dic7onary Demo
System Architecture <strong>for</strong> <strong>Ontology</strong> Development<br />
<strong>Ontology</strong><br />
Management<br />
Tier<br />
<strong>Ontology</strong> Manager<br />
‐ Domain management<br />
‐ Editor management<br />
‐ Term management<br />
<strong>Ontology</strong><br />
Construction<br />
Tier<br />
Seman7c MediaWiki<br />
‐ XML converter<br />
‐ Table editor<br />
<strong>Ontology</strong><br />
Application<br />
Tier<br />
<strong>Ontology</strong><br />
Viewer<br />
Reverse<br />
Dic7onary<br />
Rela7on<br />
Finder
Rela7ons of Data from Data Defini7on
Type of Ontologies<br />
Terminology<br />
Key Word<br />
Defini7on<br />
Knowledge<br />
Sharing<br />
Key word<br />
Gaze2eer<br />
Synonym/Antonym<br />
Is‐a, part‐of<br />
name type Zip Other<br />
Coordinate and<br />
land name<br />
coordinate name<br />
23, 1101 A<br />
209, 2345 B<br />
345, 9876 C<br />
A mountain 277-2345 A-2<br />
F River 345-3456 B-2<br />
G Building 370-0031 C-2<br />
Metadata<br />
UML, XML schema<br />
Data model
Geographic <strong>Ontology</strong> Development<br />
Gazetteer <br />
Society<br />
utilization<br />
Land name<br />
AAAA<br />
BBBB<br />
Coordinate<br />
1111, 3333<br />
2222, 4444<br />
utilization<br />
Spatial In<strong>for</strong>mation <br />
Exchange, Convert<br />
Indicate on Map
Primitive<br />
Geographic <strong>Ontology</strong> Development<br />
Land name Coordinate point<br />
Place Name A Coordinate 1<br />
Place Name B Coordinate 2<br />
Mandatory<br />
Language Category Life cycle Editing history<br />
English<br />
Political<br />
boundary<br />
1990-04-01<br />
mountain 2006-11-14<br />
2007-11-14<br />
Optional<br />
2006-11-14 01:10:30register<br />
2006-11-14 01:10:30 register<br />
2006-11-15 08:11:45edit<br />
Other name English name Scale Relation MBR Image<br />
file<br />
Land name<br />
A-2<br />
Land name 10 isNear(<br />
thisX<br />
15 contains(th<br />
is) = Y<br />
Coordinate 3,<br />
Coordinate 4<br />
XXX.jpg<br />
Note
Geographic <strong>Ontology</strong> Development
Geographic <strong>Ontology</strong> Development<br />
ID Place name Lat Lon
Geographic <strong>Ontology</strong> Development<br />
ID<br />
Place name<br />
La7tude<br />
Longitude<br />
Language<br />
Country <br />
category<br />
Scale<br />
MBR<br />
Rela7on<br />
Life cycle<br />
Edi7ng Date
Data<br />
Specification<br />
Data Model Registry Architecture<br />
User<br />
Spatial Data<br />
Manual<br />
Document<br />
retrieval<br />
UML Class<br />
Diagram<br />
XML Schema<br />
registry<br />
Keyword<br />
Data Model<br />
metadata<br />
<br />
<br />
Input Output<br />
<br />
<br />
<br />
Link<br />
Model DB<br />
retrieval<br />
Data model element<br />
Data model<br />
Retrieval<br />
result<br />
Providing<br />
files<br />
Part of data<br />
model<br />
decompose
Data Model Registry
Summary<br />
• <strong>Ontology</strong> <strong>for</strong> Sharing In<strong>for</strong>ma7on<br />
– <strong>Ontology</strong> Manager<br />
– Seman7c Media Wiki <strong>for</strong> <strong>Ontology</strong> Development<br />
– Table editor<br />
• <strong>Ontology</strong> Applica7on<br />
– <strong>Ontology</strong> Viewer<br />
– Reverse Dic7onary<br />
– Rela7on finder<br />
• Gaze`eer<br />
• Data Model Registry
Change language