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
I think the //plugin/@name attribute is currently being misused by ign-gazebo, since it currently contains an ignition::gazebo::systems::SystemName and might not be unique among its sibling elements. This is a violation of the SDFormat 1.7 spec, which requires that sibling elements of any type should have unique names. It even violates the convention of earlier versions of the SDFormat spec, which required sibling elements of the same type to have unique names.
I think it would be more suitable to use a custom namespaced attribute to store the system name and give a unique name in the name attribute instead:
Is this already supported by SDFormat? If so, I suggest we:
add support for it on Citadel
convert all our examples to use the new syntax
deprecate the use of name as the class name on Edifice
remove the use of name as the class name on Ign-F
Well, we currently accept all unrecognized attributes and elements, which includes the namespaced ones; we need to re-enable warnings / errors for unrecognized fields. Some discussion here: gazebosim/sdformat#327
I think the
//plugin/@name
attribute is currently being misused byign-gazebo
, since it currently contains anignition::gazebo::systems::SystemName
and might not be unique among its sibling elements. This is a violation of the SDFormat 1.7 spec, which requires that sibling elements of any type should have unique names. It even violates the convention of earlier versions of the SDFormat spec, which required sibling elements of the same type to have unique names.I think it would be more suitable to use a custom namespaced attribute to store the system name and give a unique name in the name attribute instead:
The text was updated successfully, but these errors were encountered: