<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Hi Pedro,<br>
<br>
This is a very valid question. <br>
When we were implementing OGC OpenSearch Geo/Time extension in
pycsw, the CSW 3 implementation was about to start. <br>
We noticed that the OpenSearch Temporal was defined a bit
differently in CSW3 document than the OpenSearch Geo/Time
document.<br>
So we decided to ask both CSW3 and OpenSearch authors for their
opinion.<br>
The question back then was something like this:<br>
<br>
"Looking at the CSW3 document (12-176r4) under Table 6 the
preferred parameter for OpenSearch Temporal is
&time={start}/{end}&
<br>
Looking at the OpenSearch document (10-032r8) in Table 3 I see
that "start" and "end" are mentioned separately. I understand that
those are tokens in the OpenSearch description document and not
actually KVP parameters.
"<br>
<br>
The response we got was that they are both valid as long as you
define them correctly in the template document.<br>
The opensearch parameters are placeholders that you can replace. <br>
On page 13 of OGC 10-032r8 you 'll also find the following remark:<br>
"Clients should take special consideration to the fact that
according to the OpenSearch specification the OpenSearch
parameters usage is not restricted to the URL query string and can
be used as templates values in any of URL components (e.g. path,
host).
<br>
EXAMPLE 6 An example URL template with OpenSearch parameters on
the URL path
<br>
<a class="moz-txt-link-freetext" href="http://example.com/rss/">http://example.com/rss/</a>{startPage}/?q={searchTerms}
<br>
"<br>
<br>
We decided to follow the CSW3 way.<br>
<br>
Best regards,<br>
Angelos<br>
<br>
<br>
<br>
On 02/19/2016 04:58 PM, Pedro G Silva wrote:<br>
</div>
<blockquote
cite="mid:CAJG0=QggaFPk-td=V65gkrO3d5itcq-3HYVDUT68Phr4_2_xEw@mail.gmail.com"
type="cite">
<pre wrap="">Hi
Using opensearch on pycsw I noticed 2 things:
-lack of start page and copunt (already fixed on
<a class="moz-txt-link-freetext" href="https://github.com/geopython/pycsw/issues/402">https://github.com/geopython/pycsw/issues/402</a>)
-the time:start and end format dont feel like the standard used/written in
the draft.
Current descriptor URL:
<a class="moz-txt-link-freetext" href="http://100.100.0.200/csw?mode=opensearch&service=CSW&version=2.0.2&request=GetRecords&elementsetname=full&typenames=csw:Record&resulttype=results&q=">http://100.100.0.200/csw?mode=opensearch&service=CSW&version=2.0.2&request=GetRecords&elementsetname=full&typenames=csw:Record&resulttype=results&q=</a>{searchTerms?}&bbox={<a class="moz-txt-link-freetext" href="geo:box">geo:box</a>?}&time={time:start?}/{time:end
?}
On this document
<a class="moz-txt-link-freetext" href="http://www.opensearch.org/Specifications/OpenSearch/Extensions/Time/1.0/Draft_1">http://www.opensearch.org/Specifications/OpenSearch/Extensions/Time/1.0/Draft_1</a>
time
start and end is referred as &dtstart={time:start?}&dtend={time:end?}
Notice the lack of / to separatae start and time and the use of &, just
like another argument.
This email is to promote discussion about which format to use or why the
current one should be used, {time:start?}/{time:end?} or
&dtstart={time:start?}&dtend={time:end?}
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
pycsw-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:pycsw-devel@lists.osgeo.org">pycsw-devel@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/pycsw-devel">http://lists.osgeo.org/mailman/listinfo/pycsw-devel</a></pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
Angelos Tzotsos, PhD
OSGeo Charter Member
<a class="moz-txt-link-freetext" href="http://users.ntua.gr/tzotsos">http://users.ntua.gr/tzotsos</a></pre>
</body>
</html>