Building Open Specs
                 (for the web)




David Recordon                   November 5, 2008
ApacheCon US     ...
Open Source



              http://www.flickr.com/photos/jagelado/16631508/
http://www.illustratorworld.com/artwork/2238/
“Open Data is increasingly
important as services
move online.”
             —Tim O'Reilly (OSCON '07)
realtime data inside!




quot;It's like flying on an iPhone!quot;
                                 http://flickr.com/phot...
http://flickr.com/photos/
mag3737/1914076277/
Social Application


      • Each with a few great features
        (UNIX philosophy)
      • Creating combined value
    ...
http://flickr.com/photos/factoryjoe/2545757754/
http://adactio.com/journal/1357
My 20+ Social Networks
Interoperable Platforms
Joseph Smarr (Plaxo)
The “Open Stack” (for the social web)




Identity & Profile            !        OpenID + hcard

Discovery                ...
They Are Quite Similar...

• Communities ranging from individuals to companies
• Occurring outside of formal standards bod...
Standards Bodies
And share problems...
Licensing (IPR)
Foundations
“Best Practices”
Community
...but Open Source solved this
opensource
          TM



  initiative
The Open Web
 Foundation
Licensing (freely implementable by anyone)

Copyright (ideally Creative Commons for each spec)

Community (to support the ...
Licensing (freely implementable by anyone)

Copyright (ideally Creative Commons for each spec)

Community (to support the ...
Licensing (freely implementable by anyone)

Copyright (ideally Creative Commons for each spec)

Community (to support the ...
Licensing (freely implementable by anyone)

Copyright (ideally Creative Commons for each spec)

Community (to support the ...
Licensing (freely implementable by anyone)

Copyright (ideally Creative Commons for each spec)

Community (to support the ...
Two Stages
1) License
2) Incubator
http://OpenWebFoundation.org/
http://groups.google.com/group/open-web-discuss
Questions?
david@sixapart.com
Learning from Apache to create Open Specifications
Learning from Apache to create Open Specifications
Learning from Apache to create Open Specifications
Learning from Apache to create Open Specifications
Learning from Apache to create Open Specifications
Learning from Apache to create Open Specifications
Learning from Apache to create Open Specifications
Learning from Apache to create Open Specifications
Learning from Apache to create Open Specifications
Learning from Apache to create Open Specifications
Learning from Apache to create Open Specifications
Learning from Apache to create Open Specifications
Learning from Apache to create Open Specifications
Learning from Apache to create Open Specifications
Learning from Apache to create Open Specifications
Upcoming SlideShare
Loading in...5
×

Learning from Apache to create Open Specifications

2,742

Published on

I should really sync audio to these slides since most of the information is not on the slides.

Open source development has reached a stable and remarkable maturity. With services like SourceForge and Google Code for hosting projects, the Open Source Initiative to vet and curate Open Source licenses, and organizations like the FSF and Apache where like-minded developers can work together to build sustainable and open communities around Open Source projects, and the support of hundreds of thousands of developers and major corporations alike, the success of open source is firmly established.

Yet when we turn our attention away from open source and instead to specifications and standards for the open web, much of this infrastructure doesn't yet exist. Formal standards bodies may enforce interoperability, but they don't always guarantee that a standard is freely implementable by everyone or that the development community is open to all potential contributors. As software development is increasingly centered on protocols and formats instead of simply source code, many newer initiatives, like Microformats, OpenID, OAuth and OpenSocial, have had to each invest time and money reinventing the legal and organizational infrastructure required to ensure that the specifications they create are open and their communities are healthy and run in meritocratic fashions.

Isn't there a better way? What can we learn from the open source movement that will help us create open specifications for the web?

The newly created Open Web Foundation is tackling this exact question by borrowing heavily from the proven model established by the Apache Foundation. This talk discusses the Open Web Foundation's progress so far, our goals for the future, and how you can get involved.

Published in: Technology, Education
2 Comments
3 Likes
Statistics
Notes
No Downloads
Views
Total Views
2,742
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
0
Comments
2
Likes
3
Embeds 0
No embeds

No notes for slide

Learning from Apache to create Open Specifications

  1. 1. Building Open Specs (for the web) David Recordon November 5, 2008 ApacheCon US New Orleans
  2. 2. Open Source http://www.flickr.com/photos/jagelado/16631508/
  3. 3. http://www.illustratorworld.com/artwork/2238/
  4. 4. “Open Data is increasingly important as services move online.” —Tim O'Reilly (OSCON '07)
  5. 5. realtime data inside! quot;It's like flying on an iPhone!quot; http://flickr.com/photos/sathishcj/1868113345/
  6. 6. http://flickr.com/photos/ mag3737/1914076277/
  7. 7. Social Application • Each with a few great features (UNIX philosophy) • Creating combined value • Building blocks for new value http://www.slideshare.net/stoweboyd/building-social-applications
  8. 8. http://flickr.com/photos/factoryjoe/2545757754/
  9. 9. http://adactio.com/journal/1357
  10. 10. My 20+ Social Networks
  11. 11. Interoperable Platforms
  12. 12. Joseph Smarr (Plaxo)
  13. 13. The “Open Stack” (for the social web) Identity & Profile ! OpenID + hcard Discovery ! XRDS-Simple Authorization ! OAuth Relationships & Contacts ! PoCo + XFN Activities ! ATOM + ?? Gadgets ! OpenSocial
  14. 14. They Are Quite Similar... • Communities ranging from individuals to companies • Occurring outside of formal standards bodies • Open Source implementations in many languages • Major adoption at an increasing pace • Open specifications designed to be freely implementable
  15. 15. Standards Bodies
  16. 16. And share problems...
  17. 17. Licensing (IPR)
  18. 18. Foundations
  19. 19. “Best Practices”
  20. 20. Community
  21. 21. ...but Open Source solved this
  22. 22. opensource TM initiative
  23. 23. The Open Web Foundation
  24. 24. Licensing (freely implementable by anyone) Copyright (ideally Creative Commons for each spec) Community (to support the Open Web) Incubation (creating new open specifications for the web)
  25. 25. Licensing (freely implementable by anyone) Copyright (ideally Creative Commons for each spec) Community (to support the Open Web) Incubation (creating new open specifications for the web)
  26. 26. Licensing (freely implementable by anyone) Copyright (ideally Creative Commons for each spec) Community (to support the Open Web) Incubation (creating new open specifications for the web)
  27. 27. Licensing (freely implementable by anyone) Copyright (ideally Creative Commons for each spec) Community (to support the Open Web) Incubation (creating new open specifications for the web)
  28. 28. Licensing (freely implementable by anyone) Copyright (ideally Creative Commons for each spec) Community (to support the Open Web) Incubation (creating new open specifications for the web)
  29. 29. Two Stages
  30. 30. 1) License
  31. 31. 2) Incubator
  32. 32. http://OpenWebFoundation.org/
  33. 33. http://groups.google.com/group/open-web-discuss
  34. 34. Questions? david@sixapart.com

×