Meta-Props Duplicated Per Profile

[VladimirAlexiev]

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 .

• gl:isCompound should be cims:isCompound since it's part of the CIM metamodel, not part of GL.
• gl:Package should be cims:package for the same reason (and should start in lowercase)

This also relates #5 and is an aspect of inconsistency:
the same meta-prop should always be used with the same prefix.

[VladimirAlexiev]

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".

• Even if there's such a need, there are better ways to model it than replicate the meta-props.
• You see another inconsistency: in one case "True " is misspelled with a space