Flows @ 2009 Uk Media Ecologies
Upcoming SlideShare
Loading in...5
×
 

Flows @ 2009 Uk Media Ecologies

on

  • 3,099 views

 

Statistics

Views

Total Views
3,099
Views on SlideShare
3,094
Embed Views
5

Actions

Likes
5
Downloads
19
Comments
1

3 Embeds 5

http://www.slideshare.net 3
http://agoraphobiclife.blogspot.com 1
https://twimg0-a.akamaihd.net 1

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Flows @ 2009 Uk Media Ecologies Flows @ 2009 Uk Media Ecologies Presentation Transcript

  • Flows: st 21 Century Wealth- Generating Ecologies and an 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. st 21 Century Wealth-Generating Ecologies
  • Producer Distributor Consumer A 20th Century economic paradigm
  • RESOURCES Producer Distributor Consumer WASTE 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
  • Energy Commons Food Commons Thing Commons We the Commoners Culture Commons Access Commons 21st Century Wealth-Generating Ecologies
  • Energy Commons Food Commons Thing Commons We the Commoners Culture Commons Access Commons 21st Century Wealth-Generating Ecologies
  • II. Flows An Infrastructure for 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 participation resource allocation rapid innovation scaling
  • How? share the model, and the render interface-oriented design open, accessible, embedded standards infrastructure 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 object APIs have no meta-standard Flows Solution: "MetaAPI" Metadata delivered with presence Metadata implements/is open standard(s)
  • 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/
  • 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 is an attempt to cultivate, but not capture, new infrastructure.