Skip to content

IFCCAD 2026.44.1 alpha

Pre-release
Pre-release

Choose a tag to compare

@BjornFidder BjornFidder released this 29 Oct 13:37
· 48 commits to main since this release

IFCCAD 2026.44.1 alpha

Native core source alpha — 29 October 2026. Tag: v2026.44.1.

This release adds radius, diameter, two-line angular, three-point angular,
ordinate, arc-length and jogged-radius Dimensions alongside linear and aligned.
All nine kinds share native construction, validation, measurement, formatting,
inspection and JSON/CBOR storage. Definition, optional role-specific source
relations, presentation and optional saved graphics remain separate.
The entity catalogue groups the kinds together and uses an oblique reference
line to demonstrate the difference between linear and aligned measurement.

File contracts and breaking changes

  • JSON/IFCX: ifcx_alpha, IFCCAD profile 0.2.0, import
    urn:example:ifccad:0.2.0.
  • Standalone CBOR: mapping revision 2.
  • Optional native Zstd: transport revision 1, inner CBOR mapping 2;
    feature ifccad-cbor-zstd, disabled by default.

Profile 0.1.0 and CBOR 1 from 2026.44.0 are superseded in the active reader.
Their published artifacts remain fixed; this release does not retain a reader
or provide migration for them. Keep original source drawings. Later alphas may
also break compatibility. Software, profile, CBOR and transport versions are
independent identifiers; unchanged Zstd framing does not imply inner-format
compatibility. Numbered historical conformance collections remain unchanged.

Scope and boundaries

The attached .crate and deterministic source archive contain only the native
core, its registry dependencies, schemas, tests, examples and release documents.
The package now includes the support modules required to compile its examples
and example-based tests, plus the fixture used by the SOLID/TRACE tests.
Packaging also selects its output directory explicitly
so an ancestor Cargo configuration cannot redirect the artifact unexpectedly.
No crates.io publication or prebuilt binaries are
included. GitHub's automatic repository snapshots also contain application and
archived sources; use the attached native artifacts for the standalone release.

Bounded source selectors are stored and validated; automatic associative updates,
graphics generation and shared annotation scales remain follow-up work. Stored
graphics do not establish visual equivalence or general editable CAD behavior.

DWG/DXF exchange and Explorer are separate applications. The accompanying
Explorer update selects opencaddocument
4723b0e6b4b38354853eb5ce1d0f9af23a8bbb2f (PR #7),
codec 501b694eee3433b157e56a32da4268dc8b3b5bd3 and Studio
4d1cd17dafd7d47cd76f8674835636776eb90fd6. The host's native core remains
bce9da06a8e1684e86e35f0302e3870141e6f9f9, with the same profile/CBOR contracts.
The Document fix preserves explicit line-endpoint identity after source edits.
See the active conversion contract
for supported associations and diagnosed losses.

Studio's interactive grip/undo paths can lose saved Dimension graphics in IFCX,
DWG and DXF; this is tracked separately in
OCS #2325.
The native release does not claim to fix that application history behavior.

Verification and provenance

Release verification covers the final workspace candidate, optional native Zstd,
release tooling, frontend tests and an isolated native package/archive on Windows
x86_64 MSVC with Rust/Cargo 1.98.0. It is source verification on this platform,
not qualification of prebuilt binaries across platforms. The release manifest
records the verified source and exact commands; the Explorer workflow separately
checks and deploys its browser and host bundles.

release-manifest.json identifies the tagged commit, file contracts,
verification basis and artifact hashes. SHA256SUMS covers that manifest and
the attached .crate and source archive. SOURCE-MANIFEST.json inside the
archive records each packaged file hash and its native-only scope. Published
tags and artifacts remain fixed; corrections require another release.