# Parsing a 3rd party skeleton/bone definition

**URL:** <https://discourse.threejs.org/t/parsing-a-3rd-party-skeleton-bone-definition/33573>\
**Category:** Questions\
**Tags:** skeleton, bones\
**Created:** [January 12, 2022, 11:20pm UTC](https://discourse.threejs.org/t/parsing-a-3rd-party-skeleton-bone-definition/33573 "2022-01-12T23:20:54Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![callum](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.threejs.org/callum/32/2446_2.png) [@callum](https://discourse.threejs.org/u/callum)\
**Post date:** [January 12, 2022, 11:20pm UTC](https://discourse.threejs.org/t/parsing-a-3rd-party-skeleton-bone-definition/33573/1 "2022-01-12T23:20:54Z")

</div>

I am learning about bones and skeletons by trying to parse a third party skeleton file I have converted to JSON. Each of the bones are defined by a start and end position. Some are connected to other bones and some are not.

Is this something I can do with the native three.js bone/skeleton support? There seems to be a requirement in three.js that each bone is connected to another.