Hi sornchai
short:
A DeviceLink profile is a single profile, a rigid component, so to speak, for a direct conversion of existing CMYK or RGB tonal values into corresponding CMYK or RGB tonal values of the target color space, bypassing a PCS (Profil-Connecting-Space, e.g. Lab ).
Separation characteristics such as the beginning, end and width of black, total ink amount, use of GCR, UCR, UCA are fixed in every devicelink profile and are not variable.
(Unless a correspondingly differently configured "second" or "third" dlp profile is written and saved as such ...)
It can only be used with specially compatible software (e.g. Callas PDF Toolbox, PitStop, mostly workflow RIPs, but not otherwise color management-capable layout programs such as Indesign or QuarkXpress or even Photoshop...)
A good color server is the software that was actually created for handling DeviceLink profiles, which can then work with dynamic profiles to varying degrees, depending on the manufacturer. In practice, for corresponding conversions from color space to color space (but also within the same color space ...), a different separation character such as black beginning, end, width, total color application, use of GCR, UCR, UCA and Rendering Intent can be managed and as Queue can be saved for the exact same reuse.
The DL-profile is rewritten hidden for the user for practically every job for example in ALWAN-CMYK-optimizer...
There are also "color servers" (eg also in the form of modules for a RIP or workflow) that do not have any dynamic functions. Here, rigid dlp profiles are used again, which must be made available to the color server, but in turn can no longer be varied individually (see above). Their authorization arises from the fact that the usual layout, graphics and image processing software usually cannot handle DL-profiles ...