One of the more critical, and somewhat confusing, concepts in the SDSFIE 3.0 is the notion of what constitutes a 'compliant' data set. SDSFIE 3.0 offers considerably more flexibility in schema options than earlier releases. This capability was created to permit individual DoD users some naming options to accommodate existing legacy applications that use geospatial data. But the capability comes with a risk... namely compromising the very nature of a standard.
Many new DoD contracts are being awarded with a clause stating that the data deliverables are to be submitted compliant with SDSFIE. Given the flexibility in schema naming and content, what does that really mean and how is that consistent with an absolute standard.