Attribute
Name of the attribute. Must be unique amongst its siblings.
This will also be the (local) name of the corresponding XSD element.
Whether this attribute is optional (can be omitted) or is required (must always appear).
On the corresponding XSD element, this will result in minOccurs="0"
or minOccurs="1"
respectively.
In the design phase the data type of this attribute is set to Enumeration.
Here you can set the specific XSD enumeration values for the attribute. You can choose to re-use any existing enumerations in this definition, or create a new one. All enumerations can also be managed from the global settings by clicking the button with the wrench icon to the left.
If no enumeration values are specified, XSD data type xs:string
will be used as a fallback.
Name of the attribute. Must be unique amongst its siblings.
This will also be the (local) name of the corresponding XSD element.
Whether this attribute is optional (can be omitted) or is required (must always appear).
On the corresponding XSD element, this will result in minOccurs="0"
or minOccurs="1"
respectively.
In the design phase the data type of this attribute is set to Enumeration.
Here you can set the specific XSD enumeration values for the attribute. You can choose to re-use any existing enumerations in this definition, or create a new one. All enumerations can also be managed from the global settings by clicking the button with the wrench icon to the left.
If no enumeration values are specified, XSD data type xs:string
will be used as a fallback.
By default an attribute will be represented in the XSD as an xs:element
. By enabling this setting the attribute will be represented in the XSD as an xs:attribute
instead. Visually this is indicated by an '@' character in front of the attribute name.
Enabling this will also cause either use="optional"
or use="required"
to be added to the XSD, depending on the value of the optional setting of this attribute.
By default entities will be represented in the XSD as a xs:complexType
with a xs:sequence
containing all child attributes and entities. Example of such an XML structure:
<Weight>
<Unit>kg</Unit>
<Value>100</Value>
</Weight>
Sometimes an external system requires an entity to be represented in the XSD as a xs:complexType
with a xs:simpleContent
that extends a simple type. In these specific cases you should switch to using "simple content". The same XML example would then look like this:
<Weight unit="kg">100</Weight>
To achieve this for the above example, you'd have to enable XSD simple content for attribute Value. Visually this is indicated by showing the attribute name in parentheses. The following restrictions apply to entities with "simple content":
- Exactly one attribute may have XSD simple content enabled and must not have XSD attribute enabled
- All other attributes of the same entity must have XSD attribute enabled
- The entity is not allowed to contain any child entities
In the design phase the data type of this attribute is set to Boolean.
Here you can set the specific XSD data type for the attribute. You can only choose from the XSD data types that are a subtype of the design data type.
Default is xs:boolean
.
In the design phase the data type of this attribute is set to DateTime.
Here you can set the specific XSD data type for the attribute. You can only choose from the XSD data types that are a subtype of the design data type.
Default is xs:dateTime
.
In the design phase the data type of this attribute is set to Decimal.
Here you can set the specific XSD data type for the attribute. You can only choose from the XSD data types that are a subtype of the design data type.
Default is xs:decimal
.
In the design phase the data type of this attribute is set to Integer.
Here you can set the specific XSD data type for the attribute. You can only choose from the XSD data types that are a subtype of the design data type.
Default is xs:long
.
In the design phase the data type of this attribute is set to String.
Here you can set the specific XSD data type for the attribute. You can only choose from the XSD data types that are a subtype of the design data type.
Default is nonEmptyString
.
In the design phase the data type of this attribute is set to Boolean.
Here you can set the specific XSD data type for the attribute. You can only choose from the XSD data types that are a subtype of the design data type.
Default is xs:boolean
.
In the design phase the data type of this attribute is set to DateTime.
Here you can set the specific XSD data type for the attribute. You can only choose from the XSD data types that are a subtype of the design data type.
Default is xs:dateTime
.
In the design phase the data type of this attribute is set to Decimal.
Here you can set the specific XSD data type for the attribute. You can only choose from the XSD data types that are a subtype of the design data type.
Default is xs:decimal
.
In the design phase the data type of this attribute is set to Integer.
Here you can set the specific XSD data type for the attribute. You can only choose from the XSD data types that are a subtype of the design data type.
Default is xs:long
.
In the design phase the data type of this attribute is set to String.
Here you can set the specific XSD data type for the attribute. You can only choose from the XSD data types that are a subtype of the design data type.
Default is nonEmptyString
.
Specifies a lower bound on a numeric value. Depending on the selected operator, only values greater or greater and equal to the specified value will be valid.
Technically it will generate a MinExclusive
or MinInclusive
restriction in the resulting XSD.
Specifies an upper bound on a numeric value. Depending on the selected operator, only values less or less and equal to the specified value will be valid.
Technically it will generate a MaxExclusive
or MaxInclusive
restriction in the resulting XSD.
Specifies a lower bound on a decimal value. Depending on the selected operator, only values greater or greater and equal to the specified value will be valid.
Technically it will generate a MinExclusive
or MinInclusive
restriction in the resulting XSD.
Secifies an upper bound on a decimal value. Depending on the selected operator, only values less or less and equal to the specified value will be valid.
Technically it will generate a MaxExclusive
or MaxInclusive
restriction in the resulting XSD.
Specifies an lower bound on a period value. Depending on the selected operator, only values greater or greater and equal to the specified value will be valid.
Technically it will generate a MinExclusive
or MinInclusive
restriction in the resulting XSD.
Specifies an upper bound on a period value. Depending on the selected operator, only values less or less and equal to the specified value will be valid.
Technically it will generate a MaxExclusive
or MaxInclusive
restriction in the resulting XSD.
Specifies the maximum number of characters or list items allowed. Must be equal to or greater than zero.
For example if 8 is set as max length value for the attribute password, this means that the value must be maximum 8 characters, otherwise the message will be rejected.
Specifies the minimum number of characters or list items allowed. Must be equal to or greater than zero.
For example if 5 is set as min length value for the attribute password, this means that the value must be minimum five characters, otherwise the message will be rejected.
Limits the content of an attribute to a specific set of numbers, letters or symbols that satisfy a regular expression. For example if the pattern [A-Z][A-Z][A-Z]
is added to the attribute initials, the only acceptable values for this attribute will be 3 uppercase letters from a to z, otherwise the message will be rejected.
More information about regular expressions and a quick online expression tester can be found here
Specifies the exact number of digits allowed. Must be greater than zero
Specifies the maximum number of decimal places allowed. Must be equal to or greater than zero.
Specifies a lower bound on a date/time value. Depending on the selected operator, only values greater or greater and equal to the specified value will be valid.
Technically it will generate a MinExclusive
or MinInclusive
restriction in the resulting XSD.
Specifies a upper bound on a date/time value. Depending on the selected operator, only values less or less and equal to the specified value will be valid.
Technically it will generate a MaxExclusive
or MaxInclusive
restriction in the resulting XSD.
Specifies a lower bound on a date/time value. Depending on the selected operator, only values greater or greater and equal to the specified value will be valid.
Technically it will generate a MinExclusive
or MinInclusive
restriction in the resulting XSD.
Specifies a upper bound on a date/time value. Depending on the selected operator, only values less or less and equal to the specified value will be valid.
Technically it will generate a MaxExclusive
or MaxInclusive
restriction in the resulting XSD.
Specifies a lower bound on a date/time value. Depending on the selected operator, only values greater or greater and equal to the specified value will be valid.
Technically it will generate a MinExclusive
or MinInclusive
restriction in the resulting XSD.
Specifies a upper bound on a date/time value. Depending on the selected operator, only values less or less and equal to the specified value will be valid.
Technically it will generate a MaxExclusive
or MaxInclusive
restriction in the resulting XSD.
Specifies a lower bound on a numeric value. Depending on the selected operator, only values greater or greater and equal to the specified value will be valid.
Technically it will generate a MinExclusive
or MinInclusive
restriction in the resulting XSD.
Specifies an upper bound on a numeric value. Depending on the selected operator, only values less or less and equal to the specified value will be valid.
Technically it will generate a MaxExclusive
or MaxInclusive
restriction in the resulting XSD.
Specifies a lower bound on a decimal value. Depending on the selected operator, only values greater or greater and equal to the specified value will be valid.
Technically it will generate a MinExclusive
or MinInclusive
restriction in the resulting XSD.
Secifies an upper bound on a decimal value. Depending on the selected operator, only values less or less and equal to the specified value will be valid.
Technically it will generate a MaxExclusive
or MaxInclusive
restriction in the resulting XSD.
Specifies an lower bound on a period value. Depending on the selected operator, only values greater or greater and equal to the specified value will be valid.
Technically it will generate a MinExclusive
or MinInclusive
restriction in the resulting XSD.
Specifies an upper bound on a period value. Depending on the selected operator, only values less or less and equal to the specified value will be valid.
Technically it will generate a MaxExclusive
or MaxInclusive
restriction in the resulting XSD.
Specifies the maximum number of characters or list items allowed. Must be equal to or greater than zero.
For example if 8 is set as max length value for the attribute password, this means that the value must be maximum 8 characters, otherwise the message will be rejected.
Specifies the minimum number of characters or list items allowed. Must be equal to or greater than zero.
For example if 5 is set as min length value for the attribute password, this means that the value must be minimum five characters, otherwise the message will be rejected.
Limits the content of an attribute to a specific set of numbers, letters or symbols that satisfy a regular expression. For example if the pattern [A-Z][A-Z][A-Z]
is added to the attribute initials, the only acceptable values for this attribute will be 3 uppercase letters from a to z, otherwise the message will be rejected.
More information about regular expressions and a quick online expression tester can be found here
Specifies the exact number of digits allowed. Must be greater than zero
Specifies the maximum number of decimal places allowed. Must be equal to or greater than zero.
Specifies a lower bound on a date/time value. Depending on the selected operator, only values greater or greater and equal to the specified value will be valid.
Technically it will generate a MinExclusive
or MinInclusive
restriction in the resulting XSD.
Specifies a upper bound on a date/time value. Depending on the selected operator, only values less or less and equal to the specified value will be valid.
Technically it will generate a MaxExclusive
or MaxInclusive
restriction in the resulting XSD.
Specifies a lower bound on a date/time value. Depending on the selected operator, only values greater or greater and equal to the specified value will be valid.
Technically it will generate a MinExclusive
or MinInclusive
restriction in the resulting XSD.
Specifies a upper bound on a date/time value. Depending on the selected operator, only values less or less and equal to the specified value will be valid.
Technically it will generate a MaxExclusive
or MaxInclusive
restriction in the resulting XSD.
Specifies a lower bound on a date/time value. Depending on the selected operator, only values greater or greater and equal to the specified value will be valid.
Technically it will generate a MinExclusive
or MinInclusive
restriction in the resulting XSD.
Specifies a upper bound on a date/time value. Depending on the selected operator, only values less or less and equal to the specified value will be valid.
Technically it will generate a MaxExclusive
or MaxInclusive
restriction in the resulting XSD.