barge - Embassy OS -- too lofty. I think if you combine your thoughts on how the OS will both integrate and enable these applets to work together seamlessly, with Doma's viewpoint that Premium Service utilities (over time) will manage the trust domain grid both within and across networks, then I think that you are both vehemently agreeing, but can't quite come to grips on the boundaries of your gold mines.
I do not believe that Wave will manage web-services. Rather, as you (barge have said many times) it will enable web-services. So, what does 'enable' mean in this context. Well, here is where I think you get more into Doma's definition for the value proposition. Since future applications (applets) will become a paid for, metered and compiled collection of applets (over time) the network that distributes (securely), collects, enables, meters, disables, migrates, qualifies, restores, etc will be enabled and supported by hopefully many of Wave's Premium services.
Once these TPMs and services are deployed (trusted nodes on the grid as some call it), you can then begin to view the new IT-infrastructure as a semi-open, not-yet fully programmable network. Although this generation of the grid gives the appearance of trust, is not fully trustworthy yet. Why? Because the chipsets are not the EII chipsets. They are non-programmable chipsets, capable only of managing limited functionality ~ like Key (secrets) Management.
However, as the industry matures towards EII, Wave continues to establish itself as the Utility manager within each domain. Once EII is adopted en mass, then can easily Wave move to become the utility manager across domains as well. Think of it as sort of an open-programmable ERP-like network grid of trusted servers (TANs) and Clients.
I don't think we're here yet, but both barge and doma appear to be right to me.
T123
