INSRES/XML Diagram

This diagram describes the structure of the elements and attributes of the message definition.
By defining what elements may be found within what elements, a structure for the message definition is established. This structure can be thought of as a tree where the "root" is the encompassing element and its branches are the elements and attributes that may be contained within it (as defined by the content model). In turn each branch may have branches defined by their content model.

The following example gives the conventions used to represent the elements, attributes, types and occurrences.

• "nothing" meaning one and one time only,
• ? meaning zero or one time,
• * meaning zero or more times,
• + meaning one or more times,
• {i,j} meaning i to j times (XSD only); for example, this symbol appears on the diagram for "i" and "j" equal to 2.

Elements contain other element(s) or like attributes, they can have the following types:

• string data type represents character strings in XML;
• boolean data type represents the set of literals {true, false}
• date is represented by CCYY-MM-DD where CC represents the century, YY the year, MM the month and DD the day [ISO 8601];
• time is represented by hh:mm:ss where hh, mm, ss represent hour, minute and second respectively [ISO 8601];
• integer is represented by a finte-lenght sequence of decimal digits (#x30-#x39) with an optional leading sign; if the sign is omitted, + is assumed;
• any URI is finite-length character sequences, which result in strings which are legal URIs according to [RFC 2732];
• decimal is represented by a finite-length sequence of decimal digits  (#x30-#x39) separated by a decimal indicator; an optional leading sign is allowed; if the sign is omitted, + is assumed.

The following convention is used:

• Element containing child elements has its name beginning by an upper-case, for example Envelope;
• Element containing character data and attributes have their names beginning by a lower-case, for example date;
• The names of elements or attributes combining several names contain these names separated by an upper-case, for example actionCode for action code;
• Acronyms are in upper-case, for example INSTAT or PSI; INSTAT is the acronym referring to the Intrastat declaration, PSI is the acronym for Party responsible for providing statistical information in the Intrastat system;
• Id is the abbreviation of Identification, for example envelopeId for envelopeIdentification (identification of the envelope);
• r is the abbreviation of received, for example rTotalInvoicedAmount for receivedTotalInvoicedAmount (Total invoiced amount of goods, for the received Intrastat declaration).

To make the diagram of INSRES/XML readable, it is presented in two parts:

• First part: Details related to the INSRES envelope. The class diagram of the INRES message is the basis of INSRES/XML. INSRESEnvelope root class of the class diagram becomes INSRES and Envelope first elements of INRES/XML. The envelope contains an identification (envelopeId), a date and time of preparation (DateTime), parties: -sender and receiver involved in the exchange of the envelope, test indicator and information related to the INSTAT envelope;
• Second part: Details related to the received Intrastat declarations. The following diagram corresponds with the schema of INSRES/XML in XSDL.