tecznotes

Michal Migurski's notebook, listening post, and soapbox. Subscribe to this blog. Check out the rest of my site as well.

Apr 15, 2009 4:34am

thirteen opens

Christian is at BayCHI, and I am not. "When you hear the word open they may be thnking about any one of these 13 things while you're talking about 1 or more of them..." @mlaaker:

  • (1) open source - free to use, community contributions, decentralized, high reliability (the following all @mlaaker) #bayCHI
    about 1 hour ago from TweetDeck
  • (2) open infrastructure - pay as you go (amazon....)
    about 1 hour ago from TweetDeck
  • (3) open architecture, anyone can mod your product... on your product, plug 'n' play (mozilla)
    about 1 hour ago from TweetDeck
  • (4) open standards - community driven, consensus, goal is interperability
    about 1 hour ago from TweetDeck
  • (5) open ontology ("this is one i just made up") - describe what can not be seen, future proof your data (microformats, rdfa)
    about 1 hour ago from TweetDeck
  • (6) open access - APIs, mult-channel, third-party developers, partners can build on your platform (twitter, flickr, google maps)
    about 1 hour ago from TweetDeck
  • (7) open canvas ("drifting to the user-facing side") - product becomes vehicle for 3rd-party content, your content to go (facebook et al.)
    about 1 hour ago from TweetDeck
  • 8) open content - user is the edtor, programming self-relevant content, content comes to you when , content starts hunting you down (rss)
    about 1 hour ago from TweetDeck
  • (9) open mic - product is populated entirely by users, users own their own content, products support making/discover of content (wordpress).
    about 1 hour ago from TweetDeck
  • (10) open forum - users contribute ancillary data, ratings, reviews, ranking, link submissions, heavy social interaction (digg, amazon)
    about 1 hour ago from TweetDeck
  • (11) open door (policy) - users engaged in product, organizational decisions, reveal operaton detail, open communication (getsatisfaction)
    about 1 hour ago from TweetDeck
  • (12) open borders - users own their own content, data portability, users can vote with their feet, avoid lock-in antipattern (opml)
    about 1 hour ago from TweetDeck
  • (13) open identity - user as owner of identity, metes it out to sites on their own terms, 1 ID for many sites, power to the people #bayCHI
    about 1 hour ago from TweetDeck
comments (9) | permanent link | tecznotes

subscribe to this site. | contact Michal Migurski

March 2025
Su M Tu W Th F Sa
      1
2345678
9101112131415
16171819202122
23242526272829
3031     

Recent Entries

  1. Mapping Remote Roads with OpenStreetMap, RapiD, and QGIS
  2. How It’s Made: A PlanScore Predictive Model for Partisan Elections
  3. Micromobility Data Policies: A Survey of City Needs
  4. Open Precinct Data
  5. Scoring Pennsylvania
  6. Coming To A Street Near You: Help Remix Create a New Tool for Street Designers
  7. planscore: a project to score gerrymandered district plans
  8. blog all dog-eared pages: human transit
  9. the levity of serverlessness
  10. three open data projects: openstreetmap, openaddresses, and who’s on first
  11. building up redistricting data for North Carolina
  12. district plans by the hundredweight
  13. baby steps towards measuring the efficiency gap
  14. things I’ve recently learned about legislative redistricting
  15. oh no
  16. landsat satellite imagery is easy to use
  17. openstreetmap: robots, crisis, and craft mappers
  18. quoted in the news
  19. dockering address data
  20. blog all dog-eared pages: the best and the brightest

Archives