|
http://atomenabled.org/ is where I usually point the uninitiated, as it has both technical and non-technical takes presented very cleanly. The one caveat is that that site encompasses both the format and protocol, and might be too broad for what you're looking for. Certainly http://www.atomenabled.org/developers/protocol/ is a better link than the RFC for introductory purposes, but it's still pretty technical. It would be great to have the kind of resource you describe. Who controls atompub.org, and how could one go about making it just a tad sexier? -Travis On Jul 22, 2008, at 9:57 AM, Daniel Jalkut wrote: Since good marketing questions about AtomPub have been raised lately, I thought I would point out a frustration which I'm sure is limiting the word-of-mouth branding of the protocol. When somebody is excitedly typing a blog entry about, oh, their blog editor's new AtomPub support, where do they hyperlink the word "AtomPub" to? Google leads to the authoritative sounding "atompub.org", but this page is so out of date and technically oriented, that it would be a shame to send potentially excited readers to it. Instead, I find myself linking directly to the RFC, where at least the details about what AtomPub is and what it can do are available. Proposal: atompub.org should be as flashy and marketing-oriented as can possibly be stomached. It should link prominently to the RFC and other technical resources, but also highlight in plain-english what the potential advantages of AtomPub are for end users. Finally, it should include a section highlighting and cataloging servers and clients who are taking advantage of AtomPub now. Growl is a completely unrelated technology for Mac OS X that provides system-wide floating notification support for applications. Their "about" page does a good job of summarizing what Growl is, why users might want it, and how developers can get in on the action: http://growl.info/about.php It might serve as a good conceptual template for the types of things atompub.org could express. Daniel |