Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: What should you write a new feed in?

From: "Andy Dingley <dingbat@----------.--->" <dingbat@----------.--->
To: NULL
Date: 5/2/2006 2:59:00 AM


seajays@h... wrote:
> With all the slightly different flavours of feeds, (RSS 1.0, 2.0, 0.91,
> Atom etc), what should we create 'new' feeds in, if we're coding them
> from scratch?

Damn good question.

RSS 1.0 is still the most powerful and I use it for internal workflows,
where I'm feeding a lot more than "neswfeed" content through the RSS
pipeline.  It's also easy to transcode 1.0 into Atom or 2.0

Atom is a well-thought out spec and pretty capable. It does everything
you could want for a public newsfeed. It's what I use for "newsfeeds".

RSS 2.0 has no function other than as backwards compatibility to feed
business-essential but borken newsreaders that don't understand Atom.
If you need it, then sometimes you just need it. It's still ugly
though,

0.9* are dead and buried, as is Atom 0.3 and RSS 1.1

> Will one or another 'win' the battle to become the de facto standard

No.

> will we be stuck with several different feed types all trying to do the
> same thing for a long time to come?

Yes   8-(



transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent