| … | … | @@ -22,7 +22,7 @@ We aim to create an ecosystem of specifications and tooling for accessible creat |
| 22 | 22 | |
| 23 | 23 | ## OMI glTF Working Group Process |
| 24 | 24 | |
| 25 | | OMI uses 4 stages to represent the maturity of an extension: |
| 25 | OMI uses 5 stages to represent the maturity of an extension: |
| 26 | 26 | |
| 27 | 27 | ### Stage 1 |
| 28 | 28 | |
| … | … | @@ -67,6 +67,15 @@ The extension has been ratified. It has multiple metaverse implementations, a gl |
| 67 | 67 | - [ ] Previous requirements from Stage 3 |
| 68 | 68 | - [ ] The extension has passed a consensus vote for ratification. |
| 69 | 69 | |
| 70 | ### Stage 5 |
| 71 | |
| 72 | The extension has been submitted and merged as an OMI vendor extension or submitted and ratified as a KHR or EXT extension within the [Khronos 3D Formats Working Group](https://github.com/KhronosGroup/glTF). |
| 73 | |
| 74 | #### Requirements |
| 75 | |
| 76 | - [ ] Previous requirements from Stage 4 |
| 77 | - [ ] Listing on the [Khronos glTF repository](https://github.com/KhronosGroup/glTF/tree/main/extensions) proving the extension has been approved or ratified. |
| 78 | |
| 70 | 79 | |
| 71 | 80 | ## OMI glTF Vendor Extensions |
| 72 | 81 | |
| … | … | @@ -79,6 +88,8 @@ The extension has been ratified. It has multiple metaverse implementations, a gl |
| 79 | 88 | |
| 80 | 89 | ### Stage 4 |
| 81 | 90 | |
| 91 | ### Stage 5 |
| 92 | |
| 82 | 93 | ### Extension Support Table |
| 83 | 94 | |
| 84 | 95 | <table> |