The purpose of the ePIC API is to provide a software stack for a PID service, that is sufficiently generic to fulfill the needs of a broad range of different scientific communities. This way it suffices to maintain one software stack and branching is avoided. The actual version of ePIC API does not specify the complete structure of the suffix. The strong determination to a specific structure of the handles had to be given up, because the customers partially define the suffix on there own, and partially they require a specific structure for their purposes. Nevertheless there are such structures, that are in general depending on the used prefix.
The latest documentation for using the service
You find the specification and the code of the actual ePIC API under