Skip to content
Draft
Show file tree
Hide file tree
Changes from 36 commits
Commits
Show all changes
49 commits
Select commit Hold shift + click to select a range
ff1b7c9
First iteration of proposal draft to introduce khr avatar extensions
Kjakubzak Jul 26, 2025
1413d20
Updated Contributes list as requested
Kjakubzak Jul 28, 2025
7b4723e
Addressing some comments
Kjakubzak Jul 29, 2025
de2169f
Update README.md
Kjakubzak Jul 29, 2025
de03ddb
Update README.md
Kjakubzak Jul 29, 2025
4a1f58a
Grammar am bad
Kjakubzak Jul 29, 2025
685b1c3
Updated KHR_avatar_skeleton_biped readme to be more prescriptive
Kjakubzak Jul 30, 2025
5effdee
Update the expressions extension descriptions to be more descriptive
Kjakubzak Aug 9, 2025
22b69b9
Updating the mapping extensions
Kjakubzak Aug 21, 2025
f89a0e3
Addressing minor self-nit
Kjakubzak Aug 21, 2025
a520102
Changing namespaces to KHR_character and KHR_character_avatar
Kjakubzak Sep 2, 2025
dd2159a
Small updates
Kjakubzak Sep 2, 2025
55bd217
More minor updates
Kjakubzak Sep 2, 2025
c461bab
Add virtual joint example for non-rotation-respecting virtual joint
Kjakubzak Sep 2, 2025
3822282
Update typed expression extensions to reflect a centralized expressio…
Kjakubzak Sep 2, 2025
085360f
Fit nits with last commit
Kjakubzak Sep 2, 2025
59993b8
Iterated on KHR_character_expression_procedural
Kjakubzak Sep 2, 2025
18d2d88
Testing mesh annotation refactor
Kjakubzak Sep 3, 2025
2ec0909
Changed virtual joints to virtual transforms
Kjakubzak Sep 3, 2025
c321afa
Minor nit fixes
Kjakubzak Sep 3, 2025
985455a
More implementation notes
Kjakubzak Sep 3, 2025
f560e6e
Update extensions/2.0/Khronos/KHR_character_virtual_transforms/README.md
Kjakubzak Sep 4, 2025
639579c
Minor nits and moving virtual transform to KHR
Kjakubzak Sep 9, 2025
3b34038
Update README.md
Kjakubzak Sep 9, 2025
527faa9
Merge branch 'kjakubzak/avatar_ext_mesh_annotation_consolidated' into…
Kjakubzak Sep 9, 2025
de83236
Update README.md
Kjakubzak Sep 9, 2025
9e54e51
Update extensions/2.0/Khronos/KHR_character_skeleton_biped/README.md
Kjakubzak Sep 10, 2025
522371b
Update extensions/2.0/Khronos/KHR_character_skeleton_biped/README.md
Kjakubzak Sep 10, 2025
e5c010d
Updates to bindpose, mapping, and virtual transform extension readmes
Kjakubzak Sep 21, 2025
7994f0e
Initial Draft Schemas
Kjakubzak Sep 22, 2025
8a09213
Update khr_mesh_annotation readme
Kjakubzak Sep 22, 2025
99861a3
Fixed readme typo
Kjakubzak Sep 22, 2025
d2e7cca
Addressing bad copy/paste and stale documentation
Kjakubzak Oct 7, 2025
f13ade3
Minor formatting consistency fixes
Kjakubzak Oct 7, 2025
c7ae046
Fixes to khr_character_expression_mapping
Kjakubzak Oct 13, 2025
53935f5
Change KHR_character_skeleton_biped README to be clearer
Kjakubzak Oct 16, 2025
df66d5f
Fixing KHR_character_expression_morphtarget inconsistencies
Kjakubzak Dec 10, 2025
1812744
Delaying KHR_character_avatar until we have more specific use-cases.
Kjakubzak Dec 10, 2025
3e4bff5
Delaying KHR_mesh_annotation
Kjakubzak Dec 10, 2025
8caa030
Delaying KHR_mesh_annotation_renderview
Kjakubzak Dec 10, 2025
1e93bfa
Delaying KHR_character_skeleton_biped
Kjakubzak Dec 17, 2025
56868be
Updated KHR_character_expression_morphtarget to explicitly depend on …
Kjakubzak Dec 17, 2025
34c6689
KHR_character_skeleton_bindpose update
Kjakubzak Dec 17, 2025
9dcf075
Update KHR_character to use rootNode instead of sceneIndex
Kjakubzak Dec 17, 2025
607430e
Individual Contributor ->Independent Contributor
Kjakubzak Dec 17, 2025
1c91e28
Updating README contributor lists with new TSG contributors
Kjakubzak Dec 17, 2025
3eb2b6d
KHR_character_skeleton_mapping - Inverted key/value pairs to align wi…
Kjakubzak Dec 17, 2025
f3f2c90
Updated schema references to https://json-schema.org/draft/2020-12/sc…
Kjakubzak Jan 12, 2026
ee572d4
Update KHR_character_expression.KHR_character_expression_procedural.s…
Kjakubzak Jan 12, 2026
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
151 changes: 151 additions & 0 deletions extensions/2.0/Khronos/KHR_character/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,151 @@
# KHR_character

