Skip to content

Recompute the tiers from the cleaned catalog, and drop FDX as first target - #14

Merged
kinlane merged 2 commits into
mainfrom
standards/tier-recompute-and-fdx
Aug 17, 2026
Merged

Recompute the tiers from the cleaned catalog, and drop FDX as first target#14
kinlane merged 2 commits into
mainfrom
standards/tier-recompute-and-fdx

Conversation

@kinlane

@kinlane kinlane commented Aug 17, 2026

Copy link
Copy Markdown
Contributor

Two changes: the catalog recompute from the standards work, and the recommendation change that follows from it.

From the catalog side

  • 118 → 98 industry standards, derived rather than estimated. An admission test moved twenty entries out of the type — seven Java platform specifications, five horizontal formats, two things that are software rather than standards, and five buckets into a new umbrella type. Nothing deleted.
  • Tiers are computed, not read by hand. Backfilled from a schema_forms field by fetching each body's actual artifact: A 30, B 36, C 13, D 12, seven unestablished.
  • Tier D added — no wire format at all. Filing a methodology or an identifier scheme as Tier C implies a linter is failing to reach something that was never there.
  • FIX and DICOM leave Tier C. Unlintable wire format and a machine-readable model published at source — a different problem, and a much more tractable one.
  • Demand counts downgraded to unsourced, and AIS retracted: it read 45 companies, and sampling the matched text across 250 corpora returned "Air-Insulated Switchgear" every time.

The correction that follows

Three Tier A standards publish to members only — FDX, Berlin Group, Confirmation of Payee. Derivation works fine against a closed artifact; publishing the result does not, because a derived ruleset carries the thing it was derived from. They are the most lintable standards nobody can write a public ruleset for, and no amount of tooling fixes it — it is a licensing problem wearing a technical costume.

That removes FDX as the recommended first target, which both the research page and the post led with. CAMARA now stands alone: Tier A, open across 93 repositories, a live conformance question, and a Spectral ruleset for Open Gateway promised in December 2024 that still does not exist.

Adds "published openly" as a selection criterion — the criterion whose absence caused the original error.

Where the edits landed

File Change
research/industry-rulesets.md Recompute + dated correction on the first-target recommendation
_posts/…one-standard-twice… Recompute summary + dated update note
_posts/…nobody-should-be-writing… Worked examples move FDX → CAMARA; closed-artifact caveat added to bet one

All three are already published, so every change carries a dated correction note rather than being edited silently.

Jekyll builds clean; all six of today's posts still render.

kinlane and others added 2 commits August 17, 2026 17:27
…arget

Two changes, one from the catalog side and one that follows from it.

Catalog (from the standards session, previously uncommitted):

- 118 -> 98 industry standards, derived rather than estimated. An
  admission test moved twenty entries out of the type: seven Java
  platform specifications, five horizontal formats, two things that are
  software rather than standards, and five buckets into a new `umbrella`
  type. Nothing deleted.
- Tiers are now computed from a `schema_forms` field backfilled by
  fetching each body's actual artifact, not read by hand: A 30, B 36,
  C 13, D 12, seven unestablished.
- Tier D added — no wire format at all. Filing a methodology as Tier C
  implies a linter is failing to reach something that was never there.
- FIX and DICOM leave Tier C: unlintable wire format, machine-readable
  model published at source. Different problem, more tractable.
- Demand counts downgraded to unsourced, and AIS retracted outright — it
  read 45 companies and sampling 250 corpora returned "Air-Insulated
  Switchgear" every time.

Consequent correction, which is mine:

Three Tier A standards — FDX, Berlin Group, Confirmation of Payee —
publish to members only. A derived ruleset carries the artifact it was
derived from, so it cannot be published. That makes them the most
lintable standards nobody can write a public ruleset for, and it removes
FDX as the recommended first target. CAMARA now stands alone: Tier A,
open across 93 repositories, with a Spectral ruleset promised in
December 2024 that still does not exist.

Adds "published openly" as a selection criterion, which is the criterion
whose absence caused the original error. Dated correction notes on both
the research page and the post; the exploratory post's worked examples
move from FDX to CAMARA.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
… as rulesets

A fourth relationship alongside engine / embeds / adjacent, for projects that
are not implementations of the format but publications in it — the AEP OpenAPI
Linter and the Italian government's national API guidelines rules. Both ship a
written guideline as an installable, extendable ruleset, which is the format
being used as a distribution medium rather than as one tool's config file.

Surfaced on both pages: a "Published as rulesets" section on implementations,
and "Rulesets published as standards" on tools.

This is the shortest list on either page, and it is the one that matters most to
the ruleset conformance class in #9 — these are the documents such a class would
have to hold.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@kinlane
kinlane merged commit 9f5c685 into main Aug 17, 2026
2 checks passed
@kinlane
kinlane deleted the standards/tier-recompute-and-fdx branch August 17, 2026 21:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant