remove spaces and lang tags from key values

[VladimirAlexiev]

Key values must be spelled with ultimate care because... well, they are key. This is similar to https://github.com/Sveino/Inst4CIM-KG/issues/6 but worse.

Extraneous spaces in key values are NOK because:

• People will use these values in queries
• In some cases SPARQL updates will upgrade strings to things, i.e. use them in URLs

Bad examples that come from https://github.com/Sveino/Inst4CIM-KG/issues/10, https://github.com/Sveino/Inst4CIM-KG/issues/38:

cim:UnitSymbol.VA a owl:NamedIndividual, owl:Thing ;
  rdfs:label "VA "@en ;
  eq:isenum "True" ;

cim:UnitMultiplier.M a owl:NamedIndividual, owl:Thing ;
  rdfs:label "M "@en ;

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

• "VA" and "M" are SI unit and multiplier. SI is international, so these codes cannot have lang tags
• The last one is worst: some profiles map isFixed to a value with space, others without a space

[griddigit-ci]

On the spaces. It will be good to know in which RDFS you find this. I checked in UML and I see that there are no spaces. It could be a bug in RDFS export if this is only in the 501 Ed2 Beta - I expect this is a bug in CimSyntaxGen prototype that was done 4 years ago

Also as a background. It looks like we have an agreement now to exchange in basic units i.e. no M but in form 1e6

[VladimirAlexiev]

@griddigit-ci

• this is https://cim.ucaiug.io/ns#UnitSymbol.VA. It is defined in IEC61970-600-2_CGMES_3_0_0_RDFS_501Ed2CD_DL and 7 more profiles
• See https://github.com/Sveino/Inst4CIM-KG/issues/38 about "M"

[VladimirAlexiev]

We checked, this only happens in Ed2 not in 2020.