Release 2.3.0

Release 2.3.0 [30-Oct-2026]

cim-compare 2.3.0 compares user-defined tagged values, such as baseuri and baseprefix, which earlier releases never compared, and keeps the report's summary counts in view while you scroll. It also fixes three defects: since 2.2.0, diagram highlight outlines stopped partway down the elements they mark; link end and attribute metadata headings showed names in capitals; and metadata tables redlined changed names, unlike every other short value. One behaviour changes from 2.2.0: an element whose only change is a tagged value is now reported as changed. Visit the README or public site for full details.

Enhancement Issue #169:
User-defined tagged values, such as baseuri and baseprefix, have never been compared on any element, so a tag added, removed or changed on a package, class, attribute or association appeared nowhere in the comparison XML or the report. They are read from both forms EA's "UML 1.3 (XMI 1.1)" export writes (in the element's tag list, and as separate tags naming their element, which is how EA writes package tags) and compared on packages, classes, attributes, associations and association ends. The comparison XML records them as EA's own Compare Utility does, as a Tagged Values group under the element with one item per tag. The report shows a Tagged values section on packages and classes, a table in association cards and their ends, and an attribute's tags in its ⓘ metadata. An element whose only change is a tag is reported as changed. EA compare logs given as input show their tagged values the same way.

Enhancement Issue #175:
The summary counts (Packages, Classes, Diagrams) stay under the report header while you scroll, so a count filter is always one click away. A control at the right of the counts sets what stays in view: Off, Counts (the default) or Counts + legend. The choice is remembered in the browser, and the p key cycles it. The package outline and the elements you jump to sit below whatever is pinned. Printing is unchanged.

Defect Issue #165:
A diagram's highlight outlines often covered a class's name and stereotypes but stopped above its attributes. Since 2.2.0 (#139, #141), outlines are placed from the size the model stores for each element, measured against an SVG of the diagram. EA often draws an element taller than that stored size, for example when stereotypes are added to a class and EA draws the extra stereotype lines above its name, but the outline kept the stored height; only a wider drawing was taken into account. Each outline now takes the size EA drew the element at, in height as well as width. In a CIM16 comparison where extension packages add stereotypes to CIM classes, 878 of 2,058 outlines were too short; none are now. This affected reports from EA project files with any image type except EMF, and from XMI files with SVG images.

Defect Issue #172:
In a changed link's card, the heading over each end's table showed the class or role name in capitals with the rest of the heading, for example "SOURCE END — BASEVOLTAGE". The name now keeps its own case: "SOURCE END — BaseVoltage". The heading of an attribute's ⓘ metadata had the same problem ("ATTRIBUTE METADATA — OPERATINGQUANTITYTYPE") and is fixed the same way.

Defect Issue #179:
Metadata tables redlined a changed name or alias, though its baseline value is shown beside it, while every other short property in those tables shows the new value as plain text. Tables now redline only free text (notes); a renamed class, package or diagram shows its new name as plain text beside the old one, as a renamed attribute already did (#67). Redlines elsewhere are unchanged: descriptions, attribute notes and multiplicities, and role names and multiplicities in link cards.