The UCI could be achieved with software, no specific hardware requirements, it would work on whatever hardware technologies the Internet would be working on at any given time. It would only require the definition of the protocols to be used by all the software parts involved.
The UCI goal is to connect in the most efficient way “requests” with their “answers”, or “demand” with “provider”. The requests can be as broad as life is, and can be done by individuals, groups, companies. Therefore it seems obvious that for every “subject” a specialized software should be built, within the protocols and communication standards defined in the UCI.
The User Pod
First thing we need are the interfaces for the users to post his requests and get the answers. A “user” being any individual person on his behalf or for a group or company. There should be one single login to all his possibilities in the UCI, a central account to his UCI Pod. The access to the Pod should be possible from any device, cellular, computer, TV .. i.e any device hooked to the Internet. The Pod would contain different specialized interfaces for different purposes as well as a message center, let’s say the Job Search Interface and Travel Deal Search Interface. I described the way to work in the Pod in a previous post “One day in the UCI“.
Service Providers
We need the architecture to answer to the needs of the User, let’s call them Service Providers. They are the ones that would have the answers to the requests of the user are are interested in getting to the User. There would be no limitation in the number of Service Providers in total or for any specific subject, these would usually be the ones that currently have a website in the Web Centric Internet, often with a business model behind their service. They could be passive or active in their behavior, i.e. they could wait for user requests to come or they could in the search of users.
Users & Providers Directory
The key to connect Users and Providers would be the Directories, where a list of who, and what it requests or offers would be listed. Some kind of Yellow Pages for services and White Pages for Users.
Engines Connecting it All
And finally the software engines that would connect it all, Users with Users, Users with Providers, Providers with Users. Thanks to the Yellow and White pages the engines would know who, where and how to contact.
[...] User side of the UCI architecture is all to be done, the Service Providers part could be put up to work with less effort if the [...]
[...] say current websites) to communicate through the Middle Agent (MA). This model fits with my view of the [...]
[...] say current websites) to communicate through the Middle Agent (MA). This model fits with my view of the [...]