Namespace: |
|
Content: |
complex, 9 elements |
Defined: |
globally in common-1.xsd; see XML source |
Includes: |
definitions of 9 elements |
Used: |
at 1 location |
XML Representation Summary |
|||||
<...> | |||||
|
|||||
</...> |
<xsd:complexType name="AccountConstructionType"> <xsd:sequence> <xsd:choice> <xsd:annotation> <xsd:documentation> Reference to a resource that should host the implied account. </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:annotation> <xsd:documentation> Resource that should host the implied account. </xsd:documentation> </xsd:annotation> </xsd:element> </xsd:choice> <xsd:choice> <xsd:annotation> <xsd:documentation> Type of account that should be created on the resource. This must point to the a valid accountType definition in the resource object (in schemaHandling section). This element is optional. If not specified then the account type marked as default in the resource definition should be used. </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:annotation> <xsd:documentation> Expression that determines type of account that should be created on the resource. TODO: more The variables should be set as follows: $user - the user that this account will belong to $assignment - an assignemt that is assigning the object in which context is this expression evaluated (e.g. assignment of role) </xsd:documentation> </xsd:annotation> </xsd:element> </xsd:choice> <xsd:annotation> <xsd:documentation> The account is implied only if the condition is evaluated to true. If condition is not present, it is assumed to be true. </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:annotation> <xsd:documentation> Account attribute values implied by this role. When the role is assigned the attributes specified below should be assigned values specified below. When the role is unassigned, the values specified below should be removed unless some other role is still specifying them. TODO: this is very simplistic now. Later we need flags for value removal, authoritativeness, merging approach, etc. </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element maxOccurs="unbounded" minOccurs="0" name="entitlement" type="tns:EntitlementConstructionType"> <xsd:annotation> <xsd:documentation> Assignments implied by this role. When the role is assigned the assignable types (groups, native roles) specified below should be assigned to the account. When the role is unassigned, the assignable types specified below should be unassigned unless some other role is still specifying them. TODO: this is very simplistic now. Later we need flags for value removal, authoritativeness, merging approach, etc. </xsd:documentation> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:complexType> |
Type: |
tns:ValueConstructionType, complex content |
Defined: |
<xsd:element maxOccurs="unbounded" minOccurs="0" name="attribute" type="tns:ValueConstructionType"> <xsd:annotation> <xsd:documentation> Account attribute values implied by this role. When the role is assigned the attributes specified below should be assigned values specified below. When the role is unassigned, the values specified below should be removed unless some other role is still specifying them. TODO: this is very simplistic now. Later we need flags for value removal, authoritativeness, merging approach, etc. </xsd:documentation> </xsd:annotation> </xsd:element> |
Type: |
tns:ExpressionType, complex content |
Defined: |
<xsd:element minOccurs="0" ref="c:condition"> <xsd:annotation> <xsd:documentation> The account is implied only if the condition is evaluated to true. If condition is not present, it is assumed to be true. </xsd:documentation> </xsd:annotation> </xsd:element> |
Type: |
xsd:string, simple content |
Defined: |
<xsd:element maxOccurs="1" minOccurs="0" ref="tns:description"/> |
Type: |
tns:EntitlementConstructionType, complex content |
Defined: |
<xsd:element maxOccurs="unbounded" minOccurs="0" name="entitlement" type="tns:EntitlementConstructionType"> <xsd:annotation> <xsd:documentation> Assignments implied by this role. When the role is assigned the assignable types (groups, native roles) specified below should be assigned to the account. When the role is unassigned, the assignable types specified below should be unassigned unless some other role is still specifying them. TODO: this is very simplistic now. Later we need flags for value removal, authoritativeness, merging approach, etc. </xsd:documentation> </xsd:annotation> </xsd:element> |
Type: |
anonymous complexType, complex content |
Defined: |
<xsd:element maxOccurs="1" minOccurs="0" ref="c:extension"/> |
Type: |
tns:ResourceType, complex content |
Defined: |
<xsd:element minOccurs="0" name="resource" type="tns:ResourceType"> <xsd:annotation> <xsd:documentation> Resource that should host the implied account. </xsd:documentation> </xsd:annotation> </xsd:element> |
Type: |
tns:ObjectReferenceType, complex content |
Defined: |
<xsd:element minOccurs="0" name="resourceRef" type="c:ObjectReferenceType"> <xsd:annotation> <xsd:documentation> Reference to a resource that should host the implied account. </xsd:documentation> </xsd:annotation> </xsd:element> |
Type: |
xsd:string, simple content |
Defined: |
<xsd:element minOccurs="0" name="type" type="xsd:string"> <xsd:annotation> <xsd:documentation> Type of account that should be created on the resource. This must point to the a valid accountType definition in the resource object (in schemaHandling section). This element is optional. If not specified then the account type marked as default in the resource definition should be used. </xsd:documentation> </xsd:annotation> </xsd:element> |
Type: |
tns:ExpressionType, complex content |
Defined: |
<xsd:element minOccurs="0" name="typeExpression" type="c:ExpressionType"> <xsd:annotation> <xsd:documentation> Expression that determines type of account that should be created on the resource. TODO: more The variables should be set as follows: $user - the user that this account will belong to $assignment - an assignemt that is assigning the object in which context is this expression evaluated (e.g. assignment of role) </xsd:documentation> </xsd:annotation> </xsd:element> |
This XML schema documentation has been generated with DocFlex/XML RE 1.8.5 using DocFlex/XML XSDDoc 2.5.0 template set. DocFlex/XML RE is a reduced edition of DocFlex/XML, which is a tool for programming and running highly sophisticated documentation and reports generators by the data obtained from
any kind of XML files. The actual doc-generators are implemented in the form of special templates that are designed visually
using a high-quality Template Designer GUI basing on the XML schema (or DTD) files describing the data source XML. DocFlex/XML XSDDoc is a commercial template application of DocFlex/XML that implements a high-quality XML Schema documentation generator with simultaneous support of framed multi-file HTML,
single-file HTML and RTF output formats. (More formats are planned in the future). A commercial license for "DocFlex/XML XSDDoc" will allow you:
Once having only such a license, you will be able to run the fully-featured XML schema documentation generator both with DocFlex/XML (Full Edition) and with DocFlex/XML RE, which is a reduced free edition containing only the template interpretor / output generator. No other licenses will be required! But this is not all. In addition to it, a commercial license for "DocFlex/XML SDK" will allow you to modify the XSDDoc templates themselves as much as you want. You will be able to achieve whatever was impossible to do with the template parameters only.
And, of course, you could develop any template applications by your own! Please note that by purchasing a license for this software, you not only acquire a useful tool,
you will also make an important investment in its future development, the results of which you could enjoy later by yourself.
Every single your purchase matters and makes a difference for us! To purchase a license, please follow this link: http://www.filigris.com/shop/ |