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
Some data models are re-used inside data structures with restrictions applied. E.g. EntityAddressType is used within NodeManagementDetailedDiscoveryEntityInformationType but only allowing the field entity. In this case the device field will also sent if set, which is the normal case.
Right now the implementation ignores all these all allows and serializes all fields. It has no functional impact, as the other unknown or not-defined fields should be ignored by the receiver anyway. And because all fields are structurally always optionals, and therefor new fields can be added in future version of SPINE without breaking compatibility, this won't be a real problem. Even though formally this is incorrect and a certification would most likely fail because of this.
The text was updated successfully, but these errors were encountered:
Some data models are re-used inside data structures with restrictions applied. E.g.
EntityAddressType
is used withinNodeManagementDetailedDiscoveryEntityInformationType
but only allowing the fieldentity
. In this case thedevice
field will also sent if set, which is the normal case.Right now the implementation ignores all these all allows and serializes all fields. It has no functional impact, as the other unknown or not-defined fields should be ignored by the receiver anyway. And because all fields are structurally always optionals, and therefor new fields can be added in future version of SPINE without breaking compatibility, this won't be a real problem. Even though formally this is incorrect and a certification would most likely fail because of this.
The text was updated successfully, but these errors were encountered: