Syndication is like sausage, major Congressional legislation and Bruce Jenner. You might be better off not knowing how it's made.
Dave Winer, the co-creator of RSS and the person most responsible for its widespread adoption, argues that the current version of the RSS specification must never be revised in order to protect the stability of the format:
These constraints have served us well. They have kept the platform stable, so Microsoft could take two years to adopt it from top to bottom in their Windows operating system, and not have RSS change while they did their work.
This position deserves strong consideration, though I must point out that under his leadership the board made six revisions to the specification.
If the current spec is treated as the final word on the matter, there are practical consequences to that decision for RSS software developers, publishers and users.
One of the biggest involves podcasting.
An RSS feed may carry podcasts and other media files, storing them in enclosures associated with items in the feed.
There's disagreement among developers over whether the spec permits more than one enclosure in each item. Some believe that because it doesn't explicitly forbid multiple enclosures, they're permitted. Others can demonstrate that the spec author's intent was to allow no more than one.
The publishing tools Blogware, Movable Type and WordPress all produce RSS feeds with multiple enclosures per item.
The political weblog Power Line, published with Movable Type 3.15, offers a podcast feed that includes multiple enclosures.
This feed doesn't work properly in some popular podcast-enabled RSS clients, including Bloglines, FeedDemon, Google Reader and new software being developed by Microsoft, the company whose top-to-bottom support for RSS is cited as the reason to leave the spec alone.
The preview edition of Microsoft Internet Explorer 7 only downloads the first enclosure in each item. Power Line users who listen to its podcasts with that browser must manually download the other enclosures, which removes the biggest advantage of podcasting -- instant availability of the files.
When Microsoft rolls out the browser later this year, millions of new users will be introduced to RSS and podcasts for the first time.
If no group has the authority to resolve the enclosures issue, all podcasters relying on multiple enclosures will be publishing RSS feeds that don't work for what is potentially their largest audience.
Maggie Dew, the geocacher who journeyed to the center and brought back photos, has planted a cache not far from the city at a '60s landmark called Peace Point:
Some friends and I had a little shop in downtown Coffeyville called the Hobbit Hole. We had a peace flag in the front window, and it wasn't long before someone decided to lob a brick through it. During the same period, some of my friends put up a huge peace symbol on a tall pipe on this bluff overlooking Coffeyville. It could be seen from quite a distance, and it was written up in the Coffeyville Journal. Again, in less than a week's time, someone cut it down. A piece of that pipe still sticks out of the ground today. Take a walk out to this viewpoint overlooking the town and contemplate why, to some, the concept of peace is such a fearful and loathsome thing.
The satellite photos on Google are prompting a lot of sightseeing, as I found while obsessing over Google Maps during the preparation of the story. My favorite discovery is the Palm Beach UFO.
Palm Beach County has a large population of elderly residents, bringing its median age up to 42. I don't want to reach a definitive conclusion until the subject's covered by Coast to Coast, but the high-altitude weather balloon theory is no fun at all. I'm thinking aliens came back to fetch more cocoons and have non-contact laser-light sex with Steve Guttenburg's rib cage.
The Feed Validator tests syndicated documents for adherence to the specification and provides other warnings that are helpful when publishing a feed for the first time.
It supports the three formats in wide use today -- Really Simple Syndication, RDF Site Summary and Atom -- and is an open source project that takes bug reports and suggested patches from the public.
Kudos to lead developers Sam Ruby, Mark Pilgrim, Joseph Walton and Phil Ringnalda for their work the past three years on the project.
An internal poll of Wikipedia editors strongly favored the publication of the image, which puts the online encyclopedia in the same position as media organizations that have taken criticism for reprinting them.
"Making and also looking the figures of Mohammed is forbidden," wrote one editor who called the decision to include them an insult to Islam. "Every time I enter the page I click as fastly as I can to the 'discussion' to don't see the cartoon."
Contributors to Wikipedia are 4-to-1 in favor of their inclusion. "Most of the arguments to censor this image are despicable," one stated. "It is the honour and duty of any free man to stand against such things."
Wikipedia's discussion page for the article includes a Cascading Style Sheets tip that enables users to turn off display of the image:
- You will need to be logged in as a user in order to do this.
- Open your monobook.css page, this will be User:yourUserName/monobook.css
- Add the following line: #mi{display: none;}
Reading the arguments taking place within the internal talk pages of Wikipedia gives an appreciation for the immensity of the encyclopedia's mission, which seems guaranteed to land cofounder Jimbo Wales and other participants squarely in the center of every heated political and speech controversy from now until the end of time.
Wales personally deleted the main talk page about the cartoons Feb. 1, pleading for more civility:
This is not the appropriate place for a general philosophical discussion about Islam, freedom of speech, terrorism, religious tolerance, etc. Not only is this talk page not the right place for it, Wikipedia is not the right place for it. Here, we are polite, thoughtful, smart, geeky people, trying only to do something which is undoubtably good in the world: write and give away a free encyclopedia.
While egosurfing to read opinions of the RSS Advisory Board, I found a plea posted last night by a Cadenhead who fears that her 67-year-old mother's fight with liver cancer may be nearing its end:
I want to have an idea of what to expect. Liver cancer is not supposed to spread, is it? How long do patients suffer? What is my family going to have to watch her go through? We're all really scared and upset, but I think it would help us if we had an idea of how long a patient actually suffers in the end.
If anyone has experience with circumstances like that, here's the Cancer Forums signup page.
RSS Playground uses a sample RSS document as a starting point, letting you change the values and create a new document that will remain online for 72 hours.
I used the tool this afternoon to see what the Feed Validator does when it encounters a feed containing RFC 2822 date-time values.
Because this tool's being used to support ongoing development of the proposed specification for RSS, the default values are taken from that proposal rather than the current specification.
Dave Winer:We've heard from a number of people about an uneasy (and unfounded) sense that something is happening with respect to the RSS 2.0 spec. Just by way of clarification, nothing has changed from the perspective of Harvard, which is the owner and trustee of the RSS 2.0 spec. ... While we are delighted to know that many members of the RSS community continue to work on relevant issues to move the industry along in various ways, including related to the spec itself, Harvard has no involvement with any of these efforts.
1. The spec is owned by Harvard. 2. The RSS Advisory Board, when it existed, performed a support function. Later, in case anyone was still confused, we disclaimed: "It does not own RSS, or the spec, it has no more or less authority than any other group of people who wish to promote RSS."
As a member of the RSS Advisory Board for the past 21 months and the current chair, I am surprised to learn that the organization doesn't exist.
I joined the board at Winer's invitation in May 2004, not long before he resigned.
The group operated in private without a charter, and as I said at the time, the reason I joined was to help guide Really Simple Syndication to a public, participatory model like that enjoyed by Atom and RDF Site Summary (a.k.a. RSS 1.0).
Doing anything on the board became difficult in the last half of 2005 when outside commitments kept members Adam Curry and Steve Zellers from participating, so for six months it was inactive. I served as webmaster, keeping the site free of comment spam but taking no actions regarding the RSS specification.
In January, I invited former board members Andrew Grumet, Brent Simmons, Jon Udell and Winer to a private mailing list to discuss whether it should shut down or recruit new members. The decision that came out of that list was to continue in a publicly accountable fashion, which culminated in a charter and eight new members.
Before they were asked to join, Winer told me in a Jan. 21 e-mail, "You can carry on the business in any way you want as far as I'm concerned, I just want that site, and the spec, to be left as-is. I won't even object if there's a pointer to the new site you want to start on the old one."
In part to address his concerns (and some voiced by Palfrey), I launched a new site for the board and we've been working on a newly written specification that seeks to resolve long-standing issues with RSS that make it difficult to implement, such as a lack of clarity on whether an item's description is the only element that can carry HTML. (The spec's not official -- it's published to solicit public review for at least 60 days. I encourage people who are interested in it to join the RSS-Public mailing list.)
Winer has now decided that the board doesn't exist and never had authority over the RSS specification, even though it has published six revisions from July 2003 to the present.
I don't agree, but now that the board's fully public, we're in a position to make his wish a reality.
The eight new members of the board are independent, strong-minded people who are well-respected in the syndication community. The organization has been trusted to publish the most-widely adopted Really Simple Syndication specification for three years, and I believe we should continue to do that, either by completing and adopting the proposed spec or relying on the current version.
I also think there's an opportunity for us to help improve détente among syndication developers by working with the creators of Atom and RDF Site Summary on areas of common concern such as the Feed Validator and the common syndication icon.
If we had shut down the board last month, I believe a new group would be needed to make RSS easier to implement and resolve issues with the format.
But my viewpoint's only one of nine.
If the board believes that nothing more should be done on RSS and the 2003 spec published by Harvard should be the last word on the subject, a vote of five members would close it down.