The MTConnect Standard is published through four artifacts — SysML XMI, XSDs, prose, cppagent reference — and they occasionally disagree.
This page catalogues the divergences MTConnect.NET has identified, where they were filed upstream for resolution, and which artifact the library currently follows.
Every divergence has been filed against the standard body's tracker at projects.mtconnect.org. The Redmine ticket numbers below are the canonical references; visit them for the standard maintainers' resolution timeline.
ASSET_COUNT Default Representation
Disagreement: SysML XMI / XSD vs cppagent.
The MTConnect Standard's three formal sources disagree on whether an ASSET_COUNT DataItem defaults to representation="VALUE" (scalar) or representation="DATA_SET":
- SysML XMI declares
AssetCount.result : integeras auml:DataType, not auml:Class. The spec's own rule ("ifDataItem::representationis not specified, it MUST be determined to beVALUE") yields VALUE. - XSD declares the canonical
AssetCountelement assubstitutionGroup='IntegerEvent'withxs:simpleContent— a scalar. ParallelAssetCountDataSetandAssetCountTableelement declarations co-exist as opt-in alternates. → VALUE. - cppagent reference
Agent::verifyDeviceauto-injectsrepresentation="DATA_SET"when noASSET_COUNTDataItem is declared andschemaVersion >= 2.0. → DATA_SET.
Library posture: follows SysML XMI and XSD — ASSET_COUNT defaults to VALUE.
The library does NOT auto-inject representation="DATA_SET" on devices that omit ASSET_COUNT.
Consumers who need cppagent-parity DATA_SET behavior can author the DataItem with representation="DATA_SET" explicitly in the device model.
Filed: Redmine #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 (SysML Model Related Issues).
DataSet vs Table Result Class Disagreement
Disagreement: SysML XMI vs XSD.
For DataItems with representation="DATA_SET" or representation="TABLE", the SysML XMI declares the result property's type as a single DataSet class shared between the two representations, while the XSD declares two distinct complex types (DataSetType and TableType) with non-overlapping element shapes.
Library posture: follows the XSD's two-class shape — DataSetEntry and TableEntry are distinct classes (MTConnect.Observations.DataSetEntry, MTConnect.Observations.TableEntry).
The on-the-wire output is XSD-validated; consumers parsing the XML never see ambiguity.
Filed: Redmine #3893 (SysML Model Related Issues).
Feature Persistent-ID Typo Across SysML and XSD
Disagreement: spec internal consistency.
A typo in the property name persistentId is preserved as persisitentId across both the SysML XMI and the XSDs from v1.4 through the latest published release.
The typo is in the same character position on both artifacts, suggesting a copy-and-paste origin rather than independent transcription.
Library posture: the library serializes the typo as-published, with no silent correction.
Consumers receive persisitentId on the wire because that is what the XSD requires; a future spec release that fixes the typo will trigger a coordinated bump on both sides.
Filed: Redmine #3894 (SysML Model Related Issues).
Component Class Hierarchy SysML vs XSD
Disagreement: SysML XMI vs XSD.
A subset of Component classes have a different parent class in SysML than they do in the XSD.
For example, LinearComponent derives from Axis in SysML and from AxisType (the XSD-only intermediate) in the XSD.
The hierarchy difference does not affect the wire shape — both forms produce the same element names — but it affects type-system code generators that compile against both artifacts.
Library posture: the source generator follows SysML for the C# class hierarchy and lets the XSD handle the wire shape independently.
The generated LinearComponent inherits from AxisComponent in C#, and the XSD-side LinearType deriving from AxisType is handled at serialization time by the XML formatter.
Filed: Redmine #3891 (SysML Model Related Issues).
JSON Wire Format Not Normative — No JSON Schema Generator
Disagreement: missing normative artifact.
The MTConnect Standard's Part_5 prose describes the JSON wire format descriptively, but no normative JSON Schema is published.
Consumers parsing JSON output today rely on the cppagent reference's byte shape rather than a versioned schema.
The library follows cppagent for the JSON-CPPAGENT codec but cannot validate its output against a missing-from-the-standard schema.
Library posture: the JSON-CPPAGENT codec is byte-tested against golden cppagent output; the JSON v1 codec is regression-tested against itself. A normative JSON Schema, if the standard body publishes one in a future release, would convert the byte-parity tests into schema-validated tests.
Filed: Redmine #3889 (Agent Working Group).
How Divergences Are Tracked
Every divergence flows through the same pipeline:
- Discovery — a test, a code review, or a consumer report surfaces a spec inconsistency.
- Verification — the divergence is reproduced against every published version of the affected artifact.
- Source citation — the exact line numbers / element IDs / prose sections are recorded for every artifact involved.
- Library posture decision — the library follows the artifact that wins under the source-of-truth hierarchy.
- Upstream filing — a Redmine ticket is filed against the standard body.
- Audit trail — the ticket URL is referenced from this page and from the test fixtures that pin the library's posture.
When the standard body resolves a ticket (either accepting the library's posture or amending the standard), the library follows the resolution. Where the resolution requires a wire-format change, the change is gated on the spec version the resolution targets (existing wire output for earlier versions is unchanged).
Where to Next
- Compliance by version and wire format — version-by-version envelope coverage, and the XML / JSON / SHDR posture.
- Spec cross-references — the source-of-truth hierarchy that drives every posture decision above.
- Test harness — how the divergence-pinning tests run locally.