After zooming through terminology lifecycle management in the past few weeks, let’s continue with off-the-wall Beatles references and a case study.
Earlier we elaborated a bit on various aspects of terminology governance and conceptualization as a method of constructing a self-maintained ecosystem. And now that we have all angles covered, there’s no reason to labour the point, let’s say thank you and good night.
Fortunately for all of us with an inkling to solve problems, once the terminology processes are kicked off and localization is in full swing, issues of different nature are bound to crop up.
We hope you are already famished for another LABS post after last week’s hiatus. With all the terminology talk in the industry on best practices, database creation and concepts, there’s no immediate urge for us to add to the sea of discussions. Not that we already have a silver bullet for all the issues, but there are two topics where the eloquence seems to be subsiding. Interoperability and lifecycle management are not hitting the charts, but they are key issues for integrated, flexible solutions, so we try to say a few words edgeways this week about our experiences.