GEOSS Future Products Workshop 2013

A GeoSocial API for GEOSS UsersTo Discover, Generate and Access Those Future Products

Pat CappelaereEmail: pat@cappelaere.comTwitter: @cappelaereSlideshare: http://www.slideshare.net/cappelaereLinkedIn: http://www.linkedin.com/pub/pat-cappelaere/0/163/236

Mar 26-28 2013Silver Spring MD

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

Big API Gap For The International Disaster Community

Big Data... Complex GeoSpatial API 3

BigData

Why: Conflicting API Needs

Engineers

GEOSS End Users (Mass Market)

REST RPC1995

SOA2000-2005

ROA (RESTful)2005-2012

Better Move ButStill Too Low Level

Big IT Investment

GeoSocial API is Not A Replacement API

GeoSocialAPI

SOA ROA RESTRPC

Service Implementation

Client Implementation

Workflows, Processes…

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

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...

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.•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.

Your Services Should Publish The Goals

10

Goals

Provide Activity

Sequences (aka Behaviors)

To Access Data

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

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-2

EO-1 MODIS Landsat

ModelsOthers..

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 DrumsTelling Stories

in Jungle

Facebook Story-Telling

Get Flood MapFloods - Port-Au-Prince, Haiti

16

Server

Client

But Not A Replacement For Low Level API

THANK YOU

Email: pat@cappelaere.comTwitter:@cappelaere

Skype:patrice_cappelaerehttp://www.slideshare.net/cappelaere

Viaduc de Millau, France

An API for People and

Machines

17