OverviewFilesCommitsIssuesDocsReleasesPeers

gltf-extensions commits / e2d7c1b

Add clarifications
e2d7c1bb32cb19815bebb2e40d6dae3d3cbfea5b
by Robert Long <robert@robertlong.me> · 2021-10-28T22:35:22.000Z

Changed files (1) +2 -2

README.md +2 -2
……@@ -30,11 +30,11 @@ A draft proposal has been submitted to the working group and is receiving feedba
3030
3131### Stage 2
3232
33The draft proposal should precisely describe the extension in it's initial form and there should be at least one metaverse implementation of the extension in development and valid sample assets for testing by other potential implementors. This implementation will be used to test the viability of the extension and provide an example for other implementors. Edits to the extension should be voted on and decided by consensus in weekly OMI glTF Working Group meetings.
33The draft proposal should precisely describe the extension in it's initial form and there should be at least one metaverse implementation of the extension in development and valid sample assets for testing by other potential implementors. The proposal should contain valid a JSON schema describing the extension in its entirety as well as a markdown document explaining the purpose, features, and properties of the extension. This implementation will be used to test the viability of the extension and provide an example for other implementors. Edits to the extension should be voted on and decided by consensus in weekly OMI glTF Working Group meetings.
3434
3535### Stage 3
3636
37The extension has multiple metaverse implementations, a glTF Validator implementation, valid sample assets, and at least one readily available tool for generating content using this extension. The extension at this stage is ready for a vote for ratification. Final modifications should be voted on and decided by consensus in weekly OMI glTF Working Group meetings.
37The extension has multiple metaverse implementations, a glTF Validator implementation, valid sample assets, and at least one readily available tool for generating content using this extension. The implementations, sample assets, and content creation tool should all consume or produce assets that can be verified by the glTF Validator. The extension at this stage is ready for a vote for ratification. Final proposal modifications should be voted on and decided by consensus in weekly OMI glTF Working Group meetings.
3838
3939### Stage 4
4040