What we did last year on WP2:

04/21/23 1

WP2 Discovery mechanism of the OpenKnowledge system

(“Semantic routing”)

(presented by Ronny Siebes)

OpenKnowledge project reviewWP2 -Discovery

04/21/23 2

1. Functional description + architecture of the OK- System (D2.1a and D2.1b) [additional work as a decision to get an actual working prototype and final system]

2. Emulation of routing mechanisms (D2.2?)

3. Implementation discovery service (prototype and beyond)

What we did last year on WP2:


04/21/23 3

1. What is the Open-Knowledge System?1. Current limitations leading to a validation of our

system.2. What are our goals of the Open-Knowledge System?

1. Large scale in humans and machines2. Diffentiation between types of participants, like

average user, programmers …3. Low integration effort with existing work4. Open participation5. Re-use, re-use and re-use6. Means to evaluate who is good and who’s not

3. Why the Open-Knowledge system is a good idea?1. Comparison with MAS, P2P, Grids, WWW, SW

4. How would the system look like?1. User perspective (‘screenshots’ and functionality)2. System overview in a technical sense (covered by

D2.1b)

Functional description + architecture of the OK-system


04/21/23 4

5. Can we give examples where the system will be useful?1. Emergency response 2. Bio- informatics3. SW tool development

6. Which techniques will be applicable?1. Interaction models2. Mapping3. Query relaxation4. Discovery5. Trust + reputation6. Media2semantics7. Semantic web tools

7. How will we evaluate the system? (for each point of 6 we say how)

Functional description + architecture of the OK-system


04/21/23 5

-Compared JXTA, Pgrid and FreePastry-JXTA implementation has many bugs and algorithm does not scale-Pgrid takes lots of time to stabalize-FreePastry is easy and works

-Compared different routing algorithms-Emulations of hundreds of nodes on the DAS2

Emulation experiments


Discovery implementation

04/21/23 6OpenKnowledge project reviewWP2 -Discovery

04/21/23 7

Coordinator

Discovery Node

PeerDiscoverySystem

OrganizationRelated to WP1: communication


04/21/23 8

4

5

7

6

89

1

23

IM

IM

IM

Code

OKC

IM

Code

OKC

Coordinator

Discovery Node

Peer

Publishing

ABC


04/21/23 9

4

5

7

6

8

1

23

IM

IM

Code

OKC

IM

Code

OKC

OkcIM

Code

OkcIM

Code

OKC

?

OKCOKC

Coordinator

Discovery Node

Peer

Discovering Descriptions

ABC


04/21/23 10

4

5

7

6

1

23

IM

IM

OKC

OKC

IM

OKC

OKC

OKCIM

OKC

OKCIM

OKC

OKCOKCOKC

OKC

IM

OKC

IM

OKC

OKCOKCOKCIM

OKC

Coordinator

Discovery Node

Peer

Retrieving Implementations

ABC


04/21/23 11

4

5

7

6

1

23

ABC

IM

IM

Code

OKC

IM

Code

OKC

OKCIM

Code

OKCIM

Code

OKCOKCOKC

OKC

IM

Code

IM

Code

OKCOKCOKCIM

Code5

6

7

1

IM

Code

OKCOKC

IM

Code

OKCOKCIM

Code

OKC

Coordinator

Discovery Node

Peer

Subscribing to Interactions


04/21/23 12

4

5

7

6

1

23

ABC

IM

IM

Code

OKC

IM

Code

OKC

OKCIM

Code

OKCIM

Code

OKCOKCOKC

OKC

IM

Code

IM

OKC

OKCOKCOKCIM

Code

56 71

IM

Code

OKCOKC

IM

Code

OKCOKCIM

Code

OKC

ABC 5

6 71

IM

Coordinator

Discovery Node

Peer

Coordinator Initialization


04/21/23 13

4

5

7

6

1

23

ABC

IM

IM

Code

OKC

IM

Code

OKC

OKCIM

Code

OKCIM

Code

OKCOKCOKC

OKC

IM

Code

IM

Code

OKCOKCOKCIM

Code

56 71

IM

Code

OKCOKC

IM

Code

OKCOKCIM

Code

OKC

ABC 5

6 71

ABC 5

6 71A

BC 5

6 71r( inquirer, initial )

r( oracle, necessary, 1 )

A( inquirer, ID2 ) :: ask(W) => a( oracle, ID )<- toknow(W) then definition(W,D) <= a(oracle, ID) then null <- show(W,D)

B( oracle, ID ) :: ask(W) <= a(inquirer, ID2 ) then definition(W,D) => a(inquirer, ID2) <- define(W,D)

C( translator, ID ) :: ask(W) <= a(ioracle, ID2 ) then definition(W,D) => a(inquirer, ID2) <- define(W,D)

Interaction Model

Coordination


Documents

What we did last year on WP2: