Domain: atomenabled.org
Stories and comments across the archive that link to atomenabled.org.
Comments · 16
-
I doubt it
Newsreaders are amazingly stupid. Google Reader, for example, will ignore both your "301 Permanent Redirect" and ignore your Atom link="self" as well. Something tells me it will ignore your "410 gone" too. You should test what major newsreaders (MyYahoo, Bloglines, Google Reader) do when you deep-six a feed with a 410.
Even still, 410 is stupid. A 301 redirect to something generic would be better, even if the readers are too brain dead to get the message. 410="lost traffic".
-
Time to evolve
All the best "RSS" feeds are Atom (http://atomenabled.org/)
-
Re:From the perspective of an RSS neophyte
Atom is the IETF standard syndication format (RFC 4287), and is supported by a lot of software (i.e. there's 67 feed readers listed as supporting Atom, so it's hardly some obscure format).
-
Re:what's
Atom is also spelled R S S, just ask mozirra! Of course, a format can't dictate the behavior of your reader...
-
Why they should not use "RSS" (the letters)
At least "RSS" is the *name* of the technology.
Surely you've heard of Atom? Do you suggest to display an "RSS" icon for that, too? Or have two icons? What if a site offers both formats?
Nah, a single, neutral icon is the better choice here. Granted, it may not be the most intuitive one imaginable, but it should not mention the technology behind the feed.
Actually, that's an old web wisdom: Don't mention the mechanics. Looks like the Firefox and IE developers got that one right for once.
-
go atom
and do yourself a favor: http://www.atomenabled.org/
-
Re:Embrace and extend
Let it not go unsaid (sorry if others have brought this up) that RSS is a crappy standard to build upon, but then, Micrsoft liked SOAP enough to mangle it. RSS is a defacto standard thanks to the wide userbase; but it was ill-conceived from the start. What kind of 'standard' needs an extension just to be able to account for more than one author of a piece of content?
Atom would have been a far better building block... -
Atom is scary
Is it a spec for a document, or a software application? All this talk of "posting new content into the feed"..
http://www.atomenabled.org/developers/tutorials/ap i-quick-guide.php
Someone needs to write a simple RSS->Atom migration guide, leaving out all the content-management crappola. -
Atom RSS
With Atom all official and whatnot, why would anyone be working on RSS 3.0?
Atom seems far superior to RSS 2.0 and much farther along than RSS 3.0.
Is someone trying to give Dave Winer a heart attack? -
Re:I would consider...
Well, these are are XML syndication formats. In other words, they move headlines and article summaries from server to user in machine-parseable format.
There's RSS, which is the reigning de facto standard, but it also is regrettably very, very liberally specified, and even less frequently heeded. Everyone's extending it to their own heart's content more or less competently. There are lots of different variations. Not easy to implement, not easy to learn.
Atom is an attempt to make a real standard-like standard out of RSS's best features and some of its own. It tastes more commitee-like, is probably initially less funny to implement on the server end (if you're lazy), but it is very nicely standardised and as a result it's far easier to write a parser for it, too, so client support is coming fast. And, it's more than just a syndication format: There's API for publishing and the atom format can, as such, also be used as a standardised weblog backup/storage format.
You may find the Atom web page quite informative.
-
Re:RSS vs. Atom vs. RDF
RDF (Resource Description Framework) is a meta-language, like XML. Except it's not even really a language, it's a model. Extra confusing because there are different syntaxes available, one of which is XML.
RSS 2.0 (Really Simple Syndication, I think) is what most people are talking about when they say RSS these days. Based on the original RSS 0.9x format, some people complain it's underspecified.
RSS 1.0 (RDF Site Summary) is a completely different specification, using the same basic concept & elements but all in the RDF model. Its detractors claim that RDF is too damned confusing (I won't argue there) and make the usual comments about ivory-tower intellectuals.
Atom's (not an acronym) the new kid, it hasn't actually been released yet but should be coming very soon - within weeks/months. Difficult to say anything about it until it's finalised, but it's got some nice stuff. I particularly like the Atom API. Clean & RESTful, mmm-mmm good. In my opinion (Atom ~= RSS 1.0) > RSS 2.0, but don't take my word for it as I'm fairly new to all this.
-
Re:Whither standards?
First off, Firefox also includes Atom support.
Secondly, Atom is more than a syndication format. Atom also includes a counterpart of the Blogger API for authoring. Thus you only have to deal with one standards group for both authoring and distribution.
Thirdly, Atom is a open standard with an open development and review system, unlike RSS.
Lastly, the RSS which? 0.9x, 1.0, 2.0, they are all quite different. -
Re:-1, Flamebait! :-)Well, first of all, note the smiley! Basically, there was a big flamewar about RSS around the release of RSS 2.0. Dave Winer wanted something that was really simple, whereas a whole lot of other people wanted RSS to be the first real Semantic Web application.
RSS as in RSS 2.0 stands for Really Simple Syndication, while when the R in RSS stands for RDF, we're talking Semantic Web.
So, if you had mentioned the two in the wrong fora at the wrong points in time, it would invariably have set off a huge flamewar...
What resulted from the flamewar was a fork, and Atom was created. Now, it doesn't seem to me Atom is a Semantic Web application either, and I probably lost many points here....
There seems to be some peace possibilities though.
Anyway, the funny thing I meant to point out was that one could inadvertly spark a flamewar by just saying the wrong things yet meaning nothing bad about it...
-
Re:I can help
there is no point using CSS without using XHTML, IMHO.
If you can come up with a single persuasive reason why anyone should use XHTML 1.0 over HTML 4.01 I'll be impressed. The standards are practically identical, except XHTML introduces concerns over stylesheet linking (you should be using <?xml-stylesheet .. ?> rather than <link>), content type (application/xhtml+xml, *not* text/html), content negotiation (client doesn't report XHTML support in Accept:? The right thing to do is to send it.. HTML 4!), breaking browsers which properly support HTML+SGML (you know <br /> means something completely different in HTML, right?), and an almost complete lack of support in IE (what's there is is mainly a hack, just like serving XHTML as text/html to more powerful browsers).
The only compelling reason I can think of is that XML's nicer to parse (might as well provide an Atom feed or so rather than encourage parsing your XHTML) and has a bunch of nasty API's and languages to manipulate it (DOM, XSLT, etc). Be honest; how many sites actually use an XSLT pipeline to generate content? Those that do can either just emit HTML (which XSLT supports anyway), or really should add the extra complication to do either; XHTML only doesn't make a lot of sense.
And yes, I got on The X-Philes, and was once the only site on there which actually linked stylesheets in properly. I can't say it was worth it beyond sheer geek appeal*
* (Which means I'll probably do it again in future sites, bah ;) -
Re:RSS?
-
Don't like the name ?
Fine !
Call it Atom.