From 962ec4ba62182dfc61818645904e50c3cc4e768f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Otto=20Boly=C3=B3s?= Date: Mon, 17 Aug 2026 22:10:38 +0200 Subject: [PATCH 1/2] docs(compliance): drop stale v2.6/v2.7 byte-identical claim --- docs/compliance/known-divergences.md | 10 ---------- 1 file changed, 10 deletions(-) diff --git a/docs/compliance/known-divergences.md b/docs/compliance/known-divergences.md index 8d2a28d08..bfa997928 100644 --- a/docs/compliance/known-divergences.md +++ b/docs/compliance/known-divergences.md @@ -18,16 +18,6 @@ The MTConnect Standard's three formal sources disagree on whether an `ASSET_COUN **Filed**: [Redmine #3890](https://projects.mtconnect.org/issues/3890) (Agent Working Group). -## v2.6 SysML XMI byte-identical to v2.7 - -**Disagreement**: spec release versioning. - -The published v2.6 SysML XMI file (`MTConnectSysMLModel_V2.6.xml`) is byte-identical to v2.7. v2.6 and v2.7 should differ — the spec release cadence assumes each major increment has at least one substantive XMI change — and the byte-identical publication suggests a release-engineering mistake at the standard body, not a deliberate "no-change" version. - -**Library posture**: `MTConnectVersions.Version26` and `Version27` are both shipped as distinct constants because the spec body advertises both as released versions. Any type's `MinimumVersion = Version26` is treated as equivalent to `Version27` for serialization gating. - -**Filed**: [Redmine #3892](https://projects.mtconnect.org/issues/3892) (SysML Model Related Issues). - ## DataSet vs Table result class disagreement **Disagreement**: SysML XMI vs XSD. From 47c0469ecb359c2383dea0cc371f353bf17009fa Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Otto=20Boly=C3=B3s?= Date: Wed, 19 Aug 2026 17:53:25 +0200 Subject: [PATCH 2/2] =?UTF-8?q?docs(compliance):=20drop=20sibling=20byte-i?= =?UTF-8?q?dentical=20claims=20=E2=80=94=20atomic=20fix=20per=20bug-class?= =?UTF-8?q?=20rule?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- docs/compliance/per-version-matrix.md | 2 +- docs/cookbook/migrate-versions.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/compliance/per-version-matrix.md b/docs/compliance/per-version-matrix.md index a8291094d..42efc6b0c 100644 --- a/docs/compliance/per-version-matrix.md +++ b/docs/compliance/per-version-matrix.md @@ -51,7 +51,7 @@ A subset of spec-version-introduced types the matrix tracks (the full inventory - **v2.3**: `Quality` field on Observation made first-class. - **v2.4**: Rich-template Pallet measurements (`HeightMeasurement`, `WidthMeasurement`, `LoadedHeightMeasurement`, etc.) replace free-form `Measurement`. - **v2.5**: spec-internal cleanup; no new wire-format-visible types. -- **v2.6**: per the spec's `Part_3` cleanup; v2.6 SysML XMI is byte-identical to v2.7 per the spec's own publication (see [Compliance: Known divergences](/compliance/known-divergences)). +- **v2.6**: per the spec's `Part_3` cleanup; introduces new asset-linkage types (`AssociatedAssetId`, `AssetAdded`) and `CuttingTorch` component. - **v2.7**: spec cleanup; multiple minor enum and attribute additions. Every introduction is auditable through the generated `.g.cs` files under `libraries/MTConnect.NET-Common/`, which carry the per-type `MinimumVersion` value sourced from the SysML model's `introducedAtVersion` ([`mtconnect/mtconnect_sysml_model`](https://github.com/mtconnect/mtconnect_sysml_model)). diff --git a/docs/cookbook/migrate-versions.md b/docs/cookbook/migrate-versions.md index 928f40e8c..7d727e2af 100644 --- a/docs/cookbook/migrate-versions.md +++ b/docs/cookbook/migrate-versions.md @@ -24,7 +24,7 @@ The high-frequency-of-impact version transitions: | v2.2 → v2.3 | low | `Quality` first-class on Observations | new `quality` attribute on Observations | | v2.3 → v2.4 | medium | rich-template Pallet measurements (typed classes replace free-form `Measurement`) | new Measurement element names in `MTConnectAssets` | | v2.4 → v2.5 | low | spec-internal cleanup; no new wire-format-visible types | no new attributes | -| v2.5 → v2.6 | low | v2.6 XMI is byte-identical to v2.7 in the published spec | no wire-format change | +| v2.5 → v2.6 | low | new asset-linkage types + `CuttingTorch` component | additive; no breaking changes | | v2.6 → v2.7 | low | spec cleanup; minor attribute additions | no breaking wire-format changes | The "impact" column is the typical code-side surface area for a consumer / agent author. None of the transitions above are forced-rewrite; the library handles each through version-aware serialization.