element <tns:inbound> (local)
Namespace:
Type:
Content:
complex, 4 elements
Defined:
XML Representation Summary
<tns:inbound>
   
Content: 
tns:description?, tns:valueFilter*, tns:source?, tns:target
</tns:inbound>
Content model elements (4):
tns:description, tns:source (in tns:inbound), tns:target (in tns:inbound), tns:valueFilter
Included in content model of elements (1):
tns:attribute (in tns:accountType)
Annotation
Defines how the attribute values are used (assigned) in case of information flow from resource to IDM, e.g. in case of synchronization, reconciliation or discovery. In case a source expression is used, the expression variables should be as follows: $user - the user to whom the account belongs $account - the account that has been changed (after the change) Explanation: This is not a "value construction" as it is not constructing a new attribute value. It is rather using attribute value that was set be someone else. A simpler way how to express the assignement is needed here, especially a simple way how to express assignment target. Some rules may use that information and we definitelly need that to generate correct relative change descriptions.
XML Source (see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" name="inbound" type="tns:ValueAssignmentType">
<xsd:annotation>
<xsd:documentation>
Defines how the attribute values are used
(assigned) in
case of information flow from resource to
IDM, e.g.
in
case of synchronization, reconciliation or discovery.

In case a
source expression is used, the
expression
variables should
be as
follows:
$user - the user to whom the account belongs
$account - the
account that
has been changed (after the change)

Explanation: This
is not a "value construction" as it
is not constructing a new
attribute value. It is rather
using attribute
value that was set be
someone else.
A simpler way how to express the
assignement is needed
here, especially a simple way how
to express assignment
target.
Some rules may use that
information and we
definitelly need that to
generate correct relative
change descriptions.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
Content Element Detail (all declarations; 4/4)
tns:description
Type:
xsd:string, simple content
Defined:
XML Source (see within schema source)
<xsd:element maxOccurs="1" minOccurs="0" ref="tns:description"/>

tns:source
Type:
tns:ExpressionType, complex content
Defined:
locally within tns:ValueAssignmentType complexType
Source of assignement. R-value. The value (or values) will be copied from this place or from the result of the expression. Depending on how this type is used, the source may be implicit. Therefore the source definition is optional. The expression will most likely contain variables. Please refer to the documentation of containing or derived type for more details.
XML Source (see within schema source)
<xsd:element minOccurs="0" name="source" type="c:ExpressionType">
<xsd:annotation>
<xsd:documentation>
Source of assignement. R-value.
The value (or
values) will be copied from this place
or from the
result of
the
expression.
Depending on how this type is used, the source may be
implicit. Therefore the source
definition is optional.

The
expression will most likely contain variables.
Please refer to the
documentation of
containing or
derived type for more
details.
</xsd:documentation>
</xsd:annotation>
</xsd:element>

tns:target
Type:
tns:XPathType, mixed content
Defined:
locally within tns:ValueAssignmentType complexType
Destination of the assignment. L-value. The value (or values) will be copied to this place. It is an XPath pointer that must point to an existing, mutable part of XML document. The copy will replace all existing values. But that behavior may change in the future.
XML Source (see within schema source)
<xsd:element name="target" type="c:XPathType">
<xsd:annotation>
<xsd:documentation>
Destination of the assignment. L-value.
The value
(or values) will be copied to this place.
It is
an XPath
pointer
that must point to an existing,
mutable part of XML document.

The
copy will replace all existing
values. But that
behavior may change
in the future.
</xsd:documentation>
</xsd:annotation>
</xsd:element>

tns:valueFilter
Type:
tns:ValueFilterType, complex content
Defined:
List of filters that will be applied to the value before it even gets processed by this assignment. The filters will get applied even before the expression. The filters will be executed in chain in the order as specified here. The filters are supposed to "clean up" or transcode the value to comply with usual XML standards. (but see the note in ValueFilterType documentation)
XML Source (see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" ref="tns:valueFilter">
<xsd:annotation>
<xsd:documentation>
List of filters that will be applied to the
value before
it even gets processed by this
assignment. The
filters
will
get applied even before the expression.

The filters will be
executed in chain in the
order as
specified here.

The
filters are
supposed to "clean up" or transcode
the value to comply with usual
XML
standards.
(but see the note in
ValueFilterType documentation)
</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/