ANNEX 1: TECHNICAL REQUIREMENTS - Europatrade.ec.europa.eu/doclib/docs/2015/july/tradoc_153618.pdfA detailed presentation of the technical requirements for datasets is available in:

1

ANNEX 1:

TECHNICAL REQUIREMENTS

Table of Contents 1. Introduction .................................................................................................................................... 2

1.1. The dataset ............................................................................................................................. 3 1.2. Typical delivery workflow ..................................................................................................... 3

2. LOT 1 Introduction ......................................................................................................................... 4 3. LOT 1 Deliverables ........................................................................................................................ 4

3.1. Contents ................................................................................................................................. 4 3.2. Files and file format ............................................................................................................... 4

4. LOT 1 Dataset ................................................................................................................................ 5 4.1. Principle ................................................................................................................................. 5 4.2. Zip file .................................................................................................................................... 5 4.3. Contents ................................................................................................................................. 5

5. LOT 1 XML .................................................................................................................................... 8 5.1. EU Import Requirements ....................................................................................................... 8 5.2. EU Document Mapping ....................................................................................................... 11 5.3. MS Document Mapping ....................................................................................................... 12

6. LOT 2 Introduction ....................................................................................................................... 13 7. LOT 2 Deliverables ...................................................................................................................... 13

7.1. Contents ............................................................................................................................... 13 7.2. Files and file format ............................................................................................................. 13

8. LOT 2 Dataset .............................................................................................................................. 13 8.1. Principle ............................................................................................................................... 14 8.2. Zip file .................................................................................................................................. 14 8.3. Contents ............................................................................................................................... 14

9. LOT 2 XML .................................................................................................................................. 16 9.1. Schema ................................................................................................................................. 16 9.2. Examples .............................................................................................................................. 17

10. HTML Files - Introduction ....................................................................................................... 18 11. HTML Files - General constraints ............................................................................................ 18 12. HTML Files - Contents ............................................................................................................ 18 13. HTML Files - Latest revision date ........................................................................................... 18 14. HTML Files - Links ................................................................................................................ 18

14.1. External Links ...................................................................................................................... 19 14.2. Links to auxiliary documents ............................................................................................... 19 14.3. References to Official Journal .............................................................................................. 19 14.4. References to consolidated legislation/CELEX. .................................................................. 19

15. HTML Files - CSS ................................................................................................................... 20 15.1. Style constraints ................................................................................................................... 20 15.2. Example of CSS file ............................................................................................................. 21 15.3. Example of HTML file ........................................................................................................ 21

2

1. INTRODUCTION

The present annex lists the technical requirements applicable to the contractor's deliverables.

It is organized according to the following structure:

Annex 1A: technical requirements for Lot1: EU and Member States' Import requirements

Annex 1B: technical requirements for Lot2: Internal taxation

Annex 1C: technical requirements for HTML files

Annex 1D: schema definitions

The Import Requirements and Internal taxation are available upon a product specific search in the 'My

export' section under the tab 'Requirements' of the EH website : http://exporthelp.europa.eu

Although great care has been given to the definition of the technical requirements, DG Trade reserves

the right to make changes to them during the contracting period. An updated version of the technical

requirements will be provided, as appropriate. The occurrence of such modifications will in no case

modify the price.

http://exporthelp.europa.eu/

3

1.1. The dataset

All data pertaining to a given MS country or EU must be delivered as a single zip file, called "dataset".

It is the smallest entity considered for updating the information.

The naming convention for the zip file is: <aa><ss>_<cc><yy>_<rr>v<vvv>

where

<aa> = application (always "eh" for Export Helpdesk)

<ss>= section ("it" for internal taxes) or ("ir" for import requirements)

<cc>= "eu" or ISO-2A country code of concerned Member State

<yy>= contract year to which the dataset is related (e.g. a dataset delivered in December

2013 for example might apply to contractual obligations related to year 2014 in which

case yy must be set to '14')

<rr>= revision number (also a contractual notion : it is checked against the number of

yearly updates the contractor has committed to)

