The WIA-AUTO-018 standard defines a comprehensive framework for railway system technologies, including signaling systems, train control, communication protocols, passenger information systems, and safety mechanisms.
Scope: Signaling Systems: ETCS (European Train Control System), CBTC (Communications-Based Train Control), PTC (Positive Train Control) · Train Control: Automatic Train Operation (ATO), Automatic Train Protection (ATP), Automatic Train Supervision (ATS) · Communication: GSM-R (GSM for Railways), LTE-R (LTE for Railways), TETRA · Passenger Information: Real-time arrival/departure, station displays, mobile integration · Platform Safety: Platform Screen Doors (PSD), automatic gap detection · Safety Protocols: SIL (Safety Integrity Level) 4 compliance, fail-safe mechanisms
This simulator demonstrates the canonical envelope shape defined in the standard's Phase 1 specification. Click the button below to generate a sample envelope; the output is a JSON document that conforming implementations can verify with the reference CLI.
Every envelope in this standard is signed with Ed25519 over the canonical JSON form (RFC 8785 JCS). The signature covers all fields except the signature itself; downstream consumers verify by re-canonicalising and re-checking the Ed25519 signature against the publisher's tenant key registered in the WIA-OMNI-API trust fabric.
# Reference verification flow (pseudocode)
canon = jcs_canonicalise(envelope_without_signature)
ok = ed25519_verify(publisher_pubkey, canon, envelope.signature.value)
assert ok, "envelope signature does not verify"The metrics below reflect the standard's validator score and the cohort of conforming implementations registered with the WIA trust fabric. Numbers are illustrative; the actual figures evolve as the ecosystem grows.
This page is a Phase 1 envelope simulator for the WIA-AUTO-018
standard. It is intentionally minimal: a working demonstration of
the envelope shape, not a production implementation. Production
implementations carry signing keys in the WIA-OMNI-API trust
fabric, validate against the schema registry, and emit envelopes
through the Phase 2 HTTP surface documented under
../api/.
The simulator is provided so that engineers evaluating the
standard can see a concrete envelope without standing up a full
publisher endpoint. The reference CLI under ../cli/
produces equivalent envelopes from the command line, which is
the recommended path for any non-trivial experimentation.
For deeper context, the eBook companion volumes describe the domain rationale for each envelope field. Field choices in this standard are not arbitrary: each field exists to answer a question that downstream auditors, regulators, or interoperability partners would otherwise have to derive from the publisher's narrative documentation.