RSS and weblogs tag team mano a mano vs. syndication and broadcatching
the weblog of Lucas Gonze: RSS and weblogs tag team mano a mano vs. syndication and broadcatching. "The reason for the awkwardness is that RSS is about content from the creator of the RSS feed, while playlists are about deep linking to resources not owned by the linker. (Thanks to Alf Eaton for this insight)."
The funny thing is I was thinking about emailing Lucas about his thoughts on RSS 2.0 and the proper integration of audio posts and playlists integration into it when I saw this post.
I don't know if I totally agree that RSS is always about content from the creator and never and can't be about deep linking to resources not owned by the linker. I think that is what Alf's insight is stating. Maybe when CNET uses RSS that is the case, but I don't think that is the case when webloggers and blog software output RSS.
Lucas points to some good links about the integration of RSS 1.0 and playlists. It looks likes he's spent some time thinking about this subject. I just don't know if I missed a whole online conversation around the subject and how he and maybe others came to his/their conclusions.
When I try to think about this area's awkwardness, I keep thinking something is missing. Maybe we need to study the best practices of mixing the two. Should there be more then one "best" way in RSS of refering to playlist as a whole and others for deriving playlists out of audio rich RSS?
One thing I noticed and remember from when the big pubs starting using RSS. They made sure their feeds conformed to the RSS specs but used it slightly different from how it was being by others up to then. They made RSS work for them and created there own best practice that fit their goal. Big and smaller pubs that followed, after the initial best practice was defined and exposed, liked what they saw and copied that model for themselves. The rest is history.
The question remains for me , can RSS be tuned in a creative way, keeping with the spec, to work for playlists and audio posts in a way that defines a best practice that will be used by others.
8:03:54 AM
|