OK ... so we have libraries containing hundreds of device drivers. Hopefully, they are standardized, regardless of source (although somehow I doubt that).
I'm assuming that means some sort of interface box needs to be fitted on each piece of kit to be included in this Wonderful Scheme.
I can't help but wonder how these interfaces work (how do they "tap in"* to the kit in question), and what form these "boxes" take. And how to they connect (plug'n'play, remember) to the network (bus) - USB?
OK, so we have hundreds (or thousands) of devices on the bus at the same time, so how (and when) do they "speak up", I wonder? Do they "push", or wait to be "pulled" (polled) from a central controller. And how often ... stuff like that. If they "push" when something changes, well that would be almost all of the time, would it not? Perhaps they only start
bleating at some pre-set trigger point, such as in alarm conditions.
And, not only how much is all this expected to cost, but who is going to fit all these interfaces (and how are the equipment OEM's reacting to issues like warranties on their kit, and so forth)?
And (lastly) ... do we assume that
legacy equipment is going to be left out of all this (thereby providing yet another reason for it "not being supported" - and hurried off to the nearest skip) ... or is the spec (protocols, standards
etc.) of this "open architecture" (as claimed) going to be published, in case others wish to have a go at "retro fitting" interfaces to older kit if necessary?
It might be stating the obvious, but not all types of kit will be needing consideration here. For instance, I doubt that my old favourite, the Roberts Pump, will be getting the
Cerner treatment!
*
OK ... via the appropriate driver - but how?
