Follow-up to the datatype discussion in #53 (and #49), which concluded that we "need to have RDFS that defines the datatype".
Problem
CGMES 3.0 RDFS declare literal attribute types as CIM primitives, e.g. <cims:dataType rdf:resource="#Float"/>, leaving the concrete XSD datatype (xsd:float, xsd:integer, xsd:string, xsd:boolean, xsd:dateTime, …) unresolved in the profile itself. Generic RDF/SHACL tooling therefore cannot type-check numeric/boolean values without an external mapping, and validators default literals to strings (see #53).
Proposal
Provide an Enhanced RDFS variant of the CGMES 3.0 profiles in which each literal attribute carries its resolved XSD datatype (e.g. rdfs:range xsd:float), so that sh:datatype constraints can be generated directly and native libraries can validate values.
- The original RDFS remain unchanged; the Enhanced variant is an additional, tooling-friendly artifact.
- Prior art: the CIM→XSD resolution already captured in the QoCDC datatype map
CGMES_v2_4_constraints/ValidationConfiguration/DatatypesMapping/RDFdatatypes.rdf — note that is cim16, so CGMES 3.0 (CIM100) needs its own mapping.
Goal
A consistent "Enhanced RDFS (with XSD datatypes)" concept across NCP, CGMES 3.0 and CGMES 2.4 (companion issue for 2.4).
Related
#53, #49, #92, #1.
Follow-up to the datatype discussion in #53 (and #49), which concluded that we "need to have RDFS that defines the datatype".
Problem
CGMES 3.0 RDFS declare literal attribute types as CIM primitives, e.g.
<cims:dataType rdf:resource="#Float"/>, leaving the concrete XSD datatype (xsd:float,xsd:integer,xsd:string,xsd:boolean,xsd:dateTime, …) unresolved in the profile itself. Generic RDF/SHACL tooling therefore cannot type-check numeric/boolean values without an external mapping, and validators default literals to strings (see #53).Proposal
Provide an Enhanced RDFS variant of the CGMES 3.0 profiles in which each literal attribute carries its resolved XSD datatype (e.g.
rdfs:range xsd:float), so thatsh:datatypeconstraints can be generated directly and native libraries can validate values.CGMES_v2_4_constraints/ValidationConfiguration/DatatypesMapping/RDFdatatypes.rdf— note that iscim16, so CGMES 3.0 (CIM100) needs its own mapping.Goal
A consistent "Enhanced RDFS (with XSD datatypes)" concept across NCP, CGMES 3.0 and CGMES 2.4 (companion issue for 2.4).
Related
#53, #49, #92, #1.