Specifications to define data assets managed as products
๐ In recent years, several specifications have emerged to define data assets managed as products. Today, two main types of specifications exist:
1๏ธโฃ ๐๐ฎ๐๐ฎ ๐๐ผ๐ป๐๐ฟ๐ฎ๐ฐ๐ ๐ฆ๐ฝ๐ฒ๐ฐ๐ถ๐ณ๐ถ๐ฐ๐ฎ๐๐ถ๐ผ๐ป (๐๐๐ฆ): Focused on describing the data asset and its associated metadata.
2๏ธโฃ ๐๐ฎ๐๐ฎ ๐ฃ๐ฟ๐ผ๐ฑ๐๐ฐ๐ ๐ฆ๐ฝ๐ฒ๐ฐ๐ถ๐ณ๐ถ๐ฐ๐ฎ๐๐ถ๐ผ๐ป (๐๐ฃ๐ฆ): Focused on describing the data product that manages and exposes the data asset.
๐ The ๐ข๐ฝ๐ฒ๐ป ๐๐ฎ๐๐ฎ ๐๐ผ๐ป๐๐ฟ๐ฎ๐ฐ๐ ๐ฆ๐๐ฎ๐ป๐ฑ๐ฎ๐ฟ๐ฑ (๐ข๐๐๐ฆ) by Bitol is an example of the first specification type, while the ๐๐ฎ๐๐ฎ ๐ฃ๐ฟ๐ผ๐ฑ๐๐ฐ๐ ๐๐ฒ๐๐ฐ๐ฟ๐ถ๐ฝ๐๐ผ๐ฟ ๐ฆ๐ฝ๐ฒ๐ฐ๐ถ๐ณ๐ถ๐ฐ๐ฎ๐๐ถ๐ผ๐ป (๐๐ฃ๐๐ฆ) by the Open Data Mesh Initiative represents the second.
๐ค But what are the key differences between these two approaches? Where do they overlap, and how can they complement each other? More broadly, are they friends, enemies, or frenemies?
๐ I explored these questions in my latest blog post. The image below might give away some spoilers, but if you're curious about the full reasoning, read the post.
โค๏ธ I'd love to hear your thoughts!
#TheDataJoy #DataContracts #DataProducts #DataGovernance | 29 comments on LinkedIn
specifications have emerged to define data assets managed as products