This is a brief history of RSS from July 2000 to November 2000, during which time RSS 0.9x and RSS 1.0 forked. I try to focus on specific people and conversations that document why the fork occurred. I was not involved in any of this, but much (not all) of the discussion has been publicly archived. So this is very much an
outsider's history, and like any history, it is necessarily biased, selective, and incomplete.
6/28/2000. Eric van der Vlist: Will RSS fork?
Following a thread on the syndication mailing list, Rael Dornfest has announced an "RSS Modularization Spec(ish) page" defining how RSS could be extended using namespace based modules.
7/5/2000. Leigh Dodds: RSS Modularization
Perhaps the key benefit of RSS is its simplicity. The syntax for the format is easy to understand, and there are only a few self-explanatory tags to learn. This makes RSS files relatively trivial to produce. Dave Winer of Userland has recently added some new online documentation for RSS 0.91, adding historical notes as well as capturing details of its common usage patterns.
Developers on the RSS and Syndication mailing lists are now discussing future directions for RSS, the hope being to build on current successes and provide richer functionality.
8/14/2000. Rael Dornfest: RSS 1.0 Specification Proposal
Abstract: RSS ("RDF Site Summary") is a lightweight multipurpose extensible metadata description and syndication format. RSS is an XML application, conforms to the W3C's RDF Specification and is extensible via XML-namespace and/or RDF based modularization.
Design Goals: The modular extension of existing RSS through XML Namespaces and RDF stressing backward compatibility with RSS 0.9 for ease of adoption by existing syndicated content producers.
Interested parties are invited to join a working group on the newly-created RSS-DEV mailing list at:
8/16/2000. Aaron Swartz: Re: Thoughts, questions, and issues
[addressing Dave Winer] If I understand you correctly, you want to create a set of elements for RSS that are widely supported and you're free to do that. Just create your own namespace and tie it into the proposal. You say namespaces are confusing, but I have to disagree with you there. When used properly, they can actually make XML easier to understand.
... RSS is now (or once again) an RDF format, which has its benefits and drawbacks. It does make RSS more complicated, which is a downside. However, as R.V. Guha pointed out to me, you can easily escape from RDF if you don't like it by using the rdf:parseType="literal" attribute. Again, I think this is likely a best-of-both-worlds move.
8/16/2000. Dave Winer: Re: Thoughts, questions, and issues #2
So, Aaron, because we disagree you get to make the rules?
So sad it comes to this. If you'd stop and think you'd realize there's a win-win here, all it takes is a little listening and considering other points of view.
So sad, because there will be two RSS 1.0s.
So confusing, so embarassing.
(And a waste of time!)
See you in the market.
8/16/2000. Paulo Gasper: Re: Thoughts, questions, and issues #2b
Your statement (above) works both ways.
IMHO, Aaron even gave an example to illustrate why he thinks that way. It seems to me that he is trying to reason over that. Not forcing.
8/16/2000. Dave Winer: Re: Thoughts, questions, and issues #2c
Paulo, the force comes from the choice of the RSS 1.0 name. Doesn't leave much wiggle room.
8/16/2000. Dave Winer: Re: Thoughts, questions, and issues #3. (Note: here Dave is not replying to Aaron's messages quoted above, but to someone else entirely.)
That's fine. But I'm going to keep going. I'm tired of debating this stuff. I've been having a lot of fun in the last couple of months, and it's only been in the last few days that it started to turn into the usual hand-wringing, trying to keep you from hearing things that apall you. Enough is enough. These guys want to own RSS. I put a ton of work into it. Somehow reconcile that with your appalled-ness. This is not a nice thing that's going on. I'm apalled.
8/16/2000. Paul Freeman: The RDF approach needs to answer some valid criticism
- To enable the average developer to cope, a syndication format must be simple to create and be easily read by a human. The rdf approach requires too much studying and background knowledge to easily pick up and is too hard for humans to read and create manually.
- RSS should also be easy to parse and create using any software environment which developers care to use. Some software environments are too weak to handle RDF and the namespace syntax.
... If the RDF approach is to be widely accepted and adopted then 1) and 2) require solutions. Not all of them may be technical, but better software tools support is part of a solution which does not require the simple syntax required by the "expanded core". This software tools support should span *all* of the environments which people need to use... and we shouldn't sneer at people who try to parse this stuff in Perl, VB or even, shock horror, Macromedia Flash.
8/17/2000. Paulo Gasper: Re: Thoughts, questions, and issues #4
That seems to be the main problem: RDF focus.
RSS became a popular format with people that couldn't care less about RDF. The value of RSS is that popularity.
There are a lot of private little "RSS processors" and this [proposed RSS 1.0] standard does not care much about them.
8/20/2000. Aaron Swartz: Re: Thoughts, questions, and issues #5
I think the answer from the RSS-DEV people (I'm sort of guessing, correct me if I'm wrong) is that the writers shouldn't have to understand the spec -- they should be able to use tools that will generate the RSS for them.
... The fact is, as far as I'm concerned, nobody but the programmers should have to deal with these specs. There seems to be a lot of confusion here, that RSS files are meant to be written by hand. Perhaps that was true with the old spec, but it doesn't need to be, and is even less true with the new one. The specs are written for programmers, to allow them to write programs that communicate.
... To the writers -- don't worry, we haven't forgotten about you. In fact, we care about you more than ever. You don't need to be messing with the XML by hand -- that's not what it's designed for, it's designed for programs. We've tried to create programs so that you don't have to generate the RSS file by hand, you can convert to it or do it through a web interface. If you still have trouble, let us know, we're here to help, not to scare.
8/20/2000. Lynn Siprelle: Re: Thoughts, questions, and issues #6
[addressing Aaron] I have nothing but respect for you, *believe* me, but this is just a little too close to "don't worry your purty li'l head about it, missy."
OK, fine, so I can find some tool somewhere to generate the RSS file for me. But what if I want to parse one, which I will? I *still* have to understand the spec, and I don't. And I'm neither stupid nor technically illiterate.
... It's not just the simple writers you'll need to worry about. It's the simple webmasters who are doing things with RSS files now and who will get tripped up by these changes. If you've ever done tech support (and I have) you know that there are all kinds of people out there doing this stuff--brilliant kids like Aaron and old duffers who just wanna put up photos of the grandkids, and everyone in between.
8/20/2000. Aaron Swartz: Re: Thoughts, questions, and issues #7
[addressing Lynn] Oh, I definitely know what you mean. But here's how I see it:
- Use an automated RSS creator
- Use a web-based RSS creator with a nice interface
- Use a converter from the simple format to the more complex
- Use a pre-built RSS parser (like XML::RSS for Perl)
- Use a down-converter to a simpler format
- Ignore the new additions and just use the old stuff
8/21/2000. zac: Re: Thoughts, questions, and issues #8
[addressing Aaron] These sorts of assumptions are self fulfilling to a degree. If you write a spec assuming that some users won't interact with it then they won't.
This limits the number of people that will use the format.
People want to (and should) understand the technologies that they use. So when you build a format that puts required namespace declarations in the <channel> tag then I think you've gone down a path that isn't going to be followed by as many people.
8/21/2000. Aaron Swartz: Re: Thoughts, questions, and issues #9
I maintain that the new [proposed RSS 1.0] spec is for more technical usage than the older one. For real heavy-duty use, it will require some understanding of XML and RDF. The benefit from this is more power, but at the expense of some clarity and simplicity. I see RSS as moving away from a simple XML language for the people, and more towards a communication system for content management systems and other scripting environments. It may not be the choice you believe in, but it's a choice that the authors are making. There will always be other formats if you don't agree.
8/24/2000. Dan Libby: RSS: Introducing Myself
I was the primary author of the RSS 0.9 and 0.91 spec and the architect behind the My Netscape Network. ... I was the primary author of the RSS 0.9 and 0.91 spec and the architect behind the My Netscape Network (a separate project from My Netscape, which I also worked on). I left Netscape in 1999, in part because of what I felt was mis-handling (non-handling?) of RSS and the MN platform. I fully expected the format to die an ignominious death, and I was pleasantly surprised to recently to poke my head out of the sand and find so many people still using it. I am glad that the net community has begun adopting RSS, and would like to see it realize the original vision.
The original My Netscape Network Vision:
We would create a platform and an RDF vocabulary for syndicating metadata about websites and aggregating them on My Netscape and ultimately in the web browser. Because we only retrieved metadata, the website authors would still receive user's click-throughs to view the full site, thus benefitting both the aggregator and the publisher. My Netscape would run an RDF database that stored all the content. Preferences akin to mail filters, would allow the user to filter only the data in which they are interested onto the page, from the entire pool of data. For example, a user interested in articles about "Football" would be able to setup a personalized channel that simply consisted of a filter for Football, or even for a particular team or player. Or for all references to Slashdot.org, or whatever. This fit our personalization scheme well, and would (I hoped) give us the largest selection of content, with the greatest degree of personalization available. Tools would be made available to simplify the process of creating these files, and to validate them, and life would be good.
What Actually Happened:
- A decision was made that for the first implementation, we did not actually need a "real" RDF database, which did not even really exist at the time. Instead we could put the data in our existing store, and instead display data, one "channel" at a time. This made publishers happier anyway, because they would get their own window and logo. We could always do the "full" implementation later.
- The original RDF/RSS spec was deemed "too complex" for the "average user". The RDF data model itself is complex to the uninitiated, and thus the placement of certain XML elements representing arc types seemed redundant and arbitrary to some. Support for XML namespaces was basically non-existent. My (poor) solution was to create a simpler format, RSS 0.9, that was technically valid RDF, but dropped namespaces and created a non-connected graph. ... This marked the beginning of the Full Functionality vs Keep It Simple Stupid debate that continues to this day. ...
- We shipped the first implementation, sans tools. Basically, there was a spec for RSS 0.9, some samples, and a web-based validation tool. No further support was given for a while...
- At some point, it was decided that we needed to rev the RSS spec to allow things like per item descriptions, i18n support, ratings, and image widths and height. Due to artificial (in my view) time constraints, it was again decided to continue with the current storage solution, and I realized that we were *never* going to get around to the rest of the project as originally conceived. At the time, the primary users of RSS (Dave Winer the most vocal among them) were asking why it needed to be so complex and why it didn't have support for various features, eg update frequencies. We really had no good answer, given that we weren't using RDF for any useful purpose. ...
- We shipped the thing in a very short time, meeting the time constraints, then spent a month or two fixing it all. :-) ...
- People on the net began creating all sorts of tools on their own, and publishing how-to articles, and all sorts of things, and using it in ways not envisioned by, err, some. And now we are here, debating it all over again.
8/25/2000. O'Reilly Network: Open Source Roundtable: Radio show on RSS 1.0
O'Reilly Network publisher Dale Dougherty talks with some of the core developers behind the new spec for RDF Site Summary (RSS 1.0) about the background behind RDF, the need for a standard, and what RSS enables. (downloadable as MP3 (10MB), or as RealAudio stream)
8/26/2000. Dave Winer: Comments on O'Reilly radio show on "RSS 1.0"
The format and process they describe are highly complex. They are over-estimating content people's technical sophistication and interest in working on new formats.
IMHO, the new format should not be called RSS. There's been a fork, and the peaceful solution is to each go our own way. Calling their spec RSS is unfair. We never considered moving RSS forward without getting O'Reilly on board first. RSS 1.0 was a surprise, we found out when the spec went public. I've said this over and over to the O'Reilly people, I would wish them godspeed if they hadn't called it RSS. Should we call our spec RSS 1.0 too?
BTW, it was Netscape's decision to take the RDF out of RSS, one we heartily supported. We considered calling it Really Simple Syndication. That's the core thing about RSS, simplicity, it's almost an end-user format, easily explained in a four-screen spec designed for people who understand HTML and not much more. Once Guha left, Netscape totally dropped the RDF pretense. Now it's back.
8/26/2000. Aaron Swartz: Re: Commentary: RSS Roundtable
[re: complexity] Once again, content people can use the tools that we're creating to convert from simpler formats and write files through a Web interface.
[re: "RSS 1.0" naming] Hmm, perhaps we should consider changing the name. The problem is that many of us have so much invested in the current name, making it painful to change it. Having two RSS 1.0's would be even more confusing. I think the name is also deserved, considering the large amount of work spent on making the new spec backwards-compatible with RSS 0.9. It would be different if their we were creating a radically new spec, but we're not -- instead we're simply adding namespaces and more RDF support to an already existing spec.
[re: simplicity] We disagree on the importance of simplicity. Yes, I like simplicity, but it needs to be balanced. I don't think that's the core thing about RSS, I think the core thing about RSS is what it stands for: RDF, sites and summaries.
9/2/2000. Dave Winer: What to do about RSS?
I wish it had turned out this way, then the people who legitimately want to do a Namespaces-and-RDF syndication format would have to choose another name. To their credit, the water is muddied by the departure of Netscape from the process. So there's now an identity crisis, what is RSS, and who, if anyone, has the right to evolve it?
I think the answer to this question is totally obvious. But as one of the parties to the dispute it's not up to me to say what it is.
9/4/2000. Ken MacLeod: Re: What to do about RSS
[addressing Dave] From my pov, that the new proposal, by the majority of developers, be "RSS 1.0" seemed so obvious that it wasn't until you objected so vehemently that it even crossed my mind.
9/4/2000. David McCusker: Re: TBL
[addressing Dave] I'm not directly involved. In fact I don't want to be involved. :-) But it's clear to me you were dispossessed by the naming, and very intentionally so by the folks who chose the name. I'm sensitive to nuances in dispossession.
... Only two main things matter in gauging your dispossesion. First, you were a voluntary party to an earlier version of RSS with certain characteristics. Second, you were involuntary party to the re-use of the old name for a new (but somewhat related) version with strikingly different technical characteristics. Case closed. They owe you. If they don't pay, then they suck.
9/4/2000. Ken MacLeod: Re: TBL #2
It has been suggested that both forks use a different name.
9/4/2000. David McCusker: Re: RSS name cutting and drying
[addressing Ken] I'd noticed a pronounced absense of negotiation over the naming problem, as if the folks who came up with the proposed RSS 1.0 had responded to Dave by asking coldly, "Who are you, again?" It was the coldness that had a really bad feel to it, provoking my ire.
By the way, you're doing a fine and human job of discussing the issue in a style I think is very nice. I only really think more responsiveness is required from the RDF+NS folks. The apparent "I don't know you" reaction suggests bad faith, which folks should scramble to avoid.
[re: "it has been suggested that both forks use a different name"] That's fair if there are actually two new evolving specs, if both sides agree to sign off. It only seems wrong if one side chooses unilaterally, especially if seeming to arrogate sole ownership to itself. It's better to part ways amicably than to dump an inconvenient past partner. Folks who dump others inspire less future trust.
9/11/2000. USPTO: Trademark application #78025336: RSS
Mark (words only): RSS
Current Applicant: Userland Software
Filing Date: 2000-09-11
Current Status (2001-12-26): Abandoned: Applicant failed to respond to an Office action.
Recently I have had a standard that I co-authored stolen by a big name, totally brazen, and I've said Fuck This many times in the last few weeks, and it hasn't done any good.
9/13/2000. Dan Brickley: Re:
To be clear, are you claiming that OReilly (plus various of their naive pawns such as myself) have stolen RSS, and that you're a co-author of the intellectual work that was stolen?
If that's the case, please circulate to FoRK a list of technical innovations in "your" RSS v0.91 that are anything more than trivial elaborations on the 9th March 1997 Channel Definition Format (CDF) specification.
9/13/2000. Dan Brickley: Re: #2
You're mad at us because you think we stole your vision and corrupted it.
I'd like you to stop with the accusations of theft. Last I heard from you on that topic, you still claimed we were thieves. It'd be really nice to hear that retracted.
9/13/2000. Dave Winer: Re: #3
I will retract the statement after the name is changed to something other than RSS 1.0. Until then, however reluctantly, I will stand by the statement I made on the decentralization list, in the context it was posted.
My company has big plans for RSS, and they don't include advising developers to do namespaces and RDF.
9/13/2000. Dan Brickley: Re: #4
Is it true that the *only* thing that you feel we have stolen is the name. No ideas, no technology, no designs were stolen, just the letters 'R','S','S'. Rich Site Summary. RDF Site Summary. Real Simply Syndication. Really silly squabbles...
9/13/2000. Dave Winer: Re: #5
Dan here's what was stolen.
Before the namegrab I had some influence on and participation in the evolution of RSS.
After the grab, I have no say in its future. I'm reduced to trying to talk you out of the namegrab. I've put so many weeks into just doing that. Here's what it comes down to:
My choice is to accept your version or..?
What if I think it's wrong? What then?
The provocative act was to take the name of something that exists and put it on something new.
You may not agree, and I don't want to debate all this *yet again* but that's what I lost in this and it's not fair. I worked hard to get RSS to where it is now. Lots of months, down the drain. Why? Why do you want me to go away? What the hell did I ever do to you?
9/13/2000. Dave Winer: Greetings Syndicators!
I'd like to find out if there's interest here in working beyond RSS 0.91, adding a few features possibly, new docs and howtos, or sample code, or just asking questions about how people do stuff.
... We might even rename our work something like RSS-Classic, so the people who want to own RSS can have their way.
9/20/2000. Tim O'Reilly: Re: Asking Tim
Speaking of RSS, here's my read on what happened. (I wasn't directly involved.) A group of people involved in RSS got together to start thinking about its future evolution. Dave was part of the group. When the consensus of the group turned in a direction he didn't like, Dave stopped participating, and characterized it as a plot by O'Reilly to take over RSS from him, despite the fact that Rael Dornfest of O'Reilly was only one of about a dozen authors of the proposed RSS 1.0 spec, and that many of those who were part of its development had at least as long a history with RSS as Dave had. The only connection I can see is that the O'Reilly Network ran a series of ads on our sites promoting its stories about the RSS 1.0 spec (just as it promotes other stories on O'Reilly Network sites). Dave never approached me directly to express a point of view such as "I think the RSS spec is going in the wrong direction. Is there anything you can do to help get my point of view across to the other developers?" Instead, the first I heard of it was a series of public accusations that my company was leading a conspiracy to steal "Dave's" standard.
9/20/2000. Dave Winer: Re: Asking Tim #2
I met with Dale two weeks before the announcement, and he didn't say anything about it being called RSS 1.0. I spoke on the phone with Rael the Friday before it was announced, again he didn't say that they were calling it RSS 1.0. The first I found out about it was when it was publicly announced.
Let me ask you a straight question. If it turns out that the plan to call the new spec "RSS 1.0" was done in private, without any heads-up or consultation, or for a chance for the Syndication list members to agree or disagree, not just me, what are you going to do?
UserLand did a lot of work to create and popularize and support RSS. We walked away from that, and let your guys have the name. That's the top level. If I want to do any further work in Web syndication, I have to use a different name. Why and how did that happen Tim?
9/21/2000. Tim O'Reilly: Re: Asking Tim #3
As I understand it, it was public knowledge (or certainly your knowledge) that there was work going on on a spec to extend RSS. When it was published, it was published as a "proposed RSS 1.0 spec", and that seems completely legitimate to me, whether or not the work to develop it was done in public or private. The dozen people who worked on it have enough history with RSS to propose anything they like. You personally urged Rael to start the effort to write up what he was thinking as a proposed spec. And a "proposed RSS 1.0 spec" seems like as good a description as any for what they had come up with.
It seems to me that you immediately hardened the battle lines, and started crying foul, when you should instead have said: "I don't think that this is the right direction for RSS 1.0." If you'd kept yourself to technical substance instead of vague (and incorrect) accusations of plots masterminded by O'Reilly, this whole contretemps could have been avoided.
As Lao Tzu says, "He who feels pricked, must first have been a bubble." I believe it was your power grab to unilaterally rewrite the RSS 0.91 spec with a Userland copyright that actually started this whole thing. You were moving to claim RSS as "yours" and a group of other developers put an oar in, and you didn't like it.
... By any outside reading, your claim to have "created" RSS has no basis. Dan Brickley's posts to FoRK, the first of which I linked to above, make that fairly clear. Netscape created it, but even then, it is so similar to other things available at the time from a number of players, including Microsoft, that anyone's claim to ownership are pretty thin. Netscape created the name, and that's about as close as you can get. You certainly did a lot of work to popularize and support it.
9/21/2000. Dave Winer: Re: Asking Tim #4
Tim, when I posted my "RSS" 0.91 spec, I could have left out the OK-To-Copy copyright. The copyright applied to the writing, not the underlying format, as it clearly states. Had I left that copyright out, you wouldn't have been able to take the text and use it on another site. Talk about "no good deed going unpunished."
That spec was done openly and was only documenting current practice. There was lots of feedback. If people had problems with me doing it at the time, they didn't tell me, in fact there are comments under the spec from Rael and others, where they're helping. If they had a problem with the copyright, this is the first I'm hearing about it.
I would think that you of all people would appreciate the generosity of a copyright that allows people to steal my work. The agreement was derived from the copyright that's on IETF RFCs. It's stood the test of time, it's fair, not something to freak out over. And as I said, no one freaked out at the time.
9/21/2000. Tim O'Reilly: Re: Asking Tim #5
I'm sorry I can't help you there. It was just hearsay, not directly from any of the participants. It may be incorrect. However, I did hear from a number of people (not those involved in the proposed RSS 1.0 spec) that they thought at the time that reissuing the RSS 0.91 spec with a userland copyright was a bit tacky. I can understand why you did it, though, and I don't have a problem with it.
10/12/2000. Ken MacLeod: Re: RSS History
The way that the W3C and the IETF do it is to have working groups. Working groups are made up of people who are knowledgable of the subject (experienced users as well as developers) and are willing to extend the effort to participate in the working group. It is highly regrettable that the decision to form a working group was made only after the RSS 1.0 proposal.
... I can think of no other project or technology that went through a set of circumstances similar to this.
10/12/2000. Dave Winer: Re: RSS History #2
Thanks for the help Ken.
So I guess it would be fair to say that if an outsider looked at this, that there is no precedent for the transition that took place here, this is not how open source projects or W3C or IETF projects fork.
Some people have said that the community decided to go in the direction of Namespaces and RDF, but it's clear that that did not actually happen.
10/13/2000. Ken MacLeod: Re: RSS History #3
Right, I don't recall ever seeing anything like this before.
[re: community support] It's clear that it was not a unanimous decision, yes.
10/13/2000. Dave Winer: Community consensus
The claim has been made, offlist, that there was a community consensus to move to namespaces and RDF and modules. If there was such a consensus, now is the time to show where the record of that is. Ken provided a pointer, but it's not what I asked for, because no one asked "Is it OK if we call this RSS 1.0?"
The great thing about eGroups is that no one can tamper with the record. If there was a consensus, it *must* be evident here. I went to the trouble to read the archives over the summer. There isn't that much to read. I found no evidence that the question was ever asked on this list. I know for a fact that I was never asked to vote on the transition, and I don't think the general membership of this list was asked either.
10/15/2000. Seth Russell: Re: [syndication] changing the name of RSS
I propose that we change the name because it would:
- help heal the rift with Dave Winer,
- encourage a new attitude towards this revolutionary RDF Metadata Feed; and
- [as you indicate] clear up the confusion in the marketplace if the syndication group moves ahead with RSS 9+.
Are there any valid arguments against changing the name?
10/15/2000. Paulo Gaspar: RE: [syndication] changing the name of RSS #2
Yes, changing the name of the RSS 1.0 to something else is what makes more sense - it is the for with the most diferences from the previous version.
10/17/2000. Paulo Gaspar: RE: [syndication] Total confusion in RSS-Land
The only problem I see with your arguments is that you never talk about FORKing, giving another name to RSS 1.0. Both groups could "live amicably" if the "1.0" group would just agree on that.
... And it makes sense. Even if you do not understand why other people find the RDF solution complex, they still DO. And RSS 0.92 will be much closer to 0.91 than 1.0 is. Is up to 1.0 to get another name.
10/17/2000. Seth Russell: Pick a new name for RSS 1.0
It has been suggested by Dave Winer and others that it is inappropriate to name our standard RSS 1.0. To clear up the confusion that most certainly will emerge in the market place and to give this format a new revolutionary start, it seems appropriate to also give it a new name.
10/18/2000. Jeff Bone: Forking, the name game, the politics of naming
We all seem to acknowledge that there's too much ideological distance between the camps to reasonably work on a single effort, and therefore forking is inevitable. The controversy is purely on which effort -- the new and improved and totally revised and overly complexified effort or the brutally simple incremental improvement effort -- gets to keep using the RSS name. Given that the original stakeholders are in favor of the simpler version, IMO they should get to keep the name.
10/19/2000. Mark Ketzler: Re: Forking, the name game, the politics of naming
RSS existed and was being used by lots of folk
Group A (including some of the RSS originators) wanted to make RSS extensible etc.
Group B (including rest of the original group) wanted status quo
This is a fork by Group A. Why should Group B change the name of something that existed. How do you defend this? If the RSS-DEV WG is so concerned about the RSS brand why are you tarnishing it with this name grab?
11/7/2000. Dan Brickley: RSS-Classic, RSS 1.0 and a historical debt
Contrary to what you might hear, the RSS 1.0 proposal did not come from a bunch of outsiders who swooped in and grabbed the prestigious acronym 'RSS'. RSS 1.0 as proposed is solidly grounded in the original RSS vision, which itself had a long heritage going back to MCF (an RDF precursor) and related specs (CDF etc). This can be seen for example from Guha's longstanding involvement, and Dan Libby's account of the Netscape RSS work and endorsement of the 1.0 proposal.
... I believe we have more than adequate historical justification for calling the 'new' stuff RSS. To defend this observation requires pointing to a bunch of historical baggage that I've previously avoided publicising.
... On the basis of these various observations, we have two traditions, both rooted in Guha's MCF work.
MCF > CDF > scriptingNews > RSS 0.91 > RSS-Classic
MCF > XML-MCF > RSS 0.90 > RSS 1.0
... To stress my point once more. The RSS 1.0 proposal did not appear from out of nowhere, but is routed in 5 years work in this area. The RSS 1.0 proposers did not swoop in from nowhere to steal the 'RSS' acronym.
11/7/2000. Dave Winer: Dan Brickley's message
I just subscribed to this list for a moment, to rebut Dan's assertion that <scriptingNews> format was derived from CDF. It was not. It was derived from my experience as a web writer and web app developer and that's all. I documented my work through 1997-2000 on this stuff, publicly.
11/7/2000. Seth Russell: Re: [RSS-DEV] RSS-Classic, RSS 1.0 and a historical debt
[addressing Dan Brickley] Look, this thing is past the point of justifications being important. ... Now, personally I don't have any vested interest (ego) in either the WG group or in Dave's group. But it doesn't feel right to me. I don't understand the divisive stubbornness that keeps the WG from just changing the name. But I do see the political magic that would happen if we just changed it. Especially since XRSS is the better name anyway and actually names this thing politically correct.
Heal the Rift
Change the name!
The name was never changed.