Changes

Jump to navigation Jump to search
889 bytes added ,  10:08, 21 August 2018
Added normalized ingredients
Line 45: Line 45:  
The basic input are the individuals. So far only the ingredients have been identified as necessary.
 
The basic input are the individuals. So far only the ingredients have been identified as necessary.
   −
====Ingredients ====
+
==== Raw ingredients ====
The creation of the ontology starts with instances. These are the ingredients as found on in the ingredient lists. An instance is defined as the the text between ingredient dividers. This includes any percentage, organic markup and allergen markup. In combination with the language used, it gives a first indication of the ingredient class. For the same class multiple instances are possible.
+
The creation of the ontology starts with the ingredients as found on the ingredient lists. A ''raw ingredient'' is defined as the the text between two ingredient dividers (where are these defined?). This might include any percentage, organic markup, allergen markup, origin and sub-ingredients. In combination with the language used, it gives a first indication of the ingredient class.
   −
Any new ingredient individual must have a data property, which defines the data corresponding to the individual. The data property ''hasName valueString'' is used to infer the corresponding classes. It is assumed that the valueString has the format languageCode:string.
+
==== Normalized ingredients ====
 +
The ''raw ingredients'' must be transformed to ''normalized ingredients''. A ''normalized ingredient'' is a single string in a western script (assumes that the western script can be read by any one in the world). A ''normalized ingredient'' is preceded by the language code of the ingredient. Usually this in english if the translation is available. (It is possible that the from language is needed for a better comprehension when classifying ingredients).
 +
 
 +
Normalizing ingredients implies that any variant of an an ingredient in any language is mapped onto a single name. The normalizing procedure is mainly going through a pattern recognition procedure.
 +
 
 +
For protégé this implies that any normalized ingredient individual must have a data property, which defines the data corresponding to the individual. The data property ''hasName valueString'' is used to infer the corresponding classes. It is assumed that the valueString has the format languageCode:string. This data property can then be used to classify an ingredient. It is possible that the other information of the product is required for a better classification.
    
=== Classes ===
 
=== Classes ===
3,393

edits

Navigation menu