Strictly speaking only the LDraw spec and the meta-commands comes under the remit of the LDraw Standards Committee. The library organisation has normally been handled by the Library Admin following consultation. Four of the five Standards Committee members (Allen, Roland, Travis, me) have been actively involved in this discussion and at least three of us seem to agree on XML, so I think we are good. Roland, do you agree with XML?
A "spec" doesn't need to be over-complex, but if we want applications to use the new LOD config file properly we should publish its structure and usage assumptions. For example
- All primitives will always be found in the DEFAULT folder: ldraw/p;
- Different resolutions may be present in other LOD folders
- STUDLOGO folders, if defined, can optionally be used to enhance the selected LOD
A "spec" doesn't need to be over-complex, but if we want applications to use the new LOD config file properly we should publish its structure and usage assumptions. For example
- All primitives will always be found in the DEFAULT folder: ldraw/p;
- Different resolutions may be present in other LOD folders
- STUDLOGO folders, if defined, can optionally be used to enhance the selected LOD
Chris (LDraw Parts Library Admin)