<vvv>= a numeric version number (3 digits) for the update (no contractual semantics

attached here)

Examples:

Lot 1

o "ehir_eu09_01v004.zip" is the 1rst

revision for import requirements at EU level in

2009 (version 4)

o "ehir_fr09_02v004.zip" is the 2nd

revision for import requirements of France in 2009

(version 4).

Lot 2

o "ehit_fr09_02v004.zip" is the 2nd

revision for internal taxes of France in 2009 (version

4).

A detailed presentation of the technical requirements for datasets is available in:

Annex 1A: technical requirements for Lot1: EU and Member States' Import requirements

Annex 1B: technical requirements for Lot2: Internal taxation

1.2. Typical delivery workflow

A typical workflow leading to successful dataset delivery could be:

the data provider uploads a dataset to a protected area,

the system checks the dataset, validates if it is compliant, and provides feedback with the

reason(s) for failure if applicable,

the contractor fixes the dataset and attempts a new upload,

if the system checks are successful, the dataset is then available in the draft area,

the contractor previews the dataset in the draft area,

if satisfied, the contractor submits the dataset to the Commission (the dataset is then

transferred in submitted area)

the content administrator at the Commission reviews the dataset

the content administrator accepts the dataset

the dataset is now in the production area and visible by the general public.

4

ANNEX 1A

LOT1: EU and Member States' Import Requirements

Technical requirements

2. LOT 1 INTRODUCTION

The present annex lists the technical requirements applicable to the contractor's deliverables for Lot1:

EU and Member States' Import Requirements.

3. LOT 1 DELIVERABLES

3.1. Contents

According to the Terms of References for Lot1, the contractor shall provide the following information

as summarized in the next table.

EU level MS level

Overview document Overview

General Requirement documents General Requirement documents (if any)

Specific Requirement documents Specific Requirement documents

Information linking documents and

products of Combined Nomenclature

(CN) taking into account:

- origin countries

- exceptions

Information for Mapping between

document identifiers and files including

document labels (titles)

Information for Mapping between document

identifiers and files

3.2. Files and file format

The documents related to overview, general and specific requirements must be provided as individual

html files and must be identified by a unique document identifier.

The information linking these documents and the products (taking into account the possible exceptions

and specificities related to the origin country) must be provided as XML file using the document

identifier as references to the overview, general and specific requirement documents.

At EU level, the information concerning the Mapping between the document identifiers and files must

be provided as XML file. This XML file will also contain the Requirement labels (or document titles)

in several the languages (English, Spanish, French and Portuguese).

At MS level, the information concerning the Mapping between the document identifiers and files must

be provided as a XML file.

5

The following section details the required packaging into a structured "dataset" and the file naming

conventions to be used for deliverables related to Lot1: Import Requirements.

4. LOT 1 DATASET

4.1. Principle

All data pertaining to EU or a given MS must be packaged and delivered as a single zip file, called the

"dataset", that will be used for updating the Export Helpdesk database.

Therefore, the information required for Lot 1 (Import Requirements) will be delivered as follows:

one dataset for EU

one dataset for each of the 28 MS (28 datasets)

4.2. Zip file

The zip file contains a folder named "eu" or the ISO2-alpha MS code (lowercase)

This folder contains:

the "Import Requirements" xml file (only at EU level)

the "Document Mapping" xml file

one subfolder "main" containing the English version of:

o the overview document

o the general requirement documents

o the specific requirement documents

one subfolder "main_<lang>1" for the translations into Spanish, French and Portuguese of:

o the overview document

o the general requirement documents

one subfolder "auxi" for all auxiliary documents referenced by the overview, general and

specific requirement files

4.3. Contents

4.3.1. Import Requirements, EU and MS Document Mapping

Information related to Import Requirements, EU and MS Document Mapping must be stored into

XML files.

General rules

Each XML file will follow the following rules:

UTF-8 encoding

conventions for file names:

o only lowercase characters,

o first character is alphabetical

o no special characters or spaces

