What Public Beta means

The specification is in use — at a pilot printer, in software, by agents — and it is still being refined. Beta is a statement about change, not about access: everything is open to read; some of it may still move.

Stable now

Term URIs (ptpge.org/v1/…) never break: a published URI resolves indefinitely, and a deprecated term keeps resolving and names its successor. The identity method ptpge-cfs/1 is fixed — a fingerprint computed today is the same fingerprint in ten years.

May still change

Labels and definitions may be sharpened. Translations marked with an asterisk (*) are machine drafts awaiting professional review. Product templates may gain axes and values; new terms are added as the industry asks for them. Document schemas are in preparation.

How change happens

Every change is additive and dated: a data version (today 2026-10-06), an entry in the changelog, and an Atom feed to subscribe to. Nothing is silently altered. Deprecation always comes with a successor.

«proposed» on a term

Most terms carry status proposed: published, usable, resolvable — but not yet confirmed by an industry review. The status will change to approved term by term as review happens; the URI does not change.

What you can rely on

Build against URIs and fingerprints, not against labels. Pin a data version if you need reproducibility (version.json). Read is open and will stay open; no key, no registration, no limit for normal use.

Found something?

A missing term, a wrong translation, a template that does not fit a real product: write to post@ptpge.org, or apply for a steward key and propose it directly. Beta testers' findings are folded back into the specification within days — see the changelog.

When does beta end?

When the specification has been reviewed by the industry's own bodies and the first set of terms is marked approved. The pill in the header disappears; nothing you built changes.