Comments on: How not to do RSS http://www.barelyfitz.com/blog/archives/2006/07/12/396/ Patrick Fitzgerald of BarelyFitz Designs Tue, 09 Mar 2010 20:45:38 -0500 http://wordpress.org/?v=2.8.4 hourly 1 By: sasha http://www.barelyfitz.com/blog/archives/2006/07/12/396/comment-page-1/#comment-25841 sasha Mon, 01 Sep 2008 15:52:57 +0000 http://www.barelyfitz.com/blog/archives/2006/07/12/396/#comment-25841 <a href="http://index1.kaytm.com" rel="nofollow">tuberculin syringes 1cc</a> <a href="http://index2.kaytm.com" rel="nofollow">veris</a> <a href="http://index3.kaytm.com" rel="nofollow">walt disney resorts</a> <a href="http://index4.kaytm.com" rel="nofollow">simple elegance prom dress missouri</a> <a href="http://index5.kaytm.com" rel="nofollow">fan network</a> <a href="http://index1.kaytm.com" rel="nofollow">tuberculin syringes 1cc</a> <a href="http://index2.kaytm.com" rel="nofollow">veris</a> <a href="http://index3.kaytm.com" rel="nofollow">walt disney resorts</a> <a href="http://index4.kaytm.com" rel="nofollow">simple elegance prom dress missouri</a> <a href="http://index5.kaytm.com" rel="nofollow">fan network</a>

]]> By: pat http://www.barelyfitz.com/blog/archives/2006/07/12/396/comment-page-1/#comment-5105 pat Thu, 13 Jul 2006 14:37:59 +0000 http://www.barelyfitz.com/blog/archives/2006/07/12/396/#comment-5105 > The brilliance is that it’s perfectly acceptable according to the RSS 2.0 specification. According to the spec, the GUID is "a string that uniquely identifies the item"; however, these people are setting it to a random value each time the feed is retrieved. Since that's not really a GUID, it should not be provided. The GUID seems perfectly fine for entry identification, but since it can be misused (as in this case) some RSS aggregators (like SharpReader) choose to deal with it in other ways. > The brilliance is that it’s perfectly acceptable according to the RSS 2.0 specification.

According to the spec, the GUID is “a string that uniquely identifies the item”; however, these people are setting it to a random value each time the feed is retrieved. Since that’s not really a GUID, it should not be provided.

The GUID seems perfectly fine for entry identification, but since it can be misused (as in this case) some RSS aggregators (like SharpReader) choose to deal with it in other ways.

]]> By: Danny http://www.barelyfitz.com/blog/archives/2006/07/12/396/comment-page-1/#comment-5103 Danny Wed, 12 Jul 2006 23:27:28 +0000 http://www.barelyfitz.com/blog/archives/2006/07/12/396/#comment-5103 The brilliance is that it's perfectly acceptable according to the RSS 2.0 specification. Duplicate items are unavoidable with (especially when aggregating from multiple sources) unless they are clearly identified. RSS 2.0 is totally sloppy on entry identification. But at least it's simple, eh? The brilliance is that it’s perfectly acceptable according to the RSS 2.0 specification. Duplicate items are unavoidable with (especially when aggregating from multiple sources) unless they are clearly identified. RSS 2.0 is totally sloppy on entry identification. But at least it’s simple, eh?

]]> By: Scripting News Annex » Scripting News for 7/12/2006 http://www.barelyfitz.com/blog/archives/2006/07/12/396/comment-page-1/#comment-5102 Scripting News Annex » Scripting News for 7/12/2006 Wed, 12 Jul 2006 18:25:34 +0000 http://www.barelyfitz.com/blog/archives/2006/07/12/396/#comment-5102 [...] Patrick Fitzgerald sheds some light.  [...] [...] Patrick Fitzgerald sheds some light.  [...]

]]>