Flows @ 2009 Uk Media Ecologies

2,702 views

Published on

Published in: Technology
1 Comment
6 Likes
Statistics
Notes
No Downloads
Views
Total views
2,702
On SlideShare
0
From Embeds
0
Number of Embeds
7
Actions
Shares
0
Downloads
20
Comments
1
Likes
6
Embeds 0
No embeds

No notes for slide

Flows @ 2009 Uk Media Ecologies

  1. 1. Flows: st 21 Century Wealth- Generating Ecologies and an Infrastructure for Open Everything
  2. 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. 3. I. st 21 Century Wealth-Generating Ecologies
  4. 4. Producer Distributor Consumer A 20th Century economic paradigm
  5. 5. RESOURCES Producer Distributor Consumer WASTE A 20th Century economic paradigm
  6. 6. Maker Sharer User A 20.5th Century economic paradigm
  7. 7. Making Sharing Using A 20.5th Century economic paradigm
  8. 8. Making/Using Sharing 21st Century Wealth-Generating Ecologies
  9. 9. Normal to Power Law Distributions
  10. 10. Energy Commons Food Commons Thing Commons We the Commoners Culture Commons Access Commons 21st Century Wealth-Generating Ecologies
  11. 11. Energy Commons Food Commons Thing Commons We the Commoners Culture Commons Access Commons 21st Century Wealth-Generating Ecologies
  12. 12. II. Flows An Infrastructure for Open Everything
  13. 13. What kind of infrastructure can facilitate the distributed economy? transparent and open highly abstracted implementation agnostic plural and diverse
  14. 14. Why? facilitates self-selected participation resource allocation rapid innovation scaling
  15. 15. How? share the model, and the render interface-oriented design open, accessible, embedded standards infrastructure exists with representation design for adaptability
  16. 16. Share the model and the render
  17. 17. Interface oriented design: translation-affordances Interface Translation
  18. 18. 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?"
  19. 19. Connect , not replace , other infrastructures. image source: http://wiki.aardrock.com/Network/Boundary_Spanners cc by-nc-sa
  20. 20. 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).
  21. 21. 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)
  22. 22. 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/
  23. 23. 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)
  24. 24. Flows is an attempt to cultivate, but not capture, new infrastructure.

×