[georss] [Geodata] OpenSearch GEO, OAI-MPH, CSW, GeoRSS. All miss a defined way to transfer service information

[Stefan Keller]

Great! What about:

  <dc:format>osgeo:http://geonetwork3.fao.org/ows/1[application/vnd.ogc.wms]
</dc:format>

'osgeo' is a hierarchical scheme name as required by the URI RFC 2396. Let's
call it an osgeoURL. It consists of an underlying URL-reference followed by
the mime type in brackets. An osgeoURL can be defined with the following
ABNF:

    osgeoURL = "osgeo:" URI-reference "[" mime-type "]"

Any occurence of the characters "[", "]" (and probably "=", and "," as well)
in the URL-reference MUST be encoded. (This proposal was inspired by
http://trevp.net/cryptoURL/draft-ietf-cryptoURL-01.html).

To Andrew: Some time ago I tried to summarize what OAI-PMH is here:
http://gis.hsr.ch/wiki/OAI-PMH#OAI-PMH . But you probably better look at the
source code and the live 'demo' called 'OAI Repository Explorer':
http://www.openarchives.org/pmh/tools/

To Raj: I'm wondering that librarians stick with Z39.50 because that's a
dinosaur! AFAIK there is SRU (http://www.loc.gov/standards/sru/) as the
'modern' successor (which is actually also using CQL like CSW). Here again
I'd like to be aware that Z39.50/SRU imply an online-query approach as
opposite to harvesting.
2007/10/9, Schuyler Erle <schuyler at nocat.net>:
>
> * On  9-Oct-2007 at  1:33PM PDT, Jeroen Ticheler said:
>
> > So:
> > <URI>application/vnd.ogc.wms, http://geonetwork3.fao.org/ows/1,
> > national_boundaries_africa, National administrative boundaries of
> > Africa</URI>
> > <URI>application/vnd.google-earth.kml+xml, http://www.fao.org/
> > geonetwork/srv/en/google.kml?id=2&layers=sub-
> > national_boundaries_africa, National administrative boundaries of
> > africa, National administrative boundaries of africa</URI>
> >
> > etc...
> > This kind of formatting allows most clients to properly asses what
> > they can do with the URI provided and is easy to maintain as
> > mimetypes are pretty well defined.
>
> I think you're on the right track with the MIME typing, but I'm
> concerned about your syntax and semantics there. First off, your
> example doesn't look like a URI :) and second, what if the title, URL,
> or description contains a comma? I think you have the right idea but
> I'd encourage you to look at structuring the representation
> differently...
>
> SDE
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.eogeo.org/pipermail/georss/attachments/20071010/341b21e9/attachment-0001.html