Some additional note from specification:
There is no discussion of how the aliases are assigned in the server. This should be discussed.

Recommendation: add APIs for
CreateAlias
ReadAlias (this is just a normal browse / read operation - so probably does not need a method)
UpdateAlias
DeleteAlias

A general purpose server requires configuration by the system integrator. This individual will assign aliases to control programs, HMI tags, alarms, etc.
There may be servers that do not use pre-assigned Aliases, perhaps because different companion specs use different aliases for the same or overlapping data.

In a large system that can be many UA servers, each from a different vendor. Without an API for CRUD operations in the UA server, each server will require a custom tool to assign aliases - this will create a burden on the integration engineer This
person will have to align the aliases on multiple servers using multiple custom tools. This will create a barrier that few will want to try to overcome.

Another alternative - which might be used mroe often is to define all (or most) AliasNames in An AliasName Server (using any custom tool) and just assign the references to the target nodes (in what ever server they are assigned to)

The Alias service set can be defined globally (as a service set) and per-category (as methods).

System responses for name conflicts and resolution must be defined - e.g. if a category method Create("foo") is called and that Alias is already defined under a different category what is the system response? Can the same Alias appear under multiple categories?

Assign to Paul soon.