Chuq Von Rospach wrote:
> We, the techies, have to worry about transport layers and list setups and
> interoperability. I want my customers simply to be able to say "what
> information do I want?" and "how do I want it delivered?" and hide all of
> the other magic from them. So it's not necessarily new, but tighter,
> better integration to make all those pieces function together well, and
> technology that lets a user USE the tools instead of having to learn them...
Just like I don't need to know how a dynamo or nuclear power plant works
in order to turn on the lights, or know how phone company switches
work to make a phone call.
The only issue I see is that it presumes that everyone is conforming to
some generally accepted standards. A touch tone phone doesn't work on a
pulse-only line (if there are any left), nor does my electric clock radio
work in Italy.
If there were generally accepted standards, we wouldn't be arguing about
whether -request reaches a human or a mechanical interface, would we? :-)
Chuq, if/when you get to the stage of needing help on this, let me know.
Coming up with a model that handles both the techie aspects and the user
aspects is critical to its success. We're probably starting to range a bit
too far from the basic subject of this list, is there another forum for
getting into the details further?
--
Mike Nolan
