Semantic Web: Implications for Modeling and Simulation System Interoperability

1
Semantic Web Implications for Modeling and
Simulation System Interoperability

• Paper 04F-SIW-030
• Curtis Blais

2
Authors

• Curtis Blais, NPS MOVES
• clblais_at_nps.edu
• Lee Lacy, Dynamics Research Corporation
• LLacy_at_drc.com

3
Outline

• Military MS Challenges
• Semantic Web
• Ontologies
• Applications
• Summary

4
Military MS Challenges

• Interoperability Capability of a system to
  automatically provide services to and accept
  services from other systems to achieve a desired
  outcome (Draft DoD MSMP)
• Composability Capability to select and assemble
  reusable simulation components in various
  combinations into software systems to meet user
  requirements (M. Petty)

5
Interoperability
LCIM Levels of Conceptual Interoperability
Model refer to A. Tolk, 04S-SIW-009
6
Composability

• Succinct functional modules/services
• Fully described capabilities
• Defined interfaces

key problem is the semantics of the component,
not the syntax. Dr. Axel Lehmann, Fall SIW
Plenary


Desired Capability
Distributed Components
Realized Capability
7
Semantic Web

• An extension of the current Web in which
  information is given well-defined meaning, better
  enabling computers and people to work in
  cooperation.
• Berners-Lee, et. al., 2001
• Transforming documents to information (data in
  context)
• Enabling automated reasoning
• Equally accessible to human and software agents

8
The Evolving Web
Web of Knowledge
Proof, Logic and Ontology Languages
Shared terminology Machine-Machine Communication
2010
Resource Description Framework Extensible Markup
Language
Self-Describing Documents
2000
HTML/HTTP
Foundation of the Current Web
1990
Based on Berners-Lee, Hendler Nature, 2001(from
Hendler presentation)
9
Evolution not Revolution

• Semantic web concepts leverage the current web
• Current web is an excellent foundation to build
  upon because it is
• Interoperable
• Platform-independent
• Scaleable
• Distributed
• Ubiquitous

Tim Berners-Lee
10
Semantic Web Stack
Source I. Herman Introduction to the Semantic
Web, 12 November 2003. http//www.w3.org/2003/Ta
lks/0624-BrusselsSW-IH/26.html
11
Extensible Markup Language (XML)

• Universal format for structured documents and
  data on the Web
• Meta-language used to define data interchange
  formats
• Open, vendor-neutral, platform-independent
  standard
• Supported by Commercial Off-the-Shelf (COTS) and
  Government Off-the-Shelf (GOTS) software tools
• Companion standards (e.g., XSLT) provide
  additional features (family of technologies)

12
XML Schema

• XML Schema specification defines standard
  datatypes and provides a mechanism for defining
  new datatypes
• Provides a basis for validating XML documents

13
Resource Description Framework (RDF)

• Used to associate property/value pairs with
  resources (subject-predicate-object)
  assertions
• Resource is anything identifiable with a Uniform
  Resource Identifier (URI)
• Expressed in XML

Recommendation
14
RDF Schema

• Adds higher-level descriptive capabilities (e.g.,
  classes and class hierarchies)

15
Ontology

• Formal specification of a conceptualization
  ontologies formally specify domain concepts in
  shared vocabularies
• Concepts and relations among concepts
• Properties, attributes, values, constraints,
  rules
• Semantic Web provides a standard method for
  representing ontologies using metadata

16
Ontology Spectrum
Inference Engines
Rules Logic
Semantic Levels
17
Why Develop an Ontology?

• Ontologies can assist in
• Navigating the information space
• Share a common understanding of the structure
  (McGuinness, 2001)
• Make domain assumptions explicit
• Communication Semantics (Dale, 2000)
• Impose logic for inferencing
• Multi-level, relative meaning
• Enable reuse of domain knowledge
• Codifies local expertise
• Transferable form

18
Ontology Languages

