For OWS-10, WFS standards group chair Peter Vretanos (at al) demonstrated enhancements to OGC web services including service identifiers and a GetAssociations operation that allows discovery of related services. This has not yet (AFAIK) made it in to any standard but would in my view be a useful enhancement for GeoServer as it addresses the problem of how to discover relationships between services.
The OWS-10 part starts at slide 36 in this presentation to the Geneva Technical Committee meeting in June (not presented due to lack of time but had been discussed with the WFS/FES SWG). Republished here with Peter's permission (the original location is password protected): http://siss.csiro.au/siss/wfs-fes-swg/20140611_WFS_SWG_Minutes.ppt
Sounds fine Ben, I always thoughts publishers were supposed to stick up an OGC catalog to publish their associations (thus keeping individual services focused and “simple”).
I thought we had a little metadata that can tie WMS layers to WFS featureTypes (online resource or something?).
For OWS-10, WFS standards group chair Peter Vretanos (at al)
demonstrated enhancements to OGC web services including service
identifiers and a GetAssociations operation that allows discovery of
related services. This has not yet (AFAIK) made it in to any standard
but would in my view be a useful enhancement for GeoServer as it
addresses the problem of how to discover relationships between services.
The OWS-10 part starts at slide 36 in this presentation to the Geneva
Technical Committee meeting in June (not presented due to lack of time
but had been discussed with the WFS/FES SWG). Republished here with
Peter’s permission (the original location is password protected): http://siss.csiro.au/siss/wfs-fes-swg/20140611_WFS_SWG_Minutes.ppt
Service registries (e.g. GeoNetwork) require manual addition of service URLs. GeoNetwork can then harvest the service URL to discover feature types, but there is nothing that relates different services. For example, separate WMS, WFS, and WCS service instances could all describe the same data. Current workflows involve manual registry curation and ugly hacks such as free text keywords (not controlled vocabularies); these are not portable across CS/W or Z39.50 harvesting.
Peter's OWS-10 work proposes a way of standardising discovery of these relationships for *all* OWS services.
Kind regards,
Ben.
On 18/08/14 11:29, Jody Garnett wrote:
Sounds fine Ben, I always thoughts publishers were supposed to stick up
an OGC catalog to publish their associations (thus keeping individual
services focused and "simple").
I thought we had a little metadata that can tie WMS layers to WFS
featureTypes (online resource or something?).
Jody Garnett
--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
Software Engineer
CSIRO Mineral Resources Flagship
Australian Resources Research Centre