Definition of an interface for a knowledge repository

  • warning: Parameter 1 to theme_field() expected to be a reference, value given in /var/www/drupal/drupal-6.28/includes/theme.inc on line 171.
  • warning: Parameter 1 to theme_field() expected to be a reference, value given in /var/www/drupal/drupal-6.28/includes/theme.inc on line 171.
  • warning: Parameter 1 to theme_field() expected to be a reference, value given in /var/www/drupal/drupal-6.28/includes/theme.inc on line 171.
  • warning: Parameter 1 to theme_field() expected to be a reference, value given in /var/www/drupal/drupal-6.28/includes/theme.inc on line 171.
  • warning: Parameter 1 to theme_field() expected to be a reference, value given in /var/www/drupal/drupal-6.28/includes/theme.inc on line 171.
  • warning: Parameter 1 to theme_field() expected to be a reference, value given in /var/www/drupal/drupal-6.28/includes/theme.inc on line 171.

The knowledge repository, identified as a system for delivering agricultural standards represented as encoded rules, consists of three primary elements. These elements are the catalogue server interface, through which the actual rule servers are discovered, the rule server interface and the encoding schema of the agricultural standards as rules. The encoding schema was specified as part of FutureFarm Deliverable 4.1.1. This document describes the server and catalogue interfaces and contains formal specifications as appendices.

The catalogue servers are a listing service for the rule servers to allow easy discovery of relevant rule servers for any given task. The rule servers have an interface similar to the catalogue servers and are intended to provide agricultural standards represented as a collection of rules and various metadata relevant to the use of the standards. The encoding scheme for the rules is an XML schema that describes how the agricultural standards and their metadata are encoded for convenient automatic management.

All of the described services are based on REST which is a simple yet powerful mechanism for implementing Web-services without resorting to the use of the more complex SOAP and related technologies. Existing technologies have been used extensively throughout the development process.

AttachmentSize
FFD4.2_Repository_Interface_Definition_final.pdf107.84 KB
FFD4.2_Appendix_A_final.pdf136.9 KB
FFD4.2_Appendix_B_final.pdf147.54 KB
Powered by Drupal