WFS The description of the abstract test suite is not clear in some cases.
OGC Change Request
https://portal.opengeospatial.org/public_ogc/cr_admin.php?CR...
All Fields marked with * are mandatory.
Change Request 181
#:
Assigned OGC 11-128
Document #:
Name: *Panagiotis (Peter) A. Vretanos
Organization: *CubeWerx Inc.
Email: *pvretano@cubewerx.com
Document
Name/Version:
*OpenGIS Web Feature Service 2.0 Interface Standard (also ISO 19142) / 2.0
OGC Project
Document:
*09-025r1
If this is a revision of a previous submission and you have a Change Request Number, then check here:
Enter the CR number here:
Enter the Revsion Number that you are revising here:
Title:
Source:
*The description of the abstract test suite is not clear in some cases.
*schneider@lat-lon.de
Work item code:
Category:
* A (corresponds to a correction in an earlier release)
Reason for *
change:
Having a look at Annex A.1.2 of the WFS 2.0 specification (Basic WFS),
I still wonder if "Verify the following list of conformance
tests: [...] ,A.2.11.2, [...], A.2.20.1,
A.2.20.2, [...]" really implies that the respective
functionality must be available (even if not announced by the
server).
A.2.11.2: Version navigation
A.A.2.20.1, A.2.20.2: Response paging
IMHO, this would imply that every Basic WFS has to implement
1 of 2
9/15/11 11:32 PM
OGC Change Request
https://portal.opengeospatial.org/public_ogc/cr_admin.php?CR...
"Response" as well as "Feature versions"
conformance classes!? Or can an implementation still be Basic WFS
compliant even if it does not offer Version navigation/response paging
(and sets the respective conformance classes in the capabilities to
FALSE)?
Summary of *
change:
Revise the description of the ATS to clarify that a Basic WFS does not
need to implement "Response Paging" or "Feature
versions".
Consequences if
not approved:
Clauses affected: *
A.1.2 and others
Additional
Documents
affected:
Supporting
Documentation:
Comments:
Status:
Assigned
Assigned To:
WFS DWG
Disposition:
2 of 2
Referred and Posted
9/15/11 11:32 PM
https://portal.opengeospatial.org/public_ogc/cr_admin.php?CR...
All Fields marked with * are mandatory.
Change Request 181
#:
Assigned OGC 11-128
Document #:
Name: *Panagiotis (Peter) A. Vretanos
Organization: *CubeWerx Inc.
Email: *pvretano@cubewerx.com
Document
Name/Version:
*OpenGIS Web Feature Service 2.0 Interface Standard (also ISO 19142) / 2.0
OGC Project
Document:
*09-025r1
If this is a revision of a previous submission and you have a Change Request Number, then check here:
Enter the CR number here:
Enter the Revsion Number that you are revising here:
Title:
Source:
*The description of the abstract test suite is not clear in some cases.
*schneider@lat-lon.de
Work item code:
Category:
* A (corresponds to a correction in an earlier release)
Reason for *
change:
Having a look at Annex A.1.2 of the WFS 2.0 specification (Basic WFS),
I still wonder if "Verify the following list of conformance
tests: [...] ,A.2.11.2, [...], A.2.20.1,
A.2.20.2, [...]" really implies that the respective
functionality must be available (even if not announced by the
server).
A.2.11.2: Version navigation
A.A.2.20.1, A.2.20.2: Response paging
IMHO, this would imply that every Basic WFS has to implement
1 of 2
9/15/11 11:32 PM
OGC Change Request
https://portal.opengeospatial.org/public_ogc/cr_admin.php?CR...
"Response" as well as "Feature versions"
conformance classes!? Or can an implementation still be Basic WFS
compliant even if it does not offer Version navigation/response paging
(and sets the respective conformance classes in the capabilities to
FALSE)?
Summary of *
change:
Revise the description of the ATS to clarify that a Basic WFS does not
need to implement "Response Paging" or "Feature
versions".
Consequences if
not approved:
Clauses affected: *
A.1.2 and others
Additional
Documents
affected:
Supporting
Documentation:
Comments:
Status:
Assigned
Assigned To:
WFS DWG
Disposition:
2 of 2
Referred and Posted
9/15/11 11:32 PM