GEOSS Future Products Workshop 2013 Mar 26-28 2013A GeoSocial API for GEOSS Users Silver Spring MDTo Discover, Generate and Access Those Future ProductsPat CappelaereEmail: email@example.comTwitter: @cappelaereSlideshare: http://www.slideshare.net/cappelaereLinkedIn: http://www.linkedin.com/pub/pat-cappelaere/0/163/236
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 Big Data... Complex GeoSpatial API 3
Why: Conflicting API NeedsEngineers Big IT Investment SOA 2000-2005 Better Move But Still Too Low Level REST RPC ROA (RESTful) 1995 2005-2012 GEOSS End Users (Mass Market)
GeoSocial API is Not A Replacement API GeoSocial APIClientImplementation SOA ROA REST RPCServiceImplementation Workflows, Processes…
GEOSS RealityGEOSS 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 Users Care AboutProductsSo We Need To Help Them Meet Specific Goals Such AsGenerating Specific Products (Ex: Flood Map)This May Involve Satellite Tasking, Image Processing,Notification, Distribution...
Donald Norman: Designing For People “Designers have to produce things that tame complexity.” http://www.jnd.orgStages of Execution:-•Start at the top with the goal, the state that is tobe achieved.•The goal is translated into an intention to do someaction.•The intention must be translated into a set of internalcommands, an action sequence that can be performedto satisfy the intention.•The action sequence is still a mutual even: nothinghappens until it is executed, performed upon theworld. The Design of Everyday Things. New York. 1986 9
Your Services Should Publish The Goals Goals Provide ActivitySequences (aka Behaviors)To Access Data 10
Users Need To Be Shown A Yellow Brick RoadTo FollowHypermediaAction LinksCode-on-demandAnd Decision Gates On The Client Side! Behaviors
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
Floods - Port-Au-Prince, Haiti Get Flood MapClientServerBut Not A Replacement For Low Level API 16
An API for People and MachinesViaduc de Millau, France THANK YOU Email: firstname.lastname@example.org Twitter:@cappelaere Skype:patrice_cappelaere 17 http://www.slideshare.net/cappelaere