[[WIS]]
== Web Integration Service
=== GetCapabilities operation
==== Introduction
The Web Integration Service (WIS) is an aggregation service whose only purpose is to provide a list of references to a suite of other, perhaps related OGC services available at an endpoint.
In keeping with the evolutionary refinement and reuse goal stated in Clause 6.1, the web integration service only defines a single operation, GetCapabilities, and responds using a standard OGC capabilities document whose content section lists the available services accessible at that end point.
A web integration service shall implement the KVP-encoding of the GetCapabilities operation.
A web integration service may optionally implement the XML-encoding of the GetCapabilities operation.
==== Request
===== UML
The following figure defines the schema of the GetCapabilities request.
[[get_capabilities_uml]]
.UML class diagram for the GetCapabilities operation
image::includes/images/UML_GetCapabilities.png["UML_GetCapabilities",scaledwidth="50%",align="center"]
===== KVP encoding
The KVP encoding of the GetCapabilities request shall be as specified in OGC 06-121r3:2009, 7.2.2. The value of the service parameter shall be fixed to "WIS".
===== XML encoding
The following XML Schema fragment defines the XML-encoding of the GetCapabilities request.
----
----
==== Response
===== UML
The WIS's response to a GetCapabilities request is essentially a standard OGC capabilities document with a content section composed of zero or more ows:ServiceIdentification sections each describing one OGC web service available at the endpoint.
The following figure defines the schema of the ServiceIdentification section:
[[service_ident_uml]]
.UML class diagram for the ServiceIdentification section
image::includes/images/UML_ServiceIdentification.png["service_ident_uml",scaledwidth="80%",align="center"]
Each service is characterized by its type (i.e. WMS, WMTS, WFS, etc.), the base
URL of the service and the standard ServiceIdentification description of the
service from Web Service Common (see OGC 06-121r9).
The value of the "type" parameter can be a token – such as the three letter
acronyms commonly used by OGC – or a _<>_ for the service.
The value of the "baseURL" parameter is the service URL to which
GetCapabilities request (see 06-121r9, Clause 7) parameters are appended
to form a valid request URL.
===== XML encoding
The following XML Schema fragment defines the schema for the XML-encoded
response to a WIS GetCapabilities request.
----
----
==== NoOp operation
This engineering report defines an additional WIS operation named "NoOp" that all clients shall ignore. The NoOp operation only exists to satisfy XML validation requirements for capabilities documents imposed by the Web Service Common standard (see OGC 06-121r9, 7.4.6) which requires that OGC web services implement the GetCapabilities operation plus one additional operation. Clearly, the web service common standard did not anticipate the usefulness of a service that only implements the GetCapabilities request. A change request has been posted against OGC 06-121r9 to remove this requirement (see OGC 14-026).
==== Security considerations
Given the focus on security in Testbed-12, it is worth mentioning that the
content of a WIS capabilities document may be tailored to suite the
authentication level of the user. An authenticate user may see more services
listed in the capabilities document than a non-authenticated user might.
==== Relationship to CSW
The question may be raised about the difference between a WIS and a CSW
registry service. Unlike a CSW, the WIS provides a light weight, standalone,
peer-to-peer discovery mechanism that clients may use to interrogate a providers
offerings at an endpoint. The discovery possible using the WIS is not quite as
rich as that possible using a CSW but it may be sufficient for many user cases
including the harvesting use case described in
_<>_ clause. From an implementation
standpoint, the WIS is certainly a more lightweight implementation.
==== Example
In response to the following request:
----
http://www.somcorp.com/wis?service=WIS&request=GetCapabilities
----
a web integration service might generate the following capabilities document:
----
SomeSERV
A suite of OGC web services by Some Corp.
SomeSERV
7.0.1
Some Corp.
John Smith
Senior Developer
+1-416-555-1234
+1-416-555-5678
1 Main St., Suite 1
SomeCity SomeProvince
X1X 2Y2
Canada jsmith@somecorp.com
KVP
application/xml
application/x-bxml
SomeSERV WMS
OGC-compliant cascading web map server (WMS) by Some Corp.
WMS
1.3.2
1.3.1
1.3.0
1.1.1
1.1.0
1.0.0
The USGS National Map Web Feature Service (subset)
This web feature service offers a subset of the USGS National Map. The National Map is a collaborative effort among the USGS and other Federal, State, and local partners to improve and deliver topographic information for the Nation. The geographic information available from The National Map includes hydrography, boundaries, transportation, structures, and land cover. Other types of geographic information can be added within the viewer or brought in with The National Map data into a Geographic Information System to create specific types of maps or map views. The National Map is a significant contribution to the National Spatial Data Infrastructure (NSDI) and currently is being transformed to better serve the geospatial community by providing high quality, integrated geospatial data and improved products and services including new generation digital topographic maps.
WFS
USGS
TNM
Web
Feature
Service
hydrography
boundaries
transportation
structures
land
cover
WFS
2.0.0
1.1.0
1.0.0
None
None
The USGS National Map Web Feature Service (subset)
This web feature service offers a subset of the USGS National Map. The National Map is a collaborative effort among the USGS and other Federal, State, and local partners to improve and deliver topographic information for the Nation. The geographic information available from The National Map includes hydrography, boundaries, transportation, structures, and land cover. Other types of geographic information can be added within the viewer or brought in with The National Map data into a Geographic Information System to create specific types of maps or map views. The National Map is a significant contribution to the National Spatial Data Infrastructure (NSDI) and currently is being transformed to better serve the geospatial community by providing high quality, integrated geospatial data and improved products and services including new generation digital topographic maps.
WFS
USGS
TNM
Web
Feature
Service
hydrography
boundaries
transportation
structures
land
cover
WFS
2.0.0
1.1.0
1.0.0
None
None
SomeSERV WCS - OWS9
OGC-compliant web coverage server (WCS) by Some Corp.
WCS
1.1.2
1.1.1
1.0.0
SomeSERV WCS - STDS
OGC-compliant web coverage server (WCS) by Some Corp.
WCS
1.1.2
1.1.1
1.0.0
Catalogue Service Web (CSW) by Some Corp.
The Some Corp. Catalog Service Web (CSW) implements a web registry service that complies to the Open Geospatial Consortium Inc.'s Catalogue Service implementation specification V2.0.2 (see 07-006r1) which specifies the interfaces, bindings, and a framework for defining application profiles required to publish and access digital catalogues of metadata for geospatial data, services, and related resource information. Metadata act as generalized properties that can be queried and returned through catalogue services for resource evaluation and invocation or retrieval of the referenced resource.
catalogue
CSW
2.0.2
none
none
----
Since this capabilities document is composed mostly of standard OGC components it is an easy task to extend an OGC catalogue to consume this document. The catalogue can then automatically determine which services are offered by this provider and harvest each one in turn also maintaining the associations between the web integration service and its child services.