#14 Knowledge First Approach and Reusing Existing Standards for Data Mesh - Interview w/ Juan Sequeda

Sign up for Data Mesh Understanding's free roundtable and introduction programs here: https://landing.datameshunderstanding.com/Please Rate and Review us on your podcast app of choice!If you want to be a guest or give feedback (suggestions for topics, comments, etc.), please see hereEpisode list and links to all available episode transcripts (most interviews from #32 on) hereProvided as a free resource by Data Mesh Understanding / Scott Hirleman. Get in touch with Scott on LinkedIn if you want to chat data mesh.Juan's contact info and related links:Email: juan at data.worldTwitter: @juansequeda / https://twitter.com/juansequedaLinkedIn: https://www.linkedin.com/in/juansequeda/Catalog & Cocktails Podcast: https://data.world/podcasts/Juan's post about Zhamak's appearance on the Data Engineering Podcast: https://www.linkedin.com/pulse/my-takeaways-data-engineering-podcast-episode-mesh-zhamak-sequeda/Juan's post about knowledge first: https://www.linkedin.com/feed/update/urn:li:activity:6884179569277059072/Standards related links:Dublin Core Metadata Initiative: https://dublincore.org/RDF (Resoruce Description Framework): https://www.w3.org/2001/sw/wiki/RDFOWL (Web Ontology Language): https://www.w3.org/OWL/PROV-O: The PROV Ontology: https://www.w3.org/TR/prov-o/In this episode, Scott interviews Juan Sequeda, Principal Scientist at data.world and co-host of the Catalog and Cocktails podcast. They discussed Juan's knowledge first approach: putting the meaning and value of the data first instead of focusing on the amount of data we are handling/producing. Knowledge first has 3 components, 1) context, 2) people, and 3) relationships. Juan is a big proponent of knowledge graphs and the relationships side is one many people miss.Juan also gave some thoughts on what his approach to data mesh hinges on: treating data as a product and finding a balance between centralization and decentralization for all the aspects of building out an implementation. Juan mentioned Intuit's approach of fixed, flexible/extensible, or customizable as a good general tool and to look for (and embrace) what he calls intellectual friction.Lastly, Juan and Scott talked about the general drive to reduce toil, of reinventing the wheel re data interoperability and standard schemas in data mesh. Juan points to a lot of existing research and standards - e.g. RDF, OWL, and many more (see below) - as a starting point.Data Mesh Radio is...