• Introduction
• Technical analysis
• Issues and recommendations
• European SIF

OWS SOAP Binding

Summary

“INSPIRE Drafting Team Network Services (DT NS) has adopted SOAP 1.1 protocol binding while current on-going works of OGC Standard Working Group, especially OWS Common 1.2 SWG and WMS, tends to adopt SOAP 1.2 protocol binding. SOAP 1.1 and SOAP 1.2 are not compatible.

INSPIRE DT NS recommends the usage of header of SOAP message to store recurring information while OGC OWS Common 1.2 SWG use only the body of the message as an envelop of a POST request. Consequently Information like language parameter is present in body part in OGC standard while store in heard in INSPIRE implementing rules.”

Classification

Category	Access and Processing services
Identifier	ISSUE-WMS-001
Type of recommended activity	Revising existing specifications / standards
Organisations addressed	INSPIRE DT NS, OGC Architecture Board, OWS Common 1.2 SWG, WMS 1.4 SWG.

Additional information

Context	The draft INSPIRE Network Services SOAP Framework specifies the use of SOAP in conformity to WS-I Basic Profile 1.2. SOAP 1.1 will be the initial SOAP version used for the INSPIRE SOAP framework. The change request 06-094r1 on OWS Common 1.2 SWG recommends the use of SOAP 1.2 as messaging protocol. INSPIRE seems to be about to adopt this choice as soon as the WS-I Basic Profile 2.0 will change from draft to final version. SOAP protocol is supported by OGC by including the POST request into the body of a SOAP message, including parameter such as requested language or security information. From its side INSPIRE DT NS recommends the usage of SOAP header message to store recurrent information such as multilingualism and authentication parameter.
Rationale	SOAP 1.1 and SOAP 1.2 are not compatible each other. Recurrent parameters such as multilingualism or security parameters are expected to be present in SOAP header on INSPIRE side although present in the body of the message and vice versa.
Dependencies	None
Further background information	Technology Watch Report - Data Access and Processing [PDF] Comparative analysis report (version 2) [PDF] Comparative Analysis Report (version 2) - Annex Recommendations [PDF]
Main discussion points	SOAP protocol version selection Usage of header and body part of a SOAP message
Roadmap	Inform addressed organisations, follow up activities.