• DAMLOIL (http//www.daml.org)
• Developed by DARPA team of researchers
• Language based on description logic technology
• Starting point for W3C Semantic Web initiative
• Adds additional language features for describing
  ontologies (e.g., cardinality)
• Builds on RDF(S)
• Web Ontology Language OWL
• Evolution of DAMLOIL
• Brings DAMLOIL into W3C processes
• Minor changes to the language
• See http//www.w3.org/2001/sw/WebOnt/

19
Application of Semantic Web to Military MS

• Data Mapping transferring information from one
  data model to another data model (see
  04F-SIW-111)
• Scenario Generation expressing and populating a
  scenario for use in MS for training, analysis,
  mission planning, rehearsal, etc.

20
MOOTW FAST Toolbox Project

• Integration of various models, simulations, data
  bases and computational tools into a deployable
  package (laptop) for MOOTW mission planning
• Current Components
• Toolbox Controller
• Unit Order of Battle Data Access Tool (UOB DAT)
• Joint Conflict and Tactical Simulation (JCATS)
• Diplomatic and Military Operations in a
  Non-warfighting Domain (DIAMOND)
• Interim Static Stability Model (ISSM)
• Canadian Forces Landmine Database (CFLD)
• XPOD Manipulation Tool (XMT)

21
Extending Unit Data Interchange
JCATS
DIAMOND
xsd
xsd
xslt
xslt
SAI-FAST-DIF
xsd
xslt
UOB Data Access Tool
UOB.xml
US and Coalition C4ISR
exports
xsd
xslt
C2IEDM
MAJ Glenn Hodges MOVES Thesis September 2004
xsd
22
Data Mapping

• Extension of property values
• Enhancement/refinement of property values
• Different grouping of property values
• Extension of propertied concepts
• Different grouping of propertied concepts
• Extension of associated concepts
• Enhancements/refinements of associated concepts

Key objective is expression of semantics to
enable software to automatically perform the
mappings and to auto-generate data
transformations.
See 04F-SIW-111
23
Scenario Generation

• Training Capabilities Analysis of Alternatives
  (February 2004)
• Scenario generation for training and mission
  planning is difficult and time-consuming
• No automated scenario generation tools exist
• CAPT Jeff Kline, USN NPS Systems Engineering
  (August 2004)
• The greatest barrier to the use of modeling and
  simulation in the 72-hour planning cycle is the
  time to generate scenarios.

24
Scenario Information (RD3)
RD3 Rapid Distributed Database Development
25
Automated Scenario Generation

• Scenario Description (Operations Order) to
  Populated Scenario Data

Semantic Discovery and Composition
Scenario Description
Where
Who
What
Maps
Weather
When
Terrain
Intelligence
Scenario Data
Forms of Expression -C2 Information Exchange Data
Model -Battle Management Language -Military
Scenario Definition Language
Forces
Behaviors
Distributed Resources
26
Elements of the Problem (1)

• Description
• Scenario (orders, plans, problem specification,
  requirements)
• Resources (inferred from scenario description)
• Services (data sources)
• Ontologies specification of a
  conceptualization
• Classes in the domains of interest
• Instances
• Relationships
• Properties (and property values)
• Functions and processes
• Constraints and rules

27
Elements of the Problem (2)

• Dynamic, distributed resources
• Web-based
• New sources, new products
• Web Technologies
• Open standards
• Universal Resource Identifier (URI) for
  identification
• Extensible Markup Language (XML) for description
• Web services for communications and distributed
  processes
• Beyond Web services, strong semantics logical
  assertions, classification, formal class models,
  rules, trust

28
RD3 Production Process and Strong Semantics
29
QUESTIONS?

• For more information, contact
• Curtis Blais
• MOVES Institute
• Naval Postgraduate School
• Monterey, CA
• 831-656-3215
• clblais_at_nps.edu

30
Backup Slides
31
Extensible Modeling and Simulation Framework
(XMSF)

• A composable set of standards, profiles, and
  recommended practices for Web-based MS
• Exploit industry investment in Web technologies
  for military MS
• Open standards
• XML-based languages and common ontologies for
  semantics
• Service-oriented architectures
• Enable a new generation of distributed MS
  applications to emerge, develop, interoperate

http//www.MovesInstitute.org/xmsf
32
Web Services
How a client talks to a Service provider depends
on the WSDL
Web services registry
WSDL
Green pages
White pages
Yellow pages
WSDL
From Coyle, F. P., XML, Web Services and the
Data Revolution, Addison-Wesley, 2002
UDDI
UDDI
XML/SOAP
XML/SOAP
Web
Web services provider uses UDDI to register a
Web service within the repository
Web services client uses UDDI to find an
appropriate Web service
XML/SOAP
UDDI
WSDL
UDDI Universal Description, Discovery and
Integration WSDL Web Services Description
Language SOAP Simple Object Access Protocol FTP
File Transfer Protocol HTTP Hyper Text Transfer
Protocol SMTP Simple Mail Transfer Protocol
SOAP
SMTP
HTTP
FTP
33
Web Services Stack
Processes Discovery, Aggregation, Choreography,
MANAGEMENT
SECURITY
Descriptions Web Services Descriptions (WSDL)
Messages
SOAP
Communications HTTP, SMTP, FTP, JMS, IIOP,
From World Wide Web Consortium (W3C), Web
Services Architecture
34
Semantic Web Services Stack
35
From L. Obrst, Ontologies for Semantically
Interoperable Systems and C. Bussler, et. al.,
A Conceptual Architecture for Semantic Web
Enables Web Services