1 / 6

EarthCube Web Services

EarthCube Web Services. Summarizing Concept-Award Progress for the EarthCube Charrette of June 2012 by Dave Fulker (for Tim Ahern, PI). Team Members & Disciplines. Other Participants (partial list). The Core Ideas.

aleda
Download Presentation

EarthCube Web Services

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. EarthCube Web Services Summarizing Concept-Award Progress for the EarthCube Charrette of June 2012 by Dave Fulker (for Tim Ahern, PI)

  2. Team Members & Disciplines

  3. Other Participants (partial list)

  4. The Core Ideas • Purpose: enable horizontal & vertical integration of data & info via simple, standardized web services • "Simple" means • Invoked via URLs, etc. • Understandable to humans & programs • Emphasis on high-level products over raw data • "Standardized" means • EarthCube-wide agreement/adoption • Common patterns of invocation & output • Leveraged on existing services&standards

  5. Critical Challenges • "Simple" - the elusive trait • Surprisingly hard (even within our group) • Are extant web services (unnecessarily) complex? • Meaningful/integrative across domains • Differences in vocabularies, etc. (semantics) • Remarkable time-scale impedances… • Space-time queries - low-hanging fruit? • The semantics of space & time may exhibit the least trans-domain variation...

  6. Seeking Charrette Input • Ideas for defining "simple" web services • Enough clarity  engineering-grade specs • Meaningful (high-level) data products • Optimal forms of invocation & output • Exemplars that are • Easy to employ in "big data” and"long tail" contexts • Demostrably integrative • Use cases covering • Human interaction (with scripting?) • Web services as interfaces (EarthCube architecture)

More Related