element getEntityNameResponse
diagram de_entityResolver_diagrams/de_entityResolver_p6.png
namespace http://resolver.api.de.n2.tibco.com
properties
content complex
children entity
annotation
documentation
**PRIVATE API - Reserved for internal use**
source <xs:element name="getEntityNameResponse">
 
<xs:annotation>
   
<xs:documentation>**PRIVATE API - Reserved for internal use**</xs:documentation>
 
</xs:annotation>
 
<xs:complexType>
   
<xs:annotation>
     
<xs:documentation>Returns the name(s) of the entities identified by the given model
                version and guid.
</xs:documentation>
   
</xs:annotation>
   
<xs:sequence minOccurs="0" maxOccurs="unbounded">
     
<xs:element name="entity" type="orgdto:XmlParticipantId">
       
<xs:annotation>
         
<xs:documentation>Gives the summary information for each entity identified in the request.</xs:documentation>
       
</xs:annotation>
     
</xs:element>
   
</xs:sequence>
 
</xs:complexType>
</xs:element>

element getEntityNameResponse/entity
diagram de_entityResolver_diagrams/de_entityResolver_p7.png
type XmlParticipantId
properties
content complex
children guid name dynamic-id-attr
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  optional      
documentation
Category of this organization model entity (used to improve and validate the search).
qualifier  xs:string  optional      
documentation
Qualifier value. This is only applicable in certain circumstances, and only to entities of the entity-type PRIVILEGE or CAPABILITY.

These entities can have an association with other entities - for example, a resource may hold many capbilities a position may have many privileges. Those 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 for which the purchase order is made.
annotation
documentation
Gives the summary information for each entity identified in the request.
source <xs:element name="entity" type="orgdto:XmlParticipantId">
 
<xs:annotation>
   
<xs:documentation>Gives the summary information for each entity identified in the request.</xs:documentation>
 
</xs:annotation>
</xs:element>


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