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

Digital Twin (my playground)

I am embarking on a side project that involves memory and multimodal understanding for an…

9 months ago

“This is exactly what LLMs are made for”

I was in Toronto, Canada. I'm on the flight back home now. The trip was…

1 year ago

AI is enhancing me

AI as an enhancer of human abilities.

1 year ago

“How we fell out of love with voice assistants”

The BBC article "How we fell out of love with voice assistants" by Katherine Latham…

2 years ago

Ontology-based reasoning with ChatGPT’s help

Like so many others out there, I played a bit with ChatGPT. I noticed examples…

2 years ago

Break from work

Hi all… It’s been a while since I posted on this blog. It’s been an…

2 years ago