[cat-interop] CSW APISO ServiceTypes

[Tom Kralidis]

Rich: good points here.  FYI we are running into this (as we speak) in
MetaSearch (https://github.com/geopython/MetaSearch) as part of being
able to seamlessly add services or data within QGIS workflows:

https://github.com/geopython/MetaSearch/issues/20
https://github.com/geopython/MetaSearch/wiki/Discovery-workflow

I know that Bart van den Eijnden (on here) has also faced these issues
as part of JavaScript implementations.

Having said this, one of the major goals of cat-interop, as discussed
at foss4g 2013, is to better articulate link types to help CSW
clients.

An important step here is to have a consistent vocabulary for
gmd:protocol, or dct:references/scheme or dc:URI/@protocol

Options:
- OGC URN Policy: http://www.opengeospatial.org/ogcUrnPolicy
- ESRI: it looks like ESRI Geoportal implements the OGC URN Policy
with some extensions/additions
- Geonetwork enumerations:
https://github.com/geonetwork/core-geonetwork/blob/develop/web/src/main/webapp/WEB-INF/data/config/schema_plugins/iso19139/loc/eng/labels.xml#L1894.
 Many downstream applications are tied to these, such as GeoNode

I propose standing up a repository on GitHub (OSGeo/LinkTypes) to:

1) identify a harmonized list of link types for:
 - metadata publishers to use
 - CSW implementations to implement as required (e.g. when harvesting, etc.)
2) based on this, produce a list a possible detection
patterns/heuristics on determining what type of link is being parsed
by a given client.  This can be used to set a link type in metadata,
or guess what a URL can do

Thoughts?




On Thu, Feb 20, 2014 at 8:32 AM, Signell, Richard <rsignell at usgs.gov> wrote:
> Catalog Interoperability folks,
>
> As part of a system test for the Integrated Ocean Observing System,
> we've been trying CSW apiso queries to different endpoints and trying
> to retrieve specific service types from the retrieved records (e.g.
> WMS, WCS, OPeNDAP).  This has been revealing, but not that surprising
> -- different endpoints represent the services differently.
>
> As an example, two geoportal servers (at NODC and NGDC) I've been
> working with have:
>
> WMS:
>
> urn:x-esri:specification:ServiceType:wms:url
> urn:x-esri:specification:ServiceType:WMS
>
> OPeNDAP:
>
>  "urn:x-esri:specification:ServiceType:odp:url"
>  "urn:x-esri:specification:ServiceType:OPeNDAP"
>
> The providers at NODC and NGDC are both willing to change, and would
> be happy to use a "standardized" representation -- if only they knew
> what it was!
>
> Have folks on this list worked on this issue yet?
>
> Thanks,
> Rich
> --
> Dr. Richard P. Signell   (508) 457-2229
> USGS, 384 Woods Hole Rd.
> Woods Hole, MA 02543-1598
> _______________________________________________
> cat-interop mailing list
> cat-interop at lists.osgeo.org
> http://lists.osgeo.org/cgi-bin/mailman/listinfo/cat-interop