1. Flows:
st
21 Century Wealth-
Generating Ecologies
and
an Infrastructure for
Open Everything

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

3. I.
st
21 Century
Wealth-Generating
Ecologies

4. Producer
Distributor
Consumer
A 20th Century economic paradigm

5. RESOURCES
Producer
Distributor
Consumer
WASTE
A 20th Century economic paradigm

6. Maker
Sharer
User
A 20.5th Century economic paradigm

7. Making
Sharing
Using
A 20.5th Century economic paradigm

8. Making/Using
Sharing
21st Century Wealth-Generating Ecologies

9. Normal to Power Law Distributions

10. Energy Commons
Food Commons Thing Commons
We the Commoners
Culture Commons Access Commons
21st Century Wealth-Generating Ecologies

11. Energy Commons
Food Commons Thing Commons
We the Commoners
Culture Commons Access Commons
21st Century Wealth-Generating Ecologies

15. II.
Flows
An Infrastructure
for
Open Everything

16. What kind of infrastructure can facilitate the
distributed economy?
transparent and open
highly abstracted
implementation agnostic
plural and diverse

17. Why?
facilitates self-selected participation
resource allocation
rapid innovation
scaling

18. How?
share the model, and the render
interface-oriented design
open, accessible, embedded standards
infrastructure exists with representation
design for adaptability

19. Share the model and the render

20. Interface oriented design: translation-affordances
Interface Translation

21. 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?"

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

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

24. Presence vs. Communication
Current Solution:
APIs are inadequate because:
API documentation is separate from the object
APIs have no meta-standard
Flows Solution:
"MetaAPI"
Metadata delivered with presence
Metadata implements/is open standard(s)

25. Flows Meta-Standard
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&somestuff
http://flows.panarchy.com/flows-dev/sandbox/python/echo.py?response_type=xml&somestuff
Integration:
http://209.20.82.150/PASAdev/demo/demo1.php
uses
http://flows.panarchy.com/flows-dev/sandbox/php/twitter.php?return_type=html
http://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/

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

27. Flows is an attempt
to cultivate, but not capture,
new infrastructure.