SE Engineering Reports | OGC
14
Copyright © 2015 Open Geospatial Consortium.
world, there are many aspects of the domain such as incident location that are common across organizations. However, currently there is no data model best practice for the Law
Enforcement community to use as a reference for these common information elements. The Reference Model described in the referenced diagrams in the document is provided
as an exemplar and a starting point to help facilitate greater commonality and interoperability between organizations. As it is common within this law enforcement
domain, policing agencies will not utilize any reference model until it has been deemed a best practice. Upon acceptance the expectation is that modifications and enhancements
will occur to meet the needs of a wider, more global population.
This best practice is not meant to compete or replace existing standards such as the NIEM National Information Exchange Model standard. The NIEM emphasizes data exchange
between organizations typically within the US, and is based on XML, which reflects only a small subset of the information of interest to a full data model.
For this testbed, we analyzed only a subset of the unified reference model that relates to incident modeling and took it in account to refine the core Incident Ontology initiated
during the OGC testbed 10. Overall the Incident ontology proposed in OWS-10 was consistent with the incident model of Unified Reference Model for LEAPS and could
easily accommodate the specificities related to LEAPS by extending the proposed core Incident Ontology described in the next section.
Based on the analysis, we concluded that the unified reference model for LEAPS can be used to derive a set of foundational ontologies that serve as the basis for interoperability
throughout LEAPS domain. These ontologies should be built upon a set of core OGC’s Geospatial Ontologies and take also in account other standards such as NIEM, EDXL and
CAP. They should define the minimum-essential core set of concepts, properties and relationships for the LEAPS community. The LEAPS ontologies must be designed to
accommodate any jurisdictionmission profile specific information taxonomies, specialized concepts and relationships, using the built-in extension mechanisms of
OWL.