element <tns:accountRef> (local)

Namespace:	http://midpoint.evolveum.com/xml/ns/public/common/common-1.xsd
Type:	tns:ObjectReferenceType
Content:	complex, 2 attributes, 2 elements
Defined:	locally witnin tns:UserType complexType in common-1.xsd; see XML source

XML Representation Summary

<tns:accountRef

oid	=	xsd:string
type	=	xsd:QName

Content:

tns:description?, tns:filter?

</tns:accountRef>

Content model elements (2):

tns:description, tns:filter

Included in content model of elements (2):

tns:user, tns:user (type tns:UserType)

Annotation

Set of user's accounts. This is the set of accounts that belongs to the user in a sense that these accounts represents the user (the same physical person, they are analogous). This element contains a set of pointers to Account objects (by OID) this version will be used in repository (for storage). If this attribute is present in the User object, the account attribute for the same account OID must not be present.

XML Source (see within schema source)

<xsd:element maxOccurs="unbounded" minOccurs="0" name="accountRef" type="c:ObjectReferenceType">

<xsd:annotation>

<xsd:documentation>

Set of user's accounts. This is the set of
accounts that belongs to the user in a sense
that
these
accounts
represents the user (the
same physical person, they are
analogous).
This element contains a set of
pointers to
Account
objects (by OID) this version
will be used in repository (for
storage).

If this attribute is
present in the User
object,
the
account attribute for the same account
OID must not be present.

</xsd:documentation>

</xsd:annotation>

</xsd:element>

Attribute Detail (all declarations; 2/2)

oid

Type:	xsd:string
Use:	optional
Defined:	locally within tns:ObjectReferenceType complexType

Target of the reference. Optional only during imports. The objects stored in the repository must have the OID value filled in.

XML Source (see within schema source)

<xsd:attribute name="oid" type="xsd:string" use="optional">

<xsd:annotation>

<xsd:documentation>

Target of the reference.

Optional only during imports. The objects stored in the repository must have the OID
value filled in.

</xsd:documentation>

</xsd:annotation>

</xsd:attribute>

type

Type:	xsd:QName
Use:	optional
Defined:	locally within tns:ObjectReferenceType complexType

XSD type of the reference target object. It should be provided if the type is known (e.g. when reading object from the repository). The primary reason for this is to have some kind of type safety but especially to be able to use this in the XPaths that specify what references to resolve.

XML Source (see within schema source)

<xsd:attribute name="type" type="xsd:QName" use="optional">

<xsd:annotation>

<xsd:documentation>

XSD type of the reference target object.

It should be provided if the type is known (e.g. when
reading object from the repository).

The primary reason for this is to have some kind of
type safety but especially to be able to use
this in the XPaths that specify what references to resolve.

</xsd:documentation>

</xsd:annotation>

</xsd:attribute>

Content Element Detail (all declarations; 2/2)

tns:description

Type:	xsd:string, simple content
Defined:	by reference within tns:ObjectReferenceType complexType

XML Source (see within schema source)

<xsd:element maxOccurs="1" minOccurs="0" ref="tns:description"/>

tns:filter

Type:	tns:FilterType, empty content
Subst.Gr:	may be substituted with 10 elements
Defined:	by reference within tns:ObjectReferenceType complexType

Filter that can be used to dynamically lookup the reference OID e.g. during imports. It must not be used for normal operations and references with the filter must not be stored in the repository.

XML Source (see within schema source)

<xsd:element minOccurs="0" ref="tns:filter">

<xsd:annotation>

<xsd:documentation>

Filter that can be used to dynamically lookup the reference OID e.g. during imports.
It must not be used for normal operations and references with the filter must not
be stored in the repository.

</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:

To configure the generated documentation so much as you want. Thanks to our template technology, it was possible to support > 400 template parameters, which work the same as "options" of ordinary doc-generators. The parameters are organized in nested groups, which form a parameter tree. Most of them have their default values calculated dynamically from a few primary parameters. So, you'll never need to specify all of them. That will give you swift and effective control over the generated content!
To use certain features disabled in the free mode (such as the full documenting of substitution groups).
To select only the initial, imported, included, redefined XML schemas to be documented or only those directly specified by name.
To include only XML schema components specified by name.
To document local element components both globally and locally (similar to attributes).
To allow/suppress unification of local elements by type.
To enable/disable reproducing of namespace prefixes.
To use PlainDoc.tpl main template to generate all the XML schema documentation in a signle-file form as both HTML and incredible quality RTF output.
To format your annotations with XHTML tags and reproduce that formatting both in HTML and RTF output.
To insert images in your annotations using XHTML <img> tags (supported both in HTML and RTF output).
To remove this very advertisement text!

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/