<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; ">Jeroen,<DIV><BR class="khtml-block-placeholder"></DIV><DIV>You could certainly put a WFS / WCS URL in to DataURL, but that does not have a place for describing the semantic of the URL except as an opaque reference. Fine for a client with inside knowledge, but not very general.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Most combined services provide an implicit link by naming the layer and the featuretype identically. This is also not very general or explicit.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>My suggestion for now as a more general approach would be to use the same MetadataURL for all service offerings (layers, featuretypes, coverages, etc.) based on the same data. There can also be multiple MetadataURL's in an offering, distinguished by a language or schema label. One could even define a dataIdentifier schema (e.g. URN schema) to hold this specific ID information. Yes, at least one MetadataURL should point at a real data description, but a URI it can also be a global key for the association across any number of services. A client could then match the URI between capabilities documents to determine the association and a catalog could show (all of) the service offerings for a given dataset.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Cheers,</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Josh</DIV><DIV><BR><DIV><DIV>On Nov 9, 2005, at 1:19 PM, Jeroen Ticheler wrote:</DIV><BR class="Apple-interchange-newline"><BLOCKQUOTE type="cite">Hi!<DIV>We are trying to find the (most suitable) way of associating a WFS or a WCS to an existing WMS service. The purpose of this is that we can use WMS to display the interactive maps while we use the WFS/WCS to extract data from the server and make it available to the user as GML, shapefile, GeoTIFF etc... to be downloaded from an FTP or directly for local use.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>The problems we have are two-fold:</DIV><DIV>1- What is the best location in a Capabilities document to do this? We want our client application to know of the existence of the WFS or WCS service.</DIV><DIV><SPAN class="Apple-tab-span" style="white-space:pre"> </SPAN>What we think as best candidates are:</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV><SPAN class="Apple-style-span"><SPAN class="Apple-tab-span" style="white-space:pre"> </SPAN>- the <B>DataURL</B> element </SPAN></DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV><SPAN class="Apple-style-span">(definition: A server may use DataURL to offer a link to the underlying data represented by a particular layer. The </SPAN></DIV><DIV>enclosed Format element indicates the file format MIME type of the data file.)</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV><SPAN class="Apple-style-span"><SPAN class="Apple-tab-span" style="white-space:pre"> </SPAN>- or the <B>FeatureListURL</B> element </SPAN></DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV><SPAN class="Apple-style-span">(definition: A server may use a <FeatureListURL> element to point to a list of the features represented in a Layer. </SPAN></DIV><DIV>FeatureListURL is not inherited by child layers. The enclosed Format element indicates the file format MIME </DIV><DIV>type of the feature list.)</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>2- If we use one of these, we think of putting in the link to the service and a suitable MIME type. We have seen the following MIME types used for WMS and WFS getCapabilities requests, but are not sure they are standard and also we didn't find any reference to a similar WCS MIME type. What to do???</DIV><DIV><SPAN class="Apple-tab-span" style="white-space:pre"> </SPAN></DIV><DIV>We found:</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV><SPAN class="Apple-tab-span" style="white-space:pre"> application/vnd.ogc.w</SPAN><B>m</B><SPAN class="Apple-tab-span" style="white-space:pre">s_xml</SPAN></DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>and</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV><SPAN class="Apple-tab-span" style="white-space:pre"> application/vnd.ogc.wfs_xml</SPAN></DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV><SPAN class="Apple-tab-span" style="white-space:pre"> </SPAN>- Should we use these MIME types to indicate the URL points to a WMS or WFS getCapabilities?</DIV><DIV><SPAN class="Apple-tab-span" style="white-space:pre"> </SPAN>- Should we assume we can use <SPAN class="Apple-tab-span" style="white-space:pre"> application/vnd.ogc.w</SPAN>c<SPAN class="Apple-tab-span" style="white-space:pre">s_xml </SPAN>for a WCS getCapabilities MIME type!?</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>We have not found any of the application/vnd.ogc MIME type registered at <A href="http://www.iana.org/assignments/media-types/">http://www.iana.org/assignments/media-types/</A> What should be our conclusion on that?</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Thanks in advance!</DIV><DIV>Ciao,</DIV><DIV>Jeroen & Stefano</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">_______________________________________________</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">OpenSDI mailing list</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><A href="mailto:OpenSDI@lists.eogeo.org">OpenSDI@lists.eogeo.org</A></DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><A href="http://lists.eogeo.org/mailman/listinfo/opensdi">http://lists.eogeo.org/mailman/listinfo/opensdi</A></DIV> <BR class="Apple-interchange-newline"></BLOCKQUOTE></DIV><BR></DIV></BODY></HTML>