Military Communications and Information Technology: A Trusted ...

More documents

Recommendations

Info

248 Military Communications and Information Technology... soapenv:Envelope xmlns:soapenv=”http://schemas.xmlsoap.org/soap/ envelope/” xmlns:ns=”http://my.org/ns/”> CarCollision YES roadblock Figure 6. Sample InsigmaEventOntology request sent by CM B. Rules In order to extend a domain knowledge about additional semantic relations between OWL classes we defined several SWRL rules. SWRL [13] language is used to enhance expression of OWL language. It is based on a combination of the OWL DL and OWL Lite sublanguages of the OWL Web Ontology Language with the Unary/ Binary Datalog RuleML sublanguages of the Rule Markup Language. SWRL enables extending the set of OWL axioms to include rules. SWRL rules are of the form of an implication between an antecedent (body) and consequent (head). The intended meaning can be read as: whenever the conditions specified in the antecedent hold, then the conditions specified in the consequent must also hold. Both the antecedent and consequent consist of zero or more atoms. An empty antecedent is treated as trivially true (i.e. satisfied by every interpretation), so the consequent must also be satisfied by every interpretation; an empty consequent is treated as trivially false (i.e. not satisfied by any interpretation), so the antecedent must also not be satisfied by any interpretation. Atoms in these rules can be of the form of simple assertions: C(x), P(x, y), or functions: sameAs(x, y) or differentFrom(x, y), where C is an OWL description, P is an OWL property, and x, y are either variables, OWL individuals or OWL data values. SWRL rules can be extended by using some built-in functions which are the limitations expressing in SWRLB (Semantic Web Rule Language Built-in) language. These limitations may be put into values occurrence in rules and express relationships between them, for example x>y. When defining the IEO model we considered different approaches. They all resulted in different possibilities in defining and automatically processing rules. The best choice for us was to define three classes as enumerated ones with strictly defined set of individuals: Result describes results of event, Threat which define dangers and Actions describes set of public safety services organization. These classes are used by SWRL rules that enhance semantic relationships in IEO. Some examples of SWRL rules are depicted in Fig. 7.
Chapter 3: Information Technology for Interoperability and Decision... 249 RoadEvent(x) ^ hasResult(x, leakageOfDangerousSubstance) -> hasAction(x, CallingTheFireBrigade) RoadEvent(x) ∧ hasInjured(x, y) ∧ swrlb:containsIgnoreCase(y, \”YES\”) → RoadAccident(x) RoadEvent(x) ^ hasResult(x, fire) -> hasAction(x, CallingTheFire- Brigade) Figure 7. Examples of IEO SWRL rules In order to execute SWRL rules we used Jess engine. It is a Java-based rule engine that provides an opportunity for constructing a software with some peace of artificial intelligence contained in facts and rules. This tools is free to use for two years for research purposes. Jess rule engine supports execution of SWRL rules and is used in many expert systems which require some reasoning mechanism. InsigmaEvent(x) ^ has_action(x, y)→ sqwrl:select(y) Figure 8. Example of SQWRL query The knowledge inferred on the basis of ontology model and rules exists in working memory. It is not set in the OWL model. In order to retrieve this knowledge we can use Semantic Query-enhanced Web Rule Language (SQWRL) which is built on the basis of SWRL [14]. SQWRL takes a standard SWRL rule antecedent and effectively treats it as a pattern specification for a query. Figure 8 depicts an SQWRL query for public safety services which should be notified about existing event detected in INSIGMA system. CallingTheAmbulance CallingTheFireBrigade CallingThePolice RoadAccident TrafficDifficulties CarCollision Fire PoorVisibilityDanger Figure 9. Example of the reasoning module SOAP response
Page 1 and 2:
Military Communications and Informa
Page 3 and 4:
Contents Foreword .................
Page 5:
Contents 5 Methodology for Gatherin
Page 8 and 9:
8 Military Communications and Infor
Page 11 and 12:
Building a Layered Enterprise Archi
Page 13 and 14:
Chapter 1: Concepts and Solutions f
Page 15 and 16:
Page 17 and 18:
Page 19 and 20:
Page 21 and 22:
Applying NAF for Performance Analys
Page 23 and 24:
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
Page 35 and 36:
Page 37 and 38:
Openness in Military Systems Jessic
Page 39 and 40:
Page 41 and 42:
Page 43 and 44:
Page 45 and 46:
Page 47 and 48:
Page 49 and 50:
The Concept of Integration Tool for
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
CFBLNet: A Coalition Capability Ena
Page 63 and 64:
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
Page 71 and 72:
Selected Aspects of Effective RCIED
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81:
Page 84 and 85:
84 Military Communications and Info
Page 86 and 87:
Page 88 and 89:
Page 90 and 91:
Page 92 and 93:
Page 94 and 95:
Page 96 and 97:
Page 98 and 99:
Page 100 and 101:
100 Military Communications and Inf
Page 103:
Chapter 2 Communications and Inform
Page 106 and 107:
Page 108 and 109:
Page 110 and 111:
Page 112 and 113:
Page 114 and 115:
Page 116 and 117:
Page 118 and 119:
Page 120 and 121:
Page 122 and 123:
Page 124 and 125:
Page 126 and 127:
Page 128 and 129:
Page 130 and 131:
Page 132 and 133:
Page 134 and 135:
Page 136 and 137:
Page 138 and 139:
Page 140 and 141:
Page 142 and 143:
Page 144 and 145:
Page 146 and 147:
Page 149 and 150:
Use of Cross Domain Guards for CoNS
Page 151 and 152:
Chapter 2: Communications and Infor
Page 153 and 154:
Page 155 and 156:
Page 157 and 158:
Page 159:
Page 162 and 163:
Page 164 and 165:
Page 166 and 167:
Page 168 and 169:
Page 170 and 171:
Page 172 and 173:
Page 174 and 175:
Page 176 and 177:
Page 178 and 179:
Page 180 and 181:
Page 182 and 183:
Page 184 and 185:
Page 186 and 187:
Page 188 and 189:
Page 190 and 191:
Page 192 and 193:
Page 194 and 195:
Page 196 and 197:
Page 199: Chapter 3 Information Technology fo
Page 202 and 203: 202 Military Communications and Inf
Page 239 and 240: Run-Time Ontology on the Basis of E
Page 241 and 242: Chapter 3: Information Technology f
Page 247: Chapter 3: Information Technology f
Page 253 and 254: A Robust and Scalable Peer-to-Peer
Page 265 and 266: Automatic Exploitation of Multiling
Page 281 and 282: Information Fusion Under Network Co
Page 293: Chapter 3: Information Technology f
Page 298 and 299:
Page 300 and 301:
Page 302 and 303:
Page 305 and 306:
Commanding Multi-Robot Systems with
Page 307 and 308:
Chapter 3: Information Technology f
Page 309 and 310:
Page 311 and 312:
Page 313 and 314:
Page 315 and 316:
Page 317 and 318:
Application of CID Server in Decisi
Page 319 and 320:
Page 321 and 322:
Page 323 and 324:
Page 325 and 326:
Page 327 and 328:
Page 329 and 330:
Page 331 and 332:
Managing Lessons Learnt from Daily
Page 333 and 334:
Page 335 and 336:
Page 337 and 338:
Page 339 and 340:
Page 341 and 342:
Page 343:
Page 347 and 348:
Federated Cyber Defence System - Ap
Page 349 and 350:
Chapter 4: Information Assurance &
Page 351 and 352:
Page 353 and 354:
Page 355 and 356:
Page 357:
Page 360 and 361:
Page 362 and 363:
Page 364 and 365:
Page 366 and 367:
Page 368 and 369:
Page 370 and 371:
Page 372 and 373:
Page 374 and 375:
Page 377 and 378:
Development of High Assurance Guard
Page 379 and 380:
Page 381 and 382:
Page 383 and 384:
Page 385 and 386:
Page 387 and 388:
Page 389 and 390:
Page 391 and 392:
Page 393 and 394:
Page 395 and 396:
Network Traffic Characteristics for
Page 397 and 398:
Page 399 and 400:
Page 401 and 402:
Page 403 and 404:
Page 405 and 406:
Page 407 and 408:
Page 409 and 410:
Page 411 and 412:
Page 413 and 414:
Page 415 and 416:
Methodology for Gathering Data Conc
Page 417 and 418:
Page 419 and 420:
Page 421 and 422:
Page 423 and 424:
Page 425 and 426:
Page 427 and 428:
Page 429:
Page 432 and 433:
Page 434 and 435:
Page 436 and 437:
Page 439 and 440:
On Multi-Level Secure Structured Co
Page 441 and 442:
Page 443 and 444:
Page 445 and 446:
Page 447 and 448:
Page 449 and 450:
Page 451 and 452:
Page 453 and 454:
Page 455 and 456:
Generation of Nonlinear Feedback Sh
Page 457 and 458:
Page 459 and 460:
Page 461 and 462:
Page 463:
Page 466 and 467:
Page 468 and 469:
Page 470 and 471:
Page 472 and 473:
Page 474 and 475:
Page 476 and 477:
Page 478 and 479:
Page 480 and 481:
Page 482 and 483:
Page 485 and 486:
Modern Usage of “Old” One-Time
Page 487 and 488:
Page 489 and 490:
Page 491 and 492:
Page 493 and 494:
Page 495:
Page 498 and 499:
Page 500 and 501:
Page 502 and 503:
Page 504 and 505:
Page 506 and 507:
Page 508 and 509:
Page 511 and 512:
A Abut Fatih 161 Akcaoglu Ismail 11
show all

Military Communications and Information Technology: A Trusted ...

Create successful ePaper yourself

Delete template?

Save as template?