5.1

Table Of Contents
The examples omit XML namespace identifiers from most responses. The following fragment shows how some
of them appear in a typical response body.
<VApp
xmlns="http://www.vmware.com/vcloud/v1.5"
...
xmlns:ovf="http://schemas.dmtf.org/ovf/envelope/1"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.vmware.com/vcloud/v1.5
https://vcloud.example.com/api/schema/v1.5/master.xsd">
...>
...
</VApp>
Common vCloud API Attributes
Most vCloud API objects have a number of common attributes. With the exception of name, none of these
attributes are required in request bodies, and are ignored if included. All of them are included in response
bodies.
Object Name
Every object requires a name attribute. The string value of this attribute is included in all object references, and
can be used as the display name for the object. The value of name must be unique within a given scope.
Table 12-3. Requirements for Unique Object Names
Object Type Name Scope
ProviderVdc Cloud
Org Cloud
Vdc Organization
Catalog Organization
CatalogItem Catalog
vAppTemplate None
vApp Organization
Vm vApp
Media Catalog
Disk None
Network Container (Organization vDC, vApp, or cloud)
vCloud API Programming Guide
310 VMware, Inc.