o maximum length of 256 characters

file extension: ".xml"

1 where <lang> is "es", "fr", "pt"

6

UNIX files

The XML file must comply with the W3C XML schemas provided in chapter 5.

File naming conventions

The naming convention for the xml files is: <aa><ss>_<ttt>_<cc><yy>_<rr> v<vvv>

where


<ss>= section ("ir" for import requirements)

<ttt>=information type

o "req" for requirements

o "map" for mapping information

<cc>= "eu" or ISO-2A country code of concerned Member State

<yy>= contract year to which the dataset is related

<rr>= revision number

<vvv> = a numeric version number for the update (no contractual semantics attached

here)

Examples:

"ehir_req_eu09_01v004.xml": 1rst

revision for import requirement information at EU level in 2009

(version 004).

"ehir_map_eu09_01v004.xml": 1rst

revision for document mapping at EU level in 2009.

"ehir_map_fr09_02v004".xml": 2nd

revision for document mapping for France in 2009.

4.3.2. Overview, general, specific requirements and recent/upcoming changes

Information related to the overview, general, specific requirements and recent/upcoming changes are

stored into html files located in the "main" folder.

General rules

This information must be provided in individual html files compliant with the text formatting

instructions detailed in Annex IC.


For these files, the filename will be built with the following rules:

File type EU level MS level

overview ovr_eu_<version>.htm ovr_<ms>_<version>.htm

general requirement gen_<reqcode>_eu_<version>.htm gen_<reqcode>_<ms>_<version>.htm

specific requirement req_<reqcode>_eu_<version>.htm req_<reqcode>_<ms>_<version>.htm

recent changes

(requirements)

ir_rct_<date>.htm -

upcoming changes

(requirements)

ir_upc_<date>.htm -

recent changes (taxes) it_rct_<date>.htm -

upcoming changes

(taxes)

it_upc_<date>.htm -

7

where

<reqcode> unique requirement identifier 2

<ms> ISO2A Member State country code

<version> provider version

<date> date in format YYYYMMDD

Filenames for translated documents will be built with the following rules

File type EU level

overview ovr_eu_<version>_<lang>.htm

general requirement gen_<reqcode>_eu_<version>_<lang>.htm

where <lang> is "es", "fr" or "pt"

Derogations to this rule must be justified and agreed by DG Trade.

Note that the "version" part of the filename is under the exclusive control of the information provider.

It will not be used directly by the Export Helpdesk application and is only present for communication

purposes between DG Trade and the information provider.

In the case of recent and upcoming changes the contractor can specify more than one file per type

(requirements recent changes, requirements upcoming changes, taxes recent changes and taxes

upcoming changes). If more than one file per type is present, the last file (based on the file name date)

will be used.

4.3.3. Auxiliary files

