A description of the service. Provides help text on how
to use the service.
A list of data that can be used to uniquely identify a particular instance of a service.
Multiple instances of a service can exist across different domains (for instance, a service
that is associated with a particular virtual machine or a particular host). In such cases,
the service name is insufficient to identify the service and location data can be used
to identify the instance of interest. A service may publish as much location data
as is needed to identify it (e.g, vmware.host. or vmware.vm. or both).
The particular choice of locations have to be agreed upon by
the client and the service.
The managed object that presents this service.
A service name. Each service is expected to create a unique name
for itself that can be used to locate the service. This name
does not need to be unique across hosts or other such locations though.
Properties inherited from DynamicData