Release 2.2.0

[tviegut]

Release 2.2.0 [01-Oct-2024]

CIMTool 2.2.0 is a minor release with both enhancements and important defect fixes.

Enhancement Issue #116:
With the recent introduction of UUID and URI in CIM18 CIMTool was updated to support the new domain types.

Enhancement Issue #141:
CIMTool was updated to support Sparx EA IDs within the intermediary internal XML representation that it generates and makes available for use by custom XSLT transform builders. This update was a part of R&D work being done within the standards community as part of potential use of LinkML as a semantic representation. As a result the LinkML builder introduced in *CIMTool 2.1.0 has been updated to include ea_guid in its generated output. This can be used for more direct traceability to the UML elements (classes, attributes, associations, etc.) as natively identified within a Sparx EA UML model. Note that ongoing work on the IEC 61970-501 Ed 2.0 draft standard is currently exploring LinkML as a semantic representation for the CIM.

Enhancement Issue #142:
A new alpha release of a CIMTool builder is introduced that generates IEC 61970-501 Ed 2.0 draft spec RDFS. This is for experimentation purposes only and will be updated across releases to reflect the latest development of Ed 2.0 of the 501 standards.

Enhancement Issue #143:
Introduced in this release is support for the generation of UML class diagrams for graphical representation of your profile definitions in CIMTool. PlantUML is used as the internal representation due to its ability to meet a wide variety of requirements within the CIM and IEC standards community. Amongst these requirements has includes research in leveraging AsciiDoc for DevOps based standards publication generation. In addition, PlantUML diagrams can be included in Draw.io (newly named Diagrams.net) diagrams. PlantUML can easily be integrated into AsciiDoc, Markdown, or in online contexts that leverage PlantML plugins to integrate diagrams.. This initial release includes PNG and SVG export of your PlantUML diagrams along with visual real-time visualization of invalid or incomplete elements in your profile as you build it. Visit the CIMTool website for forthcoming instructional videos on how to utilize new features. The use of PlantUML class diagrams for validating a profile will be included.

Defect Issue #154:
The CIMTool RDFS2020 builder made available in the 2.0.0 release required additional development to both fix areas not in proper alignment with that generated by CimConteXtor. It should be noted that the builder currently generates RDFS2020 schema's with "flattened" CIMDatatypes (i.e. value, unit, multplier attributes note defined within the generated RDFS). The final development for generating the "unflattened" CIMDatatypes (i.e. that explicitly define value, unit, multiplier, etc.) will be in a future release.

Defect Issue #156:
A post CIMTool 2.1.0 release task was to extensively test and address known issues related to profiling custom extensions using the newly supported 64-bit EA 16.x .qea, .qeax, and '.feap' project file types introduced in 2.1.0. This was decided to allow for 2.1.0 to be released to end users that only needed to profile using normative CIM without extensions. The outcome of this effort allows for profiling using a single EA project file (e.g. .qea or .eap) as your schema via the use of the baseuri tagged value for specifying the namespaces for your extensions extensions with the .eap/.qea project file. The resulting behavior when profiling using these new schema formats is designed to mirror the same behavior observed when using baseuri with multiple .xmi files to model extensions.

Enhancement Issue #155:
An new radio button has been added to the namespace list on the "Import Schema" dialog. The option allows selection of the existing namespace schema to be selected when re-importing a new version of the same named schema. When selected the namespace field auto-populate with the existing namespace. This solves a usability issue for end users who are working against base CIM with custom extensions and who need iteratively to re-import schema changes as their model evolves. It eliminates end users exiting the dialog in order to copy the namespace in the preferences screen to be able to paste a custom namespace into the field.

NOTE: This release does not yet address the issues as reported in the 2.0.1 release notes. Fixes for custom extensions in RDFS XSLT builders is now targeted for the 2.3.0 release.

---

This discussion was created from the release Release 2.2.0.