Calhoun: The NPS Institutional Archive Faculty and Researcher Publications
Faculty and Researcher Publications Collection
2004
Semantic Web: Implications for Modeling and Simulation System Interoperability Lacy, Lee W. Paper 04F-SIW-030, Proceedings of the Fall 2004 Simulation Interoperability Workshop, Simulation Interoperability Standards Organization, Orlando, FL http://hdl.handle.net/10945/31177
2004 Fall SIW
Semantic Web: Implications for Modeling and Simulation System Interoperability Paper: 04F-SIW-030 Curtis Blais
2004 Fall SIW
Authors Ø Curtis Blais, NPS MOVES
[email protected] Ø Lee Lacy, Dynamics Research Corporation
[email protected]
2004 Fall SIW
Outline Ø Military M&S Challenges Ø Semantic Web Ø Ontologies Ø Applications Ø Summary
2004 Fall SIW
Military M&S 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)
2004 Fall SIW
Interoperability LCIM Level 5: Conceptual
Common world-view established
LCIM Level 4: Pragmatic/ Dynamic
Information and its use and applicability are exchanged
LCIM Level 3: Semantic
Data in context (information) is exchanged
LCIM Level 2: Syntactic
Data exchangeable in standard formats
LCIM Level 1: Technical
Physical connectivity established
LCIM Level 0: No Connection
No interoperability intended
LCIM: Levels of Conceptual Interoperability Model; refer to A. Tolk, 04S-SIW-009
2004 Fall SIW
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
2004 Fall SIW
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
2004 Fall SIW
The Evolving Web Proof, Logic and Ontology Languages
Web of Knowledge Shared terminology Machine-Machine Communication
2010 Resource Description Framework Extensible Markup Language
HTML/HTTP
Self-Describing Documents
Foundation of the Current Web
2000
1990
Based on Berners-Lee, Hendler; Nature, 2001(from Hendler presentation)
2004 Fall SIW
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
2004 Fall SIW
Semantic Web Stack
Source: I. Herman: Introduction to the Semantic Web, 12 November 2003. http://www.w3.org/2003/Talks/0624-BrusselsSW-IH/26.html
2004 Fall SIW
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)
Recommendation
2004 Fall SIW
XML Schema Ø XML Schema specification defines standard datatypes and provides a mechanism for defining new datatypes Ø Provides a basis for validating XML documents
Recommendation
2004 Fall SIW
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 resources
properties
resources
literals
Recommendation
2004 Fall SIW
RDF Schema Ø Adds higher-level descriptive capabilities (e.g., classes and class hierarchies)
Working Draft
2004 Fall SIW
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
Ontology Spectrum Rules & Logic
Inferenc e Engines
Strong semantics Modal Logic First Order Logic
Local Domain Theory
Description Logic DAML+OIL, OWL Unified Modeling Language
Semantic Levels
Conceptual Model RDF/S XTM Extended ER
2004 Fall SIW
Is disjoint subclass of with transitive property
Is subclass of
Thesaurus ER
Has narrower meaning than
Schema
Taxonomy Relational Model
Weak semantics
Is subclassification of Source: Daconta, M. C., Obrst, L. J., and Smith, K. T., The Semantic Web: A Guide to the Future of XML, Web Services, and Knowledge Management, Wiley Publishing, Inc., Indianapolis, 2003.
2004 Fall SIW
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
2004 Fall SIW
Ontology Languages Ø DAML+OIL (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 DAML+OIL Brings DAML+OIL into W3C processes Minor changes to the language See: http://www.w3.org/2001/sw/WebOnt/
2004 Fall SIW
Application of Semantic Web to Military M&S Ø 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 M&S for training, analysis, mission planning, rehearsal, etc.
2004 Fall SIW
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)
2004 Fall SIW
Extending Unit Data Interchange JCATS
DIAMOND xsd
xslt
xsd xslt
SAI-FAST-DIF xsd xslt
UOB Data Access Tool
exports
UOB.xml xsd xslt
MAJ Glenn Hodges MOVES Thesis September 2004
C2IEDM xsd
US and Coalition C4ISR
2004 Fall SIW
Data Mapping Ø Extension of property values Ø Enhancement/refinement of property values Key grouping objective of is expression of semantics Ø Different property values to enable software to automatically Ø Extension ofperform propertied concepts and to the mappings data transformations. Ø Differentauto-generate grouping of propertied concepts Ø Extension of associated concepts Ø Enhancements/refinements of associated concepts See 04F-SIW-111
Scenario Generation
2004 Fall SIW
Ø 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.”
Scenario Information (RD3*)
2004 Fall SIW
*RD3: Rapid Distributed Database Development
2004 Fall SIW
Automated Scenario Generation Scenario Description (Operations Order) to Populated Scenario Data
Scenario Description
Where
Semantic Discovery and Composition
Who
What When Forms of Expression -C2 Information Exchange Data Model -Battle Management Language -Military Scenario Definition Language
Weather
Maps
Intelligence
Terrain
Scenario Data Behaviors
Forces
Distributed Resources
2004 Fall SIW
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
2004 Fall SIW
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
RD3 Production Process and Strong Semantics
2004 Fall SIW
2004 Fall SIW
QUESTIONS? For more information, contact: Curtis Blais MOVES Institute Naval Postgraduate School Monterey, CA 831-656-3215
[email protected]
2004 Fall SIW
Backup Slides
2004 Fall SIW
Extensible Modeling and Simulation Framework (XMSF)
Ø A composable set of standards, profiles, and recommended practices for Web-based M&S Ø Exploit industry investment in Web technologies for military M&S: – Open standards – XML-based languages and common ontologies for semantics – Service-oriented architectures
Ø Enable a new generation of distributed M&S applications to emerge, develop, interoperate http://www.MovesInstitute.org/xmsf
Web Services How a client talks to a Service provider depends on the WSDL WSDL
Web services
WSDL
registry
UDDI to find an appropriate Web service
XML/SOAP
UDDI
WSDL
SOAP FTP
HTTP
Green pages White pages Yellow pages From: Coyle, F. P., XML, Web Services and the Data Revolution, AddisonWesley, 2002
Web Web services client – uses
2004 Fall SIW
SMTP
Web services provider – uses UDDI to register a Web service within the repository 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
2004 Fall SIW
Web Services Stack Processes Discovery, Aggregation, Choreography, …
S E C U R IT Y
Descriptions Web Services Descriptions (WSDL)
Messages SOAP Extensions Reliability, Correlation, Transactions, …
SOAP Communications HTTP, SMTP, FTP, JMS, IIOP, … From: World Wide Web Consortium (W3C), Web Services Architecture
M A N A G E M E N T
2004 Fall SIW
Semantic Web Services Stack OWL, OWL-S, OWL-Rules
Service Entities, Relations, Rules
RDF/S
Service Instances
BPEL4WS (Business Process Execution Language for Web Services) Trading Partner Agreement
Service Flow & Composition Service Agreement
UDDI/WS Inspection
Service Discovery (focused & unfocused)
UDDI
Service Publication
WSDL
Service Description
WS Security
Secure Messaging
SOAP
XML Messaging
HTTP, FTP, SMTP, MQ, RMI over IIOP
Transport
OWL, OWL-S, OWL-Rules
Service Entities, Relations, Rules
RDF/S
Service Instances
BPEL4WS (Business Process Execution Language for Web Services) Trading Partner Agreement
2004 Fall SIW
Service Flow & Composition Service Agreement
UDDI/WS Inspection
Service Discovery (focused & unfocused)
UDDI
Service Publication
WSDL
Service Description
WS Security
Secure Messaging
SOAP
XML Messaging
HTTP, FTP, SMTP, MQ, RMI over IIOP
Transport
From: L. Obrst, Ontologies for Semantically Interoperable Systems and C. Bussler, et. al., A Conceptual Architecture for Semantic Web Enables Web Services