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.
It’s almost Christmas, already Hanukkah, Ashura is closing in, not to mention that Kwanzaa and Gita Jayanti is on the horizon, so it’s time to put up the lights. Our contribution to the festivities is an unusually short post, celebrating company branding – and pimping with CSS.
The topic du jour is still terminology lifecycle management, specifically governance and maintenance – if you missed the first part, you can catch up here.
Last week we have cut the development and architecture bits short, because they are intertwined with the concept of governance. If you wish to see all the work put into creating, authoring and structuring last another day, factor in roles, responsibilities, communication structure, collaboration model, permissions and transparency.