Studios · Standards and terminology
Definara: one term, every standard.
The technical terms of content provenance, digital identity, cybersecurity, AI, 3D, geospatial, robotics, supply chain and digital twins. Each domain is laid out as a whole picture, and each term comes with a plain-language definition, an example in practice, how each source uses it, and where the sources mean different things by the same word.
What is inside
The same word, different meanings.
Teams that work across standards lose weeks to words that look shared but are not. Three entries from Definara show why.
- 01Claim (C2PA)In C2PA, the data structure that lists the assertions of a manifest by their hashes and records who made them. The claim is what gets signed.Where the sources differ. In C2PA a claim is the signed structure that binds the assertions together. In the W3C Verifiable Credentials Data Model a claim is a single statement about a subject, such as a date of birth.Sources: C2PA Technical Specification
- 02VerifierThe role that receives a presentation and checks it.Where the sources differ. eIDAS and the EU wallet framework use relying party, which also carries registration duties under EU law.Sources: Verifiable Credentials Data Model 2.0; OpenID for Verifiable Credentials specifications and OpenID Connect
- 03Level of DetailHow detailed a representation of an object is. CityGML 3.0 defines levels 0 to 3 for each object.Where the sources differ. CityGML levels describe how much of a real object is modeled. 3D Tiles uses a measured geometric error. OpenUSD added level-of-detail support for rendering. Ask which one is meant.Sources: CityGML; 3D Tiles; OpenUSD glossary
What Definara gives you
A reference you can trust in a design review, a procurement or a standards meeting.
A plain-language definition
Every term is explained by Hkdolts in a sentence or two, without jargon, so a product lead and an engineer read it the same way.
Every source, with its version
Each entry links to the specifications and regulations that define it, with the version we follow and whether Hkdolts takes part in that body.
Where the sources differ
When the same word means different things in two standards, the entry says so and explains the difference before it costs you a meeting.
Quoted only where the license allows
Open specifications are shown word for word with their license notice. Paid standards are linked, never copied.
Your list, exported
Keep the terms you use with your own notes, and export them as JSON-LD or CSV for a glossary, a specification or a team wiki.
Suggest what is missing
Tell us where a technical term is defined and our editors review it. Everyday words are not added.
11 domains
The number on each is how many terms it holds today. Inside, every domain opens as a map of its subtopics, so the terms read as one picture.
- 42Content provenanceConcepts and roles · The manifest and its parts · Binding and durability · Signing, trust and validation · What the record says · Disclosure and regulation
- 67Digital identity and credentialsRoles · Identifiers and DIDs · The credential · Presenting and exchanging · Status and lifecycle · EU digital identity framework · Assurance and authentication · Governance and trust ecosystems
- 36AI governance and regulationWhat counts, and who is responsible · Risk classes and duties · Transparency · Risk-management frameworks · Testing, oversight and monitoring
- 59AI and ML engineeringModels · Training and adaptation · Inference and generation · Retrieval and grounding · Agents and protocols · Attacks and weaknesses · Evaluation and operations
- 59Cybersecurity and cryptographyCryptographic building blocks · Keys, certificates and transport · Post-quantum cryptography · Identity and access · Zero trust architecture · Threats and attacks · Frameworks and management · Regulation and reporting
- 563D and scene descriptionOpenUSD scene model · Composition · Properties and time · Schemas, shading and physics · Files and packaging · glTF delivery · Materials and rendering · Captured and neural scenes · Web 3D and humanoids
- 33Immersive and spatial systemsKinds of experience · Devices and runtimes · Tracking and spatial understanding · Interaction · Rendering and comfort · Web and shared worlds · Safety, privacy and regulation
- 34Geospatial and placesReference and position · Features and data models · APIs and encodings · 3D cities and streaming · Imagery, grids and coverages · Open map data and places
- 46Machine data, robotics and autonomyMachine data (MTConnect) · Industrial connectivity (OPC UA) · Robot software (ROS 2) · Robots and safety · Automated driving · Simulation and physical AI
- 30Software and AI supply chainBills of materials · The SPDX model · Identifiers and licensing · Vulnerabilities · Build integrity and provenance · Regulation
- 43Data, cloud and digital twinsCloud and edge · Catalogs and lineage · Semantics and linked data · Data spaces and usage control · EU data rules · Connected things · Digital twins
Open Definara
Access is by invitation. Sign in with the email your invitation was sent to, or request one from the sign-in screen.
- 1SearchFind a term by name, abbreviation or domain.
- 2CompareSee every source that defines it, and where they differ.
- 3KeepAdd it to your list with a note, and export it.
Common questions
Who can use it?
Definara is by invitation, like our consoles. Request an invitation from the sign-in screen; we review each request and reply by email.
Which terms are included?
Technical terms only: words defined, or used with a specific meaning, in a specification, a regulation or a recognized technical body. Everyday vocabulary is left out on purpose.
Why are some definitions not shown word for word?
We quote a source only when its license allows it, with its notice. For paid standards and restricted licenses, we link to the source and the definition you read is our own.
How current is it?
Each source shows the version we follow and the date we last checked it. When a body publishes a new version, we review the terms that depend on it.
Can I use it in my own documents?
Yes. Export your list as JSON-LD or CSV. Keep the source links, and the license notice of any quoted definition, when you reuse it.