Earlier this year, I have met counterparts that were not aware of differences of data management maturity amongst the different sectors. <\/p>\n\n\n\n\n\n\n\n
Despite my explanation, they were furious I would call myself “data expert”, although I was not fully using their own sector’s vocabulary.<\/p>\n\n\n\n
I have been architecturing information for more than 20 years, and governing raw data for longer. Information has become data, with a wide range of new jobs. <\/p>\n\n\n\n
I can honorably do most of these jobs in the public sector, where data governance is still a work of art. But the banking system is high way above, in terms of regulations and specific vocabulary. <\/p>\n\n\n\n
I will write a full article on these sectors’ differences. <\/p>\n\n\n\n
Here is a glossary, for those who, like me, mix “too much” vocabularies of different fields.<\/p>\n\n\n\nWeb information architecture<\/th> Data architecture<\/th><\/tr><\/thead> content search engine<\/td> data catalog<\/td><\/tr> categories, tags<\/td> taxonomy<\/td><\/tr> data source<\/td> data lineage<\/td><\/tr> content <\/td> data asset<\/td><\/tr> content management<\/td> master data management<\/td><\/tr> APIs<\/td> data marketplace<\/td><\/tr> dataset <\/td> data basket<\/td><\/tr> content description<\/td> data glossery, data search<\/td><\/tr> database design<\/td> data modeling<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n