KR> Fair enough. =) You could add some kind of demarcation between KR> items, but you'd have to ensure that demarcation won't potentially KR> show up as part of a string. KR> You could also do something like: "Hypervisor: QEMU 0.9.1" My problem with that is that I believe the caption is intended to be something displayed by a client to a user. Either as a part of a larger client-generated string, or as it is. Doing something like the above, or trying to make the values separated by a delimiter means that the client is forced to parse it up to display it the way they want. For example, if they wanted to display the caption as: "Xen System: $CAPTION" It might break some visual guidelines to have that read: "Xen System: Hypervisor: QEMU 0.9.1" which is kinda awkward. So, I dunno, it's not a very formal interface and thus shouldn't really be parsed by the client as it could change. But if we try to strive for something that could reasonably be displayed to the user as it is, that seems reasonable to me. -- Dan Smith IBM Linux Technology Center Open Hypervisor Team email: danms@us.ibm.com