Data Contracts: Creating APIs for Your Data

APIs mostly are used to expose capabilities, but of course they can also be used to provide access to data. But is there something different when it comes to "Creating APIs for Your Data"? There are indeed some differences as current efforts around data contracts are showing. Simon Harrer of INNOQ explains why data contracts exist and what they are. They are indeed similar to APIs, but they also are different in a variety of interesting ways. For a more structured discussion, we are looking at data contracts from a variety of angles: • Ownership: Who owns the data? • Terms: What are the terms and conditions for using the data? • Models: What are the data models exposed in the dataset? • Definitions: What are the reusable definitions of the dataset? • Examples: Can I get a few examples for the data in this dataset? • Quality: What are quality indicators for the dataset? • SLAs: What are available service level agreements? • Servers: Where is the data available and how is it organized? While there currently is no established stable standard for data contracts, there are various sources of information and standardization efforts underway. This is a list of resources to get you started: 👉 Book on Data Contracts - https://www.amazon.com/Driving-Data-Quality-Contracts-comprehensive/dp/1837635005 👉 Data Contract Specification - https://datacontract.com 👉 Open Data Contract Standard - https://bitol.io #api #apimanagement #opendata #datamanagement #datacontracts #datamesh #data #informationmanagement #decentralization #gettingapistowork #digitaltransformation