 Critical Infrastructure Collaborative Environment Architecture: Computational Viewpoint |
0.5.0 |
03-063r1 |
Joshua Lieberman |
2003-06-02 |
| *RETIRED* The objective of this document is to provide a vendor-neutral interoperable framework that enables collaborating communities to rapidly and collaboratively publish, discover, integrate and use geospatial information concerned with the protection of critical infrastructure systems in a range of sectors. Specifically, this document specifies a Computational Architecture viewpoint for a Critical Infrastructure Collaborative Environment (CICE). |
| Critical Infrastructure Collaborative Environment Architecture: Engineering Viewpoint |
0.7.1 |
03-055r1 |
Louis Rose |
2003-06-02 |
| *RETIRED* specifies the Engineering Viewpoint for the Critical Infrastructure Collaborative Environment (CICE). This open, distributed processing environment crosses organizational boundaries and includes a variety of components deployed within multiple communities. The CICE leverages OGC Web Services the publication of the availability of critical infrastructure services and data; the registration and categorization of published service and data providers; and the discovery and use of needed critical infrastructure services and data |
| Critical Infrastructure Collaborative Environment Architecture: Enterprise Viewpoint |
0.7.0 |
03-061 |
Geoffrey Ehler |
2003-05-19 |
| *RETIRED* specifies the Enterprise viewpoint for the Critical Infrastructure Collaborative Environment (CICE). |
| Critical Infrastructure Collaborative Environment Architecture: Information Viewpoint |
0.3.1 |
03-062r1 |
Richard Martell |
2003-06-27 |
| *RETIRED* specifies the information viewpoint for the Critical Infrastructure Collaborative Environment (CICE). |
| EA-SIG Collaboration White Paper |
1.0 |
04-085 |
Richard Creps,Victor Brown,Bill Floyd,John Garcia,Jeff Grinstead,Robert Kraus,Steve Matney,Robert Qu |
2004-02-20 |
| *RETIRED* The focus of collaboration services discussed in this white paper is on applications that directly support user interaction and on the applications that monitor, manage and control these interactive services. |
| EA-SIG Discovery White Paper |
1.0 |
04-086 |
Jeff Harrison,A.J. Maren,Jeff Stohlman,Mike Meyer,Glenn Pruitt,John Clink,Hans Polzer,Mark Schiffner |
2004-02-20 |
| *RETIRED* This document describes the role of Discovery Services in the net-centric enterprise. The network centric enterprise is an environment with an almost infinite variety of resources. In this rich environment, suitable resources can be found to support almost any operational need. The problem, however, is finding the appropriate resources when they are needed. Discovery services address this problem. |
| EA-SIG Enterprise Service Management White Paper |
1.0 |
04-087 |
Matt Murray,Jeff Stollman,Shue-Jane Thompson,Terry Plymell,Eli Hertz,Chuck Heazel |
2004-02-20 |
| *RETIRED* This document focuses on the goals, objectives, capabilities and recommendation for the ESM Core Enterprise Service. The charter for this team was to address three fundamental questions:
* What it Enterprise Service Management?
* What can we buy or build today?
* How should we invest for the future?
This paper responds to those questions by defining and describing ESM, discussing what is being done today, and what the group sees for the future of ESM? |
| EA-SIG Mediation White Paper |
1.0 |
04-088 |
Paul Lunceford,Steve Matney,Tom Huggins,Chuck Heazel |
2004-02-20 |
| *RETIRED* This document focuses on the goals, objectives, capabilities and recommendation for the Mediation Core Enterprise
Service. |
| Feature Portrayal Service |
0.0.30 |
05-110 |
Arliss Whiteside, Bill Woodward, co-editor |
2006-04-19 |
| This document specifies the interface to a Feature Portrayal Service (FPS), which applies styles to digital features to produce a map image. The styles applied are identified or specified by the client, and are applied to digital feature data retrieved from a Web Feature Service (WFS) identified by the client. |
| Geocoder |
0.7.6 |
01-026r1 |
Serge Margoulies |
2001-03-28 |
| *RETIRED* Geocoding is the process of linking words, terms and codes found in a text string to their applicable geospatial features, with known locations. (Locations are defined as geometry; usually points with x, y coordinates.) |
| Geoparser |
0.7.1 |
01-035 |
Jeff Lansing |
2001-03-27 |
| *RETIRED* Geoparsing refers to the capability to process a textual document and identify key words and phrases that have a spatial context. |
| GeoXACML, a spatial extension to XACML |
0.0.1 |
05-036 |
Andreas Matheus |
2005-06-17 |
| This OGC document proposes one possible solution for the declaration and enforcement of access
restrictions for object-oriented geodata, available through a Service-based Geo Data Infrastructure. It is the
intension of the author to motivate the requirement for such an access control, give a problem statement,
discuss an alternative approach and describe the solution, based on GeoXACML. |
| Level 0 Profile of GML3 for WFS |
0.0.10 |
03-003r10 |
Peter Vretanos |
2004-05-10 |
| *RETIRED* This is a GML application profile known as Level 0 - also known as Simple GML. |
| Location Organizer Folder |
1.0 |
01-037 |
Ron Lake |
2001-03-30 |
| *RETIRED* The Location Organizer Folder (LOF) is a GML document that provides a structure for organizing the information related to a particular event or events of interest. |
| OpenGIS Geographic Objects Implementation Specification *RETIRED* |
1.0.0 |
03-064r10 |
Greg Reynolds |
2005-05-04 |
| *THIS STANDARD HAS BEEN RETIRED*
The OpenGIS® Geographic Objects Interface Standard (GOS) provides an open set of common, lightweight, language-independent abstractions for describing, managing, rendering, and manipulating geometric and geographic objects within an application programming environment. It provides both an abstract object standard (in UML) and a programming-language-specific profile (in Java). The language-specific bindings serve as an open Application Program Interface (API). |
| OpenGIS Grid Coverage Service Implementation Specification |
1.0 |
01-004 |
Louis Burry |
2001-01-12 |
| **This document has been retired. It is not supported. You should consider using Web Coverage Service.**
This specification was designed to promote interoperability between software implementations by data vendors and software vendors providing grid analysis and processing capabilities. |
| OpenGIS Transducer Markup Language *RETIRED* |
1.0.0 |
06-010r6 |
Steve Havens |
2007-07-02 |
| *THIS STANDARD HAS BEEN RETIRED*
The OpenGIS® Transducer Markup Language Encoding Standard (TML) is an application and presentation layer communication protocol for exchanging live streaming or archived data to (i.e. control data) and/or sensor data from any sensor system. A sensor system can be one or more sensors, receivers, actuators, transmitters, and processes. A TML client can be capable of handling any TML enabled sensor system without prior knowledge of that system.
The protocol contains descriptions of both the sensor data and the sensor system itself. It is scalable, consistent, unambiguous, and usable with any sensor system incorporating any number sensors and actuators. It supports the precise spatial and temporal alignment of each data element. It also supports the registration, discovery and understanding of sensor systems and data, enabling users to ignore irrelevant data. It can adapt to highly dynamic and distributed environments in distributed net-centric operations.
The sensor system descriptions use common models and metadata and they describe the physical and semantic relationships of components, thus enabling sensor fusion.
This is one of the OGC Sensor Web Enablement (SWE) [http://www.opengeospatial.org/ogc/markets-technologies/swe] suite of standards.
|
