{"action":"created","issue":{"url":"https://api.github.com/repos/KhronosGroup/glTF-Validator/issues/80","repository_url":"https://api.github.com/repos/KhronosGroup/glTF-Validator","labels_url":"https://api.github.com/repos/KhronosGroup/glTF-Validator/issues/80/labels{/name}","comments_url":"https://api.github.com/repos/KhronosGroup/glTF-Validator/issues/80/comments","events_url":"https://api.github.com/repos/KhronosGroup/glTF-Validator/issues/80/events","html_url":"https://github.com/KhronosGroup/glTF-Validator/issues/80","id":311347541,"number":80,"title":"Top-level orphan objects","user":{"login":"emackey","id":1235080,"avatar_url":"https://avatars2.githubusercontent.com/u/1235080?v=4","gravatar_id":"","url":"https://api.github.com/users/emackey","html_url":"https://github.com/emackey","followers_url":"https://api.github.com/users/emackey/followers","following_url":"https://api.github.com/users/emackey/following{/other_user}","gists_url":"https://api.github.com/users/emackey/gists{/gist_id}","starred_url":"https://api.github.com/users/emackey/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/emackey/subscriptions","organizations_url":"https://api.github.com/users/emackey/orgs","repos_url":"https://api.github.com/users/emackey/repos","events_url":"https://api.github.com/users/emackey/events{/privacy}","received_events_url":"https://api.github.com/users/emackey/received_events","type":"User","site_admin":false},"labels":[{"id":408842316,"url":"https://api.github.com/repos/KhronosGroup/glTF-Validator/labels/enhancement","name":"enhancement","color":"84b6eb","default":true}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":3,"created_at":"2018-04-04T18:47:49Z","updated_at":"2018-04-06T14:31:08Z","closed_at":null,"author_association":"MEMBER","body":"I recently ran into a problem, possibly a bug in an exporter (or an incorrect model), where several `mesh` objects appeared to be duplicates of others, and were not referenced by any nodes.\r\n\r\nCould we add checking, maybe for everything except `scene` that objects should be referenced by other objects?  This is not required by the glTF spec, but can indicate wasted data or export issues.  So, it could be an `info` or even a `hint` level message."},"comment":{"url":"https://api.github.com/repos/KhronosGroup/glTF-Validator/issues/comments/379271290","html_url":"https://github.com/KhronosGroup/glTF-Validator/issues/80#issuecomment-379271290","issue_url":"https://api.github.com/repos/KhronosGroup/glTF-Validator/issues/80","id":379271290,"user":{"login":"emackey","id":1235080,"avatar_url":"https://avatars2.githubusercontent.com/u/1235080?v=4","gravatar_id":"","url":"https://api.github.com/users/emackey","html_url":"https://github.com/emackey","followers_url":"https://api.github.com/users/emackey/followers","following_url":"https://api.github.com/users/emackey/following{/other_user}","gists_url":"https://api.github.com/users/emackey/gists{/gist_id}","starred_url":"https://api.github.com/users/emackey/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/emackey/subscriptions","organizations_url":"https://api.github.com/users/emackey/orgs","repos_url":"https://api.github.com/users/emackey/repos","events_url":"https://api.github.com/users/emackey/events{/privacy}","received_events_url":"https://api.github.com/users/emackey/received_events","type":"User","site_admin":false},"created_at":"2018-04-06T14:31:07Z","updated_at":"2018-04-06T14:31:07Z","author_association":"MEMBER","body":"> What do you think of making this check disabled by default\r\n\r\nWe call out empty nodes with `info` level.  Is there a reason we can't/shouldn't have this enabled by default?  I would be OK even reducing it further to `hint`, the lowest level, if needed.  But conceptually this feels quite similar to empty nodes and unused texcoords.\r\n\r\nTo get the tests working, I think it's fine for most of the tests to explicitly ignore this one.  The tests are kind of a special case where orphan objects are used all over the place to test things.  Maybe the test harness can even turn this off by default, and only 1 or 2 tests explicitly turn it back on.\r\n\r\nInterested to hear from @donmccurdy too."}}
{"actor":{"display_login":"emackey"}}