Evening, So one thing I did see validated by the rm-wg document was the trend towards compute/network/storage that we're fast settling on ourselves. Our current terminology however is far more specific - we've picked up "Drive" and "Server" from ElasticHosts for example. While this does make sense a lot of the time there's nothing to say that OCCI can't be used for VDI for example, where the "servers" are in fact "clients". Take it a step further and you've got things like Dreamhost PS<http://dreamhost.com/hosting-vps.html>which kind of like a virtual provate server in that it behaves like one (it can be restarted via their API<http://wiki.dreamhost.com/API#dreamhost_ps-reboot>etc.), only it refers to resource allocations in a shared hosting environment or MySQL instances. Granted that's outside of our remit but ther'es no point stopping them from using it by choosing our terminology poorly. In fact a lot of these functions can apply equally to physical machines as they can to lightweight threads in an Apache process (and everything in between including, of course, virtual machines which are currently our primary target). I've been trying to think of other resources outside of these three main types but even strange things like ISDN interfaces (yes, this sort of thing does appear in enterprise data centers) can be handled via PCI passthrough parameters on a virtual machine. All in all, unless anyone has any concerns about this approach I'd like to adopt this terminology throughout. Sam