Several features have been moved to the RSS 3 Full spec because they are useless to low scale aggregators. For example, the Firefox Livemarks don't need enclosures or images.
However, enclosures, images and other dandy things are available in RSS 3 Full.
The separation does not create two flavors, just two modes of implementation depending on use.
'Internet Famous'? Well, getting hatemail is really a downside, isn't it?:)
Anywho, why not Atom? I don't like Atom and believe that with more documentation, RSS stands a good chance.
Competition, if moderately friendly and not destructive, is beneficial to both parties.
I'd be lying if I said that I didn't know that Atom was nearing completion. I wouldn't be lying if I said that I didn't know that Atom has become a candidate recommendation (or whatever the term is) or that I announced it on this day because of it.
As for the Initial Draft, it could be termed the Alpha version and is available on the site under http://www.rss3.org/specifications.html#archive. It was simply given to review to several people before announcing it publicly.
It's explained in the terminology page and the terminology section in the spec.
In short - normative equals "for implementation", "non-normative" means "of recommendation or suggestion nature" and "informative" means, well, "for further details only".
I'll swear in court if necessary (though if necessary, then we've gone too far, haven't we?) that I had no idea the IETF approved Atom until reading the comments here.
It was published today because it got finished today, simple as that.
Oh, sorry. Can you point out where is this particular line so I'll edit "should" to "must"? Actually, I think I'll re-edit the entire line. It should not "strive" but rather "be" backward compatible, as it already is.
Slashdot Mirror
Several features have been moved to the RSS 3 Full spec because they are useless to low scale aggregators. For example, the Firefox Livemarks don't need enclosures or images. However, enclosures, images and other dandy things are available in RSS 3 Full. The separation does not create two flavors, just two modes of implementation depending on use.
'Internet Famous'? Well, getting hatemail is really a downside, isn't it? :)
Anywho, why not Atom? I don't like Atom and believe that with more documentation, RSS stands a good chance.
Competition, if moderately friendly and not destructive, is beneficial to both parties.
Authentication sounds more like an API thing rather than a feature of the format. If you care to elaborate, email the editor
I'd be lying if I said that I didn't know that Atom was nearing completion. I wouldn't be lying if I said that I didn't know that Atom has become a candidate recommendation (or whatever the term is) or that I announced it on this day because of it. As for the Initial Draft, it could be termed the Alpha version and is available on the site under http://www.rss3.org/specifications.html#archive. It was simply given to review to several people before announcing it publicly.
It's explained in the terminology page and the terminology section in the spec. In short - normative equals "for implementation", "non-normative" means "of recommendation or suggestion nature" and "informative" means, well, "for further details only".
I'll swear in court if necessary (though if necessary, then we've gone too far, haven't we?) that I had no idea the IETF approved Atom until reading the comments here. It was published today because it got finished today, simple as that.
Oh, sorry. Can you point out where is this particular line so I'll edit "should" to "must"?
Actually, I think I'll re-edit the entire line. It should not "strive" but rather "be" backward compatible, as it already is.