Skip to content

docs(compliance): drop stale v2.6/v2.7 XMI byte-identical claim #228

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
ottobolyos wants to merge 2 commits into
base: master
Choose a base branch
from
+2 −12
Draft

docs(compliance): drop stale v2.6/v2.7 XMI byte-identical claim #228

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
962ec4b
docs(compliance): drop stale v2.6/v2.7 byte-identical claim
ottobolyos Aug 17, 2026
47c0469
docs(compliance): drop sibling byte-identical claims — atomic fix per…
ottobolyos Aug 19, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 0 additions & 10 deletions docs/compliance/known-divergences.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down
2 changes: 1 addition & 1 deletion docs/compliance/per-version-matrix.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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)).
Expand Down
2 changes: 1 addition & 1 deletion docs/cookbook/migrate-versions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down