coordinate props should be xsd:decimal

Sveino / Inst4CIM-KG

Instance of CIM Knowledge Graph

Apache License 2.0

5 stars 1 forks source link

coordinate props should be xsd:decimal #96

Open VladimirAlexiev opened 1 month ago

VladimirAlexiev commented 1 month ago

CGMES-NC/ttl/GridDisturbance-AP-Voc-RDFS2020.ttl, CGMES/ttl/61970-600-2_GeographicalLocation-AP-Voc-RDFS2020_v3-0-0.ttl define cim:PositionPoint.xPosition as xsd:string. It's better if all coordinate props are declared xsd:decimal.

Sveino commented 1 month ago

I open a ticked on this before the latest release. This was rejected since some vendor where using text reference - I do not remember exactly. This is one of the reason for move with GeoSPARQL. I am hoping that we are able to address the recommondation or alternative to cim:Location to use GeoSPARQL in CIM18. So for CIM17 we need to add the validation that it is an xsd:decimal as part of of SHACL.

VladimirAlexiev commented 1 month ago

The value will still be a string, but there'll be an extra bit (datatype) to say what it is.

This cannot hurt consumption
But I can see why the vendor is hesitant to add this bit on production

Let's keep it open, maybe the vendor will agree one day.

This is a tiny change compared to the massive change of adding datatypes for 3704 props that declare a datatype. I wonder what will that vendor say to that? ;-)