t_SOADefinition_Messages_Message

aggregationChild part aggregation mode.Child parts must appear in the order specified (sequential), in any order (random) or only one choice of the children may appear (single). When "ref" is set, the aggregation from the referenced message part is used and the aggregation on the reference is ignored.Valid values based on“string”.sequentialThe contained parts must appear in their order of declaration.randomThe contained parts may appear in any order.singleOnly one of the contained parts may appear. This implies a 'choice'.description : stringMessage description.lax : booleanTrue to allow and ignore unidentifiable child parts in a raw message when parsing.Lax is mainly used during message parsing. Set it to true to allow and ignore unidentifiable child parts in a raw message when parsing. If lax is false - the default - the parser will throw an error if it encounters a message part that is not in the message definition, like an extra XML attribute or a CSV column. When "ref" is set, the lax setting from the referenced message part is used and the lax setting on the reference is ignored. Example For an RSS message definition, you probably want to set the root tag to "lax" as most RSS feeds have custom attributes added to their XML.  If a custom attribute was found in a message that your message definition didn't expect and the "lax" flag was false, the message would be rejected.name : identifierThe message name.Valid values based on“string”.:?[\p{L}_][\p{L}\p{N}_]*(:[\p{L}_][\p{L}\p{N}_]*)*Value must begin with a letter or an underscore. Case and length are not restricted. Letters, numbers and underscores are allowed. Colon is used as a scope separator. Spaces and other punctuation characters are not allowed.ref : stringMessage defining this part (and any subparts). If the ref is set to another message name, then this part will be defined by the structure of that message.