Blogapps 1.0.1

RSS and Atom in Action forum: The latest version of is Blogapps 1.0.1, which was released August 6, 2006 (today) to make the examples compatible with the latest version of the Windows RSS Platform (i.e. the one that shipped last week with IE7 beta 3). Also in 1.0.1 are some fixes to the Blogapps servers' Atom protocol implementation.
I've mentioned this before, but I'll mention it again now that the book is out. I'm going to be hosting, supporting and maintaining the examples for RSS and Atom in Action as Blogapps -- an open source project at Java.NET.

RSS and Atom in Action


The book has arrived.



Get your copy today!

Top 50 namespaces used in feeds


Mihai Parparita has published an interesting list of the top 50 extension namespaces used in RSS and Atom feeds. I'm pleasantly surprised to see XHTML in the #2 spot. The top 5 are Dublin Core, XHTML, Blogger.com Atom API extensions, Blogger.com Atom draft extensions and the Content Module (via Dave Winer).

Looking for a tech job around RTP?


The Southeast VC blog has a good summary of local tech news sites, recruiters, networking opportunities and actual companies that are currently hiring here in the Raleigh-Durham Research Triangle Park (RTP) area. He didn't mention Microsoft, which has around 100 employees (most working on Team System) -- last I heard they're hiring.

Windows RSS Platform API complete


I won't have time to check out IE7 beta 3 and the final Feeds API until this weekend, but I'm happy to see that Microsoft addressed my number one complaint, which was:
Support feed and item ids. The item.id property does not reflect the RSS <guid> or Atom <id> of the item/entry in the original feed. Plus, it's an integer -- not the right type for a URN. If you want to get the actual feed or item/entry id you have to parse the XML. Make it easy to get the real id if there is one.
And in Walter vonKoch's list, you can see that they fixed the problem:
5. Added FeedItem.Guid to reflect xml element <atom:id> or <guid>

7.3 Renamed Feed.Id to Feed.LocalId

