OGC Testbed 10

Request for Quotations (RFQ)


Call for Participation (CFP)


OGC Testbed 10

Annex B - Architecture

RFQ Issuance Date: 15 July 2013

Proposal Due Date: 26 August 2013

Copyright © 2013 Open Geospatial Consortium
To obtain additional rights of use, visit http://www.opengeospatial.org/legal/


A significant part of OGC is the Interoperability Program (IP), which conducts international initiatives such as Testbeds, Pilot Projects, Interoperability Experiments, and Interoperability Support Services. These are all designed to encourage rapid development, testing, validation, and adoption of open, consensus based standards and best practices. Descriptions of these various initiatives can be found here:


The OGC Testbed 10 is a Testbed within the Interoperability Program. OGC Testbed 10 is a global, hands-on and collaborative prototyping activity designed for rapid development and delivery of Service-Oriented Architecture (SOA) components and services, as well as experience leading to documented best practices. The results of this program are initially documented as Engineering Reports and submitted to OGC’s Technical Committee for consideration as discussion papers, candidate specifications, and best practices. Upon formal adoption within the OGC Specification Program, standards and best practices are then made publicly available.  Discussion papers may also be made publicly available, with the understanding that these do not represent a formal position of the OGC. 

An index to the policies and procedures governing OGC can be found here:


The policies and procedures that define the OGC Interoperability Program are available here:


The purpose of Annex B is to describe the detailed context and requirements for Testbed 10  development, which involves multiple interdependent activity threads. The requirements and architectures presented here are based upon a collaborative effort between OGC Testbed 10 Sponsors and OGC’s IP program and project management staff, called the IP Team. The OGC Testbed 10 architecture builds on the results from previous and ongoing OGC IP initiatives, existing OGC discussion papers and specifications, OGC Technical Committee activities, and publicly available documentation from related standards organizations including ISO, W3C, OASIS, and others.

Section 2
provides an overview of the OGC Testbed 10 development threads.
Section 3
discusses the architectural approach and technical baseline for OGC Testbed 10.
Section 4
discusses the architectural approaches and issues for each of the OGC Testbed 10 development threads.

The OGC public website provides a Glossary of Terms that may be useful to aid in understanding and interpretation of terms and abbreviations contained throughout this RFQ.

2Thread Summaries

2.1Cross-Community Interoperability (CCI) Thread

Go to CCI

The Cross-Community Interoperability (CCI) thread seeks to build on interoperability within communities sharing geospatial data and advance semantic mediation approaches for data discovery, access and use of heterogeneous data models and heterogeneous metadata models.  This thread will explore the creation of domain ontologies and tools to create, assemble, and disseminate geographic data provided voluntarily by individuals. In addition to build integration across all OGC web services with the intent to provide a better understanding of service content and the relationships or associations that exist between OGC services and resources/content. The topics within CCI include:

Go to CCI

2.2Open Mobility Thread

Go to Open Mobility

Client applications are mobile. They can be found in enterprise desktop environments, workhorse tablets, or phone platforms. Information services are mobile. They are distributed across clouds, internal servers and even individual users. And they consist of raw data and just-in-time processing capabilities. With such an adaptive, open environment, security is a must. The Open Mobility thread of OGC Testbed 10 explores the geospatial standards requirements to implement these concepts.

Topics in this thread include:

Go to Open Mobility


Go to Aviation

The Aviation Thread of OGC Testbed 10 seeks to develop and demonstrate the use of the Aeronautical Information Exchange Model (AIXM) and especially the Flight Information Exchange Model (FIXM) in an OGC Web Services environment.

The work to be performed in this thread includes the following:

Go to Aviation

2.4Types of Deliverables

The OGC Testbed 10 threads require several types of deliverables:

Documents - Engineering Reports (ER), Information Models (IM), Encodings (EN), Change Requests (CR):
will be prepared in accordance with OGC published templates as defined on the OGC portal. Engineering Reports will be delivered by posting on the OGC Portal Pending Documents list when complete and the document has achieved a satisfactory level of consensus among interested participants, contributors and editors. Engineering Reports are the formal mechanism used to deliver results of the Interoperability Program to sponsors and to the OGC Specification Program Domain and Specification Working Groups for consideration.

Implementations - Services, Clients, Datasets and Tools:
will be provided by methods suitable to its type and stated requirements. For example, services and components (ex. WFS) are delivered by deployment of the service or component for use in the testbed via an accessible URL. A Client software application or component may be used during the testbed to exercise services and components to test and demonstrate interoperability; however, it is most often not delivered as a license for follow-on usage. Implementations of services, clients and data instances will be developed and deployed in the Aviation thread for integration and interoperability testing, in support of the agreed-up thread scenario(s) and technical architecture. The services, clients and tools may be invoked for cross-thread scenarios in demonstration events.

Note that certain draft deliverables will be required by the Interim Milestone at the date for use in cross-thread development. These early deliverables will be designated and handled on a thread-by-thread basis.


3OGC Testbed 10 Baseline

3.1OGC Reference Model

Reference: OGC Reference Model version 2.1, document OGC 08-062r7


The OGC Reference Model (ORM) provides an architecture framework for the ongoing work of the OGC. Further, the ORM provides a framework for the OGC Standards Baseline. The OGC Standards Baseline consists of the member-approved Implementation/Abstract Specifications as well as for a number of candidate specifications that are currently in progress.

The ORM is a living document that is revised on a regular basis to continually and accurately reflect the ongoing work of the Consortium. We encourage respondents to this RFQ to learn and understand the concepts that are presented in the ORM.

The structure of the ORM is based on the Reference Model for Open Distributed Processing (RM-ODP), also identified as ISO 10746. This is a multi-dimensional approach well suited to describing complex information systems. This Annex of the OGC Testbed 10 RFQ will use one or more of the upper four viewpoints of RM-ODP: Enterprise, Information, Computational, and Engineering, as shown in the figure below, for discussing the context for each activity thread in OGC Testbed 10.

Figure 1 – RM-ODP Viewpoints used in OGC Reference Model

3.2OGC Standards Baseline

The OGC Standards Baseline, at any point in time, is the set of all Adopted Standards plus all other technical documents that have been made available to the public by the OGC Technical and Planning Committees. The Standards Baseline comprises all member-approved Implementation Standards, Abstract Standards, and Best Practices documents. These standards and related documents are freely available to the public at this website:


Each major section of the thread descriptions below identifies the relevant standards and other useful references, both normative and informative. The context of the description will make it clear whether a standard is normative (normally expressed as “will” or “shall” be used) or informative (“may” or “should”).