Given the lack of usage of this requirement, I propose we either remove the entire section regarding thin/full etc... or make it clear that it's optional to support various levels of OVAL results. In reality there aren't any OVAL results consumers, so mandating different levels of OVAL results is overkill, and if we are aiming for more adoption of SCAP 3.0, the fewer requirements like this the better.
Given the lack of usage of this requirement, I propose we either remove the entire section regarding thin/full etc... or make it clear that it's optional to support various levels of OVAL results. In reality there aren't any OVAL results consumers, so mandating different levels of OVAL results is overkill, and if we are aiming for more adoption of SCAP 3.0, the fewer requirements like this the better.