CLI URDF Validation
It would be nice if the package also installed an executable script that could be used to validate URDFs (and return a non-zero exit code for unparsable URDFs). If it did this, it would make it easy to include as an automated CLI check to validate if the URDF is properly formatted.
Sounds good! Any ideas / expectations on what should constitute an "invalid" URDF? The closest that comes to mind is the ROS specification (which could be extracted from the docs: http://wiki.ros.org/urdf/XML/robot). But e.g. should proper file names (that reference meshes) also be tested?
@clemense Testing other referenced assets would be nice, but I imagine it could be done as an optional feature (behind a flag).