This chapter describes the behavior if the OPC UA Client call the method “RemoveIODD”.
It is described that all instances from ObjectType “IOLinkIODDDeviceType specific Type X” will be removed from Address Space.
However, these points are missing in my opinion:

1. What happened with the IODD File(s) on the filesystem?
   => Proposal: Delete
2. What happened with ObjectType „IOLinkIODDDeviceType specific Type X”
   => Proposal: Delete from Address Space or Vendor-Specific
3. What happened with specific OPC UA DataType Structures und Enumerations, which were created in Address Space from „IOLinkIODDDeviceType specific Type X”?
   => Proposal: Delete from Address Space or Vendor-Specific
   An OPC UA Server with IODD Support shall always handle this use case without errors:
   • Client transfers IODD Typ A per Object “TransferIODD“ to the server. Server creates specific OPC UA ObjectType / DataType / Enumerations from IODD:
   • Client removes IODD Typ A per Methode “RemoveIODD” from Server. Server removes all instances of the ObjectType. Additionally server removes files from file system and cleanup address space (ObjectType, Enumeration, Structure from the IODD)
   • Client transfers IODD Typ A per Object “TransferIODD” to the server again. Server recreates specific ObjectType / DataType / Enumerations from IODD without any error