's Blog

Warning! Your web access to http://eo1.geobliki.com might be declined.

Security has been tightened up for the RESTful OGC Services.

Done as part of OWS-5 interoperability experiment for RESTful services, OAuth 1.0 has been implemented as our security protocol between consumer applications and our web services (sps, wfs, sos). We have made an additional assumption that users could pre-grant access to consumers such as workflows to allow for unattended operations to simplify the protocol one step further. For more information, go to: http://eo1.geobliki.com/pages/oauth

Workflow interoperability is a major concern for the OGC and the WfMC. A simple and RESTful API is critical for early adoption. With the help of John Mettraux of OpenWFE fame, Matt Zukovsky, Keith Swenson and many others, we are documenting this effort dubbed WfXML-R leveraging many years of work done by Keith and the WfMC group.

We need some help and early adopters. Continuous feedback to the nascent specification would be appreciated.

Subscribe to WfXML

Email:

Visit this group

Generating just-in time data products for first responders require the chaining of many web services using workflows.

Our interesting challenge is multi-fold. First responders from various organizations will need access to data provided by other organizations in case of emergencies. Single sign-on is a must. Trusted relationships between organizations is critical to grant access of sensitive data or assets to remote users in a seamless manner.

Access profiles may need to be exchanged at login to determine the access rights of those incoming users.

With the OGC, we are working on RESTful APIs for SensorWeb Enabled Data Nodes. Fairly sophisticated workflows will access remote web services to task satellites, process the data and deliver custom products to the end-users. This needs to be done securely on behalf of the end-users that may grant temporary or permanent access to costly resources to those workflows.

As part of OWS-5, we will be demonstrating that capability fairly shortly. This will require the tight integration of Identity standards such as OpenID 2.0 and the emerging OAuth.

This is part of our effort to provide a simpler but secure resource oriented architecture (ROA) that will scale up to support a broader community in a federated environment.

This is the trademark of Transformation + Innovation. i had the priviledge to present a few slides during a breakfast presentation on a RESTful WfXML: A User Centric Resource-Oriented Approach to Workflows as they apply to the orchestration of OGC services with some examples taken during the recent South California fires.

A very interesting talk from Dennis Wisnosky, CTO of the DoD Business Mission Area on Agile Architectures…talking about a challenge for DoD!

This current work is sponsored by the OGC (as part of OWS-5) and NASA. It is also getting a lot of attention from the Workflow Management Coalition (WfMC) as a complementary approach to the existing SOAP-based WfXML API for Workflow Interoperability.

| View | Upload your own

Popular Science Technology Article Here

“…Right now, in addition to Ikhana, that network includes two high-tech satellites that are also being used to monitor the wildfires. The Terra and Earth Observing-1 (EO1) satellites have sensors that use telescopes and cameras to scan the planet for natural disasters and send data back for scientists to review. The Terra’s sensor has a one-kilometer range—large enough to locate hotspots from space but too huge to focus in on specific sites. The EO1 has a 30-meter range for closer views of natural disasters, and the UAV delivers even more detailed information. NASA is working to combine these tools to create a web of sensors that rescue workers could use to find the information they needed quickly and efficiently…”

The EO-1 SensorWeb Enabled Data Node GeoBliki is at the center of the EO-1 tasking and data publishing using GeoRSS Feeds. Using OpenGeoSpatial (OGC) standards, the satellite can be tasked and the data custom processed using workflows. Products are then distributed via a subscription mechanism.

The framework is open-source and based on Ruby-on-rails. Integrating sensors for the SensorWeb is a matter of quickly duplicating those data nodes with some minor customization for the sensor itself.