client-side action and UUID identifier

[Mike Overbeck]

Reading this example action:

https://www.ftrack.com/en/2015/04/write-first-ftrack-action.html

There are many example actions in the Ftrack documentation with varying structures, but this is the only one that I've seen that sets the action identifier with an uuid, making the identifier unique to each action instance, which is helpful in avoiding crosstalk between users using the same Ftrack-connect plugins.

Another example like this uses an internal register function inside the class to filter the action by user.

https://help.ftrack.com/en/articles/1040465-actions?_ga=2.50864737.958893569.1596582072-1449533465.1596225075

Which of these methods would be considered best practice to safely configure a client-side action?