7.4 Renamed FeedItem.Id to FeedItem.LocalId
In doing that they broke some code in my book (I'll fix the examples download this weekend), but I can't really complain about that.

Plus, check out Walter on MSDN TV talking about the RSS in IE7.

Heretics!

Gilad Bracha: "It has come to our attention that some people want to program in things other than Java"

Beyond Blogging at the Triangle .NET user group


I'll be speaking on RSS and Atom next week (Wednesday August 9th) at the Triangle .NET user group. I'll cover RSS and Atom feed formats, the Windows/IE7 RSS Platform and the Atom protocol. Details are on the Tri-NUG website.

Tags: topic:[RSS], topic:[Atom], topic:[IE7], topic:[.NET]

Tri-XML 2006 presentation


Here's the abstract of the talk I gave this morning at Tri-XML 2006:
Beyond blogging: Atom format and protocol. Like XML-RPC and SOAP before, feeds and publishing protocols were born in the blogopshere and quickly moved beyond blogging. Nowadays, web service providers are using RSS/Atom feeds and REST-based publishing protocols as lightweight alternatives to SOAP. And developers are finding new ways to combine web services from different sites into new applications, known as "mash-ups" in the lingo of Web 2.0. If you'd like to do the same, then attend this talk to learn about the new IETF Atom feed format (RFC-4287) and the soon-to-be-finalized Atom protocol, which together form a strong foundation for REST-based web services development.
Here's a rough outline of the talk:
  • Introduction
    • Beyond blogging
    • Blogs hit the hit time
    • The web is bloggy
    • Atom as an alternative to WS-*
  • Understanding feeds
    • Birth of RSS
    • RSS 1.0: the RDF fork
    • The simple fork and RSS 2.0
    • Atom: the standard
  • Parsing feeds
    • Fetching and parsing feeds
    • Universal Feed Parser
    • ROME utilities
    • Windows RSS platform
  • Serving feeds
    • Approaches for generating and serving feeds
    • Feed autodiscovery
    • Styled feeds
  • Atom protocol
    • Compared to MetaWeblog
    • REST based approach
    • Introspection
    • Collections
    • Extending Atom
  • Atom protocol in action
    • Getting a service doc
    • Getting collections
    • Posting an entry
    • Posting an image
  • Demo: interacting with an Atom server via command-line
And here are the slides: TriXML2006-BeyondBlogging.pdf

Tags: topic:[Atom Publishing Protocol], topic:[Atom], topic:[APP], topic:[RSS], topic:[feeds]

Socialtext Open good, but under the MPL?

I'm glad to hear that Socialtext Open is now the first "commercial open source" wiki and I'm interested to see how the Socialtext move plays out. I do wonder why they choose MPL instead of CDDL, which is basically MPL plus bug fixes (see the summary of changes).

Tags: topic:[CDDL], topic:[Open Source], topic:[wiki]

Implementing the Atom Publishing Protocol


That's the title of Joe Gregorio's latest article on XML.com, which shows how to implement most of the Atom protocol (draft #8) in Python. No matter what language you program in, the article is an excellent introduction to the protocol.

Tags: topic:[Atom Publishing Protocol], topic:[Atom], topic:[APP]

MS Word 2007 to speak Atom Publishing Protocol


atom logoJoe Gregorio mentioned in his BarCampRDU session that Microsoft Word 2007 will be able to blog via the Atom Publishing Protocol (APP). Not sure how I missed this news back in may when Tim Bray blogged it, but I did. I need to tune-up my Technorati searches.

And speaking of Tim and the APP, Tim's talking APP at OSCON this week. He's going to talk about APP as universal web glue and maybe even doing some demos that involve Roller and my work-in-progress APP implementation.

And by the way, I've made a number of small fixes to Roller's APP implementation this week and I'm considering doing a Blogapps server 1.0.1 release these weekend -- just in time for the book, which ships on August 1st.

Tags: topic:[BarCampRDU], topic:[OSCON], topic:[APP], topic:[Atom], topic:[Atom protocol]

BarCampRDU, let's do it again!


Congrats and thanks to the organizers, volunteers, Red Hat and other sponsors for making BarCampRDU a great success. I really enjoyed it. In case you have no idea what a "barcamp" is here's the deal. According to the BarCamp wiki, a BarCamp is "an ad-hoc gathering born from the desire for people to share and learn in an open environment."

The event started around 9AM Saturday morning with a quick introduction from conference organizer Fred Stutzman. Everybody who wanted to propose a session lined up at the front of the room and gave a 30 second pitch for their idea. Most of the proposals were technical like "linux systems admin" or "atom publishing protocol," but there were some non-technical ideas too. For example there was a session on "how to juggle" and one on "how to dance with girls" (not sure how that turned out, given the M/F ratio).

After the session pitches, the session leaders claimed spots on the schedule, which was a 10-foot by 15-foot sheet of paper taped to the wall. Next attendees voted for sessions by putting tick marks on the schedule using magic markers. Based on the votes and conversations between session leaders, some sessions were combined and some were moved to smaller or larger meeting rooms -- all right on the spot. It was amazing how well that worked and how quickly we were able to arrive at a schedule and by 10AM we were all attending sessions.

The sessions themselves were not so unconventional. They were definitely more interactive than the usual tech-conference format, but generally followed the normal speaker/audience model. I'm not complaining. I enjoyed the sessions, learned a lot and heard a lot of interesting stories. I attended sessions on open source business and it's ability to innovate (Tarus Balog and ), RESTful Notification Architecture (Seairth Jacobs), social networks (Fred Stutzman) and the Atom publishing protocol (Joe Gregorio).

That's all I have time for tonight. If you want more info, Fred Stutzman has a great round-up of the blog and news coverage (and check it out -- I was mentioned in the News & Observer article) plus some guidelines for running your own BarCamp. I hope we'll do another one this year -- I'd like to help out next time around.

Tags: topic:[BarCampRDU]

BarCamp RDU!



BarCamp RDU is here! I'm getting excited and getting reading to drive over to Durham for the pre-event party tonight. Tomorrow's line-up looks awesome and Atom protocol is on the agenda thanks to Joe Gregorio.

Forrester on Roller

Forrester: As an open source solution, Roller has been deployed only in a few instances, but it has been used by thousands of bloggers on a single installation. It features an excellent ability to allow administrators to manage permissions across blogs, but individual blog management is cumbersome, and robust content management workflow tools are lacking. Roller is ideally suited for companies that want to deploy blogs in an enterprise where content management and oversight will be minimal.
Since I participated in the study, I was able to read the full report, both the Roller report ($795) and the market overview ($995). Roller didn't do so well in the comparison chart (see Charlene Li's post), but we're still ranked as a strong contender -- especially for companies interested in Sun-style trust-your-employees blogging. Overall, I think the report is fair and accurate. I definitely agree that parts of Roller's authoring/admin UI are cumbersome and in need of redesign, but Forrester isn't very specific about the areas that need improvement.

Today's links [July 18, 2006]

ApacheCon US 2006 - October - Austin, TX


If you want to learn all about Apache Roller (incubating) project status, features, architecture and all the cool new features coming in Roller 3.0 then you'll want to make plans to attend ApacheCon US 2006 in Austin, TX. In other words: my Roller talk was accepted.

Raleigh bloggers meetup tonight at Cafe Cyclo



Cafe Cyclo sign
For more info, see the Raleigh Bloggers wiki.

Today's links - July 15, 2006

Busy week and Roller 3.0 update


It's been a very busy week and I've scarcely had time to catch up on email and blog reading and other critically important activities. I spent almost the entire week deep in Roller 3.0 development. Here's a quick update on our work.

Things are looking really good in Roller 3.0 and I'm really happy with the refactoring work we've done in the blog/feed rendering system. Our charter for 3.0 was to completely rework Roller's URL structure and to introduce the concept of a site-wide frontpage blog, but doing that work required a lot of refactoring -- a lot of ripping out crufty old and patched-up code with clean and shiny new abstractions. The results look great.

Thanks to Allen's new URL work, the rendering system is now pluggable, the caching system is easier to understand and maintain, we're approaching a point where we'll be able to offer the option of static rendering and, of course, the URL structure is much nicer, more conventional, logical and able to handle multi-language blogs.

As part of the new frontpage blog work, we introduced some new page models an macros to make it easy to display site and planet-wide blog community information, including a user and blog directory. But we didn't stop there -- we've implemented a completely new set of models and macros for all blogs and we hope to deprecate all of the old macos and old themes. We'll still support them, of course, but moving forward we believe the new macros will make it much easier for bloggers and theme authors to build a library of great themes -- something that Roller is missing.

We've been working hard this week because we're really supposed to be done by now, but I've got no regrets. We set some aggressive goals and, like I said, the results look great. Now we need to quicky stabilize things, get a test build together and get some feedback from the community and especially from theme authors.

« Previous page | Main | Next page »