OWS Common 1.1 Change Request � Update Sequence and Contents Parameter Precedence
OGC Doc 08-013
Open Geospatial Consortium
CR-Form-v3
CHANGE REQUEST
OWS 1.1 CR ?
rev
1.1
Current version:
1.1
For HELP on using this form, see bottom of this page or look at the pop-up text over the symbols.
Proposed change affects:
AS
Imp Spec X
Best Practices Paper
Other
Title:
OWS Common 1.1 Change Request – Update Sequence and Contents Parameter
Precedence
Source:
Steven Keens, PCI Geomatics
Work item code:
Category:
Date: January 30, 2008
A
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)
Detailed explanations of the above categories can
be found in the TC Policies and Procedures.
Reason for change:
Provide precedence to the UpdateSequence and Contents parameters when
both are used in a single request
Summary of change: The UpdateSequence shall take precedence over the Contents parameters when
both are present in a GetCapabilities request.
Consequences if
not approved:
Clauses affected:
Other specs
Affected:
Specific OWS implementations will behave differently when faced with the two
parameters in a request.
11.5.6
Supporting Doc.
X Other core specifications
Abstract specifications
Best Practices Document
Other comments:
Status
Disposition
Any dependant upon OWS Common 1.1
The OGC Technical Committee Policies & Procedures 05-020r3
Table 1 — Parameters in GetCapabilities operation request
Names a
service
service
Definition
Service type identifier
request
request
Operation name
acceptVersio
ns
AcceptVersi
ons
sections
Sections
Prioritized sequence of one or
more specification versions
accepted by client, with
preferred versions listed first
Unordered list of zero or more
names of requested sections in
complete service metadata
document b
updateSeque
nce
updateSeque
nce
Service metadata document
version, value is “increased”
whenever any change is made
in complete service metadata
document
Prioritized sequence of zero or
more response formats desired
by client, with preferred
formats listed first
Data type and value
Character String type, not empty
Value is OWS type abbreviation
(e.g., “WMS”, “WFS”)
Character String type, not empty
Value is operation name
(e.g., “GetCapabilities”)
Sequence of Character String type,
each not empty
Value is list of x.y.z “version”
values
Sequence of Character String type,
each not empty
Value is list of section names
Allowed section names are
specified by each Implementation
Specification
Character String type, not empty
Values are selected by each server,
and are always opaque to clients
Multiplicity and use
One (mandatory)
One (mandatory)
Zero or one (optional)
When omitted, return
latest supported version
(see Subclause 7.3.2)
Zero or one (optional)
When omitted or not
supported by server,
return complete service
metadata document c
Zero or one (optional)
When omitted or not
supported by server,
return latest service
metadata document c
acceptForma
Sequence of Character String type,
Zero or one (optional)
ts
each not empty
When omitted or not
AcceptForm
Value is list of format identifiers
supported by server,
ats
Identifiers are MIME types of
return service metadata
formats useful for service metadata
document using MIME
documents
type "text/xml"
a
Although some values listed in the “Name” column appear to contain spaces, they shall not contain
spaces.
b
The “Sections” parameter specifies which XML elements within a service metadata document shall be
returned, within a (usually abbreviated) “Capabilities” element. The allowed section name values shall be
specified by each Implementation Specification, as specified in Subclause 7.3.3.
c
When in conflict, the “UpdateSequence” parameter shall take precedence over the “Sections” parameter
when both paremeters are present in a request. Table 7 lists the conflict condition.
Table 2 Use of updateSequence parameter
Operation request
updateSequence value
None
Any
Equal
Service metadata
updateSequence value
Any
None
Equal
Server response
most recent service metadata document
most recent service metadata document
service metadata document with only
“version” and “updateSequence”
parameters a
most recent service metadata document
Lower
Higher
exception report with exceptionCode =
Higher
Lower
InvalidUpdateSequence b
a
When the request contains a “Contents” parameter and an “UpdateSequence” parameter and the
request “UpdateSequence” value is equal to the service metadata “UpdateSequence” value then the server
shall respond as specified in this table.
Last Revision Date: 2 December 2017
Page 2
Open Geospatial Consortium
CR-Form-v3
CHANGE REQUEST
OWS 1.1 CR ?
rev
1.1
Current version:
1.1
For HELP on using this form, see bottom of this page or look at the pop-up text over the symbols.
Proposed change affects:
AS
Imp Spec X
Best Practices Paper
Other
Title:
OWS Common 1.1 Change Request – Update Sequence and Contents Parameter
Precedence
Source:
Steven Keens, PCI Geomatics
Work item code:
Category:
Date: January 30, 2008
A
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)
Detailed explanations of the above categories can
be found in the TC Policies and Procedures.
Reason for change:
Provide precedence to the UpdateSequence and Contents parameters when
both are used in a single request
Summary of change: The UpdateSequence shall take precedence over the Contents parameters when
both are present in a GetCapabilities request.
Consequences if
not approved:
Clauses affected:
Other specs
Affected:
Specific OWS implementations will behave differently when faced with the two
parameters in a request.
11.5.6
Supporting Doc.
X Other core specifications
Abstract specifications
Best Practices Document
Other comments:
Status
Disposition
Any dependant upon OWS Common 1.1
The OGC Technical Committee Policies & Procedures 05-020r3
Table 1 — Parameters in GetCapabilities operation request
Names a
service
service
Definition
Service type identifier
request
request
Operation name
acceptVersio
ns
AcceptVersi
ons
sections
Sections
Prioritized sequence of one or
more specification versions
accepted by client, with
preferred versions listed first
Unordered list of zero or more
names of requested sections in
complete service metadata
document b
updateSeque
nce
updateSeque
nce
Service metadata document
version, value is “increased”
whenever any change is made
in complete service metadata
document
Prioritized sequence of zero or
more response formats desired
by client, with preferred
formats listed first
Data type and value
Character String type, not empty
Value is OWS type abbreviation
(e.g., “WMS”, “WFS”)
Character String type, not empty
Value is operation name
(e.g., “GetCapabilities”)
Sequence of Character String type,
each not empty
Value is list of x.y.z “version”
values
Sequence of Character String type,
each not empty
Value is list of section names
Allowed section names are
specified by each Implementation
Specification
Character String type, not empty
Values are selected by each server,
and are always opaque to clients
Multiplicity and use
One (mandatory)
One (mandatory)
Zero or one (optional)
When omitted, return
latest supported version
(see Subclause 7.3.2)
Zero or one (optional)
When omitted or not
supported by server,
return complete service
metadata document c
Zero or one (optional)
When omitted or not
supported by server,
return latest service
metadata document c
acceptForma
Sequence of Character String type,
Zero or one (optional)
ts
each not empty
When omitted or not
AcceptForm
Value is list of format identifiers
supported by server,
ats
Identifiers are MIME types of
return service metadata
formats useful for service metadata
document using MIME
documents
type "text/xml"
a
Although some values listed in the “Name” column appear to contain spaces, they shall not contain
spaces.
b
The “Sections” parameter specifies which XML elements within a service metadata document shall be
returned, within a (usually abbreviated) “Capabilities” element. The allowed section name values shall be
specified by each Implementation Specification, as specified in Subclause 7.3.3.
c
When in conflict, the “UpdateSequence” parameter shall take precedence over the “Sections” parameter
when both paremeters are present in a request. Table 7 lists the conflict condition.
Table 2 Use of updateSequence parameter
Operation request
updateSequence value
None
Any
Equal
Service metadata
updateSequence value
Any
None
Equal
Server response
most recent service metadata document
most recent service metadata document
service metadata document with only
“version” and “updateSequence”
parameters a
most recent service metadata document
Lower
Higher
exception report with exceptionCode =
Higher
Lower
InvalidUpdateSequence b
a
When the request contains a “Contents” parameter and an “UpdateSequence” parameter and the
request “UpdateSequence” value is equal to the service metadata “UpdateSequence” value then the server
shall respond as specified in this table.
Last Revision Date: 2 December 2017
Page 2