Like "corporate blogging", "enterprise RSS" is an overloaded term. In each case, these terms could mean many things that vary among many people. I make no attempt to create definitions at this time - that's a job for the community and Wikipedia.

"Enterprise RSS is as misleading a term as Corporate Blogging - both imply within the firewall but are invariably used to refer to internet rather than intranet solutions." -- Euan Semple (DIGILAB)

Euan is correct (in my view) - typically corporate-anything in the software world suggests an internal (behind-the-firewal) implementation. However, many tools are deployed behind the firewall, but are invariably used on (or for) the public Internet. Content management systems are good examples and we call such products (like Interwoven and Vignette) "enterprise content management systems". But we don't necessarily assume these tools are only for the creation and managment of content employed for secure use within the fire-wall or corporate network. In fact, an enterprise cms is typically used predominantly for the distribution of public information.

Any use of RSS in an enterprise is in indeed "enterprise rss", isn't it? The same applies to "corporate blogs". It seems dumb to even have to state the obvious because it's the context where these tools are employed that makes it possible to arrive at an agreeable definition. For example, here in Colorado there is a gasoline station "enterprise" that uses RSS to update gas pump pricess dynamically all over the state. This is a very busy feed of late. Does this use-case qualify under the definition of enterprise RSS? I suspect it is - but it's not what Euan (or most people) might think of "enterprise RSS". And why isn't it? -- Because RSS was popularized by bloggers, so the vast majority of people believe RSS is somehow connected with blogging and even one-in-the-same; this couldn't be further from the truth of course.

Corporate blogging also suffers from a similar indigestion - the term blog carries with it a fair degree of baggage that pinpoints it as a technology used for publishing to the open Internet. Again, a blog used for any "corporate" purpose is [by definition] a corporate blog. Blogs are used for outward marketing purposes and internal knowledge management purposes. To further complicate this discussion, imagine a blog used for knowledge management in the corporate marketing department. Most blog tools are designed for public content publishing. While this doesn't necessarily rule out those tools for corporate use, many use-cases within corporate environments are ruled out for any blog systems that dont have a security and permissions architecture.

Having said this, we point to our own use of the term Enterprise RSS with an agnostic view of the definition because we know that each customer may have different business requirements . We do the same with Corporate Blogging. Our enterprise RSS platform and Blogsite.com each support security and permissions that easily address public and private business requirements. 

I think the notion of security is a key ingredient to better definitions on this subject.

Sure - RSS is big and using it for integration, or creating RSS through integration, is obviously an important idea especially given that there are so many opporunities to improve legacy content systems.

From a search perspective, it's a great idea - create dynamic RSS feeds based on search result. This lets you monitor an information system for recent changes that match a specific query. We call that "persistent search".

I'm not sure it's a "big play" though. MSN and Yahoo are now providing such features and although Google doesn't provide it [directly], their API makes it possible. And A9 has recently introduced a cool model (OpenSearch) that leverages RSS in a unique way, so Google is there (indirectly).