18 April 2005

XML Concepts: Actively transforming an e-mail only notification platform into an RSS feed-generating platform

One of the flaws with an e-mail newsletter is the presumption that readers will read everything.

But this isn't how a feed gets consumed.

It would be nice if there was a way to not simply RSSify an e-mail letter, but actually create a tool that would transform an e-mail generator into something that created individual feeds for each subject or topic.


XML Transform Platform

Adjusting platforms from e-mail to feed-generating systems


This externally adjust an email-only notification system to one that uses RSS feeds. This would not RSSify an e-mail newsletter.

This doesn't turn a page into an RSS feed; nor does it convert an email newsletter into an RSS feed.

Rather this approach would grab an entire platform; inject a mid-term black box between the platform and the content-reader; and then adjust all the outputs from e-mail to an RSS feed.

They key on this would be to create a mirror-like external structure that took all the outputs, and then transformed them into a feed.

This would not be like bot-a-blog that is a subscription service. That is passive.

This system would aggressively inject itself into the code on the mirror-site, and not simply transform the output to RSS, but actively adjust the e-mail notification system to one that uses RSS feeds.

Where to do this and why

Imagine if you're in a situation where the external platform was broken, providing corrupt data, and you were unable to get the peer to cooperate.

Yet, you've still got readers that needs this information.

I could imagine a situation where the external platform [although corrupted, messed up, and otherwise providing non-usable data via e-mail] may need some external tweaking to bring the data into compliance with standards.

Also, suppose you have a major platform that only has e-mail notification; but you have many other expected searches and content to show up. You don't want a single-feed for that site.

Rather, you want a way of auto-generating separate feeds for the different content streams. Clearly, the content hasn't been yet created. Readers-content providers do not want to have to wade through the e-mail to RSS feed to separate the content into clippings.

Rather, it would be nice to simply accept the original platform as it is [with all its mixed up content in one e-mail] and then have a future capability to separate the content into separate feeds that are based on the reader's needs.
One of the flaws with an e-mail newsletter is the presumption that readers will read everything.

But this isn't how a feed gets consumed.

It would be nice if there was a way to not simply RSSify an e-mail letter, but actually create a tool that would transform an e-mail generator into something that created individual feeds for each subject or topic.


XML Transform Platform

Adjusting platforms from e-mail to feed-generating systems


This externally adjust an email-only notification system to one that uses RSS feeds. This would not RSSify an e-mail newsletter.

This doesn't turn a page into an RSS feed; nor does it convert an email newsletter into an RSS feed.

Rather this approach would grab an entire platform; inject a mid-term black box between the platform and the content-reader; and then adjust all the outputs from e-mail to an RSS feed.

They key on this would be to create a mirror-like external structure that took all the outputs, and then transformed them into a feed.

This would not be like bot-a-blog that is a subscription service. That is passive.

This system would aggressively inject itself into the code on the mirror-site, and not simply transform the output to RSS, but actively adjust the e-mail notification system to one that uses RSS feeds.

Where to do this and why

Imagine if you're in a situation where the external platform was broken, providing corrupt data, and you were unable to get the peer to cooperate.

Yet, you've still got readers that needs this information.

I could imagine a situation where the external platform [although corrupted, messed up, and otherwise providing non-usable data via e-mail] may need some external tweaking to bring the data into compliance with standards.

Also, suppose you have a major platform that only has e-mail notification; but you have many other expected searches and content to show up. You don't want a single-feed for that site.

Rather, you want a way of auto-generating separate feeds for the different content streams. Clearly, the content hasn't been yet created. Readers-content providers do not want to have to wade through the e-mail to RSS feed to separate the content into clippings.

Rather, it would be nice to simply accept the original platform as it is [with all its mixed up content in one e-mail] and then have a future capability to separate the content into separate feeds that are based on the reader's needs.
" />