Code generators need something in the NodeSet to trigger the generation of a constant for the MachineryBuildingBlocks BrowseName.
We do this with Properties by include unattached Variables. The same is needed for MachineryBuildingBlocks.

This is an issue because the code generated for the MachineTool NodeSet assumes a constant is defined in the Machinery spec because the Namespace of the MachineryBuildingBlocks component is the Machinery specification. There is no work around that does not require hand editing auto-generated code or a complete rewrite of BrowseName handling by generators.

As general principle: if a specification defines a normative BrowseName like MachineryBuildingBlocks then that BrowseName must be defined in a machine readable format.

The unofficial convention with the Core NodeSets has been to add unattached Variables into the NodeSet but there are other options including:

1) A separate BrowseName file like we do with NodeIds;
2) A new top-level element in the NodeSet that defines normative BrowseNames without Nodes;
3) Recommend the creation of an Interface when such BrowseNames are defined on an Object;

But the key point is these BrowseNames are defined somewhere in a machine-readable format. Users should not have copy and paste from a PDF.