Naming conventions for interface types

For the naming of the DLL file usually the identifiers of the host system to be served or the interface in general are used.
Ideally in such a way that the designation remains unambiguously identifiable and also speaking. The designation of the namespace should ideally be kept identical.
To ensure that the source/origin of the interface is known, it should always be preceded by a company name at best.

Types are ideally given a speaking type name. Since the namespace is already defined in the type library, the composite type name then results as follows:

company.namespace.typename

Example: Pranke.Sap.Invoic01 or optionally with a child namespace to define subtypes for example.

company.namespace.subnamespace.typename

Example: Pranke.FXL.Invrpt.Stock and Pranke.FXL.Invrpt.Movement.

Note: Use the type description to give hints about the message direction in or out.