- an XML list of all elements and attributes in the the XML template - without data (version 1.3, 2008-07-30)
- an XML list of only mandatory elements and attributes in the XML template - without data (version 1.3, 2008-07-30)
- documentation of the XML Schemata for the EuroFIR Food Data Transport Package 1.3 (version 1.1, 2009-08-29) 
- documentation of the XML Schemata for the EuroFIR Meta Data Transport Package 1.0 (version 1.1, 2009-08-29)  
- full documentation of the XML Schemata for EuroFIR Food Data and Meta Data transport Packages (version 1.1, 2009-08-29)

For an example of how the XML Food Data Transport Package 1.3 might look with data included, see this XML example.
 

1.  A static XML file with the LanguaL indexed food list (output from LanguaL FPI).

2.  A RESTful service on your server delivering your selected food composition data (for specific foodids) in the XML FDTP template format to the eSearch facility, i.e. script (ASP, PHP, Java, etc.), which is called with one or more foodid parameters, e.g.   http://somedomain.tld/Restfulservice.script?foodid=xxxxx, yyyyy,zzzzz, which delivers data for the three foodids xxxxx,yyyyy,zzzzz (see also the XML FDTP example just above).

For the upcoming EuroFIR Web Services you may also want to implement a RESTful service, which delivers the full list with the parameter “foodid=all”. The list of food ids is only limited by the size of the URL max length (see for example http://www.boutell.com/newfaq/misc/urllength.html). In order to avoid server errors on this, EuroFIR eSearch is splitting the request up in smaller bits, if the number of characters in the URL gets too long – also in order not to stress the server too much.
 

A specific sub-task group, TG3.1, led by KTL and involving DTU, UGR, MATIS, MRI, ETZH, IMR, BGU, POLYTEC, and DFI, will design and describe specifications to a request-response based Web service communication between EuroFIR partner websites. For this, the request interface has to be designed and the basic requests have to be defined. Then the first three websites using the Web services will be implemented by the month 54 and the rest by the month 57. The current eSearch will be expanded using the new specifications, and a new user interface for connecting the websites will be designed. The experience building the websites will be collected for dissemination to other partners as best practice guidelines. The sub-task group communicates on the closed Wiki based website hosted by KTL.