List of business rules that have been breached by the input and that will
require the user to correct in order to print labels on resubmission of
XML input file.
This element contains a consignment number and optional customer reference.
These values are used to distinguish a consignment from any other consignment.
This value appears on a routing label and is used as the key for a consignment.
This identifies the market type for the consignment comprising the origin
country and whether the consignment is being shipped domestically or
internationally and within which international trading block, e.g. 'EU'.
The dimensions (height, width, length) and weight of the consignment,
piece or article. Data must be provided in metres for dimensions,
kilograms for weight.
Information relating to name and address for a participant
in the consignment.
Examples of a participant are:
The Sender - the company sending the consignment
The Receiver - the company receiving the consignment
The Collection Address - the address from which the consignment is picked up
The Delivery Address - the address to which the consignment should be delivered
Information relating to name and address for a participant
in the consignment.
Examples of a participant are:
The Sender - the company sending the consignment
The Receiver - the company receiving the consignment
The Collection Address - the address from which the consignment is picked up
The Delivery Address - the address to which the consignment should be delivered
A piece line describes a kind of piece sharing the same physical attributes.
(A piece is a package, box, envelope or shippable unit. All pieces which are
identical are defined for convenience as a piece line with a number of units.)
For example if there are 5 boxes of 0.1m x 0.2m x 0.3m of weight 0.1kg and
1 box of 0.4m x 0.4m x 0.4 of weight 0.5kg this equates to two piece lines as
follows:
PieceLine1: 0.1m x 0.2m x 0.3m, weight 0.1kg, number of units=5
PieceLine2: 0.4m x 0.4m x 0.4m, weight 0.5kg, number of units=1
This element is used to identify all the pieces that should be grouped
together by the given reference. The list of sequence numbers is included
(one sequenceNumber element per piece) with a single pieceReference element.
The XML Instance Representation table above shows the schema component's content as an XML instance.
The minimum and maximum occurrence of elements and attributes are provided in square brackets, e.g. [0..1].
Model group information are shown in gray, e.g. Start Choice ... End Choice.
For type derivations, the elements and attributes that have been added to or changed from the base type's content are shown in bold.
If an element/attribute has a fixed value, the fixed value is shown in green, e.g. country="Australia".
Otherwise, the type of the element/attribute is displayed.
If the element/attribute's type is in the schema, a link is provided to it.
For local simple type definitions, the constraints are displayed in angle brackets, e.g. <<pattern = [1-9][0-9]{3}>>.
If a local element/attribute has documentation, it will be displayed in a window that pops up when the question mark inside the attribute or next to the element is clicked, e.g. <postcode>.
Abstract(Applies to complex type definitions and element declarations). An abstract element or complex type cannot used to validate an element instance. If there is a reference to an abstract element, only element declarations that can substitute the abstract element can be used to validate the instance. For references to abstract type definitions, only derived types can be used.
Collapse Whitespace PolicyReplace tab, line feed, and carriage return characters with space character (Unicode character 32). Then, collapse contiguous sequences of space characters into single space character, and remove leading and trailing space characters.
Disallowed Substitutions(Applies to element declarations). If substitution is specified, then substitution group members cannot be used in place of the given element declaration to validate element instances. If derivation methods, e.g. extension, restriction, are specified, then the given element declaration will not validate element instances that have types derived from the element declaration's type using the specified derivation methods. Normally, element instances can override their declaration's type by specifying an xsi:type attribute.
Nillable(Applies to element declarations). If an element declaration is nillable, instances can use the xsi:nil attribute. The xsi:nil attribute is the boolean attribute, nil, from the http://www.w3.org/2001/XMLSchema-instance namespace. If an element instance has an xsi:nil attribute set to true, it can be left empty, even though its element declaration may have required content.
Prohibited Derivations(Applies to type definitions). Derivation methods that cannot be used to create sub-types from a given type definition.
Prohibited Substitutions(Applies to complex type definitions). Prevents sub-types that have been derived using the specified derivation methods from validating element instances in place of the given type definition.
Replace Whitespace PolicyReplace tab, line feed, and carriage return characters with space character (Unicode character 32).
Substitution GroupElements that are members of a substitution group can be used wherever the head element of the substitution group is referenced.
Substitution Group Exclusions(Applies to element declarations). Prohibits element declarations from nominating themselves as being able to substitute a given element declaration, if they have types that are derived from the original element's type using the specified derivation methods.
Target NamespaceThe target namespace identifies the namespace that components in this schema belongs to. If no target namespace is provided, then the schema components do not belong to any namespace.