Click to select an item for details.

GeoJSON is a format for encoding a variety of geographic data structures.

JavaScript Object Notation (JSON) is a text-based, language-independent data interchange format. It is defined in IETF RFC 8259 and ECMA-404.

A Universally Unique IDentifier (UUID) URN Namespace defines a Uniform Resource Name namespace for UUIDs (Universally Unique IDentifier), also known as GUIDs (Globally Unique IDentifier).

Information technology -- Document Schema Definition Languages (DSDL) Part 3: Rule-based validation -- Schematron.

DMA TR 8350.2, 1987, Department of Defense World Geodetic System 1984 (WGS 84), Its DeÞnition and Relationships with Local Geodetic Systems.

IEEE Std 754™, IEEE Standard for Floating-Point Arithmetic.

Uniform Resource Identifier (URI): Generic Syntax A Uniform Resource Identifier (URI) is a compact sequence of characters that identifies an abstract or physical resource. This specification defines the generic URI syntax and a process for resolving URI references that might be in relative form, along with guidelines and security considerations for the use of URIs on the Internet. The URI syntax defines a grammar that is a superset of all valid URIs, allowing an implementation to parse the common components of a URI reference without knowing the scheme-specific requirements of every possible identifier. This specification does not define a generative grammar for URIs; that task is performed by the individual specifications of each URI scheme.

As a SISO Reference Product, SISO-REF-056 (DRAFT) informs SISO product developers about best practices for the style of XML documents when XML is used to specify the structure and content of data supporting a SISO Product. The document defines categories of principles and best practices to follow based on the selection of a conformance target by the SISO group developing XML products. The SISO group uses the document to tailor the principles and best practices to be followed in specific context to the XML products being produced.

The SAC Special Working Group Reference for Enumerations for Simulation (SAC SWG Enumerations) publishes, maintains, supports, and updates SISO Reference Product, SISO-REF-010, Enumerations for Simulation Interoperability.

WebLVC is a protocol for enabling web and mobile applications (typically JavaScript applications running in a web browser) to play in traditional M&S federations (which may be using Distributed Interactive Simulation (DIS), High Level Architecture (HLA), Test and Training Enabling Architecture (TENA), or related protocols and architectures). In a nutshell, WebLVC takes the semantics of DIS or HLA Federation Object Models (FOMs), and represents those using messages in the JSON (JavaScript Object Notation) format, which are typically passed between server and client using WebSockets.

The Federation Engineering Agreements Template (FEAT) benefits all developers, managers, and users of distributed simulations by providing an unambiguous format for recording agreements about the design and use of the distributed simulation. The FEAT also benefits this community by enabling the development of federation engineering tools that can read the XML schema and perform federation engineering tasks automatically.

The Federation Engineering Agreements Template (FEAT) User's guide provides specific technical guidance on the syntax and semantics required to create a conformant XML-based federation agreements document.

The Fuel Economy Federation (FEAT version) provides a simple, working example of a FEAT template.

The Fuel Economy Federation (HTML version) documents a simple, working example of a FEAT template.

SISO-STD-003-2006 defines the format and syntax for describing the elements of a template for representing BOMs. It specifies the semantics of the elements of a BOM and the syntax for constructing BOMs from those elements. In addition, this specification provides a data interchange format (DIF) for the representation of BOMs using the XML. The BOM DIF enables tools to exchange and reason about BOMs.

SISO-STD-003.1-2006 introduces methodologies for creating BOMs and implementing them in the context of a larger simulation environment. The document is a means of familiarizing the reader with the concept of BOMs and providing guidance for BOM development, integration, and use in supporting simulation development.

