Skip to content
@4d-id

4D-ID

One persistent name for everything real. An open standard for spatial identity.

4D-ID™

One persistent name for everything real. A working draft offered for community review.

Different systems can keep their own maps, coordinates, and internal IDs. Once an entity is grounded, 4D-ID gives them a shared way to refer to the same persistent thing. Grounding determines the referent; localization determines where it is; 4D-ID preserves which thing it is across systems and time.

4D-ID does not perform perception, localization, geometric registration, or rendering. Observations remain evidence, external matchers supply correspondence evidence, and authorized lifecycle decisions preserve reconciliation history.

Identities can be shared, while each deployment controls what it discloses and authorizes.

▶ Try the isolated demos at 4d-id.org — a browser sandbox of records created from caller-supplied grounding. Nothing there writes to a live namespace.

This profile describes a working draft offered for community review. It has no claimed industry adoption, standards-body adoption, or production deployment.

Repositories

Repo What it is
spec The specification. Six parts, ~100 requirements, each with a test. Start here.
reference-resolver A resolver you can run in an afternoon. Apache-2.0.
js-sdk The TypeScript / JavaScript client. npm i @4d-id/js.
demos The interactive browser demos.
adapters Implemented reference adapters for IFC and Overture GERS; other integrations remain planned.
conformance Partial diagnostics: 15 schema checks implemented of 112 defined; functional work continues.

Adapters currently implemented: IFC and Overture GERS.

Four concepts

Identity, hierarchy, pose, time. Every other clause is a rule about how those four behave under a named pressure, or a binding to a standard that already exists (OGC GeoPose and DGGS, ISO 8601, OpenXR, glTF). 4D-ID is not a new coordinate system; it is the name that lets the ones we have agree.

Working draft, open, and not adopted

The specification is a working draft offered for community review, not an adopted standard. A 4D-ID can be syntactically generated from caller-supplied grounding and a descriptor; that syntax is not identity truth. The reference resolver has no built-in authentication, so production deployments must enforce authorization policy around lifecycle operations.

A DGGS cell routes, partitions, and filters spatial records. It may appear as immutable genesis metadata in the spatial identifier form, but it is not the identity and it is not the entity's current location. The 2.4 draft also defines a non-spatial privacy mode.

Apache-2.0 for the implementation, SDKs, schemas, and conformance suite.

Popular repositories Loading

  1. spec spec Public

    Working draft for persistent spatial identity, resolution, registrations, provenance, and bounded reconciliation. Not adopted.

    Python

  2. .github .github Public

    Organization profile and community health files

  3. reference-resolver reference-resolver Public

    Partial reference resolver for 4D-ID 2.4: caller-grounded records, aliases, registrations, lifecycle, and bounded reconciliation.

    JavaScript

  4. js-sdk js-sdk Public

    JavaScript SDK for 4D-ID 2.4 records, privacy-mode identifiers, resolve-before-mint reuse, and resolver queries.

    JavaScript

  5. docs docs Public

    Documentation for the 4D-ID working draft: grounding, identity, resolution, registrations, GERS bridging, and interoperability.

  6. demos demos Public

    Browser demos and identity inspector for grounding, persistent identity, resolution, hierarchy, registrations, and reconciliation.

    HTML

Repositories

Showing 8 of 8 repositories

People

This organization has no public members. You must be a member to see who’s a part of this organization.

Top languages

Loading…

Most used topics

Loading…