"Auxiliary" files (i.e. those located in the "auxi" folder") concern all the other files referenced by the

main html files or by other auxiliary html files.

HTML files

The auxiliary html files will be compliant with the general constraints and text formatting instructions

detailed in Annex Ic.

Other files

For these auxiliary files, there are no specific naming conventions except the following ones:





o UNIX files

Note for administrative forms

In the cases where a form is to be filled by the importer, a bitmap image of this form (GIF/TIFF

format) is required. It must be included into a PDF file.

In order to achieve a readable and clear picture of the required forms on the screen, it may be

necessary to retype the original forms and transform them into bitmap graphics.

2 mnemonic alpha-numeric code based on the requirement label

8

These bitmap images should not have a width exceeding 21 cm (DIN A4). The forms should not be

filled in. If the form is not available in English, the fields need to be numbered and their content

translated and explained in the explanatory text for the requirement. The English translation should

include all details given in the original form.

5. LOT 1 XML

5.1. EU Import Requirements

5.1.1. Schema

See documents in annex 1D – schema definitions:

importRequirements.xsd

types.xsd

5.1.2. Case studies

Theses case studies are taken from the actual EH Import requirements database for illustrating the

different possibilities of the XML schema linking specific requirement to product codes taking into

account exceptions and origin list.

The following cases will be considered in the next sections:

requirement applicable to a (list of) product code(s) for all origin countries without exceptions

requirement applicable to a (list of) product code(s) for all origin countries with exceptions

requirement applicable to a (list of) product code(s) for all origin countries except those listed

in the origin list

requirement applicable to a (list of) product code(s) only for origin countries listed in the

origin list

Case 1:

The requirement related to "Eco-label for light bulbs" identified by the code "ecobulbs" is applicable

to the products (85392192, 85392198, 85392210, 85392290, 85392992, 85392998, 85393110,

85393190, and 85393900) for all origin countries without exceptions

Extract of XML file:

<specificRequirement docId="ecobulbs"> <productList> <product cnCode="85392192"/> <product cnCode="85392198"/> <product cnCode="85392210"/> <product cnCode="85392290"/> <product cnCode="85392992"/> <product cnCode="85392998"/> <product cnCode="85393110"/> <product cnCode="85393190"/> <product cnCode="85393900"/> </productList> </specificRequirement>

Case 2:

9

The requirement related to "Technical standards for meters" identified by the code "stdmet" is

applicable to the products (90261021, 90261029, 90261081, 90261089, 90281000, 90282000,

90283011, 90283019, and 90289010) for all origin countries, with an exception for the product

90291000.


<specificRequirement docId="stdmet"> <productList> <product cnCode="90261021"/> <product cnCode="90261029"/> <product cnCode="90261081"/> <product cnCode="90261089"/> <product cnCode="90281000"/> <product cnCode="90282000"/> <product cnCode="90283011"/> <product cnCode="90283019"/> <product cnCode="90289010"/> <product cnCode="90291000"> <exceptions>Only required for taximeters</exceptions> </product> </productList> </specificRequirement>

Case 3:

The requirement related to "Prior community surveillance for iron and steel products" identified by the

code "ecscsrv" is applicable to the product (72081000) for all origin countries (by convention: 'zz')

except for those included into the origin list (kz, ru).


<specificRequirement docId="ecscsrv"> <productList> …. <product cnCode="72081000"> <originList> <origin> <originCode>zz</originCode> <excluded>0</excluded> </origin> <origin> <originCode>kz</originCode> <excluded>1</excluded> </origin> <origin> <originCode>ru</originCode> <excluded>1</excluded> </origin> </originList> </product> … </productList> </specificRequirement>

Case 4:

The requirement related to "Double-checking system with quotas for iron and steel products"

identified by the code "ecsc2cwq" is applicable to the product (72081000) only for those origin

countries included into the origin list (ru).

10


<specificRequirement docId=" ecsc2cwq "> <productList> …. <product cnCode="72081000"> <originList> <origin> <originCode>ru</originCode> <excluded>0</excluded> </origin> </originList> </product> … </productList> </specificRequirement>

11

5.2. EU Document Mapping

5.2.1. Schema


euMappingList.xsd

types.xsd

5.2.2. Example

<?xml version="1.0" encoding="UTF-8"?> <euMappingList xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="ehir_map_eu.xsd"> <updateInfo countryId="eu" countryLabel="European Union" year="2006" revision="01" date="2006-04-03" updateFilename="file name" providerId="provider_1" providerName="provider_1" providerEmail="[email protected]" version="v001"/>  <euMapping> <docId>overview</docId> <docType>o</docType> <docLabelList> <docLabel lang="EN">Overview of Import Procedures</docLabel> <docLabel lang="ES">Sintesis de los procedimientos de importación</docLabel> <docLabel lang="FR">Vue d'ensemble des procédures d'importation</docLabel> <docLabel lang="PT">Generalidades sobre os procedimentos de importação</docLabel> </docLabelList> <docFileName>ovr_eu_010_0407.htm</docFileName> </euMapping>  <euMapping> <docId>packlist</docId> <docType>g</docType> <docLabelList> <docLabel lang="EN">Packing list</docLabel> <docLabel lang="ES">Lista de carga</docLabel> <docLabel lang="FR">Liste de colisage</docLabel> <docLabel lang="PT">Lista do material de acondicionamento</docLabel> </docLabelList> <docFileName>gen_packlist_eu_010_0407.htm</docFileName> </euMapping> <euMapping> <docId>sad</docId> <docType>g</docType> <docLabelList> <docLabel lang="EN">Customs Import Declaration (SAD)</docLabel> <docLabel lang="ES">Declaración Unica de Aduanas (DUA) </docLabel> <docLabel lang="FR">Déclaration douanière d'importation (DAU)</docLabel> <docLabel lang="PT">Declaração de importação aduaneira</docLabel> </docLabelList> <docFileName>gen_sad_eu_010_0407.htm</docFileName> </euMapping>  <euMapping> <docId>chedange</docId> <docType>s</docType> <!— docOrder 0 to 5 : 0 is at the top of the list and 5 at the bottom --> <docOrder>0</docOrder> <docLabelList> <docLabel lang="EN">Control of trade in dangerous chemicals</docLabel> <docLabel lang="ES">Control del comercio de productos químicos peligrosos</docLabel> <docLabel lang="FR">Contrôle du commerce des produits chimiques dangereux</docLabel> <docLabel lang="PT">Controlo do comércio de produtos químicos perigosos</docLabel>

12

</docLabelList> <docFileName>req_chedange_eu_010_0407.htm</docFileName> </euMapping> <euMapping> <docId>chedeter</docId> <docType>s</docType> <!— docOrder 0 to 5 : 0 is at the top of the list and 5 at the bottom --> <docOrder>0</docOrder> <docLabelList> <docLabel lang="EN">Marketing requirements for detergents</docLabel> <docLabel lang="ES">Requisitos de marketing para detergentes</docLabel> <docLabel lang="FR">Prescriptions de marketing pour les détergents</docLabel> <docLabel lang="PT">Requisitos para a comercialização de detergentes</docLabel> </docLabelList> <docFileName>req_chedeter_eu_010_0506.htm</docFileName> </euMapping> <euMapping> <docId>chefert</docId> <docType>s</docType> <!— docOrder 0 to 5 : 0 is at the top of the list and 5 at the bottom --> <docOrder>0</docOrder> <docLabelList> <docLabel lang="EN">Marketing requirements for EC fertilisers</docLabel> <docLabel lang="ES">Requisitos de marketing para fertilizantes de la CE</docLabel> <docLabel lang="FR">Prescriptions de marketing pour les fertilisants de l'UE</docLabel> <docLabel lang="PT">Requisitos para a comercialização de fertilizantes da CE</docLabel> </docLabelList> <docFileName>req_chefert_eu_010_0506.htm</docFileName> </euMapping> </euMappingList>

Regarding the 'docFileName', if the page needs to be displayed in another language, a simple

transformation is applied:

For Spanish, the file " req_chefert_eu_010_0506_es.htm" is taken from the "main_es" folder.

For French, the file " req_chefert_eu_010_0506_fr.htm is" taken from the "main_fr"

folder.

For Portuguese, the file " req_chefert_eu_010_0506_pt.htm" is taken from the

"main_pt" folder.

5.3. MS Document Mapping

5.3.1. Schema


msMappingList.xsd

types.xsd

13

ANNEX 1B

LOT2: Internal Taxation

Technical requirements

6. LOT 2 INTRODUCTION

The present annex lists the technical requirements applicable to the contractor's deliverables for Lot 2:

Internal Taxation.

7. LOT 2 DELIVERABLES

7.1. Contents

According to the Terms of References for Lot 2, the contractor shall provide the following information

as summarized in the next table. All information on MS internal taxes needs to provided in English,

French, Spanish, Portuguese.

EU level MS level

VAT Excise VAT Excise

overview overview overview overview

VAT information for

products of Combined

Nomenclature (CN):

- rate

- reference to additional

note (when required)

Excise and other internal

duties information for

products of Combined

Nomenclature (CN):

- rate

- reference to additional

note (when required)

additional notes documents additional notes documents

7.2. Files and file format

The overview documents must be provided as individual html files.

The VAT and Excise information must be provided as XML files containing the appropriate rates for

every product with references to the overview and additional note files.

The texts for the additional notes possibly attached to the VAT and/or Excise taxes must also be

provided as individual html files.

8. LOT 2 DATASET

14

8.1. Principle

All data pertaining to a given EU Member State or EU must be packaged and delivered as a single zip

file, called a "dataset", that will be used for updating the EH database.

Therefore, the information required for Lot 2 (Internal Taxation) will be delivered as follows:

one dataset for EU

one dataset for each of the 28 MS (28 datasets)

8.2. Zip file

The zip file contains a folder named "eu" or the ISO2-alpha MS code (lowercase)

This folder contains:

VAT xml file

Excise xml file

one subfolder "main" containing the English version of:

o VAT and Excise overview documents

o VAT or Excise additional notes referenced in the xml documents

one subfolder "main_<lang>3" for the translations into Spanish, French and Portuguese of

the overview documents

one subfolder "auxi" for all auxiliary documents referenced by the overview files

8.3. Contents

8.3.1. VAT and Excise information

VAT and Excise information will be provided as two separate XML files.

General rules

Each XML file will follow the following rules:

UTF-8 encoding






file extension: ".xml"

UNIX file

The XML file must comply with the W3C XML schemas provided in the section 4.


The naming convention for the xml files is: <aa><ss>_<ttt>_<cc><yy>_<rr> v<vvv>

where

3 where <lang> is "es", "fr", "pt"

15


<ss> = section ("it" for internal taxes)

<ttt> = information type

o "vat" for VAT information

o "exc" for excise information

<cc> = "eu" or ISO-2A country code of concerned Member State

<yy> = contract year to which the dataset is related

<rr> = revision number

<vvv> = a numeric version number for the update (no contractual semantics attached

here)

Examples:

"ehit_vat_fr09_01v004.xml": 1rst

revision for vat information for France in 2012 (version 4).

"ehit_exc_fr09_02v004.xml": 2nd

revision for excise information for France in 2012 (version 4).

8.3.2. Overview and additional notes

Information related the overview and the additional notes possibly associated to vat, excise and other

internal duties will be provided as html files located into the "main" folder.

General rules

The overview texts (VAT and Excises) for EU and MS must be provided as individual html files

compliant with the text formatting instructions detailed in Annex 1C.

The texts for the additional notes possibly attached to the VAT and/or Excise taxes must also be

provided as individual html files, compliant with the text formatting instructions detailed in Annex

1C.


For these files, the filename will be built with the following rules:

File type EU level MS level

overview ovr_<type>_eu_<version>.htm ovr_<type>_<ms>_<version>.htm

notes Not applicable note_<type>_<ms>_<noteid>_<version>.htm

where

<type> type of taxes ("vat" for VAT, "exc" for excises)

<ms> ISO2A Member State country code

<noteid> note unique identifier

<version> provider version

Filenames for translated documents will be built with the following rules:

File type EU level

overview ovr_eu_<version>_<lang>.htm

where <lang> is "es", "fr" or "pt"

Derogations to this rule must be justified and agreed by DG Trade.

16

Note that the "version" part of the filename is under the exclusive control of the information provider.

It will not be used directly by the EH application and is only present for communication purposes

between DG Trade and the information provider.

8.3.3. Auxiliary files

"Auxiliary" files (i.e. those located in the "auxi" folder") concerns all the other files referenced by the

main files or by other auxiliary html files.

HTML files

The auxiliary html files will be compliant with the general constraints and text formatting instructions

detailed in Annex 1C.

For these files, there are no specific naming conventions.

Other files

For these auxiliary files, there are no specific naming conventions except the following ones:





o Unix files

Note for administrative forms

In case a form is to be filled by the importer, a bitmap image of this form (GIF/TIFF format) is

required. It is proposed to include it into a PDF file.

In order to achieve a readable and clear picture of the required forms on the screen, it may be

necessary to retype the original forms and transform them into bitmap graphics.

The general requirements are that these bitmap images should not have a width exceeding 21 cm (DIN

A4). The forms should not be filled in. If the form is not available in English, the fields need to be

numbered and their content translated and explained in the explanatory text for the requirement. The

English translation should include all details given in the original form.

9. LOT 2 XML

9.1. Schema


internalTaxes.xsd

types.xsd

17

9.2. Examples

9.2.1. EU

<?xml version="1.0" encoding="UTF-8"?> <internalTaxes xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="ehit.xsd"> <updateInfo countryId="eu" countryLabel="European Union" year="2009" revision="03" date="2009-04-01" updateFilename="ehit_vat_eu09_03v002.xml" providerId="xxx" providerName="xxx" providerEmail="xxx" version="002"/> <taxType>VAT</taxType> <modifSummary></modifSummary> <overviewFile>ovr_vat_eu_0612.htm</overviewFile> </internalTaxes>

9.2.2. MS

<?xml version="1.0" encoding="UTF-8"?> <internalTaxes xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="ehit.xsd"> <updateInfo countryId="it" countryLabel="Italy" year="2009" revision="03" date="2009-04-01" updateFilename="ehit_vat_it09_03v002.xml" providerId="xxx" providerName="xxx" providerEmail="xxx" version="002"/> <taxType>VAT</taxType> <modifSummary></modifSummary> <overviewFile>ovr_vat_it_0612.htm</overviewFile> <taxList> <tax cnCode="01011010"> <taxRate>10%</taxRate> </tax> <tax cnCode="01011090"> <taxRate>10%</taxRate> </tax> … <tax cnCode="97060000"> <taxRate>20%</taxRate> <noteFile>note_vat_it_00000052_0612.htm</noteFile> </tax> </taxList> </internalTaxes>

Regarding the tags "noteFile"",and "overviewFile", if the page needs to be displayed in another

language, a simple transformation is applied:

For Spanish, the file " note_vat_at_001_0704_es.htm" is taken from the "main_es" folder.

For French, the file "note_vat_at_001_0704_fr.htm" is taken from the "main_fr" folder.

For Portuguese, the file "note_vat_at_001_0704_pt.htm" is taken from the "main_pt" folder.

For Spanish, the file "ovr_vat_it_0612_es.htm" is taken from the "main_es" folder.

For French, the file "ovr_vat_it_0612_fr.htm" is taken from the "main_fr" folder.

For Portuguese, the file "ovr_vat_it_0612_pt.htm" is taken from the "main_pt" folder.

18

ANNEX 1C

Technical requirements for HTML files

10. HTML FILES - INTRODUCTION

The present annex lists the technical requirements applicable to the contractor's deliverables for

HTML files (Lot1 and Lot2).

11. HTML FILES - GENERAL CONSTRAINTS

Each overview or general/specific requirement corresponds to one individual HTML file with the

following characteristics:

XHTML-compliant

UTF-8 encoding


o lowercase characters,


o without special characters or spaces


file extension: ".htm"

UNIX files

12. HTML FILES - CONTENTS

The contents of these files will be displayed within the HTML pages dynamically generated by the EH

web site.

In particular, the document title will be provided by the "docLabel" element from the appropriate xml

file (except for additional notes of Lot2).

For these reasons, the delivered HTML files will contain only the part normally enclosed by the

"body" tag. Therefore, the use of <html>, <head> and <body> tags is forbidden.

13. HTML FILES - LATEST REVISION DATE

All HTML files – except the additional notes for the specific internal taxes - must contain the "latest

revision date" on top of the file.

The format to be used is as follows: Latest Revision Date (dd/mm/yyyy): 01/03/52015.

14. HTML FILES - LINKS

The links created in a document shall respect the following rules.

19

14.1. External Links

If the link points to another web site, the target must be set to "new_window".

Example: <a href=”http://ec.europa.eu/trade/” target=” new_window”>DG Trade Website</a>

14.2. Links to auxiliary documents

If the link points to an administrative form (e.g. PDF files), the target must be set to "new_form".

Example: <a href="../auxi/eu_trdtx_import_licence.pdf" target="new_form">

14.3. References to Official Journal

In order to be able to generate on-the-fly links to the appropriate pages of the Official Journal web site,

the references to the Official Journal in the English version of the HTML files will be formatted as

follows:

(OJ <space> S-NNN <space> dd/mm/yyyy)

where

S: publication series (e.g. L)

NNN: publication number

dd: publication day

mm: publication month

yyyy: publication year

Example: (OJ L-275 08/11/2004)

For information, references to the Official Journal need to be given in the three other linguistic

versions (Spanish, French, and Portuguese).

Examples are:

Spanish: DO L275 08/11/2004

French: JO L275 08/11/2004

Portuguese: JO L275 08/11/2004

14.4. References to consolidated legislation/CELEX.

For ease of reference for the Export Helpdesk user, references to the consolidated legislation (CELEX)

will be included in the explanatory texts, where relevant. Inclusion of these references will be

proposed by the contractor. If accepted by DG Trade, they would be included in the update of the

explanatory texts.

References to CELEX will be formatted as follows:

(CELEX<year><type><number of the act>)

Where

3: three for secondary legislation

<year>: four digits

<type>: R for Regulation or L for Directive or D for Decision)

<number of the act>: four digits

Example: The CELEX number of Directive 2006/66/EC of the European Parliament and of the

Council will be CELEX32006L0066 (3 + 2006 + L + 0066).

The Celex number will be inserted at the end of the legal reference between brackets.

20

Example : Directive 2006/66/EC of the European Parliament and of the Council of 6 September 2006

on batteries and accumulators and waste batteries and accumulators and repealing Directive

91/157/EEC (OJ L-266 26/09/2006) (CELEX 32006L0066)

15. HTML FILES - CSS

15.1. Style constraints

The EH website uses a CSS style sheet to display the html documents.

The contractor must use the CSS predefined classes described below. The use of inline styles is

forbidden.

The titles can be of level 1, 2 or 3. The titles must be in a paragraph tag with the class= "eh_Title1" or

"class=eh_Title2" or class="eh_Title3": title level 1 title level 2 title level 3

Bullet lists can be ordered or unordered. The title of the bullet list must be placed in a paragraph tag

with the class="eh_ListTitle": Bullet list unordered title

To create a normal block text use class="eh_Normal": paragraph

To add bold text in the document use the class="eh_Bold". bold text

To add italic text use the class="eh_Italic": italic text

To indent text there are three classes available class=eh_Indented1,2,3:

indent text level 1



For the tables use class="eh_TableTitle" for the <th> tags and class="eh_TableContent" for the <td>

tags: <th class="eh_TableTitle">title</th> <td width="50%" class="eh_TableContent">content</td>

The title of a footnote should use class="eh_Footnote": footnote text

For the list of abbreviations use: Abbreviations <ul> <li class=eh_Abbreviation> abbreviation</li> <li class=eh_Abbreviation> abbreviation</li> </ul>

21

For the table of contents (used in the overview.html document) use: Table of contents <ul> <li class="eh_TocItem">item</li> <li class="eh_TocItem">item</li> </ul>

For the changes title (if present in the overview.html document) use the class="eh_ChangesTitle": changes

For Official Journal references use the class="eh_OJReference": <div class="eh_ OJReference ">(OJ L-175 08/11/2004)</div>

For references to legal texts use the class="eh_LegalReference": <div class="eh_ LegalReference ">Moniteur belge 04/04/2002</div>

15.2. Example of CSS file

See document in annex 1D: eh_styles.css

15.3. Example of HTML file

See document in annex 1D: example.html

Documents

ANNEX 1: TECHNICAL REQUIREMENTS - Europatrade.ec.europa.eu/doclib/docs/2015/july/tradoc_153618.pdfA detailed presentation of the technical requirements for datasets is available in: