Abstract
LDV FORUM – Band 21(1) – 2006 Abstract Th is article presents UniTerm, a typical representative of terminology management systems (TMS). Th e fi rst part will highlight common characteristics of TMS and give further insight into the UniTerm entry format and database design. Practise has shown that automatic, i.e. blind exchange of terminologies is diffi cult to achieve. Th e second section gives criteria where the exchange between diff erent TMS can fail and points out the relationship between the UniTerm like TMS data formats and existing terminology standards. Finally, it will be discussed what requirements have to be met in order to enable a deeper integration of terminology standards in a TMS and thus also a smoother transition between diff erent TMS. Th ese requirements are evaluated with Acolada s next generation TMS UniTerm Enterprise.
Sign-in/Register to access full text options 
Free) 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a call
