<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi<div><br></div><div>Stephen said : "... we end up swimming against the tide ..." </div><div><br></div><div>I would underline the importance of not impeding the development process in its early phases. This is not to denigrate standards such as OpenSearch but simply to underline that from an agile perspective the first few iterations in the SDLC must be upon building momentum ASAP. This entails placing a premium upon the YAGNI principle (<a href="http://en.wikipedia.org/wiki/You_ain't_gonna_need_it">http://en.wikipedia.org/wiki/You_ain't_gonna_need_it</a>). For me supporting OpenSearch is perhaps an iteration 3/4 task whereby the request/reponse parser/generator are retrofitted with appropriate OpenSearch adaptors.</div><div><br></div><div>Having said this if the group decide to support OpenSearch from day one then fair enough. </div><div><br></div><div>Mark</div><div><br></div><div><br></div><div> <br><div><div>On 8 Jun 2011, at 12:53, <<a href="mailto:stephen.pascoe@stfc.ac.uk">stephen.pascoe@stfc.ac.uk</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>Is there more detail on what it means to "federate search with ESIP"? Is there infrastructure behind the pattern described on the ESIP wiki?<br><br>I'm asking because I'm slightly cautions about tying ourselves to an infrastructure that may not meet our needs. For instance the wiki page suggests ESIP OpenSearch engines will support a single query string plus optional time constraints. If this is a hard requirement it means we can't use arbitrary OpenSearch extensions. The time extension that is supported may not meet our needs: I bet it doesn't do 360 day calendars! Multiple time dimensions anyone?<br><br>I've been here before in the context of OGC standards. We end up swimming against the tide in trying to fit our requirements into what the rest of the community want. Of course there are many great advantages to sharing standards like this. I just advocate caution.<br><br>Thanks,<br>Stephen.<br><br>---<br>Stephen Pascoe +44 (0)1235 445980<br>Centre of Environmental Data Archival<br>STFC Rutherford Appleton Laboratory, Harwell Oxford, Didcot OX11 0QX, UK<br><br><br>-----Original Message-----<br>From: Cinquini, Luca (3880) [mailto:Luca.Cinquini@jpl.nasa.gov] <br>Sent: 08 June 2011 11:37<br>To: Mattmann, Chris A (388J)<br>Cc: Pascoe, Stephen (STFC,RAL,RALSP); <a href="mailto:go-essp-tech@ucar.edu">go-essp-tech@ucar.edu</a><br>Subject: Re: [Go-essp-tech] [ESGF-Search] Opensearch and XML representation of a search query<br><br>Thanks Chris, indeed one of our goals is to federate the ESG search with ESIP...<br>Luca<br><br>On Jun 7, 2011, at 11:18 PM, Mattmann, Chris A (388J) wrote:<br><br><blockquote type="cite">Guys you may want to check out the work in ESIP going on with the Federated Search folks:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><a href="http://wiki.esipfed.org/index.php/How-To_Guide_for_Implementing_ESIP_Federated_Search_Servers">http://wiki.esipfed.org/index.php/How-To_Guide_for_Implementing_ESIP_Federated_Search_Servers</a><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Just passing it along.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Thanks!<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Cheers,<br></blockquote><blockquote type="cite">Chris<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">On Jun 7, 2011, at 7:21 AM, <<a href="mailto:stephen.pascoe@stfc.ac.uk">stephen.pascoe@stfc.ac.uk</a>> <<a href="mailto:stephen.pascoe@stfc.ac.uk">stephen.pascoe@stfc.ac.uk</a>> wrote:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><blockquote type="cite">In off-list discussions about QC we've found we need to attach QC documents to data at the simulation level. This would seem to be semantically similar to selecting all datasets for a given activity/product/institute/model/experiment which could be viewed as a query.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Unfortunately I wasn't on the Search API call yesterday but I hear OpenSearch has been floated as an implementation-neutral interface. What about using OpenSearch's XML Query syntax for representing this? E.g.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><Query xmlns="<a href="http://a9.com/-/spec/openseaerch/1.1/">http://a9.com/-/spec/openseaerch/1.1/</a>"<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"> xmlns:esgf="<a href="http://esgf.org/ns/search/">http://esgf.org/ns/search/</a>"<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"> role="request"<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"> esgf:activity="cmip5"<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"> esgf:product="output"<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"> esgf:institute="MTEST"<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"> esgf:model="ECHAM6-MPIOM-TR"<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"> esgf:experiment="amip"/><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Cheers,<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Stephen.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">---<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Stephen Pascoe +44 (0)1235 445980<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Centre of Environmental Data Archival<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">STFC Rutherford Appleton Laboratory, Harwell Oxford, Didcot OX11 0QX, UK<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">-- <br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Scanned by iCritical.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">_______________________________________________<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">GO-ESSP-TECH mailing list<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><a href="mailto:GO-ESSP-TECH@ucar.edu">GO-ESSP-TECH@ucar.edu</a><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><a href="http://mailman.ucar.edu/mailman/listinfo/go-essp-tech">http://mailman.ucar.edu/mailman/listinfo/go-essp-tech</a><br></blockquote></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++<br></blockquote><blockquote type="cite">Chris Mattmann, Ph.D.<br></blockquote><blockquote type="cite">Senior Computer Scientist<br></blockquote><blockquote type="cite">NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA<br></blockquote><blockquote type="cite">Office: 171-266B, Mailstop: 171-246<br></blockquote><blockquote type="cite">Email: <a href="mailto:chris.a.mattmann@nasa.gov">chris.a.mattmann@nasa.gov</a><br></blockquote><blockquote type="cite">WWW: <a href="http://sunset.usc.edu/~mattmann/">http://sunset.usc.edu/~mattmann/</a><br></blockquote><blockquote type="cite">Phone: +1 (818) 354-8810<br></blockquote><blockquote type="cite">++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++<br></blockquote><blockquote type="cite">Adjunct Assistant Professor, Computer Science Department<br></blockquote><blockquote type="cite">University of Southern California, Los Angeles, CA 90089 USA<br></blockquote><blockquote type="cite">++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">_______________________________________________<br></blockquote><blockquote type="cite">GO-ESSP-TECH mailing list<br></blockquote><blockquote type="cite"><a href="mailto:GO-ESSP-TECH@ucar.edu">GO-ESSP-TECH@ucar.edu</a><br></blockquote><blockquote type="cite"><a href="http://mailman.ucar.edu/mailman/listinfo/go-essp-tech">http://mailman.ucar.edu/mailman/listinfo/go-essp-tech</a><br></blockquote><br>-- <br>Scanned by iCritical.<br>_______________________________________________<br>GO-ESSP-TECH mailing list<br><a href="mailto:GO-ESSP-TECH@ucar.edu">GO-ESSP-TECH@ucar.edu</a><br>http://mailman.ucar.edu/mailman/listinfo/go-essp-tech<br></div></blockquote></div><br><div>
<div>---------------------------------------------------</div><div><span class="Apple-style-span" style="color: rgb(84, 0, 0); ">Mark Morgan</span></div><div><span class="Apple-style-span" style="color: rgb(84, 0, 0); "></span><span class="Apple-style-span" style="color: rgb(84, 0, 0); ">Software Architect / Engineer</span></div><div><span class="Apple-style-span" style="color: rgb(84, 0, 0); "></span><span class="Apple-style-span" style="color: rgb(84, 0, 0); ">Institut Pierre Simon Laplace (IPSL),</span></div><div><span class="Apple-style-span" style="color: rgb(84, 0, 0); "></span><span class="Apple-style-span" style="color: rgb(84, 0, 0); ">Université Pierre Marie Curie,</span></div><div><span class="Apple-style-span" style="color: rgb(84, 0, 0); "></span><span class="Apple-style-span" style="color: rgb(84, 0, 0); ">4 Place Jussieu,</span></div><div><span class="Apple-style-span" style="color: rgb(84, 0, 0); "></span><span class="Apple-style-span" style="color: rgb(84, 0, 0); ">Tour 45-55, Salle #207,</span></div><div><span class="Apple-style-span" style="color: rgb(84, 0, 0); "></span><span class="Apple-style-span" style="color: rgb(84, 0, 0); ">Paris 75005</span></div><div><span class="Apple-style-span" style="color: rgb(84, 0, 0); "></span><span class="Apple-style-span" style="color: rgb(84, 0, 0); ">France.</span></div><div><span class="Apple-style-span" style="color: rgb(84, 0, 0); "></span><span class="Apple-style-span" style="color: rgb(84, 0, 0); ">Tel : +33 (0) 1 44 27 49 10</span></div><div><span class="Apple-style-span" style="color: rgb(84, 0, 0); "></span><span class="Apple-style-span" style="color: rgb(84, 0, 0); ">Email: <a href="mailto:momipsl@ipsl.jussieu.fr">momipsl@ipsl.jussieu.fr</a></span></div><div>---------------------------------------------------</div><div><br></div><br class="Apple-interchange-newline">
</div>
<br></div></body></html>