Enhanced RDFS: add resolved XSD datatypes for CGMES 2.4 profiles

[Haigutus]

Follow-up to the datatype discussion in #53 (and #49), which concluded that we "need to have RDFS that defines the datatype". Companion to the CGMES 3.0 Enhanced-RDFS issue.

Problem

CGMES 2.4 RDFS declare literal attribute types as CIM primitives, e.g. <cims:dataType rdf:resource="#Float"/> / #String, leaving the concrete XSD datatype unresolved in the profile itself. This forces datatype checks to rely on an external mapping and prevents generic SHACL validators from checking numeric/boolean values.

Proposal

Provide an Enhanced RDFS variant of the CGMES 2.4 profiles in which each literal attribute carries its resolved XSD datatype (e.g. rdfs:range xsd:float), enabling direct sh:datatype generation.

• The original 2.4 RDFS remain unchanged; the Enhanced variant is an additional artifact.
• The CIM→XSD mapping for cim16 already exists as the QoCDC datatype map CGMES_v2_4_constraints/ValidationConfiguration/DatatypesMapping/RDFdatatypes.rdf, so the Enhanced 2.4 RDFS can largely be produced from it.

Goal

A consistent "Enhanced RDFS (with XSD datatypes)" concept across NCP, CGMES 3.0 and CGMES 2.4.

Related

#53, #49, #1, and the CGMES 2.4 PROF / folder-alignment work (#64, #93, PR #94).

[Haigutus]

Companion (same Enhanced-XSD-RDFS proposal, other generation): #95 (CGMES 3.0). Related: #97 (CGMES 2.4 updated-header RDFS variant).

[VladimirAlexiev]

See #53 (comment) for implementation as SPARQL Update