`NodeDefinition` might be exposing internal functionality

Looks like NodeDefinition might be exposing things that don't need to be exposed. For instance, you shouldn't be able to activate a node publicly, that's an internal thing that the library user never needs to be concerned with.

Should look at it a bit closer to see if that is the case, and try making some things more private if possible.