CGMES 2.4: add RDFS variant with the updated (OWL/DCAT) profile header used by NCP and CGMES 3.0

[Haigutus]

Context

CGMES 2.4 RDFS carry profile metadata under the old entsoe:<Profile>Version header (the baseUML / shortName / entsoeURI / entsoeUML = entsoe_v2.4.15 isFixed fields). NCP and CGMES 3.0 instead use the updated header: an owl:Ontology with dcterms/dcat metadata — dcat:keyword, owl:versionIRI, owl:versionInfo, etc. (see the README section "Addition of header schema for CGMES v3.0" and #37).

Proposal

Add a CGMES 2.4 RDFS variant whose profile header follows the updated NCP / CGMES 3.0 convention, so the same tooling (PROF generation, header/reference checks, metadata harvesting) works uniformly across NCP, CGMES 3.0 and CGMES 2.4.

The original 2.4 RDFS must remain untouched — this is an additional variant, not a rewrite of the released artifacts.

Benefits

• Uniform, machine-readable profile metadata across all releases.
• Enables profile-descriptor / PROF generation from a single header shape. The 2.4 PROF work in Improvement: Add PROF also for CGMES 2.4 #64 / Folder Structure: Align CGMES 2.4 folder structure with NCP / CGMES 3.0 #93 / PR Add PROF descriptors for CGMES 2.4 and align folder structure #94 currently has to read the old entsoe:<Profile>Version header; an updated-header variant would let it use the same path as NCP / CGMES 3.0.

Related

#37 (NC header references), #1 (header SHACL, "v2.4 enhanced"), #93.

[Haigutus]

Related: #95 and #96 (Enhanced RDFS with resolved XSD datatypes for CGMES 3.0 / 2.4).