WIA Digital Twin City

An in-browser conformance simulator for the WIA Digital Twin City standard. Paste a manifest below to validate it against the published JSON Schema and review the conformance tier the manifest claims.

Validate a manifest

Result will appear here.

Reference manifest

{
  "documentId": "wia-digital-twin-city-XXXX",
  "standardSlug": "digital-twin-city",
  "version": "1.0.0",
  "implementation": {
    "name": "REPLACE_ME",
    "build": "git-sha-or-image-digest",
    "sbom": "https://example.com/sbom.cdx.json"
  },
  "profile": { "named": "single-tenant", "version": 1 },
  "issuedAt": "2026-04-26T00:00:00Z"
}

How the simulator works

The simulator runs entirely in the browser. The JSON Schema for the manifest is fetched from the WIA Standards public registry and cached locally. Validation produces a Problem Details (RFC 9457) error report when the manifest is invalid, and a signed conformance summary when the manifest is valid.

The simulator does not transmit the manifest to any server; all processing is local. To submit a manifest for live conformance verification, use the management API documented in spec/PHASE-2-API-INTERFACE.md.

Conformance tiers

Surface — accepted data formats; self-attested.
Verified — annual third-party audit against the four PHASE documents.
Anchored — continuous evidence package per Annex G; SBOM signed (CycloneDX 1.5 + Sigstore).

Reference standards

This simulator and the underlying schema reference only ALLOW citations per the WIA citation policy: OpenAPI Specification 3.1, JSON Schema 2020-12, IETF RFC 9457, IETF RFC 9700, IETF RFC 6585, ISO/IEC 27001:2022, Sigstore (DSSE envelope, Rekor transparency log), CycloneDX 1.5.

Reference profiles

The simulator recognizes the following reference profiles:

single-tenant edge — one runtime per organization, no shared state.
multi-tenant gateway — one shared runtime serves multiple tenants via header-based isolation.
federated mesh — multiple runtimes peer to one another and publish manifests to a directory service.
air-gapped batch — no network connection between the runtime and the directory service; signed evidence package is transported out-of-band.

Time and integrity

The simulator assumes synchronized clocks (NTPv4 stratum-2 or PTP) and SHA-256 hash integrity checks. The manifest signing key is rotated per the deployment policy; the previous key is preserved in a published key history so that auditors can verify historical manifests.

Open governance

The simulators source code is published under the same MIT license as the rest of the WIA Standards project. Bugs and feature requests are tracked at github.com/WIA-Official/wia-standards/issues with the appropriate label.

Validator details

The simulator implements the structural layer of the JSON Schema 2020-12 validator. Full constraint-level validation (pattern, format, additionalProperties) is performed only by the canonical validator hosted at the WIA Standards public registry.

Glossary and acronyms

SBOM: Software Bill of Materials — a manifest of the components used to build the implementation. WIA standards use CycloneDX 1.5 or SPDX 2.3.
DSSE: Dead Simple Signing Envelope — Sigstores envelope format for signed metadata.
Rekor: Sigstores transparency log; provides an append-only public record of signed manifests.
in-toto: The in-toto Attestation Framework 1.0 specifies a portable format for build provenance and conformance evidence.
Conformance tier: The level of evidence required for an implementation to claim WIA-conformance: Surface, Verified, or Anchored.

Contact

For technical questions: standards@wiastandards.com. For press: press@wiastandards.com. For security disclosures (responsible disclosure window 90 days): security@wiastandards.com.

WIA Digital Twin City — Conformance Simulator