On The Need for Artifacts That Describe API Products

My friend Daniel Kocot over at Adorsys has another thought-provoking and specification-evolving post over at Architectural Bytes this week. I sure do love having other deep-thinking API writers in the space to exchange ideas and stories with, and this week Daniel focuses on “We Can Describe an API. But How Do We Describe an API Product?” As Daniel works through his story, he asks some great questions that I wanted to answer.