The Tactical Data Link (TDL) Product Support Group (PSG) has been renamed the Tactical Digital Information Link - Technical Advice and Lexicon for Enabling Simulation (TADIL TALES) PDG & PSG. The TDL PSG was approved by the SISO Standards Activity Committee (SAC) and Executive Committee (EXCOM). This group supersedes the Link 16 Product Development Group and will transition that group’s discussion board and document library. The TADIL TALES PDG & PSG will support the approved SISO-STD-002 Link 16 standard for IEEE 1278.1a (DIS) and IEEE 1516 (HLA) by providing a central point for interpretations of SISO-STD-002 product language, providing help desk support to the SISO community, and accepting, developing, and maintaining problem/change reports to support future product revisions. The PDG & PSG will also support other developing tactical data link standards using DIS and HLA, specifically Link 11/11B, SADL, IBS-I and IBS-S, Link 22, and VMF, and any future SISO standards developed and approved for tactical datalink simulation.

SISO-STD-007-2008 is an XML -based language designed to support military scenario development that provides the M&S community with (1) a common mechanism for verifying and loading military scenarios; (2) the ability to create a military scenario that can be shared between simulations and C4I devices; (3) a way to improve scenario consistency between federated simulations; and (4) the ability to reuse military scenarios as scenario descriptions are standardized throughout the Army, Joint, and international communities and across simulation domains (e.g. training exercise, analysis, etc). This standard defines the MSDL in terms of an XML schema, including element relationships, data types and boundary constraints, and the associated business rules of each element and its attribution.

SISO-STD-008-2010 addresses interoperability between simulation systems and other manufacturing applications. The CMSD information model is a standard representation for core manufacturing simulation data. It provides neutral structures for the efficient exchange of manufacturing data in a simulation environment. These neutral structures can be used to support the integration of simulation software with other manufacturing applications.

SISO-STD-008-01-2012 is a member of the SISO-STD-008-2010, Standard for Core Manufacturing Simulation Data – UML Model, family of standards. The specification of the CMSD information model is presented using two different methods using the (1) Unified Modeling Language (UML); and (2) XML Schema Definition Language. Together these Standards provide neutral data structures for the efficient exchange of manufacturing data in a simulation environment. These neutral data structures are used to support the integration of simulation software with other manufacturing applications.

SISO-STD-011-2014 is a standard language for expressing and exchanging plans, orders, requests, and reports across command and control (C2) systems, live, virtual and constructive (LVC) modeling and simulation (M&S) systems, and autonomous systems participating in Coalition operations. Phase 1 describes a sufficient data model to unambiguously define a set of military orders using JC3IEDM as a starting point and extending it as necessary so that the orders can be interpreted by C2, M&S, and ultimately autonomous systems. This standard describes the data model as a subset of JC3IEDM and specifies the information exchange content and structure in the form of an XML schema.

SISO-STD-001.1-2015 defines a hierarchy of object and interaction classes for the High Level Architecture (HLA) that provides the capabilities defined in IEEE Std 1278.1-1995, IEEE Standard for Distributed Interactive Simulation - Application Protocols, and its supplement, IEEE Std 1278.1-1998, IEEE Standard for Distributed Interactive Simulation - Application Protocols.

SISO-STD-001-2015 encapsulates guidance in the use of the RPR FOM. It provides descriptions of FOM classes and data types and the relationship between Distributed Interactive Simulation (DIS) and the High Level Architecture (HLA)-based RPR FOM, as well as rules for accomplishing specific distributed simulation tasks.

SISO-STD-001.1-2015 defines a hierarchy of object and interaction classes for the High Level Architecture (HLA) that provides the capabilities defined in IEEE Std 1278.1-1995, IEEE Standard for Distributed Interactive Simulation - Application Protocols, and its supplement, IEEE Std 1278.1-1998, IEEE Standard for Distributed Interactive Simulation - Application Protocols.

SISO-STD-001-2015 encapsulates guidance in the use of the RPR FOM. It provides descriptions of FOM classes and data types and the relationship between Distributed Interactive Simulation (DIS) and the High Level Architecture (HLA)-based RPR FOM, as well as rules for accomplishing specific distributed simulation tasks.

SISO-STD-014.1-2018 defines a machine-readable Extensible Markup Language (XML) schema that facilitates automated methods of mapping gateway user requirements to gateway products that can meet those requirements. It also includes the specification of gateway performance requirements and capabilities to facilitate user selection of gateways based on relative performance.

SISO-STD-014.2-2018 defines a machine-readable Extensible Markup Language (XML) schema for defining data filters in gateways that are independent of any gateway implementation. It provides a formal language for gateway developers to describe each filter and provides a foundation for the configuration of the gateways themselves.

SISO-GUIDE-006-2018 provides detailed information regarding the development of scenarios for (distributed) simulation environments and the relationship of the scenario development process with the overarching simulation environment engineering process. It is based on the Distributed Simulation Engineering and Execution Process (DSEEP) and it augments the DSEEP with additional information specific to scenario development.

SISO-STD-009-01: This standard specifies the structure and behavior of engines that can execute models represented in the Simulation Reference Markup Language (SRML). SRML is an Extensible Markup Language (XML)-based data representation that is similar to HyperText Markup Language (HTML) in that it may to be loaded and executed by end users using standardized software. Moreover, an SRML engine is analogous to a web browser in that it can load content containing executable behavior.

SISO-STD-009-00: This standard provides a specification that enables simulations and other content to be served, received, and processed using web technologies. In many ways, SRML is similar to how HTML provides a specification that enables text and other content to be structured, processed, and viewed commonly using the World Wide Web.

SISO-GUIDE-009-2017: This guide provides a user guide to the primary features of the Simulation Reference Markup Language (SRML).

This recommended practice provides implementation-level guidance to VV&A practitioners by interpreting and customizing the more generalized FEDEP activity descriptions. It focuses upon the VV&A processes that apply to federations and not the VV&A processes associated with individual federates, but does incorporate the use of the information produced by those processes. Furthermore, the recommended practice does not describe the individual verification or validation techniques that could be employed to execute the VV&A processes for federations.

Stakeholders depend on M&S to inform critical decisions. Their reliance demands rigorous and thoughtful V&V of M&S products to help them identify those that are appropriate for their intended use. The GM-VV seeks to provide guidance regarding the selection of V&V methods to efficiently and effectively establish credibility of M&S in step with its development. It establishes a V&V framework and detailed guidance for implementing the framework to develop concrete V&V solutions. The GM-VV is published in three volumes: GM-VV Vol 1 Framework, GM-VV Vol 2 Implementation, GM-VV Vol 3 Reference.

Stakeholders depend on M&S to inform critical decisions. Their reliance demands rigorous and thoughtful V&V of M&S products to help them identify those that are appropriate for their intended use. The GM-VV seeks to provide guidance regarding the selection of V&V methods to efficiently and effectively establish credibility of M&S in step with its development. It establishes a V&V framework and detailed guidance for implementing the framework to develop concrete V&V solutions. The GM-VV is published in three volumes: GM-VV Vol 1 Framework, GM-VV Vol 2 Implementation, GM-VV Vol 3 Reference.

Stakeholders depend on M&S to inform critical decisions. Their reliance demands rigorous and thoughtful V&V of M&S products to help them identify those that are appropriate for their intended use. The GM-VV seeks to provide guidance regarding the selection of V&V methods to efficiently and effectively establish credibility of M&S in step with its development. It establishes a V&V framework and detailed guidance for implementing the framework to develop concrete V&V solutions. The GM-VV is published in three volumes: GM-VV Vol 1 Framework, GM-VV Vol 2 Implementation, GM-VV Vol 3 Reference.

Command and Control Systems to Simulation Systems Interoperation (C2SIM) is a standard for expressing and exchanging Command and Control (C2) information among C2 systems, simulation systems, and robotic and autonomous (RAS) systems in a coalition context. The C2SIM standard provides a normative description of the scope and use of C2SIM. The C2SIM standard is defined in a model-driven framework that includes an ontology as formal Logical Data Model and a mechanism to extend the data model for specialized use. The normative C2SIM ontology is divided into two ontologies; core C2SIM ontology and a Standard Military Extension (SMX) that imports the core C2SIM ontology.