## Contributors

- Ken Jakubzak, Meta
- Hideaki Eguchi / VirtualCast, Inc.
- K. S. Ernest (iFire) Lee, Individual Contributor / https://github.com/fire
- Shinnosuke Iwaki / VirtualCast, Inc.
- 0b5vr / pixiv Inc.
- Leonard Daly, Individual Contributor
- Nick Burkard, Meta

## Status

**Draft** – This extension is not yet ratified by the Khronos Group and is subject to change.

## Dependencies

Written against the glTF 2.0 specification.

Requires the extensions: `KHR_xmp_json_ld`

This extension also leverages the `KHR_xmp_json_ld` pattern for attaching extensible metadata as JSON-LD blocks within glTF assets. For background on this approach, see:
[KHR_xmp_json_ld](https://github.com/KhronosGroup/glTF/tree/main/extensions/2.0/Khronos/KHR_xmp_json_ld)

## Overview

The `KHR_character` extension designates a glTF asset as representing an character. This top-level marker enables tools and runtimes to interpret the asset as containing character-specific content such as rigging, blendshapes, animation retargeting, or metadata.

This extension does not define character features directly but acts as a root declaration that character-related extensions may be present, and that consumers should treat the asset using character-specific logic and pipelines. It's part of the wider set of KHR character extensions that are meant to be building blocks to represent a contract stating functionality and data requirements between a given model and an endpoint.

The extension supports referencing the source `scene` that represents the character and optionally includes structured metadata through the `KHR_xmp_json_ld` mechanism.

## Extension Schema

```json
{
"extensions": {
"KHR_character": {
"sceneIndex": 0
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Have we already discussed the property naming sceneIndex? If not, I would prefer scene instead, following the property with the same name in the core spec.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We haven't! I actually think we might want to revisit using the scene index all together due to it being not well supported across the board (and instead use a root node index concept). If we decide against that, we can change it to just being scene

}
}
}
```

### Properties

| Property | Type | Description |
| ------------ | ------- | ------------------------------------------------------------------------------------------------------------------------ |
| `sceneIndex` | integer | Index of the glTF `scene` representing the character. Used to distinguish the character root when multiple scenes exist. |

## Metadata Attachment: KHR_xmp_json_ld

character metadata should be expressed using the `KHR_xmp_json_ld` format, a structured mechanism for attaching JSON-LD metadata blocks to glTF files. In the context of `KHR_character`, this allows consistent expression of character provenance, licensing, creator, versioning, and intended use, among others.

The `KHR_xmp_json_ld` block is placed at the root level of the glTF asset as part of the defined extension usage. Metadata keys and structures are defined in the shared Khronos character Metadata schema (TBD).

| DC/XMP_JSON_LD Property | Why | Required |
| ----------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- | -------- |
| dc:title | | Yes |
| dc:creator | | Yes |
| dc:license | | No |
| dc:rights | | No |
| dc:created | Date on which the asset was created | No |
| dc:publisher | Identifies the entity responsible for making the resource available; important for understanding the source and authority of the content. | No |
| dc:description | Context and a summary of the content | No |
| dc:subject | Can potentially be used for content tagging/association | No |
| dc:source | Important for tracing the provenance and ensuring proper attribution. | Yes |
| khr:version | | No |
| khr:thumbnailImage | | No |

## Example

```json
{
"asset": {
"version": "2.0",
"extensions": {
"KHR_xmp_json_ld": {
"packet": 0
}
}
},
"scene": 0,
"scenes": [
{
"nodes": [0]
}
],
"nodes": [
{
"name": "characterRoot"
}
],
"extensionsUsed": ["KHR_character", "KHR_xmp_json_ld"],
"extensions": {
"KHR_character": {
"sceneIndex": 0
},

"KHR_xmp_json_ld": {
"packets": [
{
"@context": {
"dc": "http://purl.org/dc/elements/1.1/",
"vrm": "https://github.com/vrm-c/vrm-specification/blob/master/specification/VRMC_vrm-1.0/meta.md"
},
"dc:title": "Example Model",
"dc:creator": {
"@list": [
"Author1",
"AuthorEmail1@email.com",
"Author2",
"AuthorEmail2@email.com"
]
},
"dc:license": {
"@list": [
"https://vrm.dev/licenses/1.0/",
"https://example.com/third-party-license"
]
},
"dc:created": "2023-05-05",
"dc:rights": "Copyright information about the model",
"dc:publisher": "Imaginary Corporation A, LLC",
"dc:description": "A sentence, or paragraph describing the character at hand",
"dc:subject": {
"@list": ["Example trait", "Another example trait"]
},
"dc:source": "imaginaryCompany.com/characterl",
"khr:version": "1.0",
"khr:thumbnailImage": 0
}
]
}
}
}
```

## Implementation Notes

- `sceneIndex` is required, representing the index of the glTF `scene` corresponding to the character. Used to distinguish the character root when multiple scenes exist.
- Consumers should use this marker as a signal to search for additional character-related extensions, including skeletal, expression, and other khronos character extensions.
- Support for `KHR_xmp_json_ld` is encouraged to ensure interoperable metadata across tools and runtimes.

## Known Implementations

## License

This extension specification is licensed under the Khronos Group Extension License.
See: https://www.khronos.org/registry/gltf/license.html
Original file line number Diff line number Diff line change
@@ -0,0 +1,18 @@
{
"$schema": "http://json-schema.org/draft-04/schema",
"title": "KHR_character glTF Document Extension",
"type": "object",
"description": "glTF extension for character-specific metadata and properties.",
"allOf": [ { "$ref": "glTFProperty.schema.json" } ],
"properties": {
"sceneIndex": {
"allOf": [{ "$ref": "glTFid.schema.json" }],
"description": "Index of the glTF scene representing the avatar. Used to distinguish the avatar root when multiple scenes exist."
},
"extensions": { },
"extras": { }
},
"required": [
"sceneIndex"
]
}
41 changes: 41 additions & 0 deletions extensions/2.0/Khronos/KHR_character_avatar/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,41 @@
# KHR_character_avatar

## Contributors

- Ken Jakubzak, Meta
- Hideaki Eguchi / VirtualCast, Inc.
- K. S. Ernest (iFire) Lee, Individual Contributor / https://github.com/fire
- Shinnosuke Iwaki / VirtualCast, Inc.
- 0b5vr / pixiv Inc.
- Leonard Daly, Individual Contributor
- Nick Burkard, Meta

## Status

**Draft** – This extension is not yet ratified by the Khronos Group and is subject to change.

## Dependencies

Written against the glTF 2.0 specification.

Requires the extension(s): `KHR_xmp_json_ld`, `KHR_character`

## Overview

The `KHR_character_avatar` extension designates a glTF asset as representing an avatar. This top-level marker enables tools and runtimes to interpret the asset as containing avatar-specific content such as rigging, blendshapes, animation retargeting, or metadata.

This extension does not define avatar features directly but acts as a root declaration that avatar-related extensions may be present, and that consumers should treat the asset using avatar-specific logic and pipelines. It's part of the wider set of KHR character and avatar extensions that are meant to be building blocks to represent a contract stating functionality and data requirements between a given model and an endpoint.

This extension is dependent on the KHR_character extension; which defines related functionality pertaining to more generalized characters.

## Implementation Notes

- Consumers should use this marker as a signal to search for additional avatar-related extensions, including skeletal, expression, and other khronos avatar extensions.
- `KHR_xmp_json_ld` is required to ensure interoperable metadata across tools and runtimes.

## Known Implementations

## License

This extension specification is licensed under the Khronos Group Extension License.
See: https://www.khronos.org/registry/gltf/license.html
Original file line number Diff line number Diff line change
@@ -0,0 +1,11 @@
{
"$schema": "http://json-schema.org/draft-04/schema",
"title": "KHR_character_avatar glTF Document Extension",
"type": "object",
"description": "glTF extension that designates a glTF asset as representing an avatar.",
"allOf": [ { "$ref": "glTFProperty.schema.json" } ],
"properties": {
"extensions": { },
"extras": { }
}
}
142 changes: 142 additions & 0 deletions extensions/2.0/Khronos/KHR_character_expression/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,142 @@
# KHR_character_expression

## Contributors

- Ken Jakubzak, Meta
- Hideaki Eguchi / VirtualCast, Inc.
- K. S. Ernest (iFire) Lee, Individual Contributor / https://github.com/fire
- Shinnosuke Iwaki / VirtualCast, Inc.
- 0b5vr / pixiv Inc.
- Leonard Daly, Individual Contributor
- Nick Burkard, Meta

## Status

**Draft** – This extension is not yet ratified by the Khronos Group and is subject to change.

## Dependencies

Written against the glTF 2.0 specification.
Requires the extension(s): `KHR_character`

## Overview

The `KHR_character_expression` extension provides a common interface for facial expression animations. It enables tools and runtimes to associate expressions like `blink`, `smile`, or `jawOpen` with specific animations in the glTF model's animations field.

When used in conjunction with the other expression extensions, enables a data contract with endpoints allowing them to understand just what kind of data is present and being powered.

This extension is purely descriptive: it does not define or store animation data itself.

## Reference Expression Categories/Vocabularies

Expressions in this context describe face-localized animations used to drive small and/or larger movements across the face and/or down-chain meshes needed for reasonable conveyance of emotion/intent.

For examples of relevant types of expressions, you can reference concepts such as:

- **Emotions** (Emotion-derived facial movements such as what [VRM defines as presets](https://github.com/vrm-c/vrm-specification/blob/master/specification/VRMC_vrm-1.0/expressions.md), e.g. `happy`, `angry`, `surprised`)
- **Visemes** (A visual representations of mouth movements for parts of speech, e.g. `aa`, `oo`, `th`)
- **FACS** ([Facial Action Coding System (FACS)](https://en.wikipedia.org/wiki/Facial_Action_Coding_System) which is a system intended to describe visually distinguishable facial movements (and is often split further based on left/right), e.g. `brow lowerer`, `chin raiser`, `lid droop`)
- **Gestures and Actions** (Larger descriptors that describe general facial actionse (but not emotion), e.g. `blink`, `smile`, `jawOpen`)

Optionally, these expressions may be aligned with industry standards (or an endpoint/experiences expected expressions set).

## Extension Schema

```json
{
"extensions": {
"KHR_character_expression": {
"expressions": [
{
"expression": "smile",
"animation": 0
},
{
"expression": "frown",
"animation": 1
}
]
}
}
}
```

### Properties

| Property | Type | Description |
| ------------- | ------- | ------------------------------------------------------------------------------ |
| `expressions` | array | Array of mappings between animation/channels and expression labels. |
| `animation` | integer | Index into the glTF `animations[]` array representing an expression animation. |
| `expression` | string | Expression name this joint contributes to. |

## Animation Integration

- Expression timing, blending, and control must use glTF `animations` channels.
- This ensures consistency, ease of implementation, and interoperability across runtimes.

Each animation channel used to drive an expression should operate within a **normalized 0-to-1 range**, where:

- `0.0` indicates the expression is fully inactive.
- `1.0` indicates the expression is fully active.

The transformation values themselves (e.g., degree of rotation or distance of translation) should scale proportionally with the normalized input range.

This approach simplifies character implementation by centralizing expression playback in the glTF animation system and unifying runtime logic for blending and prioritization.

### Recommended Interpolation for Binary Expressions

For expressions that represent binary or toggle states (such as `blinkLeft`, `blinkRight`, or `jawOpen`), the use of glTF animation channels with `"interpolation": "STEP"` is strongly recommended.

STEP interpolation ensures that an expression toggles cleanly between fully off (`0.0`) and fully on (`1.0`) states, providing crisp visual transitions and avoiding interpolation artifacts that could occur with `LINEAR` interpolation in binary scenarios.

## Extension Example w/ typed extensions

```json
{
"extensions": {
"KHR_character_expression": {
"expressions": [
{
"expression": "smile",
"animation": 0,
"extensions": {
"KHR_avatar_expression_joint": {
"channels": [0, 1]
},
"KHR_avatar_expression_texture": {
"channels": [2]
},
"KHR_avatar_expression_morphtarget": {
"channels": [4, 5]
}
}
},
{
"expression": "frown",
"animation": 1,
"extensions": {
"KHR_avatar_expression_joint": {
"channels": [0]
},
"KHR_avatar_expression_texture": {
"channels": [1, 2]
},
"KHR_avatar_expression_morphtarget": {
"channels": [3]
}
}
}
]
}
}
}
```

## Implementation Notes

- Expression states should be normalized to the [0.0–1.0] range for consistent runtime interpretation.

## License

This extension is licensed under the Khronos Group Extension License.
See: https://www.khronos.org/registry/gltf/license.html
Loading