Technical requirements

Transcription

1 ANNEX 1: TECHNICAL REQUIREMENTS Technical requirements 1. Introduction Overview of the import formalities section of the market access database Architecture The dataset The public web site The administration web site Tests performed on the submit of a dataset The database Dataset description Dataset structure XML file Introductory texts Image files XML schema Schema Schema documentation Inclusions and exclusions ModifSummary element Text formatting instructions General constraints Document title of general/specific requirements Links CSS classes CSS style sheet Example XML file Example file Display of example file in MADB Example overview file (Indonesia) Example overview file Display of the example file in MADB (Sample of the Import Overview, Indonesia) List of general and specific requirement documents... 66

2 1. INTRODUCTION The present annex lists the technical requirements applicable to the contractor's deliverables. The document also contains an overview of the export formalities section of the Market Access database and a description of the workflow of the delivery process. Although great care has been given to the definition of the present technical requirements, DG Trade reserves the right to bring changes to them. In that case, an updated version of the technical requirements would be provided shortly after the award of the contract. 2. OVERVIEW OF THE IMPORT FORMALITIES SECTION OF THE MARKET ACCESS DATABASE 2.1. Architecture The contractor delivers a separate file (called "dataset") for each country. The dataset is uploaded to an administration web site hosted by DG Trade. The dataset undergoes an automated quality check and a human quality check performed by a Commission official before being published as illustrated in the figure below. Decision to publish Country dataset The system is designed to support any number of contractors The dataset All data pertaining to a given country must be delivered as a single zip file, called the country dataset or dataset The public web site The URL of the public web site is The web site supports anonymous access for users connecting through a proxy located in EU member states or in candidate countries. The public web site has the following functionalities: 2

3 search the database by country and by product (HS code or keyword), provide an overview of the import procedures and formalities for a given country provide the list of applicable procedures and formalities for given country and product code, provide a detailed explanation of import formalities/procedures, Here is an example of an overview of import procedures and formalities: 3

4 Here is an example of a list of applicable import formalities and procedures: Here is an example of a detailed explanation of an import formality: 2.4. The administration web site Introduction The delivery of zip files by contractors is orchestrated with the help of the dedicated administration web site. Access to the administration web site is restricted to contractors and Commission officials. DG Trade is prepared to open access to this web site for interested tenderers upon request. Such an access would enable them to upload test datasets Users The users of the administration web site are the contractor and the content administrator. The content administrator is the Commission official in charge of controlling the quality of datasets and deciding when to publish them. 4

5 Dataset lifecycle and areas Each dataset has a lifecycle and transits through various "areas : Area Description draft A dataset uploaded by the contractor arrives in the draft area. It is visible by the contractor, but not by the general public. This area is considered as the "contractor's sandbox". The contractor previews the dataset he has uploaded in this area before submitting it to the content administrator. test production archive A dataset lands in this area when submitted by the contractor to the content administrator and if all submit tests performed by the system are validated. Datasets in the test area are analysed by the content administrator in order to move them to the production area. When arriving in the production area, the dataset becomes visible by the general public. When a dataset in production is replaced by a new version, it is moved to an archive area Typical delivery workflow A typical workflow leading to successful dataset delivery could be: the data provider attempts to upload a dataset, the admin web site checks the dataset (automated checking), realizes it is not compliant and provides a feedback with the reason(s) for failure, the contractor fixes the dataset and attempts a new upload, this time the upload is successful and 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, web site checks the dataset (automated checking) with some additional tests, if validated the dataset is then transferred in test area the content administrator at the Commission checks the dataset (human checking) the content administrator moves the dataset to production the dataset is now in the production area and visible by the general public. 5

6 Main functionalities Home page The home page of the administration web page is the following: Dataset upload The upload consists in transferring a dataset file. 6

7 View update status / submit The "View Update status / submit " provides a status for each country. In the screenshot below, we see for example that for the United States, we have already a dataset in production (MAAT-US07-02v001), but that a new update (MAAT-US08-01v001) has been submitted and is waiting to be moved by the content administrator to the production. Note: this screenshot depicts applied tariffs datasets but the principle is exactly the same for import formalities datasets Preview dataset This functionality allows the contractor to consult the datasets in draft area as if they would be displayed to the final user Tests performed on the submit of a dataset Check if the overview document is present Check if all general and specific documents are present Check if the external links are correct Check if the internal links are correct Check if the referenced images are present 2.6. The database The database is an Oracle database. 7

8 3. DATASET DESCRIPTION 3.1. Dataset structure Principle All data pertaining to a given country must be delivered as a single zip file, called the country dataset or dataset Naming The naming convention for the zip file is: AASS-CCYY-RRv999 where AA = application (always "MA" for Market Access) SS= section ("IF" for import formalities) CC= country code YY= contract year to which the dataset is related (!!!: a dataset delivered in December 2004 for example might apply to contractual obligations related to year 2005 in which case YY must be set to '05') RR= revision number. The revision is a contractual notion: it is checked against the number of yearly updates the contractor has committed to. A new revision number may be assigned to a dataset only if the content has been updated. 999= a numeric version number for the update (no contractual semantics attached here). The version number may be used freely by the contractor to reflect presentation or technical changes. Example: MAIF-AR10-02v004 is the 2 nd revision for applied tariffs of Argentina in Structure The zip file contains all the files of the dataset: the xml file the documents corresponding to introductory texts (overview, general requirements, specific requirements). the images An example of dataset content is given below: 8

9 Dataset validity date The date attribute of the update element in the XML schema has a very accurate definition: it is the latest date the contractor has checked the validity of the data from the content point of view. If the contractor uploads a new dataset for fixing a technical issue but does not make the content validity check, then the date must remain untouched XML file The zip file must contain a single XML file. The XML file must be in UNIX file format. The encoding of the XML file must be UTF-8. The XML file must comply with the W3C XML schema provided. The dataset should comply with the text formatting instructions detailed in chapter Introductory texts The overview and the introductory texts for each of the general and specific requirements as described above under "Introductory Texts" must be provided in separate html files. The html files must comply with the text formatting instructions given in chapter Image files In the cases where there is a form that has to be filled by the exporter, a bitmap image of this form (GIF format) is required and the text must contain an HTML link respecting the following constraints: the src attribute is set to the image file name 9

10 the alt attribute must contain the label defined in the xml file ( image_label element). Example: <img src="awb.gif" alt="air way bill form">. In order to obtain 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 introductory text for the requirement. The English translation should include all details given in the original form. The name of image files must be in lowercase, must start with an alphabetical character, may not contain special characters or spaces and must have a maximum length of 256 characters, the same applies for the html documents. 10

