element listResourcesResponse

diagram |
namespace | http://resolver.api.de.n2.tibco.com
properties |
content | complex
children | resource
annotation |
documentation
**PRIVATE API - Reserved for internal use**
source | <xs:element name="listResourcesResponse"> <xs:annotation> <xs:documentation>**PRIVATE API - Reserved for internal use**</xs:documentation> </xs:annotation> <xs:complexType> <xs:annotation> <xs:documentation> The collection of Resources associated with the identified model entity. </xs:documentation> </xs:annotation> <xs:sequence> <xs:element name="resource" type="orgdto:XmlModelEntityId" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> </xs:element>

element listResourcesResponse/resource

diagram |
type | XmlModelEntityId
properties |
minOcc | 0
maxOcc | unbounded
content | complex
children | dynamic-id-attr qualifierSet
attributes |
Name | Type | Use | Default | Fixed | Annotation
model-version | xs:int | optional | -1 |  |
documentation
Major version number of the organization model in which an organization model entity resides. If not specified, the default value will be the latest version of the organization model. (Version numbers must be compatible with, and conform to, the OSGi version number schema. For Directory Engine, only the major part of the version number is significant.)
entity-type | OrganisationalEntityType | required |  |  |
documentation
Enumerated value defining the type of the organization model entity.
guid | xs:string | required |  |  |
documentation
Globally unique ID of the organization model entity. (Although this value is unique across all entities, if the entity exists within more than one major version, it will share the same GUID.)
qualifier | xs:string | optional |  |  |
documentation
Only applicable in certain circumstances, and only to organization model entities whose entity-type is PRIVILEGE or CAPABILITY. These entities can have an association with other entities - for example, a resource may hold many capabilities, or a position may have many privileges. These associations can have a qualifying value, according to their nature, to differentiate them. For example, the PRIVILEGE to sign off a purchase order may be qualified with the maximum amount that can be signed off.
source | <xs:element name="resource" type="orgdto:XmlModelEntityId" minOccurs="0" maxOccurs="unbounded"/>

XML Schema documentation generated by XMLSpy Schema Editor http://www.altova.com/xmlspy