INSTAT/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.


Conventions and definitions of data types

Diagram

Conventions and definitions of data types

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

Occurrences of elements and attributes are represented by:

  • "nothing" meaning one and one time only,

  • ? meaning zero or one time,

  • * meaning zero or more times,

  • + meaning one or more times.

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 finite-length sequence of decimal digits (#x30-#x39) with an optional leading sign; if the sign is omitted, + is assumed;

  • anyURI is finite-length character sequences, which result in strings which are legal URIs according to [RFC 2396], as amended by [RFC 2732];

  • decimal is represented by of 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.


Diagram

First part:
Details related to the envelope
Second part:
Details related to the declaration
Third part:
Details related to the item

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 flowCode;

  • The names of elements or attributes combining several names contain these names separated by an upper-case, for example statisticalValue for statistical value;

  • 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).

To make readable the diagram of INSTAT/XML, it is presented in three parts:

  • First part: Details related to the envelope.  The class diagram of the INSTAT message is the basis of INSTAT/XML.  INSTATEnvelope root class of the class diagram becomes INSTAT and Envelope first elements of INSTAT/XML.  The envelope contains an identification (envelopeId), a date and time of creation (DateTime), different parties involved in the exchange of the envelope, other information like acknowledgement request, software used, etc … 1 to n Intrastat declarations and the number of declarations contained in the envelope.

  • Second part: Details related to the declarations. Each declaration contains identification (declarationId), different elements defining it, 0 to n statistical items and the total number of items (totalNumberLines).

  • Third part: Details related to the items of a declaration. Each item contains identification (itemNumber) and its own elements.

The following diagram corresponds with the schema of INSTAT/XML in XSDL.


First part: Details related to the envelope


Second part: Details related to the declaration


Third part: Details related to the item


Back to conventions and definitions Back to diagram

Copyright © European Communities 2002