Discovery Cluster Planning

Discovery Planning Breakout Session Notes

 

I. Lynnes

Discovery RFC; Memo for NASA Earth Science Data Systems on standards

 

Section 7: description of what doing, OpenSearch document but also data casting

Yoshi commented so added data casting. Need Ruth to check data casting is correct; can make changes directly in document

 

Added more introductory material: data casting is whole framework without the query, which is provided by provider

 

Atom is still preferred syndication format

 

[comments in doc show required/optional components for cliff's notes on document]

 

Search terms: optional, but expect at data set level but not granular 

multiple search terms separated by '+' which is equivalent to boolean 'AND' 

Discussion: why not use space? Default behavior versus special keywords. So the plus should be in URL

Put a plus, or put a plus or a space

Agreed 'AND'…but need to take back to labs, keep figuring out string

Default behavior for multiple terms is 'AND'

 

Time extension: optional. If use follow OpenSearch extension

slash in response to separate date range

 

Spatial extension: optional

having a minimum bounding box

 

Recursive OpenSearch queries: optional

drilling down to more specific queries

 

Characterizing atom link elements

How deal with versions of netCDF? --> see what rest of community is doing. Does client care that much? Most can handle 4. Matt: look around to see if acceptable way to encode (by next week)

 

Characterizing OpenDAP link elements

Make note: don't have to send back all 6

new code

 

Versioning: required

Parser resolves namespace so lose version. Added space to enable xpath discovery. Redundant about the version, but not a big deal

what version getting is not specified 

disambiguate notion of version: not the dataset, left to providers

 

Error handling: required

resolves error for success with no returns

 

Implementation

make bulleted list names (no URLs)

need to name check

add something about conformity; not up to standards yet bc didn't have them

 

II. Hua

 

Implementation coverage matrix

fill out which feature sets are being used/popular/planned but not implemented

add column root suffix OPeNDAP link elements

add columns for 'or' and 'not'

 

Anything else should add?

 

every time have RFC have reference implementation: useful?

simple enough to already implement in applications where need to use it

but an aspect of compliance testing useful if can do cheaply: gain v. cost

a quick sanity test. Need default: grand default of what to do if ask to do something canon (circle search)

have a template of capabilities

Not sure ultimately…accumulate some compliance resources

Propose writing up, Funding Friday this summer….

 

ESIP Discovery mail list for questions/issues/ambiguity

Put in RFC, explain ongoing change processes 9end of implementation section]