Standardization is a good thing. Most of my day job wouldn't make a lot of sense if I didn't believe that. We've reached a point where it should be possible to achieve consensus about what's required to identify an item and what sorts of extensions should be easily achievable. I'll support whatever the community adopts.

If you think of standardization as the best that you know today, but which is to be improved tomorrow; you get somewhere.

—Henry Ford

Standardization is a good thing. Most of my day job wouldn't make a lot of sense if I didn't believe that. And in the world of RSS, standardization is exactly what we're in a position to do. A lot of “standardization” these days is really “design by committee,” but RSS has been around for a while, there's a community of folks that understands it well and knows what works and what doesn't, and we've reached a point where it should be possible to achieve consensus about what's required to identify an item and what sorts of extensions should be easily achievable.

Sam Ruby started this discussion. Now there's a road map and lots of folks have signed up to support it. You can add my name to the list.

In the past, I've expressed a preference for the RDF-based RSS format, but consensus doesn't seem to be going in that direction. Fair enough.

I'll support whatever the community adopts.

There are no comments on this essay.
Add a comment or subscribe to (existing and future) comments on this essay.
Name:
Email*:
 *Please provide your real email address; it will not be displayed as part of the comment.
Homepage:
Comment**:
 **The following markup may be used in the body of the comment: a, abbr, b, br, code, em, i, p, pre, strong, and var. You can also use character entities. Any other markup will be discarded, including all attributes (except href on a). Your tag soup will be sanitized...