11 4. XML SCHEMA The xml files provided by the contractor must be validated against the following schema Schema <?xml version="1.0" encoding="utf-8"?> <!-- arket Access database - Import Formalities v5 - Validation dataset file) --> xs:schema elementformdefault="qualified" xmlns:xs=" xs:element name="doc"> xs:complextype> xs:sequence> xs:element ref="doc_scope" /> xs:element ref="doc_id" /> xs:element ref="doc_label" /> xs:element ref="doc_filename" /> xs:element ref="doc_order" minoccurs="0" /> xs:element ref="images_list" minoccurs="0" /> </xs:sequence> xs:element name="doc_filename" type="xs:string"> xs:documentation>file name of the document.</xs:documentation> xs:element name="doc_id" type="xs:string"> xs:documentation>unique id of the document. The first character must be alphabetical. The code may not contain special characters or spaces.</xs:documentation> xs:element name="doc_label" type="xs:string"> xs:documentation>label to be used as a document title. This label is displayed on the MADB web site.</xs:documentation> xs:element name="doc_order" type="xs:integer"> xs:documentation>defines the order of the document when displayed. Required for the general requirement documents and optional for other documents.</xs:documentation> xs:element name="doc_scope"> 11

12 xs:documentation>type of document ("O"=overview; "G"=general; "S"=specific)</xs:documentation> xs:complextype> xs:simplecontent> xs:extension base="xs:string"> xs:attribute name="doc_type" use="required"> xs:simpletype> xs:restriction base="xs:nmtoken"> xs:enumeration value="g" /> xs:enumeration value="o" /> xs:enumeration value="s" /> </xs:restriction> </xs:simpletype> </xs:attribute> </xs:extension> </xs:simplecontent> xs:element name="docs"> xs:documentation>this element contains a list of doc elements.</xs:documentation> xs:complextype> xs:sequence> xs:element ref="doc" maxoccurs="unbounded"> xs:documentation>this element describes an overview, a general requirement or a specific requirement document.</xs:documentation> </xs:sequence> xs:element name="egif"> xs:documentation>top level element.</xs:documentation> xs:complextype> xs:sequence> xs:element ref="update" /> xs:element name="modifsummary" type="xs:string"> xs:documentation>the modifsummary element must be used by the contractor to inform DG Trade of modifications introduced in the current revision with comparison to the previous revision. This info is for internal use only and is not displayed on the public web site.</xs:documentation> xs:element ref="overview" /> xs:element ref="general_requirements" /> xs:element ref="specific_requirements" /> xs:element ref="docs" /> </xs:sequence> 12

13 xs:element name="exclu_hs_code"> xs:documentation>an HS sub-code (more than 4 digits) for which the document is not applicable. All numeric (no dots allowed).</xs:documentation> xs:simpletype> xs:restriction base="xs:string"> xs:minlength value="4" /> xs:maxlength value="12" /> </xs:restriction> </xs:simpletype> xs:element name="exclu_list"> xs:documentation>a list of HS sub-codes for which the specific requirement document is not applicable.</xs:documentation> xs:complextype> xs:sequence> xs:element ref="exclu_hs_code" maxoccurs="unbounded"> xs:documentation>an HS sub-code for which the document is never applicable. All numeric (no dots allowed).</xs:documentation> </xs:sequence> xs:element name="exclu_note" type="xs:string"> xs:documentation>a free text note explaining the exception. Examples: "Not required if intended for animal use.", "Not required for , , "</xs:documentation> xs:element name="exclusions"> xs:documentation>this element is used when the specific requirement document is applicable to all products classified under a 4-digit HS code except for a few exceptional cases. This element lists those exceptions. It can take the form of a list of HS sub-codes (with more than 4 digits) for which the current specific document is not applicable. An exception can also be expressed in terms other than HS sub-codes. For example: "Not required if intended for animal use".</xs:documentation> xs:complextype> xs:sequence> xs:element ref="exclu_note"> xs:documentation>a free format note explaining the exception to the general rule.</xs:documentation> xs:element ref="exclu_list" minoccurs="0" /> 13

