Toward a Standard Rule Language for Semantic Integration of the DoD Enterprise

By Dr. Suzette Stoutenburg , Dr. Leo Obrst , Deborah Nichols , Jason Peterson , Adrian Johnson

Historically, the behavior of Department of Defense (DoD) Command and Control (C2) systems has been embedded in executable code, providing static functionality that is difficult to change.

Download Resources


PDF Accessibility

One or more of the PDF files on this page fall under E202.2 Legacy Exceptions and may not be completely accessible. You may request an accessible version of a PDF using the form on the Contact Us page.

Historically, the behavior of Department of Defense (DoD) Command and Control (C2) systems has been embedded in executable code, providing static functionality that is difficult to change. As the complexity and tempo of the world increase, C2 systems must move to a new paradigm that supports the ability to dynamically modify system behavior in complex, changing environments. Separation of rules from executable code provides the foundation for dynamic system behavior and agile response to outside events. A Rule Language Standard is required to realize the full benefits of rule separation including the sharing of rule abstractions across disparate domains, thus enabling interoperability across the enterprise.