Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


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

From: "Bob Wyman" <bob@-----.-->
To: "'Joshua Allen'" <joshuaa@---------.--->, "'Michael Champion'" <mc@-------.--->, "'XML DEV'" <xml-dev@-----.---.--->
Date: 2/2/2004 10:12:00 PM
Joshua Allen wrote:
>> original creation. (Atom defines both "created" date and "issued" 
>> date. This allows the distinction to be made.)
> Great, a techie feature.  My grandmother certainly didn't ask for
that one.  
	Well, other people's grandmothers *did*. Every day I get mail
from someone asking: "Why are you telling me that this entry which is
dated "August-2003" is "New"? How stupid is your code that it can't
read a date!"
	The lack of metadata in RSS confuses users more than it
confuses us. We have all sorts of techniques to detect if something
has changed, however, the user probably doesn't have a copy of the six
month old entry that just got updated and wouldn't want to bother
comparing the two anyway.
	With specs as vague and poorly defined as RSS, it is
exceptionally difficult for us to provide quality service to our
customers. That, ultimately is the goal. Whether or not what we're
doing is "elegant" or pleasing to the techies is only secondary.
However, given RSS, we can't deliver on the things that our users are
demanding.

		bob wyman


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