Should validate contents.xml files with .xsd

[lool]

Hi,

I just randomly bumped into this contents.xsd XML Schema:
https://qartifactory-edge.qualcomm.com/artifactory/qsc_releases/software/chip/qualcomm_linux-spf-1-0/qualcomm-linux-spf-1-0_test_device_public/r1.0_00095.0/qcm6490-le-1-0/common/build/lib/contents.xsd

Just a few minutes after we landed support for generating contents.xml files:
#29

I believe qcom-ptool should validate the contents.xml files with this xsd. I'm not yet sure where the latest version is being maintained though.

[lool]

Currently for the rb3gen2 contents.xml and .xsd:

% xmllint --noout --schema contents.xsd ./platforms/qcs6490-rb3gen2/contents.xml
./platforms/qcs6490-rb3gen2/contents.xml:18: element chipid: Schemas validity error : Element 'chipid': This element is not expected. Expected is ( hlos_type ).
./platforms/qcs6490-rb3gen2/contents.xml:23: element build: Schemas validity error : Element 'build': Missing child element(s). Expected is ( release_path ).
./platforms/qcs6490-rb3gen2/contents.xml:38: element device_programmer: Schemas validity error : Element 'device_programmer': This element is not expected. Expected is ( release_path ).
./platforms/qcs6490-rb3gen2/contents.xml:2: element contents: Schemas validity error : Element 'contents': Missing child element(s). Expected is one of ( build_tools, external_tools, workflow, oem_merge_done ).
./platforms/qcs6490-rb3gen2/contents.xml fails to validate

[lool]

@vkraleti would you know where the latest contents.xsd lives? I see missing and incorrect properties in our contents.xml with the random .xsd I found. I'd expect it would require us to have a build_id field for instance.