You are here

WP5 - Karel Charvat: White paper for AgriXchange Strategic Research Agenda

This document is intended as discussion material for future vision of strategic research priorities in the area of ICT and standardization for AgriFood sector. This document is based on previous work done mainly inside of EFITA conferences and studies related to ICT adoption, on the Strategic Research Agenda of Ami@NetFood program, results of c@r IPproject and results of FutureFarm Knowledge Management Visions. Document also reflect new principles and priorities, which are expressed in Digital Agenda for Europe and 2020 and there is intention include Rural and AgriFood ICT as important aspect of Digital Agenda for Europe and 2020.
This document now developed into the Cologne declaration to be discussed at the GeoFARMatics conference.



Ewald Petutshnig, Walter Mayer:
1. A first “simple” step could be the use of a so called “Trust Centre”. A single server, that stores and handles data according to the users’ permissions.
2. As a second step this server is spread to several other servers (or integrated into cloud), but as in cloud, it should seamlessly integrate, and no one should notice the presence of more than one server – transparency (like Google does: I don’t know where the server is located that executes my search query).
Furthermore the server(s) should be scalable (extending the server’s capacity and performance should be very easy).

Two notes from my side:

1. I like that sentence:
"Integration and orchestration among services based on semantic integration of the collaboration activities, including semantic compatibility for information and services, as well as ontologies for collaboration is priority for future solutions."
Because it hints at the real problem we have:
There are standards out there, that are only waiting to be used: GML/WFS/WPS (OGC) for geospatial information, ISOBUS for machinery data exchange, ebXML for business data, agroXML for documentation of farmers practices in a whole crop production process etc. The current gap however is, that there is no integrative view onto all of this data. A WFS can not interoperate with a ebXML MS, data from ISOBUS can not be integrated with GML data or agroXML data. Now you may say: Let's focus on only one standard and try to force the use of it to everybody. That will not work either, because standards are tailored to a certain purpose and work best under the conditions they were designed for and will not work under other conditions. So we have a real interoperability problem and ontologies may be a way to overcome that problem at least in part. Maybe focus on that aspect even a little more in the paper.

2. Include new architectural patterns like ReSTful web services, Web Oriented Architecture, Ressource Oriented Architecture and potential advantages of building a SOA that way in the paper. As it currently stands, SOA may be confused by the reader as only standing for the technology that was connected with it about five years ago: RPC-/message-orientation/SOAP etc. and that is kind of "overcome" and old-fashioned by now. The next generation of architectural patterns has already spread out on the internet and we need to face that.

Daniel from KTBL