Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


RE: [xml-dev] best practice for providing newsfeeds ?

From: "Paul Sumner Downey" <Paul.Downey@----------.--->
To: "Danny Ayers" <danny666@--------.-->,"Tim Bray" <tbray@----------.--->,"Joshua Allen" <joshuaa@---------.--->
Date: 2/1/2004 12:35:00 PM
Danny Ayers wrote:

> There's little to differentiate between these two formats on that level. 

All the RSS and Atom files seem to attempt to present the same 
data in slightly different dialects of the same language.

This nicely exposes some of the key issues in 
XML data interchange:

1) using XML simplifies token parsing, but doesn't help much 
   when processing grammars. As for being able to convey message
   semantics ... 

2) MovableType now includes 4 different templates for syndication: 
   is Stove-piping really the best way to version XML languages :-(

3) something which is quintessentially pub-sub ends up using 
   polling.

OTOH the massive success of RSS does demonstrate that simple
approaches often work best. 'Good-enough' has been the story
of the Web.

Paul


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