element <tns:attributes> (local)
Namespace:
Type:
anonymous complexType
Content:
complex, elem. wildcard
Defined:
Includes:
definition of elem. wildcard
XML Representation Summary
<tns:attributes>
   
Content: 
{any}*
</tns:attributes>
Included in content model of elements (5):
tns:account, tns:account (type tns:AccountShadowType), tns:object (type tns:ResourceObjectShadowType), tns:resourceObjectShadow, tns:shadow (type tns:ResourceObjectShadowType)
Annotation
Attribute values from the resource. The values may be freshly fetched from the resource or cached. The set of attributes may be empty, may provide a complete copy of the resource object or anything in between. This depends on the implementation of the caching and fetching strategy, configuration of the provisioning service or operation that was invoked. While this object is stored, attibutes set will contain attribute values that are (persistently) cached from the resource. At the normal case there should be at least attributes that identify the resource object on the resouce (identifiers). This will be a single attribute in a normal case, something like uid, username, DN, etc. But if a single attribute is not enough to identify the account, more than one attribute may be present. There also may be no attributes. This can happen e.g. if IDM system knows that user should have account on the resource, but the account is not yet created and no identifier is yet assigned to it. This schema does not distinguish which attributes are idenfiers are which are ordinary attributes. That can be learned from the resource schema provided byresource or resource connector. Motivation: resource schema is dynamic, the attribute that is identifier for a specific object may be different for different resources, even if the resources are of the same type (e.g. directory servers with different LDAP schema). And we do not really need to know which of the attributes is identifier in the compile-time. Knowing that in run-time is enough. Please note that this may be out of sync with regard to the resource. In some operations (e.g. lookup) it will be only milliseconds old, but in case of sotred cached values this may be days or even weeks old value. Even though there is a single extenaible element "attributes", we do not want to put its content directly to the body of resource object. Doing so will cause problems with UPA rule and it will effectively prohibit the the of type replacement extensibility on this object. This element is supposed to be used only for resource object that follow standard resource schema. It must not be used for other resource objects.
XML Source (see within schema source)
<xsd:element name="attributes">
<xsd:annotation>
<xsd:documentation>
Attribute values from the resource. The
values
may be freshly fetched from the resource or
cached. The
set of attributes
may be empty, may provide a complete copy of
the
resource object or anything in
between. This
depends on
the
implementation of the caching
and fetching strategy,
configuration of the
provisioning service or operation that was
invoked.

While this object is stored, attibutes set will
contain
attribute values that are (persistently)
cached from the
resource.

At the normal case there should be at least
attributes that identify the resource object
on the resouce
(identifiers).
This will be a single attribute
in a
normal case,
something like uid, username,
DN, etc. But if a single
attribute is not
enough to identify the
account, more than one
attribute may be present.

There also may be no attributes.
This
can happen
e.g. if IDM
system knows that user should have
account on the resource, but the account is not
yet created
and
no identifier
is yet assigned to
it.

This schema does not
distinguish which
attributes are idenfiers are which are
ordinary
attributes. That can be learned from the
resource
schema provided byresource or resource
connector.
Motivation:
resource schema is dynamic, the
attribute that is identifier
for a specific
object may be different for
different
resources,
even if the resources are of the same type
(e.g. directory
servers with different LDAP
schema). And we do not
really need
to know which
of the attributes is identifier in the
compile-time. Knowing
that in run-time is
enough.

Please
note
that this may be out of sync with
regard to the resource. In
some
operations
(e.g. lookup) it will be only
milliseconds old,
but in case of sotred cached values this may be
days
or even
weeks old value.

Even though there is a
single extenaible
element
"attributes", we do not want to put
its content
directly
to the body of resource object. Doing
so
will cause problems
with UPA rule and it will
effectively prohibit the the of type
replacement
extensibility on this
object.

This element is
supposed
to be
used only for
resource object that follow
standard resource
schema. It must not be
used for other
resource
objects.
</xsd:documentation>
<xsd:appinfo>
<a:propertyContainer/>
</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:any maxOccurs="unbounded" minOccurs="0" namespace="##other" processContents="lax"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
Content Element Detail (all declarations; 1/1)
{any element with non-schema namespace}
Defined:
within (this) tns:attributes element
XML Source (see within schema source)
<xsd:any maxOccurs="unbounded" minOccurs="0" namespace="##other" processContents="lax"/>

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/