WFS change request: Improve SOAP binding
OGC Doc 06-088
Open Geospatial Consortium
CR-Form-v3
CHANGE REQUEST
Web feature CR ?
Service (WFS)
rev
-
Current version:
1.1
For HELP on using this form, look at the pop-up text over the symbols.
Proposed change affects:
AS
Imp Spec X
Recom. Paper
Title:
WFS change request: Improve SOAP encoding
Source:
Arliss Whiteside
Work item code:
Category:
Other
Date: 2006-07-03
F
Use one of the following categories:
F (Critical correction)
A (corresponds to a correction in an earlier release)
B (Addition of feature),
C (Functional modification of feature)
D (Editorial modification)
Reason for change:
The method specified for indicating SOAP support in the OperationsMetadata
section of a Capabilities document is incompletely specified, and is based on
three assumptions that will not always be true:
a) The same end point URLs will always be used for HTTP POST transfers of
both SOAP and (bare) XML encoded operation requests.
b) SOAP encodings will be supported for all (or none) operation requests (that
allow HTTP POST transfer).
c) HTTP POST transfer of XML encoded operation requests will be supported for
all operation requests that allow SOAP encodings.
Summary of change: Improve the manner in which SOAP support is indicated in the
OperationsMetadata section of a Capabilities document, by using a
“PostEncoding” constraint.
Consequences if
not approved:
Different implementations will indicate SOAP support in different ways (using
different values for the current SupportsSOAP constraint), and that indication of
SOAP support will require fulfilling the three assumptions stated above.
Clauses affected:
13.3.6
Other specs
Affected:
Other comments:
Other core specifications
Abstract specifications
Recommendation Papers
Copyright © 2006 Open Geospatial Consortium, Inc. All Rights Reserved.
(Change Table 7b in Subclause 13.3.6 in document OGC 04-094 as
follows)
Table 7b – Operation constraints
Constraint Name
Description
SupportsSOAP
PostEncoding
Specifies the formats that can be used with HTTP POST transfer of
operation requests. The value “SOAP” shall indicate that SOAP encoded
operation requests can be handled, that the service can process requests
using HTTP POST and presented in a SOAP envelope as described in
subclause 6.7. The value “XML” shall indicate that (bare) XML encoded
operation requests can be handled. If the connect point URL is the same
for all SOAP-encoded and bare-XML operation requests, this
ows:Constraint element shall be included in the ows:OperationsMetadata
element. If the connect point URL is different for SOAP-encoded and
bare-XML operation requests, this ows:Constraint element shall be
included in each ows:Post element.
DefaultMaxFeatures
Specifies the default value for the maxFeatures attribute of the
element. If the constraint is not specified then there is not
limit on the number of features that a GetFeature request may return.
LocalTraverseXlinkScope
Defines the minimum and maximum number of levels, when traversing
local xlinks, that a WFS will try to resolve. The value * means to as many
all levels. If the constrain is not specified then the WFS will attempt to
resolve all levels.
RemoteTraverseXlinkScope
Defines the minimum and maximum number of levels, when traversing
remote xlinks, that a WFS will try to resolve. The value * means to as
many all levels. If the constrain is not specified then the WFS will attempt
to resolve all levels.
DefaultLockExpiry
Define the default lock expiry time in minutes. If the constraint is not
specified then locks will be held indefinitely and would require
administrator intervention to clear them.
Copyright © 2006 Open Geospatial Consortium, Inc. All Rights Reserved.
Open Geospatial Consortium
CR-Form-v3
CHANGE REQUEST
Web feature CR ?
Service (WFS)
rev
-
Current version:
1.1
For HELP on using this form, look at the pop-up text over the symbols.
Proposed change affects:
AS
Imp Spec X
Recom. Paper
Title:
WFS change request: Improve SOAP encoding
Source:
Arliss Whiteside
Work item code:
Category:
Other
Date: 2006-07-03
F
Use one of the following categories:
F (Critical correction)
A (corresponds to a correction in an earlier release)
B (Addition of feature),
C (Functional modification of feature)
D (Editorial modification)
Reason for change:
The method specified for indicating SOAP support in the OperationsMetadata
section of a Capabilities document is incompletely specified, and is based on
three assumptions that will not always be true:
a) The same end point URLs will always be used for HTTP POST transfers of
both SOAP and (bare) XML encoded operation requests.
b) SOAP encodings will be supported for all (or none) operation requests (that
allow HTTP POST transfer).
c) HTTP POST transfer of XML encoded operation requests will be supported for
all operation requests that allow SOAP encodings.
Summary of change: Improve the manner in which SOAP support is indicated in the
OperationsMetadata section of a Capabilities document, by using a
“PostEncoding” constraint.
Consequences if
not approved:
Different implementations will indicate SOAP support in different ways (using
different values for the current SupportsSOAP constraint), and that indication of
SOAP support will require fulfilling the three assumptions stated above.
Clauses affected:
13.3.6
Other specs
Affected:
Other comments:
Other core specifications
Abstract specifications
Recommendation Papers
Copyright © 2006 Open Geospatial Consortium, Inc. All Rights Reserved.
(Change Table 7b in Subclause 13.3.6 in document OGC 04-094 as
follows)
Table 7b – Operation constraints
Constraint Name
Description
SupportsSOAP
PostEncoding
Specifies the formats that can be used with HTTP POST transfer of
operation requests. The value “SOAP” shall indicate that SOAP encoded
operation requests can be handled, that the service can process requests
using HTTP POST and presented in a SOAP envelope as described in
subclause 6.7. The value “XML” shall indicate that (bare) XML encoded
operation requests can be handled. If the connect point URL is the same
for all SOAP-encoded and bare-XML operation requests, this
ows:Constraint element shall be included in the ows:OperationsMetadata
element. If the connect point URL is different for SOAP-encoded and
bare-XML operation requests, this ows:Constraint element shall be
included in each ows:Post element.
DefaultMaxFeatures
Specifies the default value for the maxFeatures attribute of the
element. If the constraint is not specified then there is not
limit on the number of features that a GetFeature request may return.
LocalTraverseXlinkScope
Defines the minimum and maximum number of levels, when traversing
local xlinks, that a WFS will try to resolve. The value * means to as many
all levels. If the constrain is not specified then the WFS will attempt to
resolve all levels.
RemoteTraverseXlinkScope
Defines the minimum and maximum number of levels, when traversing
remote xlinks, that a WFS will try to resolve. The value * means to as
many all levels. If the constrain is not specified then the WFS will attempt
to resolve all levels.
DefaultLockExpiry
Define the default lock expiry time in minutes. If the constraint is not
specified then locks will be held indefinitely and would require
administrator intervention to clear them.
Copyright © 2006 Open Geospatial Consortium, Inc. All Rights Reserved.