Open Specification Promise: What. How. Why.

This is great for those building protocol-based integration solutions.

?Recently, Microsoft announced a new type of licensing model aimed at making it much easier, therefore safer from a legal point of view, for developers to implement specs without having to spend a lot of time understanding complex license agreements and obscure legalese, then signing and faxing Microsoft legal documents in order to leverage a specification. This new breed of simple licensing model is called the Open Specification Promise (OSP).

Here, we chat with the minds behind OSP: Jean Paoli, co-creator of XML and General Manager of Interoperability XML Architecture, Tom Robertson, General Manager of IP and Corportate Standards Strategy, and Amy Marasco, General Manager of Standards Strategy. Want to to understand what OSP is and why we created it? Tune in and let the the folks who thought it up explain it to you.

Link to Open Specification Promise: What. How. Why.

Recent Posts

BrainExpanded – Login State Caching Issue in iOS Share Extension

As part of the BrainExpanded project, I’m building an iOS app that lets users easily…

2 weeks ago

Is AI Good or Bad?

Artificial Intelligence (AI) has rapidly evolved over the past few decades, becoming an integral part…

2 weeks ago

BrainExpanded – Copilot

Happy New Year everyone! I was planning for my next BrainExpanded post to be a…

2 months ago

BrainExpanded – The Timeline

See "BrainExpanded - Introduction" for context on this post. Notes and links Over the years,…

2 months ago

BrainExpanded – Introduction

This is the first post, in what I think is going to be a series,…

2 months ago

Digital twin follow up

Back in February, I shared the results of some initial experimentation with a digital twin.…

3 months ago