Sveino / Inst4CIM-KG

Instance of CIM Knowledge Graph
Apache License 2.0
3 stars 1 forks source link

Meta-Props Duplicated Per Profile #10

Open VladimirAlexiev opened 1 month ago

VladimirAlexiev commented 1 month ago

CGMES (but not CGMES NC) Profile namespaces redefine the same meta properties several times. Here is the count of terms per namespace:

     39 dy
     13 tp
     13 eqbd
     13 eq
     12 sv
     12 ssh
     12 sc
     11 op
     11 gl
     11 dl

Let's get the terms of 4 namespaces and put them side by side:

grep -E '(dl|eq|tp|gl):' terms-uniq.txt
term1 term2 term3 term4
dl:isAbstract eq:isAbstract tp:isAbstract gl:isAbstract
dl:isCIMDatatype eq:isCIMDatatype
gl:isCompound
dl:isConst eq:isConst tp:isConst gl:isConst
tp:isDescription
eq:isEuropean tp:isEuropean
dl:isFixed eq:isFixed tp:isFixed gl:isFixed
dl:isPrimitive eq:isPrimitive tp:isPrimitive gl:isPrimitive
dl:isUnique eq:isUnique tp:isUnique gl:isUnique
eq:isdeprecated tp:isdeprecated
dl:isenum eq:isenum tp:isenum gl:isenum

All these are CIM meta-properties that should stay in the cims: namespace.

Consider the definition of cim:StreetAddress in GL:

cim:StreetAddress a owl:Class ;
  rdfs:label "StreetAddress"@en ;
  gl:Package "Package_GeographicalLocationProfile" ;
  gl:isCompound "True" ;
  skos:definition "General purpose street and postal address information."@en .

This also relates https://github.com/Sveino/Inst4CIM-KG/issues/5 and is an aspect of inconsistency: the same meta-prop should always be used with the same prefix.

VladimirAlexiev commented 1 month ago

The only possible use could be if the same term and meta-prop have different values for different profiles. But I haven't seen such cases, eg below multiplier is fixed in both profiles.

cim:Temperature.multiplier
  sc:isFixed "True ";
  dy:isFixed "True".