flows @ 2009 uk media ecologies

Flows:21st Century Wealth-Generating Ecologies

andan Infrastructure for

Open Everything

Connecting

Who We Are: Paul B. Hartzog PaulBHartzog@panarchy.com Samuel Rose samuel.rose@gmail.com of The Forward Foundation

Why We Are Here: I. 21st Century Wealth-Generating Ecologies II. Flows - An Infrastructure for Open Everything

I.21st Century

Wealth-Generating Ecologies

Producer

Distributor

Consumer

A 20th Century economic paradigm

Producer

Distributor

Consumer

R E S O U R C E S

W A S T E

A 20th Century economic paradigm

Maker

Sharer

User

A 20.5th Century economic paradigm

Making

Sharing

Using

A 20.5th Century economic paradigm

Making/Using

Sharing

21st Century Wealth-Generating Ecologies

Normal to Power Law Distributions

21st Century Wealth-Generating Ecologies

Food Commons Thing Commons

Energy Commons

Culture Commons Access Commons

We the Commoners

21st Century Wealth-Generating Ecologies

Food Commons Thing Commons

Energy Commons

Culture Commons Access Commons

We the Commoners

II. Flows

An Infrastructurefor

Open Everything

What kind of infrastructure can facilitate the distributed economy?

transparent and open highly abstracted implementation agnostic plural and diverse

Why?

facilitates self-selected participationresource allocationrapid innovationscaling

How?

share the model, and the render interface-oriented designopen, accessible, embedded standardsinfrastructure exists with representation design for adaptability

Share the model and the render

Interface oriented design: translation-affordances

Interface Translation

The first question you should ask:

"How can I make this work with other systems?"

produces more value than

"How can I make this work best for me?"

Connect , not replace , other infrastructures.image source: http://wiki.aardrock.com/Network/Boundary_Spanners cc by-nc-sa

Presence vs. Communication

Presence: knowing something exists (URL, RFID, etc.)Communication: knowing how to communicate to it (http, sql, etc.)

Representations for communication are a matching function negotiated between senders and receivers (or requestors and responders).

Presence vs. Communication

Current Solution:APIs are inadequate because:

API documentation is separate from the objectAPIs have no meta-standard

Flows Solution:"MetaAPI"

Metadata delivered with presenceMetadata implements/is open standard(s)

Sip:http://flows.panarchy.com/flows-dev/sandbox/php/echo.php?sip Default Functionality:http://flows.panarchy.com/flows-dev/sandbox/python/echo.py?somestuff Response Type:http://flows.panarchy.com/flows-dev/sandbox/python/echo.py?response_type=html&somestuffhttp://flows.panarchy.com/flows-dev/sandbox/python/echo.py?response_type=xml&somestuff

Integration:http://209.20.82.150/PASAdev/demo/demo1.phpuseshttp://flows.panarchy.com/flows-dev/sandbox/php/twitter.php?return_type=htmlhttp://flows.panarchy.com/flows-dev/sandbox/php/twitter.php?return_type=xml

Repository:http://code.google.com/p/flows-dev/http://code.google.com/p/flows-dev/source/browse/

Flows Meta-Standard

Eliminates: Download and install (duplication)

Allows:

Distributed processing (ex. translation) Distributed access (open data) Re-using other Flows objects (extensibility) Combining other Flows objects (mashups) Just-in-time documentation (accuracy) Introspection (automation)

Flows Meta-Standard

Flows is an attemptto cultivate, but not capture,new infrastructure.