Sveino
commented
1 year ago Maybe a better (not correct syntax);
{
"@context": {
"@version": 1.1,
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"cim": "http://iec.ch/TC57/CIM100#",
"md": "http://iec.ch/TC57/61970-552/ModelDescription/1#",
"eu": "http://iec.ch/TC57/CIM100-European#",
"dm": "http://iec.ch/TC57/61970-552/DifferenceModel/1#",
"dm:DifferenceModel": {
"@id": "urn:uuid:f52f12c3-db10-4d41-a9f2-b1fe29ab4d6d",
"@container": ["@graph", "@id"]
}
},
"dm:DifferenceModel": {
"@none": [{
"@id": "urn:uuid:9d58e5bb-834c-4faa-928c-7da0bb1497d9",
"@type": "cim:ACLineSegment",
"cim:Conductor.length": {
"cim:Length.value": 50.0
}
}, {
"@id": "urn:uuid:9d58e5bb-834c-4faa-928c-7da0bb1497d9",
"@type": "cim:ACLineSegment",
"cim:Conductor.length": {
"cim:Length.value": 55.0
}
}]
}
}
ThomasRanvikEriksen
As part of creating a CIMXML to/from CIMJSON-LD converter we would need to define how the DifferenceModel file defined in the IEC 61970-552 CIMXML Model exchange format . A proposal describing the CIMXML DifferenceModel was presented for the W3C and got Tim Berners-Lee support, but was still not approved. Being able to exchange and validate changes to a digital twin model by change set is critical. It is also very useful for handling alternative changes into the future. The changes would need to be accommodated with meta-data.
A ACLineSegment object is described with the following property:
Changing the ACLineSegment object by changing the length from 50 meter to 55 meter would look like:
reverseDifferences describe the dataset that will be removed (delete). forwardDifferences describe the dataset that will be added (add) An update is describe as reverseDifferences and forwardDifferences (as shown in the example).
Proposal 1: Single Graph
Alt 2: Two graph
I do not think the example is correct. I think we might need to use the container structure shown in Example 122 in the JSON-LD 1.1 standard.
Relevant links: