Add service id field to service identification section.
OGC Change Request
https://portal.opengeospatial.org/public_ogc/cr_admin.php?CR...
All Fields marked with * are mandatory.
Change Request 165
#:
Assigned OGC 11-117
Document #:
Name: *Panagiotis (Peter) A. Vretanos
Organization: *CubeWerx Inc.
Email: *[email protected]
Document
Name/Version:
*Web Service Common Implementation Specification / 2.0.0
OGC Project
Document:
*06-121r9
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:
*Add service id field to service identification section.
*[email protected]
Work item code:
Category:
* B (Addition of feature)
Reason for *
change:
The only way catalogues have to distinguish one OGC service instance
from another is by using the service's URL (e.g its base URL or
GetCapabilities URL) which is not a reliable method. So, there needs
to be some other, more robust, way for a catalogue to distinguish one
OGC from another when it harvests them.
Summary of *
change:
1 of 2
9/15/11 11:20 PM
OGC Change Request
https://portal.opengeospatial.org/public_ogc/cr_admin.php?CR...
Add a "ServiceInstanceId" field to the service
identification section of the capabilities document. The value of the
ServiceInstanceId shall be a fixed UUID. This way, a catalogue can
distinguish one OGC service instance from another. It is important
that this value be mandatory and that it be universally unique -hence the UUID requirement.
Consequences if It just makes it that much harder for OGC catalogues to harvest OGC
services because they need to implement complex URL comparison
not approved:
functions in order to be able to robustly distinguish one OGC service
instance from another.
Clauses affected: *
T.B.D.
Additional
Documents
affected:
Supporting
Documentation:
Comments:
Status:
2 of 2
Assigned
Assigned To:
OWSCommon1.2SWG
Disposition:
Referred and Posted
9/15/11 11:20 PM
https://portal.opengeospatial.org/public_ogc/cr_admin.php?CR...
All Fields marked with * are mandatory.
Change Request 165
#:
Assigned OGC 11-117
Document #:
Name: *Panagiotis (Peter) A. Vretanos
Organization: *CubeWerx Inc.
Email: *[email protected]
Document
Name/Version:
*Web Service Common Implementation Specification / 2.0.0
OGC Project
Document:
*06-121r9
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:
*Add service id field to service identification section.
*[email protected]
Work item code:
Category:
* B (Addition of feature)
Reason for *
change:
The only way catalogues have to distinguish one OGC service instance
from another is by using the service's URL (e.g its base URL or
GetCapabilities URL) which is not a reliable method. So, there needs
to be some other, more robust, way for a catalogue to distinguish one
OGC from another when it harvests them.
Summary of *
change:
1 of 2
9/15/11 11:20 PM
OGC Change Request
https://portal.opengeospatial.org/public_ogc/cr_admin.php?CR...
Add a "ServiceInstanceId" field to the service
identification section of the capabilities document. The value of the
ServiceInstanceId shall be a fixed UUID. This way, a catalogue can
distinguish one OGC service instance from another. It is important
that this value be mandatory and that it be universally unique -hence the UUID requirement.
Consequences if It just makes it that much harder for OGC catalogues to harvest OGC
services because they need to implement complex URL comparison
not approved:
functions in order to be able to robustly distinguish one OGC service
instance from another.
Clauses affected: *
T.B.D.
Additional
Documents
affected:
Supporting
Documentation:
Comments:
Status:
2 of 2
Assigned
Assigned To:
OWSCommon1.2SWG
Disposition:
Referred and Posted
9/15/11 11:20 PM