Re: [syndication] Re: eXtensible Content Syndication (the next step for OCS)

[Aaron Swartz <aswartz@swartzfam.com>]

On Sunday, August 12, 2001, at 10:18  AM, Morbus Iff wrote:

> So, whether it's a standard or not, any solution I choose is 
> gonna have the
> title and description built into the channel list. Sadly 
> enough, I'm going
> to be steering the discussion more toward stranger burtonator 
> than friend
> Aaron Swartz. Burtonator's making a client, Aaron isn't.

Aww! I'm hurt... :-)

Actually, I am a lead developer on Peerkat: 
http://peerkat.sourceforge.net/ which *is* an RSS client, thank 
you very much.

And, for the record, I think that having title and description 
built in is a good idea. That's been my position from the 
beginning, I'm not sure why you thought otherwise... If we're 
using title and description, however, why not just use RSS?

> That's it for me this round. Concerning Aaron's followup 
> message, I think
> the dc:language should definitely be as close to required as 
> possible, but
> don't like his attribute loving format. I fear the "use RDF! use RDF!"
> admonishing.

What did attributes ever do to you, huh? When I've built SAX and 
SAX-based parsers, attribute content was much easier to get at 
than element content. I haven't used DOM tools, but I'd think 
that element and attribute content can't be too different...

Yes, I think it'd be nice to use RDF, especially since a lot of 
RSS clients will be/are using RDF datastores. However, I tend to 
think using RSS would be even better since it does just about 
everything we want out of this format, and there are a gazillion 
tools to use.

--
[ "Aaron Swartz" ; <mailto:me@aaronsw.com> ; <http://www.aaronsw.com/> ]