This XML Schema defines a job description format used to process a print job within PEAX and its toolset (Straatos, World Of Documents etc.).
It carries metadata about the job and is also used to generate job metadata for the print service provider.
<--
<xs:element name="language" type="xs:language">
<xs:annotation>
<xs:documentation>
The document language needed for controlling language-dependent post-processing.
Valid values shall be restricted to the following 2-letter language codes: de, fr, it and en.
Additional languages can be enabled as needed.
</xs:documentation>
</xs:annotation>
</xs:element>
-->
A part here means part of a document. It can also be called a sub-document. Example: there's an invoice (say 2 pages) and a form (say 1 page) that
the recipient can fill out and send in. Applications which can't (or don't want to) map this, just generate one part for the whole document.
This element contains the PEAX delivery metadata in XML form. The JSON equivalent is described at:
http://api-doc.peax.ch/#api-Delivery-deliver
Some of the metadata here is updated from the address lookup in the Partner Dictionary.
At the moment, only invoice and the generic document type are defined. More will be added later.
<-- Using PEAX delivery metadata's receiverPeaxId
<xs:element name="id" type="PEAXID">
<xs:annotation>
<xs:documentation>
The PEAX ID is usually inserted by the address validation.
</xs:documentation>
</xs:annotation>
</xs:element>
-->
The recipient metadata is mostly used for easy sorting by the print service provider and
for reference when doing forensics.
Interesting information related to this:
<a href="https://confluence.cip4.org/display/PUB/Common+Metadata+for+Document+Production+Workflow+ICS"> ICS - Common Metadata for Document Production Workflows by CIP4</a> as used in JDF (Job Definition Format).
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.