ABSTRACT
Despite being the lowest common denominator of CG applications, there is no de facto standard for geometry files. On the contrary, there is a plethora of both proprietary and open formats. One of the many reasons for this state of affairs is that each application has different requirements that are not efficiently compatible. An out-of-core path tracer will have different needs for its geometry-storing solution than a 3D editor or a game. Of course a kitchen-sink approach will offer all the needed features, but probably at the cost of computational and storage efficiency.
