[Sigia-l] Notification schema?

[Listera]

"Eric Scheid" wrote:

>> Right. But that's what I've been talking about for the past few posts: a
>> corporate setting where you control both ends. I even suggested that Joe
>> could write his own simplex/complex RSS protocol to include whatever
>> functionalities needed. That's the beauty of XML.
> 
> Firstly, in corporate settings the source of the information is not always
> under control of the consumer of that information.

Of course not. But the *developers* of that corporate RSS setup can control
both ends, if they wanted to. One of the ways to do that is the scenario I
spelled out for Joe: via a web page. They could, for instance, shift the RSS
expiry settings per user and store that at the server, which would solve the
problem you raised. (I wrote a system like that about 5 years ago, not in
RSS/XML, but in a simple text format.)

> Secondly, we're no longer talking about RSS the concept, only RSS the XML
> format. Theoretically it's possible to get RSS content delivered via various
> gateways (RSS source --> HTTP --> FTP --> NNTP --> SMTP --> HTTP --> RSS
> reader), but we're no longer talking RSS the concept.

The concept/format distinction is over my head. My focus in all this has
been that "change notification" is a problem that needs to be solved. People
have thought about this and realized that broadcasting via email is not the
best solution and came up with RSS. As I said RSS itself is in flux.
Two-three years from now we might be talking about echo 2.0 or some other
variant. But whatever it is, I hope people to pay attention to it as a
possible or even a better solution than email.

Ziya
Nullius in Verba