GitHub user VladimirAlexiev added a comment to the discussion: CIM XML (IEC 61970-552) as Lang based on current RDF/XML parser (read-only at first)
@arne-bdt: I made similar fixes towards in the fall of 2024. They use external tools and thus are very short: - https://github.com/Sveino/Inst4CIM-KG/blob/develop/rdf-improved/cim-urn-uuid.pl perl script that replaces the defective CIM XML URLs with "urn:uuid:" - https://github.com/Sveino/Inst4CIM-KG/blob/develop/rdf-improved/cim-trig.pl perl script that converts CIM XML to Trig (turlte with graphs) by splitting a DifferenceModel into `forward/backwardDifferences` graphs - https://github.com/Sveino/Inst4CIM-KG/blob/develop/rdf-improved/fix-datatypes-new.ru: SPARQL update that adds datatypes based on a long list of properties. Can be used on the command line (eg with jena's `update`) or in a semantic repository > using the datatypes from the matching profile definitions. This requires to > look into ... "md:Model.profile" - the values are like `md:Model.profile <http://iec.ch/TC57/ns/CIM/Topology-EU/3.0>` - Actual ontology URLs are like `<http://iec.ch/TC57/ns/CIM/Topology-EU#Ontology>` - whereas `owl:versionIRI <http://iec.ch/TC57/ns/CIM/Topology-EU/3.0>` so this can be matched to `md:Model.profile` Many props are redundantly defined in multiple profiles. So I use a global list of props. One needs to be vey careful about the `cim` (and `nc`) namespaces that have been changing in the past. > datatypes are mostly special datatypes like "ActivePower" which typically can > be mapped to a XSDDatatype like XSDfloat CIM datatypes are modeled wrong, see https://github.com/Sveino/Inst4CIM-KG/tree/develop/rdfs-improved#quantitykinds-and-units-of-measure https://github.com/Sveino/Inst4CIM-KG/blob/develop/rdfs-improved/fix-all.ru fixes this (and a number of other problems in the **ontologies**) Cheers! GitHub link: https://github.com/apache/jena/discussions/2529#discussioncomment-17474624 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
