[Esip-discovery] Notification of next ESIP Discovery Telecon 1:00pm PST / 4:00pm EST tomorrow

Lynnes, Christopher S. (GSFC-5860) christopher.s.lynnes at nasa.gov
Tue Oct 13 07:27:02 EDT 2015

On Oct 12, 2015, at 4:27 PM, Ruth Duerr via Esip-discovery <esip-discovery at lists.esipfed.org<mailto:esip-discovery at lists.esipfed.org>> wrote:
Hi Doug,

I’ve got a list of potential improvements to the OpenSearch spec/best practices that we ought to discuss though some are also recommendations for web service documentation in general.  See below…


Currently, there is no way to tell whether an open search end point is describing a data set search or a granule search or what.  There needs to be a way to state that (naming practices just don’t work).

These all represent some pretty significant changes, or rather enhancements. So without trying to expand the shopping list of features too much, I would like to add:
o  First, Do No Harm, i.e., don’t break existing uses of OpenSearch
o  Accommodate/identify virtual data collections (i.e., thematic heterogeneous sets of data and information resources, like a volcanic eruption virtual collection)
o  Partition these features between the standard/convention/spec (like extensions or added parameters) and best practices (like link on dataset landing page).

A parameter could do this or some other extension would be needed.  It would need to handle generic well-defined parameters so it could be validated with standard XML tooling (namespacing a substring within an attribute is not a safe long-term solution). At that point, we ought to define an exemplar for the nested search.

OSDD rel link references should be included in any child OSDD throughout any OSDD hierarchy, so that traveling both up and down the hierarchy is possible and easy.

Put the parent OSDD rel link in the ATOM result set (rss is an issue). Basic provenance. Just part of the feed metadata before the item list.

Recommend ATOM.

Make some recommendations for semantic markup in the result set content. Commonplace practice is to encode that as HTML so let's take advantage of that and include rel tags for dataset, landing page, etc, and schema.org<http://schema.org/> tags if that's still of use. We have, I think, been neglecting the utility of the search response to everyone (crawler, broker, person at a keyboard) and that is, frankly, the place where we actually get an understanding of data/no data. So let's make it useful.

We need some structure to support enumerations/controlled vocabs per parameter and an understanding of how these work with the optional/required parameters.

Also, shouldn’t each web service like this have a unique identifier? What is a unique identifier for an OpenSearch? For a dataset OpenSearch?

Lastly, shouldn't the best practice include having these service links on a data set’s landing page?

On Oct 12, 2015, at 2:11 PM, Doug Newman via Esip-discovery <esip-discovery at lists.esipfed.org<mailto:esip-discovery at lists.esipfed.org>> wrote:

Ladies and gentlemen,

Link: http://wiki.esipfed.org/index.php/Discovery_Telecon_2015-09-14

Pending Actions

  *   ESRI and Open Search Best Practices - Doug. In progress
  *   Review Web Service Mission statement http://wiki.esipfed.org/index.php/WebServiceMission - ALL
  *   Re-visit NCEI geoportal server OpenSearch capabilities using CWICSmart OpenSearch Client - Yuanjie Li
  *   ESO - Make decision on whether to wait for Draft 2 of CEOS BP or recommend CEOS BP + CEOS DEV Guide as standard for OpenSearch
  *   Contact Erin regarding the note taker for the ESIP session on Service Discovery - Ruth
  *   Continue to investigate opening up Web Services Cluster - Soren
  *   Monitor situation on AGU Union Demo session for suitability of 'Global OpenSearch' Demo - Doug


  *   OpenSearch Validation Tool
  *   OpenSearch standards decision
  *   Web Services Cluster

Webex Info

To Join the online portion of the Personal Conference meeting


  1.  Go to https://esipfed.webex.com<https://esipfed.webex.com/>
  2.  Click the “Meeting Center” tab
  3.  Select the Discovery

If a password is required, enter the Meeting Password: 23138372

To start the audio portion of the Personal Conference meeting w/ phone


  *   Call-in toll-free number (US/Canada): 1-877-668-4493
  *   Call-in toll number (US/Canada): +1-408-600-3600
  *   Call-in toll number (US/Canada)*: +1-571-918-6008

Attendee access code: 231 383 72

Doug Newman - NASA Earthdata Operations Lead
douglas.j.newman at nasa.gov<mailto:douglas.j.newman at nasa.gov>
doug_newman at raytheon.com<mailto:doug_newman at raytheon.com>
Raytheon Mission Support Solutions Intelligence, Information and Services | NASA | ECS Evolution Development Program

Note: I am not a government employee and have no legal authority to obligate any federal, state, or local government to perform any action of payment.

Esip-discovery mailing list
Esip-discovery at lists.esipfed.org<mailto:Esip-discovery at lists.esipfed.org>

Esip-discovery mailing list
Esip-discovery at lists.esipfed.org<mailto:Esip-discovery at lists.esipfed.org>

Christopher Lynnes    NASA/GSFC  301-614-5185
“We choose to go to the moon in this decade and do the other things, not because they are easy, but because they are hard..." - John F. Kennedy

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.deltaforce.net/pipermail/esip-discovery/attachments/20151013/01cdd9db/attachment.html>

More information about the Esip-discovery mailing list