This Paper Is About The Virtual Merging Engine Hatana.

TMRA
2010
Hatana
A virtual merging engine
Uta Schulze
Topic Maps Lab at the University of Leipzig
Uta.Schulze@informaBk.uni-‐leipzig.de
Einführung in Topic Maps
"Accessing the island of Hatana is a complicated process."

http://en.wikipedia.org/wiki/Hatana
Uta Schulze, Topic Maps Lab

<Uta.Schulze@informatik.uni-leipzig.de>
MoBvaBon -‐ Not that complicated
Several data sources
One view?

One query language?

?
Why puJng data into topic maps?
MaJorToM-JLI
Because we can.
ARNotations
Coming
soon
Maiana

Because we can.
Because information wants to be a topic map.

Because we can.
Because information wants to be a topic map.
Because we’d like to merge…

Why don‘t we just put everything into one big topic map and are done with?
Information
1.  changes over time

Information
2.  has copyright issues

Information
3.  has an origin that would get lost

Information
3.  has an origin that would get lost
4.  should sometimes remain in its database

Another soluBon: Hatana
Hatana creates a layer over several data sources.

Another soluBon: Hatana
Hatana creates a layer over several data sources.
This layer behaves as a topic map!

Example 1: TMRA ParBcipants (Java Live IntegraBon)

Hatana merges ...
•  strictly according to the TMDM’s equality rules of constructs

•  on demand
•  and creates „virtual” topics, associations, …

Equality rules for topics
Graham Moore, Graham Moore, Graham Moore,

Vice Admiral Footballer Topic Mapper




NAME EQUALITY

http://en.wikipedia.org/wiki/Graham_Moore_(footballer)

http://en.wikipedia.org/wiki/Graham_Moore
http://www.topicmapslab.de/people/Graham_Moore

http://en.wikipedia.org/wiki/Graham_Moore_(footballer)

http://en.wikipedia.org/wiki/Graham_Moore
IDENTIFIER EQUALITY
Virtual on demand merging
http://www.topicmapslab.de/people/
Graham_Moore

Graham_Moore

Graham_Moore

Graham_Moore
http://psi.ontopedia.net/Graham_Moore

Graham_Moore

Graham_Moore

Graham_Moore

Graham_Moore

Graham_Moore
virtual topic

virtual names
get all names
virtual topic

Virtual topic
•  empty
•  wrapper that
•  acts as topic ...
•  but stores ids of equal source topics

Example 2: Merging the Italian and Norwegian Opera
Problem
•  only 20 out of 2767 topics with equal identifiers
•  http://psi.ontopia.net/music/opera vs. http://psi.ontopedia.net/Opera
•  no editing of sources

Example 2: Merging the Italian and Norwegian Opera
Problem
•  Only 20 out of 2767 topics with same identifiers
•  http://psi.ontopia.net/music/opera vs. http://psi.ontopedia.net/Opera
•  No editing of sources
Possible solution
•  topic map with topic containing e.g. both „Opera“ identifiers
•  source: expert knowledge, Subj3ct, ...

Advantages of virtual merging
•  Combining read-only topic maps

•  Combining private with public available topic maps (Maiana feature)
•  Information about the origin
•  On demand merging
•  Playing around with identities
•  Validating topic map against a schema, database backend

Performance
•  There is runtime
•  Highly dependent of the underlying engine

Performance
•  Validation of the opera map against the TMCL Meta Schema:

•  hard merge using Ontopia: instantly
•  improved Hatana version: took quite some time

Performance

•  more improved Hatana version: a moment

Performance

•  future Hatana version: ?

ImplementaBon
•  read-only Java topic maps engine (TMAPI)

•  Topic Map System containing virtual topic maps
•  Virtual construct: empty layer storing the ids of its source constructs
•  Caching: Id-Storing

I did not talk about
•  Merging topics that reify e.g. equal names

•  Merging associations and roles
•  most time consuming
•  Cache invalidation

Next steps
•  Learning from Jack Park’s merge assertions

•  Implementing the Container in Container feature
•  Increasing performance
•  Improving the Container view in Maiana

Thank you for your attention!


This Paper Is About The Virtual Merging Engine Hatana.

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

This Paper Is About The Virtual Merging Engine Hatana.

Încărcat de

Drepturi de autor:

Formate disponibile

TMRA

"Accessing the island of Hatana is a complicated process."

Uta Schulze, Topic Maps Lab

Several data sources

Uta Schulze, Topic Maps Lab

Several data sources

One query language?

Uta Schulze, Topic Maps Lab

Several data sources

Uta Schulze, Topic Maps Lab

Uta Schulze, Topic Maps Lab

Uta Schulze, Topic Maps Lab

Uta Schulze, Topic Maps Lab

Uta Schulze, Topic Maps Lab

Uta Schulze, Topic Maps Lab

Uta Schulze, Topic Maps Lab

Hatana creates a layer over several data sources.

Uta Schulze, Topic Maps Lab

Hatana creates a layer over several data sources.

This layer behaves as a topic map!

Uta Schulze, Topic Maps Lab

Uta Schulze, Topic Maps Lab

• strictly according to the TMDM’s equality rules of constructs

Uta Schulze, Topic Maps Lab

Graham Moore, Graham Moore, Graham Moore,

Uta Schulze, Topic Maps Lab

Graham Moore, Graham Moore, Graham Moore,

Uta Schulze, Topic Maps Lab

Graham Moore, Graham Moore, Graham Moore,

Uta Schulze, Topic Maps Lab

Graham Moore, Graham Moore, Graham Moore,

Uta Schulze, Topic Maps Lab

Graham Moore, Graham Moore, Graham Moore,

Uta Schulze, Topic Maps Lab

Uta Schulze, Topic Maps Lab

Uta Schulze, Topic Maps Lab

Uta Schulze, Topic Maps Lab

Uta Schulze, Topic Maps Lab

Uta Schulze, Topic Maps Lab

Uta Schulze, Topic Maps Lab

Uta Schulze, Topic Maps Lab

Uta Schulze, Topic Maps Lab

get all names

Uta Schulze, Topic Maps Lab

Uta Schulze, Topic Maps Lab

Uta Schulze, Topic Maps Lab

Uta Schulze, Topic Maps Lab

• Combining read-only topic maps

Uta Schulze, Topic Maps Lab

Uta Schulze, Topic Maps Lab

• Validation of the opera map against the TMCL Meta Schema:

Uta Schulze, Topic Maps Lab

• Validation of the opera map against the TMCL Meta Schema:

Uta Schulze, Topic Maps Lab

• Validation of the opera map against the TMCL Meta Schema:

Uta Schulze, Topic Maps Lab

• read-only Java topic maps engine (TMAPI)

Uta Schulze, Topic Maps Lab

• Merging topics that reify e.g. equal names

Uta Schulze, Topic Maps Lab

• Learning from Jack Park’s merge assertions

Uta Schulze, Topic Maps Lab

Thank you for your attention!

•  strictly according to the TMDM’s equality rules of constructs

•  Combining read-only topic maps

•  Validation of the opera map against the TMCL Meta Schema:

•  Validation of the opera map against the TMCL Meta Schema:

•  Validation of the opera map against the TMCL Meta Schema:

•  read-only Java topic maps engine (TMAPI)

•  Merging topics that reify e.g. equal names

•  Learning from Jack Park’s merge assertions