Subject: Re: About channel - msg#00061

Previous Message by Date: click to view message preview

Re: About channel

>From an RSS-1.0 > perspective it /is/ possible to have multiple channels inside a document. > At > least from a purely XML/RDF point of view. Only from a purely XML/RDF point of view - while being valid RDF it would go against what the spec says should be in an RSS document. XML/RDF with such channels might be used for recording the data of a collection of RSS sources, and that might be useful in implementing some RSS application, but that is outside of the scope of RSS itself.

Next Message by Date: click to view message preview

Re: About channel

From: <jon@xxxxxxxxxxxxxxx> > From an RSS-1.0 > > perspective it /is/ possible to have multiple channels inside a document. > > At > > least from a purely XML/RDF point of view. > > Only from a purely XML/RDF point of view - while being valid RDF it would go against what the spec says should be in an RSS document. XML/RDF with such channels might be used for recording the data of a collection of RSS sources, and that might be useful in implementing some RSS application, but that is outside of the scope of RSS itself. Yeah, what he said. While I've often toyed with the idea of using a greater range of RDF features in RSS there's not a lot of traction for the idea. If anything I'd use it as a way to do bulk or alternative delivery of feeds. That is, use something like BitTorrent, eDonkey or other p2p freespace transports to obtain newsfeeds. Allow for 'something' to accept mutliple feed request queries and then spit them back out combine into one compressed (and possibly encrypted) RDF document. This to allow folks that have serious issues to still get the news. Like living in a country that censors delivery of regular HTTP traffic. This would of course require that reader programs understand how to operate in this fashion. But I've also given thought to the idea of using this as a way to 'pre-load' a local proxy cache. This to allow the client programs to make use of HTTP port 80 requests to the cache. But allow the cache to use alternative means. It's a cool enough idea but not enough folks seem to need it to justify the effort. -Bill Kearney Syndic8.com

Previous Message by Thread: click to view message preview

Re: About channel

>From an RSS-1.0 > perspective it /is/ possible to have multiple channels inside a document. > At > least from a purely XML/RDF point of view. Only from a purely XML/RDF point of view - while being valid RDF it would go against what the spec says should be in an RSS document. XML/RDF with such channels might be used for recording the data of a collection of RSS sources, and that might be useful in implementing some RSS application, but that is outside of the scope of RSS itself.

Next Message by Thread: click to view message preview

Re: About channel

From: <jon@xxxxxxxxxxxxxxx> > From an RSS-1.0 > > perspective it /is/ possible to have multiple channels inside a document. > > At > > least from a purely XML/RDF point of view. > > Only from a purely XML/RDF point of view - while being valid RDF it would go against what the spec says should be in an RSS document. XML/RDF with such channels might be used for recording the data of a collection of RSS sources, and that might be useful in implementing some RSS application, but that is outside of the scope of RSS itself. Yeah, what he said. While I've often toyed with the idea of using a greater range of RDF features in RSS there's not a lot of traction for the idea. If anything I'd use it as a way to do bulk or alternative delivery of feeds. That is, use something like BitTorrent, eDonkey or other p2p freespace transports to obtain newsfeeds. Allow for 'something' to accept mutliple feed request queries and then spit them back out combine into one compressed (and possibly encrypted) RDF document. This to allow folks that have serious issues to still get the news. Like living in a country that censors delivery of regular HTTP traffic. This would of course require that reader programs understand how to operate in this fashion. But I've also given thought to the idea of using this as a way to 'pre-load' a local proxy cache. This to allow the client programs to make use of HTTP port 80 requests to the cache. But allow the cache to use alternative means. It's a cool enough idea but not enough folks seem to need it to justify the effort. -Bill Kearney Syndic8.com