Publication Date: 2017-05-12
Approval Date: 2016-12-07
Posted Date: 2016-11-21
Reference number of this document: OGC 16-047r1
Reference URL for this document: http://www.opengis.net/doc/PER/t12-A075
Category: Public Engineering Report
Editor: Martin Klopfer
Title: Testbed-12 General Feature Model Engineering Report
Copyright © 2017 Open Geospatial Consortium. To obtain additional rights of use, visit http://www.opengeospatial.org/
This document is an OGC Public Engineering Report created as a deliverable of an initiative from the OGC Innovation Program (formerly OGC Interoperability Program). It is not an OGC standard and not an official position of the OGC membership.It is distributed for review and comment. It is subject to change without notice and may not be referred to as an OGC Standard. Further, any OGC Engineering Report should not be referenced as required or mandatory technology in procurements. However, the discussions in this document could very well lead to the definition of an OGC Standard.
Permission is hereby granted by the Open Geospatial Consortium, ("Licensor"), free of charge and subject to the terms set forth below, to any person obtaining a copy of this Intellectual Property and any associated documentation, to deal in the Intellectual Property without restriction (except as set forth below), including without limitation the rights to implement, use, copy, modify, merge, publish, distribute, and/or sublicense copies of the Intellectual Property, and to permit persons to whom the Intellectual Property is furnished to do so, provided that all copyright notices on the intellectual property are retained intact and that each person to whom the Intellectual Property is furnished agrees to the terms of this Agreement.
If you modify the Intellectual Property, all copies of the modified Intellectual Property must include, in addition to the above copyright notice, a notice that the Intellectual Property includes modifications that have not been approved or adopted by LICENSOR.
THIS LICENSE IS A COPYRIGHT LICENSE ONLY, AND DOES NOT CONVEY ANY RIGHTS UNDER ANY PATENTS THAT MAY BE IN FORCE ANYWHERE IN THE WORLD. THE INTELLECTUAL PROPERTY IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NONINFRINGEMENT OF THIRD PARTY RIGHTS. THE COPYRIGHT HOLDER OR HOLDERS INCLUDED IN THIS NOTICE DO NOT WARRANT THAT THE FUNCTIONS CONTAINED IN THE INTELLECTUAL PROPERTY WILL MEET YOUR REQUIREMENTS OR THAT THE OPERATION OF THE INTELLECTUAL PROPERTY WILL BE UNINTERRUPTED OR ERROR FREE. ANY USE OF THE INTELLECTUAL PROPERTY SHALL BE MADE ENTIRELY AT THE USER’S OWN RISK. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR ANY CONTRIBUTOR OF INTELLECTUAL PROPERTY RIGHTS TO THE INTELLECTUAL PROPERTY BE LIABLE FOR ANY CLAIM, OR ANY DIRECT, SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES, OR ANY DAMAGES WHATSOEVER RESULTING FROM ANY ALLEGED INFRINGEMENT OR ANY LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR UNDER ANY OTHER LEGAL THEORY, ARISING OUT OF OR IN CONNECTION WITH THE IMPLEMENTATION, USE, COMMERCIALIZATION OR PERFORMANCE OF THIS INTELLECTUAL PROPERTY.
This license is effective until terminated. You may terminate it at any time by destroying the Intellectual Property together with all copies in any form. The license will also terminate if you fail to comply with any term or condition of this Agreement. Except as provided in the following sentence, no such termination of this license shall require the termination of any third party end-user sublicense to the Intellectual Property which is in force as of the date of notice of such termination. In addition, should the Intellectual Property, or the operation of the Intellectual Property, infringe, or in LICENSOR’s sole opinion be likely to infringe, any patent, copyright, trademark or other right of a third party, you agree that LICENSOR, in its sole discretion, may terminate this license without any compensation or liability to you, your licensees or any other party. You agree upon termination of any kind to destroy or cause to be destroyed the Intellectual Property together with all copies in any form, whether held by you or by any third party.
Except as contained in this notice, the name of LICENSOR or of any other holder of a copyright in all or part of the Intellectual Property shall not be used in advertising or otherwise to promote the sale, use or other dealings in this Intellectual Property without prior written authorization of LICENSOR or such copyright holder. LICENSOR is and shall at all times be the sole entity that may authorize you or any third party to use certification marks, trademarks or other special designations to indicate compliance with any LICENSOR standards or specifications.
This Agreement is governed by the laws of the Commonwealth of Massachusetts. The application to this Agreement of the United Nations Convention on Contracts for the International Sale of Goods is hereby expressly excluded. In the event any provision of this Agreement shall be deemed unenforceable, void or invalid, such provision shall be modified so as to make it valid and enforceable, and as so modified the entire Agreement shall remain in full force and effect. No decision, action or inaction by LICENSOR shall be construed to be a waiver of any rights or remedies available to it.
None of the Intellectual Property or underlying information or technology may be downloaded or otherwise exported or reexported in violation of U.S. export laws and regulations. In addition, you are responsible for complying with any local laws in your jurisdiction which may impact your right to import, export or use the Intellectual Property, and you represent that you have complied with any regulations or registration procedures required by applicable law to make this license enforceable.
- 1. Introduction
- 2. References
- 3. Terms and definitions
- 4. Overview
- 5. Initial Requirements, Assumptions and Concepts
- 5.1. Integration of Data, Analytical Observations and Judgments
- 5.2. Correlation does not necessarily mean causation
- 5.3. Making Judgments on Facts
- 5.4. Interaction with an Integrated Information Environment
- 5.5. Relationships - Features and Associations
- 5.6. Use Case Scenario
- 5.7. Available Scenario Phases
- 5.8. Scenario Script
- 5.9. Accommodating Associations in GFM
- 5.10. WOS Approaches
- 5.11. Client Requirements
- 5.12. Initial Implementation Experiences
- 6. The General Feature Model
- 7. CSW-eb-RIM based WOS Implementation
- 8. WFS based Web Object Service
- 8.1. Introduction
- 8.2. Requirements
- 8.3. Architecture
- 8.4. Basic Service Elements
- 8.5. Authentication and Access Control
- 8.6. Hypermedia Controls
- 8.7. Summary of Resources
- 8.8. MIME Types
- 8.9. A Word about Examples
- 8.10. Service Metadata
- 8.11. Object Access & Management (GetObject/Transaction)
- 8.12. Associations
- 8.13. Classifications
- 9. Future Work
- Appendix A: Revision History
- Appendix B: Bibliography
With a growing requirement to carry out complex analysis in large multi-disciplinary, heterogeneous data collections, an approach is required to extract equivalent information from dissimilar content. The more information can be normalized, the easier it will be to correlate the content. Given that almost all data has a spatio-temporal component, this ER will look into the idea of defining a Spatial-Temporal Service and analyze which collection of data types, operations and architecture patterns would be necessary to spatial-temporal enable any content. This OGC® document reviews the General Feature Model and gives guidelines for necessary modifications to broaden its scope, so that it can be re-used for non-geospatial centric applications and extended as necessary into a general model for all object types.
The GFM and it’s capabilities have long been regarded as being of interest to the OGC / the geospatial community only. However, the proof-of-concept carried out in this activity has successfully demonstrated, that the GFM can accommodate far more requirements than anticipated. Even rather abstract items such as a judgement, a decision or the related body of evidence can be expressed as features and associations. Given that almost all information can be attributed with some spatio-temporal tag, a GFM based approach can play an important role in the integration of geospatial and non-geospatial data and systems.
This ER summarizes the work performed in Testbed-12 and provides an outlook on possible future activities. It serves as a starting point for the OGC community in general and the Geosemantics Working Group in particular to understand some of the latest discussions on semantics in geospatial contexts. It provides a number of references to more detailed material to facilitate more in-depth research and analysis.
Although this ER does not reflect the work of any OGC Working Group, it addresses topics which are currently discussed in the Defense & Intelligence DWG, Disaster Management DWG and Big Data DWG. The initial GEOINT requirements were derived from capabilities anticipated for Activity Based Intelligence (ABI), Object Based Production (OBP) and Structured Observation Management (SOM). It concentrates on summarizing the activities performed in Testbed-12 that were carried out to analyze the capabilities of the GFM to store non-geospatial data and associations. As such it provides a starting point for future work on geospatial and non-geospatial data integration.
ogcdocs, testbed-12, General Feature Model, heterogeneous data integration
WFS/FES SWG and Defence and Intelligence DWG
Given that almost all data has a spatial-temporal component, this OGC® Engineering Report evaluates the degree to which the General Feature Model can accommodate complex analysis on large multi-disciplinary, heterogeneous data collections for the purpose of extracting new information from dissimilar content. It looks into the idea of defining a Spatial-Temporal Service and Analytics platform and identifies the data types, operations and architecture patterns would be necessary to spatial-temporal enable any type of content.
This OGC® document reviews the General Feature Model and gives guidelines for necessary modifications to broaden its scope, so that it can be re-used for non-geospatial centric applications and extended as necessary into a general model for all object types.
The idea to integrate information and capture knowledge has evolved in OGC over a long period of time, accommodating the continuous changes in technology and the range of services to be integrated. The following OGC documents summarize some of this work and have been considered in the development of the initial concepts:
The Web Object Service Implementation Specification (OGC 02-049 / 03-013) aimed to satisfy a requirement of the OWS 1.2 project to manage many different types of objects, including styles, symbols and images, using a repository interface. “The specification defines a set of base XML types that define the behavior of a Web Object Service. A Web Object Service is a generic web-based repository interface. The interface supports the following operations: GetCapabilities, DescribeObjectType, GetObjectById, GetObject, LockObject and Transaction. The specification assumes that the distributed computing platform is HTTP and may define both XML (suitable for the POST method) and Keyword-Value Pair (suitable for the GET method) encodings of each operation.”
The OGC® Testbed-10 Service Integration Engineering Report (OGC 14-13r1) “specifies a means of discovering and describing associations between web resources (both OGC and non-OGC). The discovery of associations is accomplished by means a new operation named GetAssociations. The description or representation of associations is accomplished by the definition of an XML Schema for expressing associations in XML. The scope of this document is limited to the existing OGC web service framework, which predominantly uses XML. However, it is anticipated that over time the association schemas defined in this document will be extended to provide JSON snd JSON-LD expressions which are rapidly emerging encodings within and outside the OGC.”
The OGC® Testbed-11 Incorporating Social Media in Emergency Response Engineering Report (OGC 15-057) studies two different approaches to incorporating social media information into Emergency Response applications: “The first [approach] was based on the concept of using an OGC Sensor Observation Service (SOS) for handling humans as sensors is illustrated from an interoperability perspective. The developed O&M-based data model is presented and illustrated with examples from different social media platforms. This is complemented by a description of how data loading from social media platforms into an SOS server can be achieved. The second approach was based on using Linked Data to integrate social objects produced by the different social media networks. The ontology for describing social objects and activities is based on SocialML ontologies that can be extended to accommodate new activities and social objects. The integration of social sites was done through the use of RDF scrapers accessible through a REST API. The resulting knowledgebase was made available through a GeoSPARQL endpoint. Another important topic of [OGC 15-057] is the use of the OGC Web Processing Service (WPS) for analyzing the available social media data (i.e. detect clusters). “
However, the requirement to integrate heterogenous data using spatial-temporal attributes has also been addressed outside the OGC. One example explicitly mentioned in the Testbed-12 RFQ is the FGDC endorsed Time Space Position Information (TSPI) Version 2.0 standard (NGA.STND.0019_2.0), which "provides a single means of encoding spatiotemporal information for the storage, manipulation, interchange, and exploitation of spatiotemporal data. It is designed as a set of reusable data components upon which both Geography Markup Language (GML)-based application schemas and non-GML-based XML schemas may be developed. It specifies a registry-based extension mechanism enabling the development and reuse of additional spatiotemporal XML Schema components. It integrates the XML Schema for the United States Thoroughfare, Landmark, and Postal Address Data Standard, FGDC-STD-016-2011, including the necessary updates to work with the OGC® GML 3.3, Extended schemas and encoding rules."
The Testbed-12 General Feature Model ER now takes a step back from specific implementation requirements and looks into the principle capabilities of the GFM to accommodate non-geospatial data, information and associations as features.
A simple use case scenario is based on observations from non-geospatial sources, subsequent decisions based on selected observations and a requirement to create associations, which allow a user to access all associated features. The objective is to make a body of evidence for a decision accessible from various angles. This can be the traditional geospatial approach of showing a decision on a map and providing a report of associated features. However it should also be capable of providing graph-like overviews of features and associations accessible from non-geospatial systems.
All questions regarding this document should be directed to the editor or the contributors:
Gobe Hobona PhD.
Panagiotis (Peter) A. Vretanos
This initiative has demonstrated the feasibility of a Spatial-Temporal Service and Analytics Platform based on the General Feature Model. However, much work remains to be done to fully define and validate that platform. The proposed next steps in this effort can be found in Section 9.
The work carried out in this activity has not resulted in any change requests towards existing specifications.
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. The Open Geospatial Consortium shall not be held responsible for identifying any or all such patent rights.
Recipients of this document are requested to submit, with their comments, notification of any relevant patent claims or other intellectual property rights of which they may be aware that might be infringed by any implementation of the standard set forth in this document, and to provide supporting documentation.
The following documents are referenced in this document. For dated references, subsequent amendments to, or revisions of, any of these publications do not apply. For undated references, the latest edition of the normative document referred to applies.
OGC 16-046, Testbed-12 Semantic Enablement ER
For the purposes of this report, the definitions specified in Clause 4 of the OWS Common Implementation Standard [OGC 06-121r9] shall apply. In addition, the following terms and definitions apply.
ABI Activity Based Intelligence
API Application Program Interface
COM Component Object Model
CSW Catalogue Service for the Web
DCE Distributed Computing Environment
DCOM Distributed Component Object Model
ebRIM Electronic Business Registry Information Model
ER Engineering Report
GFM General Feature Model
GMLSF Simple Feature Geography Markup Language
IDL Interface Definition Language
LDP Linked Data Platform
NGA National Geospatial-Intelligence Agency
OBP Object Based Production
OWL Web Ontology Language
OWL-S Semantic Markup for Web Services
RDF Resources Description Format
RDF-QB RDF Data Cube
SHACL Shapes Constraint Language
SKOS Simple Knowledge Organization System
SOM Structured Object Management
SPARQL SPARQL Protocol and RDF Query Language
UML Unified Modeling Language
VoID Vocabulary of Interlinked Datasets
WOS Web Object Service
This ER serves as an entry point to Testbed-12 activities looking into the idea of using the GFM as a basis for integration of heterogeneous and multi-temporal geospatial and non-geospatial data. It integrates discussions from the Linked Data and Advanced Semantics for Data Discovery and Dynamic Integration thread.
The main document starts in Clause 5 with a short overview of the initial requirements, assumptions and concepts, as well as the use case scenario selected for a proof of concept demonstration.
It then maps the concepts to the use case scenario and derives an initial model based on the GFM in Clause 6.
The experiences from the proof of concept implementations as well as future work items are finally summarized inClause 9.
With a growing requirement to carry out complex analysis in large multi-disciplinary, heterogeneous data collections, an approach is required to extract equivalent information from dissimilar content. The more information can be normalized, the easier it will be to correlate the content.
Given that almost all data has a spatio-temporal component, this ER looks into the idea of defining a Spatial-Temporal Platform as a Web Object Service (WOS) and analyzes which collection of data types, operations and architecture patterns would be necessary to spatial-temporal enable any content.
It is assumed that the General Feature Model, WFS and CSW already accommodate most capabilities, although by nature of their origin, they are primarily geared towards geospatial application.
The envisioned WOS is not about merging WFS and CSW. It is about being able to serve any type of object, e.g. vector features, raster coverages, other images, sounds, or even representations of a concept or conclusion.
The WOS is thus a means to handle associations as a first class object to allow the description of relationships between arbitrary objects in a formal way as described below.
The goal is to review the General Feature Model and to research necessary modifications to broaden its scope, so that it can be re-used for non-geospatial centric applications and extended as necessary into a general model for all object types.
As part of their homeland security mission, NGA has compiled the HSIP Gold database. HSIP Gold is a compilation of 560 of the best available geospatially enabled baseline infrastructure datasets for all National & Defense Critical Infrastructure Sectors. Now they want to extend that capability by providing not just feature data, but a comprehensive integrated information environment. This environment provides a comprehensive suite of integrated information as well as analytics to derive knowledge from that information.
Central to this capability is a data aggregation service: Data is collected from open source, crowd sources, and procured from key data providers.
All data is assigned a unique identifier, and populated with discovery metadata. That metadata includes the spatial and temporal extent. Core to the data store is a global feature data set. This foundation feature data is a detailed representation of the global real-world objects. The foundation feature data provides a spatial-temporal context against which all other data can be understood.
The data holdings do not stop with data. They also include the results of analytic processes applied to the data. These results are classified as observations or judgments.
Observations identify correlations between data. These may be generated by observation or through automated analytics. Correlations are statements of fact, but do not indicate meaning.
For example, two suspected criminal operatives are in San Francisco at the same time and stayed in hotels within ½ mile from each other. This could indicate that they are planning an attack. It could be simple coincidence. The observation is a simple observance of fact. It makes no judgment as to the significance of that fact.
Judgments are the result of analytic processes, which develop conclusions from a body of evidence. They can be the result of automated or human analytic processes. A judgment must include:
the entity which generated the judgment,
the analytic process used,
the body of evidence supporting the judgment, which can include data, observations and other judgments,
a measure of confidence for the judgment, which should reflect the aggregate confidence in each evidence entity, as well as the confidence in the analytic process. A change in any of the evidence should result in a re-calculation of, or at last a flag against, the confidence in the judgment.
This information is sufficient for a user to review the analytic process and make their own assessment as to its value.
Data, observations and judgments reside in the integrated information environment and all information is spatial-temporally enabled.
This information can be compiled for distribution through a report, i.e. a compilation of observations and judgments intended for human consumption. However, such reports do not have to be in a document format. A report may also be an interactive web site, which allows users to visualize and navigate through the judgments and reasoning. They may also be dynamically updated as the underlying information changes.
Users can build their own analytics or use the analytics provided by the service. Analytics can be assembled into workflows resulting in more complex analytics.
This concept is also well described in NGA’s presentation ""Everything you wanted to know about the NSG Application Schema (NAS)"". The NAS document describes three major components of this integrated information environment:
An analytic method applied to structured data from all sources, to discover objects, relationships, or behaviors by resolving significant activity. ABI methods accelerate and deepen insight and the ability to do OBP; new insight enriches models and understanding of adversary behaviors and relationships.
A framework for organizing and sharing information, relating observations from all sources to known objects (be they units, people, locations, or events).
Based on the above mentioned conceptual ideas a feature can be almost anything. To illustrate the concept, the chosen data for the Use Case Scenario described below includes analytical observations, judgements, tweets, images and even a police radio message.
The crucial step is to move from individual features to linked features. The association describes the relationship between features and is thus the binding connection, linking objects with each other. This GFM approach works with every type of relationship.
The topic of associations has also come up in other TB12 activities and is further described in TB12 - Evaluate Semantic Enablement ER.
To evaluate the degree to which the GFM is capable of capturing information from social media and related human judgments and decisions as features, a simple use case scenario has been developed:
A large crowd moves from A to B along a predefined route,
an incident, which could temporarily block the anticipated route is reported,
the situation needs to be judged and
decisions need to be taken and potentially justified later on.
Apart from the fabricated incident at the junction, this is based on a Climate Change Protest March with 5,000+ participants. The event took place in Oakland on 7th February 2015. It was well covered by tweets before, during and after the event via @DontFrackCA.
The use case scenario and it’s associated data cover all three phases of a planned event:
During the pre-event phase, information can be derived about the topic, location and date, as well as the anticipated size and nature of the event. In the case of a planned event, where organizers and local authorities work together, this might provide information to judge the degree to which planned and actual developments align. In case of an ad hoc event, it could provide early warning indicators to trigger actions for preparedness.
During the actual event phase, social media information can be used to support situation awareness and handling. For TB12 we have inserted a tweet message reporting a suspicious package next to a junction the Climate Change Protest March plans to pass on the planned route. This requires organizers to make decisions how to proceed. The decisions are based on the current location of the crowd, which could be machine-processed information from tweets, human observations reported by radio and judgments on available information. Observations, judgments and decisions shall all be treated a features with a traceable relationship to each other.
Post-event information might be relevant to rate the effectiveness of decisions resulting actions.
Given that the scope of the GFM activity in TB12 is to proof the concept of storing heterogeneous observations and their associations in a GFM based model, it was decided to break down the scenario to a very simple chain of events:
A suspicious parcel is observed on a junction of the planned route and triggers a potential threat alert
A decision to investigate is taken based on the location of the crowd relative to the reported location
The parcel can be identified and the threat alert is cleared