14 </xs:sequence> xs:element name="general_requirements"> xs:documentation>this element contains the list of general requirement documents.</xs:documentation> xs:complextype> xs:sequence> xs:element ref="gr_list" /> </xs:sequence> xs:element name="gr_doc_id" type="xs:string"> xs:documentation>doc_id of a general requirement document.</xs:documentation> xs:element name="gr_list"> xs:complextype> xs:sequence> xs:element ref="gr_doc_id" maxoccurs="unbounded" /> </xs:sequence> xs:element name="hs_code"> xs:documentation>a 4-digit HS code.</xs:documentation> xs:simpletype> xs:restriction base="xs:string"> xs:pattern value="[0-9]{4}" /> </xs:restriction> </xs:simpletype> xs:element name="hs_label" type="xs:string"> xs:documentation>product description according to the HS nomenclature. This text is displayed on the MADB web site.</xs:documentation> xs:element name="image"> xs:complextype> xs:sequence> xs:element ref="image_label"> <xs:documentation> Short description of the image. This label is in principle identical to the alt attribute of the img tag - <![CDATA[ (<img src= awb.gif alt= Air way bill form">. ]]> </xs:documentation> 14

15 xs:element ref="image_filename" /> </xs:sequence> xs:element name="image_filename" type="xs:string"> xs:documentation>filename of the image.</xs:documentation> xs:element name="image_label" type="xs:string"> xs:documentation>label used to describe the image.</xs:documentation> xs:element name="images_list"> xs:documentation>list of the images</xs:documentation> xs:complextype> xs:sequence> xs:element ref="image" maxoccurs="unbounded" /> </xs:sequence> xs:element name="inclu_hs_code"> xs:documentation>an HS sub-code for which the document is applicable. All numeric (no dots allowed).</xs:documentation> xs:simpletype> xs:restriction base="xs:string"> xs:minlength value="4" /> xs:maxlength value="12" /> </xs:restriction> </xs:simpletype> xs:element name="inclu_list"> xs:documentation>a list of HS sub-codes for which the specific requirement document is applicable.</xs:documentation> xs:complextype> xs:sequence> xs:element ref="inclu_hs_code" maxoccurs="unbounded" /> </xs:sequence> xs:element name="inclu_note" type="xs:string"> xs:documentation>a free text note describing the applicability condition. Examples: "Only required for , ", "Only required for uncured hides and skins.".</xs:documentation> 15

16 xs:element name="inclusions"> xs:documentation>this element gives information on the scope of the specific requirement document when it is not systematically applicable to products classified under a 4-digit HS code. It can take the form of a list of HS subcodes (with more than 4 digits) for which the current document is applicable. The restriction can also be based on criteria other than HS subcodes (examples: "Only required if equipped with air conditioning units containing controlled substances").</xs:documentation> xs:complextype> xs:sequence> xs:element ref="inclu_note"> xs:documentation>a free format note explaining the restriction.</xs:documentation> xs:element ref="inclu_list" minoccurs="0"> xs:documentation>a list of HS sub-codes for which the specific requirement document may be applicable</xs:documentation> </xs:sequence> xs:element name="ov_doc_id" type="xs:string"> xs:documentation>the doc_id value of the overview document.</xs:documentation> xs:element name="overview"> xs:documentation>contains an element with the doc_id of the overview document.</xs:documentation> xs:complextype> xs:sequence> xs:element ref="ov_doc_id" /> </xs:sequence> xs:element name="product"> xs:complextype> xs:sequence> xs:element ref="hs_code" /> xs:element ref="hs_label" /> xs:element ref="sr_list" /> </xs:sequence> xs:element name="specific_requirements"> 16

17 xs:documentation>this element associates specific requirement documents to product codes.</xs:documentation> xs:complextype> xs:sequence> xs:element ref="product" maxoccurs="unbounded"> xs:documentation>this element associates specific requirement documents to one given 4-digit HS code.</xs:documentation> </xs:sequence> xs:key name="specific_requirements"> xs:selector xpath="specific_requirements/product" /> xs:field xpath="hs_code" /> </xs:key> xs:element name="sr_doc_id" type="xs:string"> xs:documentation>the doc_id value of a specific requirement document.</xs:documentation> xs:element name="sr_doc_mapping"> xs:documentation>associates a specific requirement document to a given 4- digit HS code.</xs:documentation> xs:complextype> xs:sequence> xs:element ref="sr_doc_id" /> xs:element ref="inclusions" minoccurs="0" /> xs:element ref="exclusions" minoccurs="0" /> </xs:sequence> xs:element name="sr_list"> xs:complextype> xs:sequence> xs:element ref="sr_doc_mapping" maxoccurs="unbounded" /> </xs:sequence> xs:element name="update"> xs:documentation>this element contains the details of the dataset file: year, revision, version, date, country, contractor info.</xs:documentation> xs:complextype> xs:simplecontent> xs:extension base="xs:string"> xs:attribute name="year" use="required"> xs:documentation>contract year to which the dataset is related. Example: If a dataset is uploaded in december 2009 to cover contractual obligations for 17

18 year 2010, then contract year must be set to 2010.</xs:documentation> xs:simpletype> xs:restriction base="xs:string"> xs:pattern value="[0-9]{4}" /> </xs:restriction> </xs:simpletype> </xs:attribute> xs:attribute name="revision" use="required"> xs:documentation>the revision number for that year, starting at '01'. A new revision number correspons to changes in the content (new document, modified document, modified applicability conditions...)</xs:documentation> xs:simpletype> xs:restriction base="xs:integer"> xs:totaldigits value="2" /> </xs:restriction> </xs:simpletype> </xs:attribute> xs:attribute name="date" type="xs:string" use="required"> xs:documentation>this is the latest date the contractor has checked the validity of the data content. It must not to be confused with the date of dataset upload : if a dataset is uploaded to correct a technical issue but the contractor does not check that the data is current, then the date must remain untouched. Format: yyyy-mm-dd format.</xs:documentation> </xs:attribute> xs:attribute name="country_label" type="xs:string" use="required"> xs:documentation>country name in English.</xs:documentation> </xs:attribute> xs:attribute name="country_id" type="xs:string" use="required"> xs:documentation>use ISO2A country code (ex: "US", "AR"...)See homepage upload area for list.</xs:documentation> </xs:attribute> xs:attribute name="update_filename" use="required"> xs:documentation>the name of the xml file obtained by concatenating "MAIF- ", the ISO 2 country code, the two last digits of the year, "-", the 2-digit revision number and the 3-digit version number. Example: MAIF-IN06-01v001.</xs:documentation> xs:simpletype> xs:restriction base="xs:string"> xs:length value="16" /> xs:totaldigits value="7" /> </xs:restriction> </xs:simpletype> </xs:attribute> xs:attribute name="contractor_id" type="xs:string" use="required"> 18

19 xs:documentation>a contractor ID which will be communicated by DG Trade.</xs:documentation> </xs:attribute> xs:attribute name="contractor_name" type="xs:string" use="optional"> xs:documentation>name of the contractor.</xs:documentation> </xs:attribute> xs:attribute name="contractor_ " type="xs:string" use="optional"> xs:documentation>the address that the Commission will use to send a confirmation message or to notify problems found.</xs:documentation> </xs:attribute> xs:attribute name="version" use="required"> xs:documentation>version number.</xs:documentation> xs:simpletype> xs:restriction base="xs:string"> xs:length value="3" /> xs:totaldigits value="3" /> </xs:restriction> </xs:simpletype> </xs:attribute> </xs:extension> </xs:simplecontent> </xs:schema> Importformalities_v5..xsd 19

20 4.2. Schema documentation 20

21 element doc diagram properties content complex children doc_scope doc_id doc_label doc_filename doc_order images_list used by element docs source <xs:element name="doc"> <xs:complextype> <xs:sequence> <xs:element ref="doc_scope"/> <xs:element ref="doc_id"/> <xs:element ref="doc_label"/> <xs:element ref="doc_filename"/> <xs:element ref="doc_order" minoccurs="0"/> <xs:element ref="images_list" minoccurs="0"/> </xs:sequence> element doc_filename diagram type xs:string properties content simple used by element doc annotation documentation File name of the document. 21

22 source <xs:element name="doc_filename" type="xs:string"> <xs:documentation>file name of the document.</xs:documentation> element doc_id diagram type xs:string properties content simple used by element doc annotation documentation Unique id of the document. The first character must be alphabetical. The code may not contain special characters or spaces. source <xs:element name="doc_id" type="xs:string"> <xs:documentation>unique id of the document. The first character must be alphabetical. The code may not contain special characters or spaces.</xs:documentation> element doc_label diagram type xs:string properties content simple used by element doc annotation documentation Label to be used as a document title. This label is displayed on the MADB web site. source <xs:element name="doc_label" type="xs:string"> <xs:documentation>label to be used as a document title. This label is displayed on the MADB web site.</xs:documentation> element doc_order 22

23 diagram type xs:integer properties content simple used by element doc annotation documentation Defines the order of the document when displayed. Required for the general requirement documents and optional for other documents. source <xs:element name="doc_order" type="xs:integer"> <xs:documentation>defines the order of the document when displayed. Required for the general requirement documents and optional for other documents.</xs:documentation> element doc_scope diagram type extension of xs:string properties content complex used by element doc attributes Name Type Use Default Fixed Annotation doc_type required annotation documentation Type of document ("O"=overview; "G"=general; "S"=specific) source <xs:element name="doc_scope"> <xs:documentation>type of document ("O"=overview; "G"=general; "S"=specific)</xs:documentation> <xs:complextype> <xs:simplecontent> <xs:extension base="xs:string"> <xs:attribute name="doc_type" use="required"> <xs:simpletype> <xs:restriction base="xs:nmtoken"> <xs:enumeration value="g"/> <xs:enumeration value="o"/> <xs:enumeration value="s"/> </xs:restriction> </xs:simpletype> </xs:attribute> </xs:extension> </xs:simplecontent> element docs 23

24 diagram properties content complex children doc used by element egif annotation documentation This element contains a list of doc elements. source <xs:element name="docs"> <xs:documentation>this element contains a list of doc elements. </xs:documentation> <xs:complextype> <xs:sequence> <xs:element ref="doc" maxoccurs="unbounded"> <xs:documentation> This element describes an overview, a general requirement or a specific requirement document. </xs:documentation> </xs:sequence> element egif diagram 24

25 properties content complex children update modifsummary overview general_requirements specific_requirements docs annotation documentation Top level element. source <xs:element name="egif"> <xs:documentation>top level element.</xs:documentation> <xs:complextype> <xs:sequence> <xs:element ref="update"/> <xs:element name="modifsummary" type="xs:string"> <xs:documentation>the modifsummary element must be used by the contractor to inform DG Trade of modifications introduced in the current revision with comparison to the previous revision. This info is for internal use only and is not displayed on the public web site.</xs:documentation> <xs:element ref="overview"/> <xs:element ref="general_requirements"/> <xs:element ref="specific_requirements"/> <xs:element ref="docs"/> </xs:sequence> element egif/modifsummary diagram type xs:string properties isref 0 content simple annotation documentation The modifsummary element must be used by the contractor to inform DG Trade of modifications introduced in the current revision with comparison to the previous revision. This info is for internal use only and is not displayed on the public web site. source <xs:element name="modifsummary" type="xs:string"> <xs:documentation>the modifsummary element must be used by the contractor to inform DG Trade of modifications introduced in the current revision with comparison to the previous revision. This info is for internal use only and is not displayed on the public web site.</xs:documentation> element exclu_hs_code diagram 25

26 type restriction of xs:string properties content simple used by element exclu_list facets minlength 4 maxlength 12 annotation documentation An HS sub-code (more than 4 digits) for which the document is not applicable. All numeric (no dots allowed). source <xs:element name="exclu_hs_code"> <xs:documentation>an HS sub-code (more than 4 digits) for which the document is not applicable. All numeric (no dots allowed).</xs:documentation> <xs:simpletype> <xs:restriction base="xs:string"> <xs:minlength value="4"/> <xs:maxlength value="12"/> </xs:restriction> </xs:simpletype> element exclu_list diagram properties content complex children exclu_hs_code used by element exclusions annotation documentation A list of HS sub-codes for which the specific requirement document is not applicable. source <xs:element name="exclu_list"> <xs:documentation>a list of HS sub-codes for which the specific requirement document is not applicable.</xs:documentation> <xs:complextype> <xs:sequence> <xs:element ref="exclu_hs_code" maxoccurs="unbounded"> <xs:documentation> An HS sub-code for which the document is never applicable. All numeric (no dots allowed). </xs:documentation> </xs:sequence> element exclu_note 26

27 diagram type xs:string properties content simple used by element exclusions annotation documentation A free text note explaining the exception. Examples: "Not required if intended for animal use.", "Not required for , , " source <xs:element name="exclu_note" type="xs:string"> <xs:documentation>a free text note explaining the exception. Examples: "Not required if intended for animal use.", "Not required for , , "</xs:documentation> element exclusions diagram properties content complex children exclu_note exclu_list used by element sr_doc_mapping annotation documentation This element is used when the specific requirement document is applicable to all products classified under a 4-digit HS code except for a few exceptional cases. This element lists those exceptions. It can take the form of a list of HS sub-codes (with more than 4 digits) for which the current specific document is not applicable. An exception can also be expressed in terms other than HS sub-codes. For example: "Not required if intended for animal use". source <xs:element name="exclusions"> 27

28 <xs:documentation>this element is used when the specific requirement document is applicable to all products classified under a 4-digit HS code except for a few exceptional cases. This element lists those exceptions. It can take the form of a list of HS sub-codes (with more than 4 digits) for which the current specific document is not applicable. An exception can also be expressed in terms other than HS sub-codes. For example: "Not required if intended for animal use".</xs:documentation> <xs:complextype> <xs:sequence> <xs:element ref="exclu_note"> <xs:documentation> A free format note explaining the exception to the general rule. </xs:documentation> <xs:element ref="exclu_list" minoccurs="0"/> </xs:sequence> element general_requirements diagram properties content complex children gr_list used by element egif annotation documentation This element contains the list of general requirement documents. source <xs:element name="general_requirements"> <xs:documentation>this element contains the list of general requirement documents.</xs:documentation> <xs:complextype> <xs:sequence> <xs:element ref="gr_list"/> </xs:sequence> element gr_doc_id diagram type xs:string properties content simple used by element gr_list annotation documentation doc_id of a general requirement document. source <xs:element name="gr_doc_id" type="xs:string"> 28

29 <xs:documentation>doc_id of a general requirement document.</xs:documentation> element gr_list diagram properties content complex children gr_doc_id used by element general_requirements source <xs:element name="gr_list"> <xs:complextype> <xs:sequence> <xs:element ref="gr_doc_id" maxoccurs="unbounded"/> </xs:sequence> element hs_code diagram type restriction of xs:string properties content simple used by element product facets pattern [0-9]{4} annotation documentation A 4-digit HS code. source <xs:element name="hs_code"> <xs:documentation>a 4-digit HS code.</xs:documentation> <xs:simpletype> <xs:restriction base="xs:string"> <xs:pattern value="[0-9]{4}"/> </xs:restriction> </xs:simpletype> element hs_label diagram type xs:string 29

30 properties content simple used by element product annotation documentation Product description according to the HS nomenclature. This text is displayed on the MADB web site. source <xs:element name="hs_label" type="xs:string"> <xs:documentation>product description according to the HS nomenclature. This text is displayed on the MADB web site.</xs:documentation> element image diagram properties content complex children image_label image_filename used by element images_list source <xs:element name="image"> <xs:complextype> <xs:sequence> <xs:element ref="image_label"> <xs:documentation> Short description of the image. This label is in principle identical to the alt attribute of the img tag <![CDATA[ (<img src= awb.gif alt= Air way bill form">. ]]></xs:documentation> <xs:element ref="image_filename"/> </xs:sequence> element image_filename diagram type xs:string properties content simple used by element image annotation documentation Filename of the image. 30

31 source <xs:element name="image_filename" type="xs:string"> <xs:documentation>filename of the image.</xs:documentation> element image_label diagram type xs:string properties content simple used by element image annotation documentation Label used to describe the image. source <xs:element name="image_label" type="xs:string"> <xs:documentation>label used to describe the image.</xs:documentation> element images_list diagram properties content complex children image used by element doc annotation documentation List of the images source <xs:element name="images_list"> <xs:documentation>list of the images</xs:documentation> <xs:complextype> <xs:sequence> <xs:element ref="image" maxoccurs="unbounded"/> </xs:sequence> element inclu_hs_code diagram type restriction of xs:string properties content simple 31

32 used by element inclu_list facets minlength 4 maxlength 12 annotation documentation An HS sub-code for which the document is applicable. All numeric (no dots allowed). source <xs:element name="inclu_hs_code"> <xs:documentation>an HS sub-code for which the document is applicable. All numeric (no dots allowed). <xs:simpletype> <xs:restriction base="xs:string"> <xs:minlength value="4"/> <xs:maxlength value="12"/> </xs:restriction> </xs:simpletype> element inclu_list diagram properties content complex children inclu_hs_code used by element inclusions annotation documentation A list of HS sub-codes for which the specific requirement document is applicable. source <xs:element name="inclu_list"> <xs:documentation>a list of HS sub-codes for which the specific requirement document is applicable.</xs:documentation> <xs:complextype> <xs:sequence> <xs:element ref="inclu_hs_code" maxoccurs="unbounded"/> </xs:sequence> element inclu_note diagram type xs:string properties content simple 32

33 used by element inclusions annotation documentation A free text note describing the applicability condition. Examples: "Only required for , ", "Only required for uncured hides and skins.". source <xs:element name="inclu_note" type="xs:string"> <xs:documentation>a free text note describing the applicability condition. Examples: "Only required for , ", "Only required for uncured hides and skins.".</xs:documentation> element inclusions diagram properties content complex children inclu_note inclu_list used by element sr_doc_mapping annotation documentation This element gives information on the scope of the specific requirement document when it is not systematically applicable to products classified under a 4-digit HS code. It can take the form of a list of HS sub-codes (with more than 4 digits) for which the current document is applicable. The restriction can also be based on criteria other than HS sub-codes (examples: "Only required if equipped with air conditioning units containing controlled substances"). source <xs:element name="inclusions"> <xs:documentation>this element gives information on the scope of the specific requirement document when it is not systematically applicable to products classified under a 4-digit HS code. It can take the form of a list of HS sub-codes (with more than 4 digits) for which the current document is applicable. The restriction can also be based on criteria other than HS sub-codes (examples: "Only required if equipped with air conditioning units containing controlled substances").</xs:documentation> <xs:complextype> <xs:sequence> <xs:element ref="inclu_note"> <xs:documentation>a free format note explaining the restriction.</xs:documentation> 33

34 <xs:element ref="inclu_list" minoccurs="0"> <xs:documentation> A list of HS sub-codes for which the specific requirement document may be applicable </xs:documentation> </xs:sequence> element ov_doc_id diagram type xs:string properties content simple used by element overview annotation documentation The doc_id value of the overview document. source <xs:element name="ov_doc_id" type="xs:string"> <xs:documentation>the doc_id value of the overview document.</xs:documentation> element overview diagram properties content complex children ov_doc_id used by element egif annotation documentation Contains an element with the doc_id of the overview document. source <xs:element name="overview"> <xs:documentation>contains an element with the doc_id of the overview document.</xs:documentation> <xs:complextype> <xs:sequence> <xs:element ref="ov_doc_id"/> </xs:sequence> element product 34

35 diagram properties content complex children hs_code hs_label sr_list used by element specific_requirements source <xs:element name="product"> <xs:complextype> <xs:sequence> <xs:element ref="hs_code"/> <xs:element ref="hs_label"/> <xs:element ref="sr_list"/> </xs:sequence> element specific_requirements diagram properties content complex children product used by element egif identity constraints Name Refer Selector Field(s) key specific_requirements specific_requirements/product hs_code annotation documentation This element associates specific requirement documents to product codes. source <xs:element name="specific_requirements"> <xs:documentation>this element associates specific requirement documents to product codes.</xs:documentation> <xs:complextype> <xs:sequence> <xs:element ref="product" maxoccurs="unbounded"> <xs:documentation> This element associates specific requirement documents to one given 4-digit HS code. </xs:documentation> </xs:sequence> <xs:key name="specific_requirements"> <xs:selector xpath="specific_requirements/product"/> 35

36 <xs:field xpath="hs_code"/> </xs:key> element sr_doc_id diagram type xs:string properties content simple used by element sr_doc_mapping annotation documentation The doc_id value of a specific requirement document. source <xs:element name="sr_doc_id" type="xs:string"> <xs:documentation>the doc_id value of a specific requirement document.</xs:documentation> element sr_doc_mapping 36

37 diagram properties content complex children sr_doc_id inclusions exclusions used by element sr_list annotation documentation Associates a specific requirement document to a given 4-digit HS code. source <xs:element name="sr_doc_mapping"> <xs:documentation>associates a specific requirement document to a given 4-digit HS code.</xs:documentation> <xs:complextype> <xs:sequence> <xs:element ref="sr_doc_id"/> <xs:element ref="inclusions" minoccurs="0"/> <xs:element ref="exclusions" minoccurs="0"/> </xs:sequence> element sr_list 37

38 diagram properties content complex children sr_doc_mapping used by element product source <xs:element name="sr_list"> <xs:complextype> <xs:sequence> <xs:element ref="sr_doc_mapping" maxoccurs="unbounded"/> </xs:sequence> element update diagram type extension of xs:string properties content complex used by element egif attributes Name Type Use Default Fixed Annotation year required documentation Contract year to which the dataset is related. Example: If a dataset is uploaded in december 2009 to cover contractual obligations for year 2010, then contract year must be set to revision required documentation The revision number for that year, starting at '01'. A new revision number correspons to changes in the content (new document, modified document, modified applicability conditions...) date xs:string required documentation This is the latest date the contractor has checked the validity of the data content. It must not to be confused with the date of dataset upload : if a dataset is uploaded to correct a technical issue but the contractor does not check that the data is current, then the date must remain untouched. Format: yyyy-mm-dd format. country_label xs:string required documentation Country name in English. country_id xs:string required documentation Use ISO2A country code (ex: "US", "AR"...)See homepage upload area for list. update_filename required documentation The name of the xml file obtained by concatenating "MAIF-", the ISO 2 country code, the two last digits of the year, "-", the 2-digit revision number and the 3-digit version number. Example: MAIF-IN06-01v001. contractor_id xs:string required documentation A contractor ID which will be communicated by DG Trade. contractor_name xs:string optional documentation Name of the contractor. contractor_ xs:string optional documentation The address that the 38

39 Commission will use to send a confirmation message or to notify problems found. version required documentation Version number. annotation documentation This element contains the details of the dataset file: year, revision, version, date, country, contractor info. source <xs:element name="update"> <xs:documentation>this element contains the details of the dataset file: year, revision, version, date, country, contractor info.</xs:documentation> <xs:complextype> <xs:simplecontent> <xs:extension base="xs:string"> <xs:attribute name="year" use="required"> <xs:documentation>contract year to which the dataset is related. Example: If a dataset is uploaded in december 2009 to cover contractual obligations for year 2010, then contract year must be set to 2010.</xs:documentation> <xs:simpletype> <xs:restriction base="xs:string"> <xs:pattern value="[0-9]{4}"/> </xs:restriction> </xs:simpletype> </xs:attribute> <xs:attribute name="revision" use="required"> <xs:documentation>the revision number for that year, starting at '01'. A new revision number correspons to changes in the content (new document, modified document, modified applicability conditions...) </xs:documentation> <xs:simpletype> <xs:restriction base="xs:integer"> <xs:totaldigits value="2"/> </xs:restriction> </xs:simpletype> </xs:attribute> <xs:attribute name="date" type="xs:string" use="required"> <xs:documentation>this is the latest date the contractor has checked the validity of the data content. It must not to be confused with the date of dataset upload : if a dataset is uploaded to correct a technical issue but the contractor does not check that the data is current, then the date must remain untouched. Format: yyyy-mm-dd format. </xs:documentation> </xs:attribute> <xs:attribute name="country_label" type="xs:string" use="required"> <xs:documentation>country name in English.</xs:documentation> </xs:attribute> <xs:attribute name="country_id" type="xs:string" use="required"> <xs:documentation>use ISO2A country code (ex: "US", "AR"...)See homepage upload area for list. </xs:documentation> </xs:attribute> <xs:attribute name="update_filename" use="required"> <xs:documentation>the name of the xml file obtained by concatenating "MAIF-", the ISO 2 country code, the two last digits of the year, "-", the 2-digit revision number and the 3-digit version number. Example: MAIF-IN06-01v001. </xs:documentation> <xs:simpletype> <xs:restriction base="xs:string"> <xs:length value="16"/> <xs:totaldigits value="7"/> </xs:restriction> </xs:simpletype> 39

40 </xs:attribute> <xs:attribute name="contractor_id" type="xs:string" use="required"> <xs:documentation>a contractor ID which will be communicated by DG Trade.</xs:documentation> </xs:attribute> <xs:attribute name="contractor_name" type="xs:string" use="optional"> <xs:documentation>name of the contractor.</xs:documentation> </xs:attribute> <xs:attribute name="contractor_ " type="xs:string" use="optional"> <xs:documentation>the address that the Commission will use to send a confirmation message or to notify problems found. </xs:documentation> </xs:attribute> <xs:attribute name="version" use="required"> <xs:documentation>version number.</xs:documentation> <xs:simpletype> <xs:restriction base="xs:string"> <xs:length value="3"/> <xs:totaldigits value="3"/> </xs:restriction> </xs:simpletype> </xs:attribute> </xs:extension> </xs:simplecontent> 4.3. Inclusions and exclusions Principle Specific requirements are assigned to 4-digit HS codes (using the hs_code element). There will be situations where a specific requirement is not applicable to all goods covered by the four-digit HS. There are 2 possible ways of expressing this: using the inclusions element in order to expressed all covered cases using the exclusions element in order to express that the requirement is generally applicable except for the case(s) expressed in the exclusion element. The inclusions and exclusions are often expressed as a list of product codes (under a given fourdigit HS code) but can also refer to other applicability conditions. They can also mix HS code related conditions with other applicability conditions. Here are a few examples: Only required for , , , , , Not required for , , Only required for uncured hides and skins Only required if subject to CITES Only required for if containing eiderdowns Only required for if aerosol sprays containing CFCs Only applicable to products outside the range of 8-26% milk fat content (usually falling outside , ) Only prohibited for , , Type of inclusion or XML elements Example of note (inclu_note 40

41 exclusion Inclusion expressed as a series of included HS codes Exclusion expressed as a series of exclude HS codes Inclusion, unrelated to HS codes Exclusion, unrelated to HS codes Inclusion, expressed as a mix of HS code related and non HS code related conditions. Exclusion, expressed as a mix of HS code related and non HS code related conditions. inclu_note : mandatory inclu_list : mandatory exclu_note: no exclu_list: no If inclu_note is non null, MADB displays inclu_note, otherwise MADB constructs a note based on the HS codes listed in inclu_list. The constructed note starts with "Only required for". inclu_note : no inclu_list : no exclu_note: mandatory exclu_list: mandatory If exclu_note is non null, MADB displays exclu_note, otherwise MADB constructs a note based on the HS codes listed in exclu_list. The constructed note starts with "Not required for". inclu_note : mandatory inclu_list : no exclu_note: no exclu_list: no MADB displays the inclu_note. inclu_note : no inclu_list : no exclu_note: mandatory exclu_list: no MADB displays the exclu_note. inclu_note : mandatory inclu_list : mandatory exclu_note: no exclu_list: no MADB displays the inclu_note. inclu_note : no inclu_list : no exclu_note: mandatory exclu_list: mandatory MADB displays the exclu_note. or exclu_note) Only required for , , , , , Not required for , , Only required for uncured hides and skins. Not applicable if fibre/non woven Only required for , if covered by CITES convention Not applicable to if poultry not older than one week and if poultry intended for production purposes Note wording Inclusion notes must start with one of the following phrases: 41

42 "Only required" "Only applicable" "Only prohibited" Exclusion notes must start with one of the following phrases: "Not required" "Not applicable" "Not prohibited" 4.4. ModifSummary element The modifsummary element must be used by the contractor to inform DG Trade of modifications introduced in the current revision with comparison to the previous revision. This info is for internal use only and is not displayed on the public web site. Here is an example of modifsummary content: The import documentation for Libya has been completely reviewed and adapted to new regulations. The document entitled "Trade Name Registration" has been incorporated into the report. Due to further liberalisation efforts, the documents entitled "Contract on the Importation of Goods" and "Registration with the General Company for Stationary and Office Equipment Supplies" are no longer required and thus has been excluded from the documentation. The form of the document entitled "Registration with the National Supply Corporation" has been exchanged by an enhanced version and the procedure has been adapted to the current legislation. Several other documents have been updated with regard to various details. Specific measures have been taken to encourage private trade and gradually withdraw government involvement, e.g. previous monopolies have been softened and the banking sector allows for more diversity as to the choice of the hard currency to be used in the transaction and the commercial bank. As a consequence, the following documents have been altered: "Opening of a Foreign Currency Account", "Application for Foreign Capital Investment", "Registration with the NASCO" and 42

43 5. TEXT FORMATTING INSTRUCTIONS 5.1. General constraints Each overview or general/specific requirement corresponds to one individual HTML file. The file must be XHTML-compliant. The html file must be encoded using UTF-8. The file name must be in lowercase, must start with an alphabetical character, may not contain special characters or spaces and must have a maximum length of 256 characters. The file must have the ".html" extension. The html files will be used in a Unix system, therefore the line breaks must be represented by a single Line-Feed character and not by Carriage-Return followed by a Line-Feed (like in Windows systems) Document title of general/specific requirements MADB uses the text provided in XML element doc_label to construct the page displaying the general or specific requirement. For that reason, the title of the document must not be included in the html (otherwise it would appear in double on the MADB web site) Links The links created in a document should respect the following rules. If the link points to another website, the target must be set to "external". Example: <a href= target= external >DG Trade Website</a> If the link points to another document in the data set, it must have the target set to "egif": Example: <a href="file.html" target="egif">link to document in same dataset</a> If there are bookmarks, the link also needs the target="egif" attribute. Example: <a href="#book1" target="egif"> link to a bookmark</a> <a href= file.html#book1 target="egif">link to another bookmark</a> 5.4. CSS classes DG Trade 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= "egif_title1" or "class=egif_title2" or class="egif_title3": Example: <p class="egif_title1">title level 1</p> <p class="egif_title2">title level 2</p> <p class="egif_title3">title level 3</p> 43

44 Bullet lists can be ordered or unordered. The title of the bullet list must be placed in a paragraph tag with the class="egif_list_title". Example: <p class="egif_list_title">bullet list unordered title</p> To create a normal block text use class="egif": Example: <p class="egif">paragraph</p> To add bold text in the document use the class="egif_bold". Example: <p class="egif_bold">bold text</p> To add italic text use the class="egif_italic". Example: <p class="egif_italic">italic text</p> To ident text there are two classes available class=egif_indent1 and class=indent2. Example: <p class="egif_indent1">indent text level 1</p> <p class="egif_indent2">indent text level 2</p> For the tables use class="egif_tabletitle" for the <th> tags and class="egif_tablecontent" for the <td> tags. Example: <th class="egif_tabletitle">title</th> <td width="50%" class="egif_tablecontent">content</td> The title of a footnote should use class="egif_footnote". Example: <p class="egif_footnote">footnote text</p> For the 'list of abbreviations'. Example: <p class="egif_abbreviations_title">abbreviations</p> <ul> <li class=egif_abbreviations>abbreviation</li> <li class=egif_abbreviations>abbreviation</li> </ul> For the 'table of contents' (used in the overview.html document). Example: <p class="egif_table_of_contents_title">table of contents</p> <ul> <li class="egif_table_of_contents">item</li> <li class="egif_table_of_contents">item</li> </ul> For the changes title (used in the overview.html document) use the class="egif_changes_title". Example: <p class="egif_changes_title">changes</p> 44

45 5.5. CSS style sheet Please find below an extraction of the CSS file used on the Market Access database : p.egif_title1 { font-family: Verdana, sans-serif; color: #004798; font-size: 16px; font-weight: bold; text-align: left; text-decoration: none; margin-left: 0px; margin-bottom: 4px; } p.egif_title2 { font-family: Verdana, sans-serif; color: #004798; font-size: 14px; font-weight: bold; text-align: left; text-decoration: none; margin-left: 0px; margin-bottom: 4px; } p.egif_title3 { font-family: Verdana, sans-serif; color: #004798; font-size: 12px; font-weight: bold; text-align: left; text-decoration: none; margin-left: 0px; margin-bottom: 4px; } p.egif_list_title { font-family: Verdana, sans-serif; color: #004798; font-size: 12px; font-weight: bold; text-align: justify; margin-right: 8px; line-height: 130%; margin-top: 4px; text-decoration:underline; } p.egif_italic { font-family: Verdana, sans-serif; color: #004798; font-size: 12px; font-weight: bold; text-align: justify; margin-right: 8px; line-height: 130%; margin-top: 4px; font-style:italic; } p.egif_bold { font-family: Verdana, sans-serif; color: #004798; font-size: 12px; font-weight: bold; text-align: justify; margin-right: 8px; line-height: 130%; margin-top: 4px; } p.egif_indent1 { font-family: Verdana, sans-serif; color: #004798; font-size: 12px; font-weight: normal; text-align: justify; margin-right: 8px; line-height: 130%; margin-top: 4px; margin-left:4px; } 45

46 p.egif_indent2 { font-family: Verdana, sans-serif; color: #004798; font-size: 12px; font-weight: normal; text-align: justify; margin-right: 8px; line-height: 130%; margin-top: 4px; margin-left:15px; }.egif { font-family: Verdana, sans-serif; color: #004798; font-size: 12px; font-weight: normal; text-align: justify; margin-right: 8px; line-height: 130%; margin-top: 4px; }.egif a:link { color: #004798; font-weight: bold; text-decoration: underline; }.egif a:visited { color: #004798; font-weight: bold; text-decoration: underline; }.egif a:hover { color:#3399cc; font-weight: bold; text-decoration: underline; } ul { font-family: Verdana, sans-serif; color: #004798; font-size: 12px; text-align: left; line-height: 130%; list-style-type:square; list-style-position:outside; } ul a:link { color: #004798; font-weight: bold; text-decoration: underline; } ul a:visited { color: #004798; font-weight: bold; text-decoration: underline; } ul a:hover { color:#3399cc; font-weight: bold; text-decoration: underline; } ol { font-family: Verdana, sans-serif; color: #004798; font-size: 12px; text-align: left; line-height: 130%; list-style-type: decimal; } th.egif_tabletitle { font-family: Verdana, sans-serif; color: #004798; font-weight:bold } td.egif_tablecontent{ font-family: Verdana, sans-serif; color: #004798; font-size: 12px; list-style-type:disc } p.egif_footnote { font-family: Verdana, sans-serif; color: #004798; font-size: 10pt; } li.egif_abbreviations{ font-family: Verdana, sans-serif; color: #666666; font-size: 11px; font-weight: normal; line-height: 130%; list-style-type:square } p.egif_abbreviations_title{ font-family: Verdana, sans-serif; color: #999999; font-size: 12px; font-weight: bold; text-align: left; text-decoration: none; 46

47 margin-left: 0px; margin-bottom: 4px; } li.egif_table_of_contents { list-style-type:square; list-style-position:outside; font-family: Verdana, sans-serif; color: #004798; font-size: 12px; font-weight:normal; text-align: left; margin-left: 0px; line-height: 140%; } li.egif_table_of_contents a:link { color: #004798; font-weight:normal; textdecoration: none; } li.egif_table_of_contents a:visited { color: #004798; font-weight:normal; textdecoration: none; } li.egif_table_of_contents a:hover { color: #FF6600; font-weight:normal; textdecoration: none; } p.egif_table_of_contents_title { font-family: Verdana, sans-serif; color: #004798; font-size: 12px; font-weight: bold; text-align: left; text-decoration: none; margin-left: 0px; padding-bottom: 3px; } p.egif_changes_title { font-family: Verdana, sans-serif; color:#ff6600; font-size: 12px; font-weight: bold; text-align: left; text-decoration: none; margin-left: 0px; margin-bottom: 4px; } /* table { font-family: Arial; font-size: 12px; } */ 47

48 6. EXAMPLE XML FILE In this chapter, we include a file illustrating the various aspects of the XML schema Example file The following example xml file contains information pertaining to Iran and the following HS codes: 1507 (example with one specific requirement and no inclusions nor exclusions), 2933 (example with one specific requirement having an inclusions list) 0210 (example with a few specific requirements, two of them having an exclusions list). <?xml version="1.0" encoding="utf-8"?> <egif xmlns:xsi=" xsi:nonamespaceschemalocation=" importformalities_v5.xsd"> <update country_id="ir" year="2010" revision="03" date=" " country_label="iran" update_filename="maif-ir10-01v003" contractor_id="x" contractor_name="xxx" contractor_ ="test@ec.europa.eu" version="003"/> <modifsummary>example file</modifsummary> <overview> <ov_doc_id>over01</ov_doc_id> </overview> <general_requirements> <gr_list> <gr_doc_id>mfest</gr_doc_id> <gr_doc_id>cid</gr_doc_id> <gr_doc_id>invoice</gr_doc_id> <gr_doc_id>cf_orig</gr_doc_id> <gr_doc_id>awb</gr_doc_id> <gr_doc_id>bl</gr_doc_id> <gr_doc_id>cmr</gr_doc_id> <gr_doc_id>cf_ins</gr_doc_id> <gr_doc_id>plist</gr_doc_id> <gr_doc_id>pre_ins</gr_doc_id> <gr_doc_id>reg_imp</gr_doc_id> <gr_doc_id>reg_cc</gr_doc_id> </gr_list> </general_requirements> <specific_requirements> <product> <hs_code>1507</hs_code> <hs_label>soya-bean OIL AND ITS FRACTIONS, WHETHER OR NOT REFINED, BUT NOT CHEMICALLY MODIFIED</hs_label> <sr_list> <sr_doc_mapping> <sr_doc_id>cf_ana</sr_doc_id> </sr_doc_mapping> </sr_list> </product> <product> <hs_code>2933</hs_code> <hs_label>heterocyclic COMPOUNDS WITH NITROGEN HETERO-ATOM(S) ONLY</hs_label> <sr_list> <sr_doc_mapping> <sr_doc_id>prh_imp</sr_doc_id> <inclusions> <inclu_note>only required for , , , , , </inclu_note> <inclu_list> <inclu_hs_code>293339</inclu_hs_code> <inclu_hs_code>293349</inclu_hs_code> <inclu_hs_code>293353</inclu_hs_code> <inclu_hs_code>293359</inclu_hs_code> <inclu_hs_code>293379</inclu_hs_code> 48

49 <inclu_hs_code>293399</inclu_hs_code> </inclu_list> </inclusions> </sr_doc_mapping> </sr_list> </product> <product> <hs_code>0210</hs_code> <hs_label>meat AND EDIBLE MEAT OFFAL, SALTED, IN BRINE, DRIED OR SMOKED; EDIBLE FLOURS AND MEALS OF MEAT OR MEAT OFFAL</hs_label> <sr_list> <sr_doc_mapping> <sr_doc_id>a_cites</sr_doc_id> <inclusions> <inclu_note>only required if subject to CITES </inclu_note> </inclusions> </sr_doc_mapping> <sr_doc_mapping> <sr_doc_id>cf_vet</sr_doc_id> <exclusions> <exclu_note>not required for , , </exclu_note> <exclu_list> <exclu_hs_code>021011</exclu_hs_code> <exclu_hs_code>011012</exclu_hs_code> <exclu_hs_code>021019</exclu_hs_code> </exclu_list> </exclusions> </sr_doc_mapping> <sr_doc_mapping> <sr_doc_id>cf_halal</sr_doc_id> <exclusions> <exclu_note>not required for , , </exclu_note> <exclu_list> <exclu_hs_code>021011</exclu_hs_code> <exclu_hs_code>011012</exclu_hs_code> <exclu_hs_code>021019</exclu_hs_code> </exclu_list> </exclusions> </sr_doc_mapping> </sr_list> </product> </specific_requirements> <docs> <doc> </doc> <doc> </doc> <doc> </doc> <doc> <doc_scope doc_type="o"/> <doc_id>over01</doc_id> <doc_label>overview of Import Procedures General Requirements</doc_label> <doc_filename>overview.html</doc_filename> <doc_scope doc_type="g"/> <doc_id>mfest</doc_id> <doc_label>manifest </doc_label> <doc_filename>mfest</doc_filename> <doc_order>1</doc_order> <doc_scope doc_type="g"/> <doc_id>cid</doc_id> <doc_label>customs Import Declaration </doc_label> <doc_filename>cid.html</doc_filename> <doc_order>2</doc_order> <images_list> <image> <image_label>form 1</image_label> <image_filename>cid1.gif</image_filename> </image> </images_list> <doc_scope doc_type="g"/> 49

50 </doc> <doc> </doc> <doc> </doc> <doc> </doc> <doc> </doc> <doc> </doc> <doc_id>invoice</doc_id> <doc_label>commercial Invoice </doc_label> <doc_filename>invoice.html</doc_filename> <doc_order>3</doc_order> <images_list> <image> <image_label>commercial form</image_label> <image_filename>invoice.gif</image_filename> </image> </images_list> <doc_scope doc_type="g"/> <doc_id>cf_orig</doc_id> <doc_label>certificate of Origin </doc_label> <doc_filename>cf_orig.html</doc_filename> <doc_order>4</doc_order> <images_list> <image> <image_label>certificate form</image_label> <image_filename>cf_orig.gif</image_filename> </image> </images_list> <doc_scope doc_type="g"/> <doc_id>awb</doc_id> <doc_label>air Waybill </doc_label> <doc_filename>awb.html</doc_filename> <doc_order>5</doc_order> <images_list> <image> <image_label>air Waybil form</image_label> <image_filename>awb.gif</image_filename> </image> </images_list> <doc_scope doc_type="g"/> <doc_id>bl</doc_id> <doc_label>bill of Lading </doc_label> <doc_filename>bl.html</doc_filename> <doc_order>6</doc_order> <images_list> <image> <image_label>bill of lading form</image_label> <image_filename>bl.gif</image_filename> </image> </images_list> <doc_scope doc_type="g"/> <doc_id>cmr</doc_id> <doc_label>waybill </doc_label> <doc_filename>cmr.html</doc_filename> <doc_order>7</doc_order> <images_list> <image> <image_label>cmr form 1</image_label> <image_filename>cmr1.gif</image_filename> </image> <image> <image_label>cmr form 2</image_label> <image_filename>cmr2.gif</image_filename> </image> </images_list> <doc_scope doc_type="g"/> <doc_id>cf_ins</doc_id> <doc_label>certificate of Insurance </doc_label> <doc_filename>cf_ins.html</doc_filename> <doc_order>8</doc_order> 50

51 <doc> </doc> <doc> </doc> <doc> </doc> <doc> </doc> <doc> </doc> <doc> </doc> <doc> </doc> <doc> </doc> <doc_scope doc_type="g"/> <doc_id>plist</doc_id> <doc_label>packing List </doc_label> <doc_filename>plist</doc_filename> <doc_order>9</doc_order> <images_list> <image> <image_label>form 1</image_label> <image_filename>plist.gif</image_filename> </image> </images_list> <doc_scope doc_type="g"/> <doc_id>pre_ins</doc_id> <doc_label>pre-shipment Inspection </doc_label> <doc_filename>pre_ins.html</doc_filename> <doc_order>10</doc_order> <doc_scope doc_type="g"/> <doc_id>reg_imp</doc_id> <doc_label>import Registration </doc_label> <doc_filename>reg_imp.html</doc_filename> <doc_order>11</doc_order> <images_list> <image> <image_label>form 1</image_label> <image_filename>reg.gif</image_filename> </image> <image> <image_label>form 2</image_label> <image_filename>reg.gif</image_filename> </image> </images_list> <doc_scope doc_type="g"/> <doc_id>reg_cc</doc_id> <doc_label>registration with the Chamber of Commerce </doc_label> <doc_filename>reg_cc.html</doc_filename> <doc_order>12</doc_order> <doc_scope doc_type="s"/> <doc_id>cf_ana</doc_id> <doc_label>certificate of analysis</doc_label> <doc_filename>cf_ana.html</doc_filename> <doc_scope doc_type="s"/> <doc_id>a_cites</doc_id> <doc_label>approval to Import Endangered Species and Products Thereof </doc_label> <doc_filename>a_cites.html</doc_filename> <doc_scope doc_type="s"/> <doc_id>cf_vet</doc_id> <doc_label>veterinary Certificate </doc_label> <doc_filename>cf_vet.html</doc_filename> <doc_scope doc_type="s"/> <doc_id>cf_halal</doc_id> <doc_label>halal Certificate </doc_label> <doc_filename>cf_halal.html</doc_filename> <images_list> <image> <image_label>form 1</image_label> <image_filename>cf_halal.gif</image_filename> </image> </images_list> 51

52 </egif> </docs> <doc> </doc> <doc> </doc> <doc_scope doc_type="s"/> <doc_id>a_i_bree</doc_id> <doc_label>approval to Import Breeding Animals</doc_label> <doc_filename>a_i_bree.html</doc_filename> <doc_scope doc_type="s"/> <doc_id>prh_imp</doc_id> <doc_label>prohibited Imports</doc_label> <doc_filename>prh_imp.html</doc_filename> Filename : MAIF-IR10-01v003.xml 52

53 6.2. Display of example file in MADB The content of an XML file is rendered as follows in the market access application once uploaded view the Admin site and moved to production. 53

54 54