You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment model and world SDF files are not validated when they are checked in, and there is no single convenient tool to format these files. Linux has xmllint command line utility that allows formatting (pretty-printing) such files.
Here are suggested shell scripts that could help with simple checks and formatting (the same way astyle is used for C++ files):
The tail -n +2 is needed to remove standard XML header (if it is not desirable)
In verifier the first operand produces visible output, while the second line allows $? variable to be returned from diff
Verifier basically formats the file and compares the result with original
A more elaborated check could be done - validating SDF files against their XML schema.
A full clone / cmake / make process is required to produce a directory with actual XSDs usable by xmllint (under build/sdf/1.9)
Then this validation works (slowly):
~/gz10/PX4-gazebo-models/worlds$ xmllint --schema sdformat/build/sdf/1.9/root.xsd baylands.sdf
...
baylands.sdf:28: element scene: Schemas validity error : Element 'scene': Character content other than whitespace is not allowed because the content type is 'element-only'.
baylands.sdf:156: element gravity: Schemas validity error : Element 'gravity': This element is not expected.
baylands.sdf fails to validate
I could look into it further, although implementing full schema validation would require having that XSD tree checked in, and validator is a bit slow. I also expect a lot of validation errors in the existing files, and some cleanup to follow.
@dagar - P.S. - after a closer look at generated XSD files, it looks like "include noise.sdf" statements, for example, are ignored, and the resulting imu.xsd file, for example, does not contain noise elements. Basically, generated XSDs are incomplete.
At the moment model and world SDF files are not validated when they are checked in, and there is no single convenient tool to format these files. Linux has xmllint command line utility that allows formatting (pretty-printing) such files.
Here are suggested shell scripts that could help with simple checks and formatting (the same way astyle is used for C++ files):
format-sdf.sh <file>
if [ check-sdf.sh <file> ] ...
The
tail -n +2
is needed to remove standard XML header (if it is not desirable)In verifier the first operand produces visible output, while the second line allows $? variable to be returned from diff
Verifier basically formats the file and compares the result with original
A more elaborated check could be done - validating SDF files against their XML schema.
Format of Gazebo SDF files is described here: http://sdformat.org/spec?ver=1.11&elem=sdf
There is a git repository for a C++ code-generating tool https://github.com/gazebosim/sdformat
Schema is available as part of that repository: https://github.com/gazebosim/sdformat/blob/sdf14/sdf/1.9
xmllint --schema <>
would perform such validation, if all schema files are pulled locally from the repository.Pulling a collection of usable XSDs from that repository is a bit complicated - there is an additional step, using an SDF->XSD converter (as part of the sdformat build process):
https://github.com/gazebosim/sdformat/blob/sdf14/tools/xmlschema.py
A full clone / cmake / make process is required to produce a directory with actual XSDs usable by xmllint (under build/sdf/1.9)
Then this validation works (slowly):
I could look into it further, although implementing full schema validation would require having that XSD tree checked in, and validator is a bit slow. I also expect a lot of validation errors in the existing files, and some cleanup to follow.
@dagar - per our recent conversation
The text was updated successfully, but these errors were encountered: