Redundant object properties in vsso-core

[jdacoello]

Current version of vsso-core has two object properties (hasStaticVehicleProperty, hasDynamicVehicleProperty) that should be merged into one (hasVehicleProperty).

The distinction between both is already handled by the class hierarchy as:

• VehicleProperty
  • StaticVehicleProperty
  • DynamicVehicleProperty

Thus, having also two different properties is only giving space for potential mistakes when populating the graph in practice.
Even with just one property, one can easy retrieve with SPARQL the desired information:

What are all the static vehicle properties?

SELECT * WHERE { 
?vehicle vsso-core:hasVehicleProperty ?svp .
?svp a vsso-core:StaticVehicleProperty }

What are all the dynamic vehicle properties?

SELECT * WHERE { 
?vehicle vsso-core:hasVehicleProperty ?dvp .
?dvp a vsso-core:DynamicVehicleProperty }

[felix-loesch]

I agree. This can be simplified.