> A more rational approach, IMO, would create a general description set > (probably numbering 20-50), then expanding that for more detail and for > different materials. Users of the sets could define the "zones" they wish to > use in an application profile, so no one would have to carry around data > elements that they are sure they will not use. It would also provide a > simple but compatible set for folks who don't want to do the whole "library > description" bit. This seems quite rational to me too. Sounds easy enough, so you'll have this built by the end of the week, right? :D