Review the ModelChangeEvents - and see if it would be better GeneralModelChangeEvent - check this also in Part 3 and see if both need updates.

GDS section needs to think about if a GDS is required (shall) subscribe - but maybe need to better explain what is actually required.

It would be good if the Aliases root node would have some version information to indicate when the aliases changed the last time.
This woule make it easier for GDS servers not connected all the time to all servers to detect changes without browsing the complete Alias tree at each connect.

The problem with the current spec is that it requires the NodeVersion / ModelChangeEvent for all Category / Alias nodes but this is only useful for clients that are always connected which is not possible for GDS level support. For the “disconnected” detection at the next time the client (GDS) is connected, this does not help at all since the Client must Browse and Read the complete tree to find changes. There would be no overall change detection since the NodeVersion on Root would not change if an Alias is added to a category. In this case would be even easier to only browse all Categories and Aliases and to compare them with the cache. Reading all NodeVersion properties would be a huge overhead.

This can be solved with an additional ConfigurationVersion property on the root category with DataType VersionTime.
Everytime the content of the alias tree changes, the ConfigurationVersion property must be updated.

updated text to remove ModelChange reference and a LastChange variable.

Agreed to 1.05.03 Draft changes and 1.04 Errata.