IPM Coalition

integrated pest management



A schema provides a detailed technical description of how data points should be represented. They are important for both technical and semantic interoperability.

For example ‘100 kg’ might be broken down into three fields:

  • 100 written as an integer (i.e. entered into a field where only whole number values are valid, and values such as ‘one hundred’ or ‘100.34’ or ‘approx 100’ would be rejected)
  • KG written as a value from the UNCEFACT Recommendation 20 codelist of units of measure, so that the schema can rely upon the external technical definitions of units of measure maintained by UNCEFACT, and any available conversion factors they may publish.
  • estimated written as the value from a codelist[1] maintained in the schema to record the measurement accuracy

A schema would also specify the character encoding data should be represented within, and the way data should be serialized to support exchange of data between systems.


[1] Codelists are a list of potential values that a data point may take, either from an external source (eg ISO country codes), or custom for a particular standard - for example, the measurement accuracy might be expressed as “estimated” or “weighed”

There is currently no content classified with this term.

+ Feedback