Lists Home |
Date Index |
On Mar 18, 2004, at 3:57 PM, Dare Obasanjo wrote:
> I can already get my bank account and credit card information over the
> Web using HTTP+SSL. So what is so crazy about my bank deciding to give
> me the results as an XML document instead of an HTML one? All this
> talk of 80/20 solutions and bubbles confuses me.
Fair enough. The only point I was trying to make is that if there is a
machine at the other end trying to make sense of information (e.g. an
agent checking to see if anything *I* consider bizarre is happening on
my account), there will have to be more authoritative standards for the
semantics of the data fields than appears to be politically possible.
If humans are doing the reading, HTML, XHTML, RSS+CSS, whatever is just
fine. That is tangential to the rest of the argument, but I thought
was the kind of thing people are trying to extend RSS to do.
Using SSL, however, makes the scalability problems of polling even
greater; my point is mainly that "aggregation" of information that is
unique to me is a bit of a misnomer, so I don't see the value of
leveraging the RSS+Aggregator infrastructure to do that. Better to
build a real pub-sub network?
The 80/20 worse-is-better jabber comes in because one *could* think of
RSS+Aggregators as a poor man's pub-sub network, but it scares me to
use that philosophy for information that is intrinsically sensitive and
time critical. Maybe that is mistaken (but it's not FUD, since I have
no horse in this race!).