Use a Characteristic generic hasDimension predicate instead of hasNutrientDimension, hasPhysicalDimension and hasAllergenDimension

[lecoqlibre]

Does it make sense to replace hasNutrientDimension, hasPhysicalDimension and hasAllergenDimension from NutrientCharacteristic, PhysicalCharacteristic and AllergenCharacteristic with just hasDimension like in the following snippet ?

      "dfc-b:hasNutrientCharacteristic": {
          "@type":"dfc-b:NutrientCharacteristic",
          "dfc-b:hasDimension":"dfc-m:Magnesium",
          "dfc-b:hasUnit":"dfc-m:Gram",
          "dfc-b:value":"10"
      },
      "dfc-b:hasPhysicalCharacteristic": {
          "@type":"dfc-b:PhysicalCharacteristic",
          "dfc-b:hasDimension":"dfc-m:Weight",
          "dfc-b:hasUnit":"dfc-m:Gram",
          "dfc-b:value":"100"
      },
      "dfc-b:hasAllergenCharacteristic": {
          "@type":"dfc-b:AllergenCharacteristic",
          "dfc-b:hasDimension":"dfc-m:allergenCharacteristic1",
          "dfc-b:hasUnit":"dfc-m:Allenit1",
          "dfc-b:value":"1"
      }

Doing so would ease the source code of the connector as one super class Characteristic could be used as a base class for each derived NutrientCharacteristic, PhysicalCharacteristic and AllergenCharacteristic classes.