|
1
|
In Annex 1 - Technical requirements, SECTION II – Import Formalities, item 3.1. Structure, subitem “Images [...]
|
the
![img description]() tag is allowed and will be added to the technical annex.
|
04/08/2015
|
|
|
2
|
How is the estimated value about 4 900 000 EUR distributed to each lot?
|
As indicated in the Terms of Reference, chapter 6, the budget for all lots submitted is estimated not [...]
|
05/08/2015
|
|
|
5
|
What do you exactly mean with "...complete dataset for every 10 lots submitted in lots..."?
|
The technical offer must include at least one complete dataset as described in the Annex 1 – Technical [...]
|
05/08/2015
|
|
|
4
|
According to Annex 1 - Technical requirements, SECTION II – Import Formalities, item 4.1., tabular data [...]
|
As described in the technical annex, section II item 4.1, please use a subset of the standard HTML mark-up [...]
|
05/08/2015
|
|
|
3
|
The Terms of Reference require the submission of one complete sample dataset for every ten lots for both [...]
|
Yes, this is correct
|
05/08/2015
|
|
|
7
|
In Annex 1 - Technical requirements, SECTION II – Import Formalities, item 3.1. Structure, subitem “Images [...]
|
Any relevant type of documents are to be taken into account.
|
05/08/2015
|
|
|
8
|
In the Terms of Reference, page 15, it is stated that “the indicative list of general requirements contained [...]
|
Consider the file MAIF-IR10- 01v003.xml as reference for the indicative list of general requirements. [...]
|
05/08/2015
|
|
|
20
|
In the Terms of Reference, page 15, it is stated that “the indicative list of specific requirements contained [...]
|
Consider the file MAIF-IR10- 01v003.xml as reference for the indicative list of specific requirements [...]
|
05/08/2015
|
|
|
10
|
Is the limit of 3000 characters for the “ModifSummary element” of Annex 1 - Technical requirements, SECTION [...]
|
yes
|
05/08/2015
|
|
|
19
|
The example overview file according to Annex 1 - Technical requirements, SECTION II – Import Formalities [...]
|
yes
|
05/08/2015
|
|
|
18
|
In the Terms of Reference, page 14, it is stated that “the pattern used for the documentation needs for [...]
|
Please use the example file 'overview.html' as (1) an example of the format ('pattern') to be used and [...]
|
05/08/2015
|
|
|
17
|
The example overview file according to Annex 1 - Technical requirements, SECTION II – Import Formalities [...]
|
No
|
05/08/2015
|
|
|
16
|
The example overview file according to Annex 1 - Technical requirements, SECTION II – Import Formalities [...]
|
yes
|
05/08/2015
|
|
|
15
|
The example overview file according to Annex 1 - Technical requirements, SECTION II – Import Formalities [...]
|
Content of the link is not relevant, consider this example :
|
05/08/2015
|
|
|
14
|
According to Annex 1 - Technical requirements, SECTION II – Import Formalities, item 4.1. the use of [...]
|
As explained the elements specified in SECTION II –Import Formalities, item 4.1 are allowed. Attributes [...]
|
05/08/2015
|
|
|
13
|
According to Annex 1 - Technical requirements, SECTION II – Import Formalities, item 4.1. the use of [...]
|
As the technical annex does not include the use of the "class" attribute, it shall not be used.
|
05/08/2015
|
|
|
12
|
Is it possible the get an Information about the user traffic of the database?
|
Our site registers about 4000 unique visitors per day.
|
05/08/2015
|
|
|
11
|
After ending the contract remains the content in the Database and must be updated by the new contractor [...]
|
The licence for the current datasets allows the use of the current datasets until 31th december 2015 [...]
|
05/08/2015
|
|
|
9
|
After ending the contract will the content of the databes be deleted and must be refilled by the new [...]
|
The existing datasets will be replaced by the datasets provided by the new contractor.
|
05/08/2015
|
|
|
6
|
Must the Content bought from the current contractor?
|
The content does not need to be bought from the current contractor.
|
05/08/2015
|
|
|
21
|
In Annex 1 - Technical requirements, SECTION II – Import Formalities, item 4.1. the tag
is not part [...]
|
As stated In Annex 1 - Technical requirements, SECTION II – Import Formalities, item 4.1. the tag
is [...]
|
06/08/2015
|
|
|
23
|
In Annex 1 - Technical requirements, SECTION I – Applied Tariffs, chapter 4, the , and elements are [...]
|
As stated in all the examples (MAAT-CA11-01v015.xml, MAAT-Z108-01v011.xml and MAAT-Z211-01v016.xml) and [...]
|
11/08/2015
|
|
|
22
|
In Annex 1 - Technical requirements, SECTION I – Applied Tariffs, chapter 4, the element is not listed [...]
|
As shown in the example MAAT-CA11-01v015.xml included in the documentation, HTML is allowed in
|
11/08/2015
|
|
|
25
|
Question 11 (Content Database) of this Call for tenders question list regarding the need to deliver new [...]
|
Yes, this is correct.
|
17/08/2015
|
|
|
24
|
In the exclusive list of tags in Annex 1 - Technical requirements, SECTION I – Applied Tariffs, chapter [...]
|
and elements are allowed to indicate subscript and superscript respectively. Technical annex will be [...]
|
13/08/2015
|
|