examine props-same-name-different-range for errors

(Split from https://github.com/Sveino/Inst4CIM-KG/issues/100) rdf-improved/props-same-name-different-range.csv shows 583 range differences between same-named props.

Please examine it for ontological errors. Here is a count by prop name. I've marked <<< differences that are errors, and ??? that for me are questionable .

 perl -pe 's{.*?\.(.*?),.*}{$1}' props-same-name-different-range.csv |sort|uniq -c|sort -rn
    253 kind
     79 value
     45 mode
     30 Terminal
     23 RemedialAction
     21 kd     ??? boolean vs float
     17 uelin  ??? boolean vs cim:ExcIEEEST1AUELselectorKind, cim:ExcST7BUELselectorKind, cim:ExcST7BUELselectorKind...
     14 k1     ??? boolean vs float
      9 pPccControl
      9 operatingMode
      8 oelin
      8 m
      7 type
      7 normalValue
      7 Region
      6 exclim
      5 direction
      5 Measurements
      5 DCTerminals
      3 step
      2 absoluteValue  ??? imho nc:GateInputPin.absoluteValue (xsd:boolean) should be called `useAbsoluteValue`
      1 zPosition  <<< float is right, string is wrong
      1 yPosition  <<<
      1 xPosition  <<<
      1 version   <<< md:Model.version xsd:integer is wrong, dcat:Resource.version xsd:string is right
      1 startTime
      1 section
      1 publisher
      1 minimumOffTime  ??? cim:GeneratingUnit.minimumOffTime xsd:float vs nc:PowerBidSchedule.minimumOffTime,xsd:duration
      1 governorControl
      1 fbf    ??? cim:ExcREXSFeedbackSignalKind vs xsd:boolean
      1 endTime
      1 ProposingEntity
      1 LoadGroup
      1 Limits
      1 LimitSets
      1 LimitSet
      1 EnergyConsumers
      1 EnergyConnectionSchedule
      1 DCConductingEquipment
      1 CsConverterSchedule

Sveino / Inst4CIM-KG

examine props-same-name-different-range for errors #124