Bring 2_cameras manifests into conformance with presentation-validator#77
Merged
Conversation
…t it satisfied presentation-validator
gjcope
reviewed
May 15, 2026
Contributor
gjcope
left a comment
There was a problem hiding this comment.
Looks good to me. Manifests still work as before in Voyager and X3DOM viewers.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Manifest files were edited to eliminate errors identified by the presentation-validator
Validation errors that have been fixed were primarily replacing Annotation target values tha were strings with values that were JSON objects; for these manifests the targets were Scene resources.
Adding https schema ids to resources that didnt' have them, primarily SpecificResource objects