On 10-9-2015 20:03, Hurtado, Diego Antonio wrote:
I see that the version attribute of the Network Object class is to be defined in objects of the Topology class.
Is there a reason for this attribute not to be an attribute of the Topology class directly instead of being an attribute of the Network Object class?
Yes, for future compatibility. Implementations that receive a NML schema with a version attribute should at a different location should simply ignore that attribute, but should still regard it as valid NML.
From 7 of GFD.206:
The meaning of the version attribute is only defined for specific cases (for objects of the Topology class), and should not be used in other objects. Clients that receive a version attribute for a non-Topology object should ignore that attribute.
Hope this helps! Regards, Freek Dijkstra