1. GEOSS Future Products Workshop 2013 A GeoSocial API for GEOSS Users To Discover, Generate and Access Those Future Products Pat Cappelaere Email: pat@cappelaere.compat@cappelaere.com Twitter: @cappelaere Slideshare: http://www.slideshare.net/cappelaereare.net/cappelaere LinkedIn: http://LinkedIn: http://www.linkedin.com/pub/pat-cappelaere/0/163/236 Mar 26-28 2013 Silver Spring MD

2. Do We Need Yet Another API? Current OGC API’s Too Hard for GEOSS Users Too Low-Level, Too Hard to Learn, Develop or Use What GEOSS User? Not a Professional Software Developer But Willing to Spend ~30mn to Learn An API to Get Job Done

3. Big API Gap For The International Disaster Community Big Data... Complex GeoSpatial API 3 Big Data

4. Why: Conflicting API Needs Enterprise Systems/DOD/… Engineering Community GEOSS End Users (Mass Market) REST RPC 1995 SOA 2000-2005 ROA (RESTful) 2005-2012 Better But Still Too Low Level Big IT Investment Target 2013-2015

6. GeoSocial API is Not A Replacement API GeoSocial API SOAROAREST RPC Service Implementation Client Implementation Workflows, Processes…

7. GEOSS Users Cannot Care Less For: Your Services or Discovery of Those Services (ebRIM) Your Data Model or Your Resources Your Big Data or Even Linked Data Do Not Expose Any Of That to GEOSS Users! It does not help. GEOSS Reality

8. GEOSS Users Care About Products So We Need To Help Them Meet Specific Goals Such As Generating Specific Products (Ex: Flood Map) This May Involve Satellite Tasking, Image Processing, Notification, Distribution...

9. Donald Norman: Designing For People The Design of Everyday Things. New York. 1986 9 http://www.jnd.org “ Designers have to produce things that tame complexity. ” Stages of Execution:- Start at the top with the goal, the state that is to be achieved. The goal is translated into an intention to do some action.intention The intention must be translated into a set of internal commands, an action sequence that can be performed to satisfy the intention. The action sequence is still a mutual even: nothing happens until it is executed, performed upon the world.

10. Your Services Should Publish The Goals 10 Goals Provide Activity Sequences (aka Behaviors) To Access Data

11. Users Need To Be Shown A Yellow Brick Road To Follow Hypermedia Action Links Code-on-demand And Decision Gates On The Client Side! Behaviors

12. Imagine… User Only State the Goal Web Services Figure Out What To Do and Return It To Client Some Simple Steps to Follow) Client Executes Behaviors As Code-On-Demand (Simple Javascript Running In Browser or Thin Client or SmartPhone App Get Floodmap... Get Flood Forecast... Floods - Port-Au-Prince, Haiti Goal 12 Radarsat-2EO-1MODISLandsatModelsOthers..

13. GEOSS Discovery Recommendation Active Discovery via Story-Telling (Not ebRIM) through Social Networks and Respective Communities of Interest (COI). You Tend To Do What Your Friends Do Use Activity Streams… and Pictures… Queries (OpenGraph) Supported by Products Light Semantics (RDFa) African Drums Telling Stories in Jungle

14. Facebook Story-Telling

16. Get Flood Map Floods - Port-Au-Prince, Haiti 16 Server Client But Not A Replacement For Low Level API

17. THANKYOU Email: pat@cappelaere.com Twitter:@cappelaere Skype:patrice_cappelaere http://www.slideshare.net/cappelaere/cappelaere Viaduc de Millau, France An API for People and Machines 17